Recurring service providers

Click Start now to create your ERP.AI account, then use Proto to configure Subscription Billing. Bring your accepted plans, customer accounts, meter definitions, billing review process and payment connections.

A published plan can define its base amount and an explicit contracted or metered quantity basis. The accepted allowance, aggregation and pricing mode determine how the variable amount is calculated.

An identical source event identity and payload returns its earlier accepted result. The quantity is not added again. A changed payload under the same identity becomes a conflict for investigation.

The billing candidate records its occurrence-time interval and receipt cutoff. Late accepted usage can enter an unissued replacement candidate or a reviewed adjustment for an already issued interval, preserving the earlier invoice.

Accepted changes retain an effective instant and both sets of terms. A plan with actual-seconds proration shows the old unused credit and new remaining charge separately; a no-proration plan follows its accepted rule.

The provider outcome must be verified. Pending, authorised and unknown attempts remain separate from settled receipts. A timeout keeps the original instruction identity until reconciliation prevents an accidental second charge.

A dunning stage records collection follow-up. A service change requires the accepted subscription policy and an explicit authorised lifecycle transition. Sending a reminder alone does not cancel the agreement.

Preserve the issued document and independently review the difference from its corrected source. An undercharge can produce a linked correction invoice or later billing line; an overcharge produces credits tied to the actual remaining billed line amounts. If cash needs to be returned, a separate refund request retains its own approval and observed provider outcome.