Billing use cases
The following examples show how billing is calculated when subscriptions start or end mid-month, or when licence counts change.
Subscription start and cancellation
Agency A subscribes to SHIP-HATS on 15 July and cancels on 10 October.
| Scenario | Details | Billing impact |
|---|---|---|
| Subscription start | 15 July | Charged for the full month of July |
| Subscription end | 10 October | Charged for the full month of October |
| Key takeaway | No proration | Full-month charges apply regardless of start or end date |
💡 Tip
To maximise value, subscribe at the start of a month and cancel at the end of a month.
Reducing licence count mid-month
In July, Agency A subscribes to:
- 20 Atlassian licences
- 15 GitLab licences
Later in the month, the licence counts are reduced to 10 for both tools.
| Tool | Highest licence count (July) | Reduced count | Billed count | Billing impact |
|---|---|---|---|---|
| Atlassian | 20 | 10 | 20 | Charged based on the highest count during the month |
| GitLab | 15 | 10 | 15 | Charged based on the highest count during the month |
💰 Key takeaway
Charges are based on the highest number of licences subscribed during the month, even if reduced later.
