Restrictions When Payment Is Delayed
Last updated: 2026-09-30
If you have an unpaid invoice (awaiting payment) past its due date, staged usage restrictions are applied across all projects in your organization. Stages 2 onward are counted from the month the oldest unpaid invoice was issued (or the month the chargeback occurred, if applicable). For credit card payments, as explained in Contract Status, Billing Information, and Payment Method Management, there is normally no “due date” concept at all — in this case, the moment the charge attempt fails is treated as the due date, and the restriction stages then progress on the same basis as other payment methods.
The usage restriction schedule is as follows.
| Stage | Timing | Restriction |
|---|---|---|
| 1. Notice only | On the payment due date | No feature restrictions. Only an unpaid-invoice notice is sent to members with the organization’s Owner and Billing roles, and to the billing email address. |
| 2. Write operations restricted | The 14th of the month after the reference month (the invoice’s issue month) (default) | Creating new resources (Detection Rules, Runbooks, AI Agents, Sources, Access, Tasks, etc.) and changing settings that alter what runs or what is targeted (including changes to Source settings and Access connection details, and to a task’s repeat setting or its Runbook link), as well as manual AI runs, are blocked. (*Deleting, enabling/disabling, commenting, changing status, and changing a task’s due date remain available; data ingestion and usage measurement continue.) |
| 3. Data ingestion stopped | The 28th of the month after the reference month (the invoice’s issue month) (default) | In addition to the above restrictions, data ingestion via Webhooks and similar, and outbound actions such as connecting to external services and sending notifications, are stopped. (*Existing data is retained.) |
| 4. Forced contract termination | If data ingestion is still stopped on the first day of the month that falls 3 months after the reference month (the invoice’s issue month) | The contract is automatically terminated by the system. (Applies to both card payment and bank transfer.) |
Notes on usage restrictions
- Even while usage restrictions are in effect, you can still check your contract, update your billing information, and cancel renewal (cancellation procedure) as usual from the billing management screen. However, while an invoice is past its due date, you cannot request an upgrade (apply again after payment is confirmed).
- From stage 2 (write restrictions) onward, a warning banner is shown at the top of the app screen (the “Go to billing settings” link is shown only to members with the organization’s Owner or Billing role).
- The restriction start dates (the 14th and 28th) follow a system-wide schedule and cannot be changed on your end.
- For how your data is handled (retention period, deletion schedule, etc.) if your contract is forcibly terminated due to non-payment, see Data Handling.