Meter definitions
Name the unit and accepted aggregation method before publishing prices. Summing events, using the highest measurement and selecting the latest value produce different quantities, so the plan and meter version must agree.

API, data and infrastructure services charging for an explicitly measured unit.
API, data and infrastructure services charging for an explicitly measured unit.
Name the unit and accepted aggregation method before publishing prices. Summing events, using the highest measurement and selecting the latest value produce different quantities, so the plan and meter version must agree.
Preserve event identity, occurrence time and payload digest. A retry returns the original accepted contribution. Conflicting payloads and cross-customer corrections remain exceptions instead of increasing the next bill.
Retain the accepted event set, included allowance and tier calculation with each invoice. Graduated and volume pricing follow their declared band rules and need boundary examples during configuration.
Freeze the receipt cutoff for an issued interval. A later event or approved replacement follows a reviewed adjustment path while preserving the original quantity and document the customer received.
Meter definitions
Replay-safe ingestion · Late usage corrections
Explainable rating
Same records, same gates. The configuration changes how the process runs for this team.
Visible to: Billing Manager. Visibility does not establish approval authority.
Approval conditions.
Visible to: Billing Manager. Visibility does not establish approval authority.
Approval conditions.
Independently approve PricePlans, BillingRuns, BillingAdjustments, CreditNotes, RefundRequests and UsageEvents corrections.
Independently approve PricePlans, BillingRuns, BillingAdjustments, CreditNotes, RefundRequests and UsageEvents correctionsReview configured proration, tax and collection policyInvestigate PaymentAttempts and financial exceptionsApproval conditions.
Prepare Customers, PricePlans, SubscriptionChanges and BillingRuns.
Prepare Customers, PricePlans, SubscriptionChanges and BillingRunsInvestigate UsageEvents and create authorised correction proposalsPrepare BillingAdjustments, CreditNotes and RefundRequestsView assigned customer subscription dates, issued invoices and public usage summaries.
View assigned customer subscription dates, issued invoices and public usage summariesCreate scoped customer change requests with recorded evidenceRoute disputes to Billing OperatorRead own Customers, Subscriptions, issued Invoices, issued CreditNotes and permitted UsageAggregates.
Read own Customers, Subscriptions, issued Invoices, issued CreditNotes and permitted UsageAggregatesAccept own offered terms and submit SubscriptionChangesAdd or revoke own hosted PaymentMethods through provider flow| Subscription Number | Price Plan | Current Period Start | Current Period End | Quantity |
|---|---|---|---|---|
| SBS-25832 | PP-29934 | 18 Sep | 26 Sep | 110 |
| SBS-27053 | PP-97891 | 13 Sep | 21 Sep | 330 |
| SBS-99859 | PP-86164 | 23 Sep | 02 Oct | 590 |
| SBS-16471 | PP-56059 | 27 Sep | 05 Oct | 840 |
| SBS-63877 | PP-10231 | 08 Sep | 10 Sep | 840 |
| SBS-29095 | PP-57171 | 15 Sep | 18 Sep | 140 |
View seller-entity scoped billing, collection and subscription reports.
View seller-entity scoped billing, collection and subscription reportsExport authorised summaries with sensitive tokens maskedNo changes, financial decisions or collection executionTurn accepted usage events into an explainable billing quantity.
Turn product prices into clear, versioned subscription terms.
Track subscription billing, usage and collection with a consistent reporting basis.
Issue subscription invoices with a preserved price, usage and tax calculation.
Manage accepted subscriptions, renewals and effective changes without losing earlier terms.
Follow up on unpaid invoices using the actual collection outcome.
Trace billed units through frozen event aggregates, included allowances, tiers and the published plan version.
Reconcile issued invoice net and tax amounts with approved issued line-linked credits.
Age collectible invoice balances from their agreed due dates at the selected reporting date.
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.
Related questionA 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.
Related questionGraduated pricing rates the units in each used band. Volume pricing selects a band from total billable quantity and applies that band’s configured rate to the quantity. Published tier boundaries and examples make the calculation reviewable.
Related questionAn 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.
Related questionThe 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.
Related questionAccepted 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.
Related questionThe 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.
Related questionPreserve 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.
Related questionThe app reports accepted recurring commitments, issued billing and actual collection on a stated basis. Revenue recognition and general-ledger posting belong to the configured accounting system and its approved policies.
Related questionTeams billing recurring software plans and accepted changes to seats or features.
API, data and infrastructure services charging for an explicitly measured unit.
Businesses collecting repeat service fees and maintaining customer billing history.
Create your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.