Usage event to billed quantity
Keep event identity, aggregation and pricing connected through the issued document.
3 stages · 1 approval
Roles and responsibilities
-
Step 1Capture metered usage
Event NumberSubscriptionMeterOccurred At
-
Step 2Prepare the billing interval
Run NumberSubscriptionPeriod StartPeriod End
-
Step 3Review and issue billing
Run NumberSubscriptionPeriod StartPeriod End
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Capture metered usage
Billing Operator: Receive verified event identities, reject conflicts and place accepted measurements into the correct occurrence-time interval.
Prepare the billing interval
Billing Operator: Freeze accepted terms, usage events, tier calculations, proration and tax evidence for the next invoice.
Approval required
Review and issue billing
Billing Manager: Review the prepared interval and issue its invoice once. Preserve the document and calculation the customer received.
Approvals and controls
1 approval required in this process
-
Review and issue billing
Billing Manager signs · closes the process
BillingRuns, Invoices, InvoiceLines - Preserve accepted terms and the original issued document.
- Keep missing usageTax and provider outcomes visible for resolution.
- Financial review is independent of preparation.
Keep the event trail behind the quantity
An event records both business occurrence and ingestion time. The half-open billing window includes the start and excludes the end. A cutoff freezes what the calculation knew, so a late event cannot quietly appear in an already issued bill. Keep that event for the configured adjustment route.
The same provider event identity and payload can arrive repeatedly without increasing usage. Changed payload under the same identity is a conflict. An accepted correction supersedes its linked original only after authorised review, retaining both pieces of evidence. A cross-customer replacement is rejected.
The aggregate points to its input set and meter version. Sum, Maximum and Latest answer different questions; apply the one accepted by the plan. Rating then applies the included allowance and actual tier rules. Preserve this explanation on the invoice rather than leaving the operator with only a total that cannot be reproduced.
Check the boundary case
An event exactly at the interval end belongs to the next period, while an earlier event received after the frozen cutoff follows the late-usage policy. Keep both timestamps available. A reviewer should be able to reproduce the included event set and the excluded exception without relying on today’s changing usage counter.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Capture metered usage | UsageEventsIntegrationEvents | Accept identified metering evidence |
| 2 Prepare the billing interval | BillingRunsUsageAggregatesInvoiceLines | Freeze the billing calculation |
| 3 Review and issue billing | BillingRunsInvoicesInvoiceLines | Issue the approved invoice once |
Process reports
All reportsUsage and Rating Detail
Trace billed units through frozen event aggregates, included allowances, tiers and the published plan version.
Invoice and Credit Register
Reconcile issued invoice net and tax amounts with approved issued line-linked credits.
Receivables Aging
Age collectible invoice balances from their agreed due dates at the selected reporting date.
Run by an agent
Agent support
Proto cannot invent customer acceptance, approve its own preparation, bypass account permissions or mark a provider request settled. Actual financial and commercial decisions remain with the configured authorised people.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› usage event to billed quantity · capture metered usage on UsageEvents, IntegrationEvents
✓ Billing Operator: Receive verified event identities, reject conflicts and place accepted measurements into the correct occurrence-time interval.
› usage event to billed quantity · prepare the billing interval on BillingRuns, UsageAggregates, InvoiceLines
✓ Billing Operator: Freeze accepted terms, usage events, tier calculations, proration and tax evidence for the next invoice.
› usage event to billed quantity · review and issue billing on BillingRuns, Invoices, InvoiceLines
⏸ approval · waiting for the billing manager
Other processes
3 moreAccepted plan to recurring invoice
Carry the accepted commercial version into a reviewed invoice for the agreed subscription interval.
4 stages · 2 approvals
Plan change to corrected charge
Explain changed subscription terms through proration and reviewed financial corrections.
4 stages · 2 approvals
Unpaid invoice to collection
Use the real invoice balance and observed provider outcome to guide collection and correction.
4 stages · 2 approvals