Subscription Movement
Explain additions, accepted plan changes, pauses and cancellations on a consistent as-of basis.
Carry the accepted commercial version into a reviewed invoice for the agreed subscription interval.
4 stages · 2 approvals
Follow the process from start to finish. Select a step to see who acts and what changes.
Billing Manager: Review the pricing mode, unit basis, band boundaries and effective version before publishing the prepared plan.
Publish the reviewed price versionVisible to: Billing Manager. Visibility does not establish approval authority.
Approval conditions.
Customer: Accept the offered plan, period anchor and quantity. Add a separate hosted mandate when automatic collection is part of the accepted terms.
Activate the accepted terms| 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 |
Billing Operator: Freeze accepted terms, usage events, tier calculations, proration and tax evidence for the next invoice.
Freeze the billing calculation| Run Number | Subscription | Period Start | Period End | Cutoff At |
|---|---|---|---|---|
| BR-31522 | SBS-23839 | 18 Sep | 23 Sep | 25 Sep |
| BR-98466 | SBS-94013 | 18 Sep | 27 Sep | 04 Oct |
| BR-31433 | SBS-22404 | 17 Sep | 22 Sep | 30 Sep |
| BR-72199 | SBS-90629 | 19 Sep | 26 Sep | 01 Oct |
| BR-43277 | SBS-98553 | 18 Sep | 23 Sep | 01 Oct |
| BR-70699 | SBS-55424 | 20 Sep | 22 Sep | 26 Sep |
Billing Manager: Review the prepared interval and issue its invoice once. Preserve the document and calculation the customer received.
Issue the approved invoice onceVisible to: Billing Manager. Visibility does not establish approval authority.
Approval conditions.
PricePlans, PriceTiers, UsageMeters
BillingRuns, Invoices, InvoiceLines
The customer accepts the plan version, quantity, currency and billing anchor. Automatic payment needs a separate mandate. A monthly anniversary and an annual commitment need an explicit calendar policy; neither can be inferred by adding a fixed number of days. Preserve the terms offered to the actual account.
The billing candidate uses those accepted terms and the reviewed usage or contracted quantity basis. Price catalogue edits affect future offers or accepted changes, leaving earlier agreements intact. Show any base, usage and proration components separately so the customer can understand why the total was calculated.
Before issue, confirm that the invoice’s source interval and tax result match the reviewed candidate. Invoice subtotal is net of tax; header tax is added once. Delivery failure creates a communication exception without issuing a new document or changing the invoice number.
| Stage | Records | Effect |
|---|---|---|
| 1 Publish commercial terms | PricePlansPriceTiersUsageMeters | Publish the reviewed price version |
| 2 Activate the subscription | CustomersSubscriptionsPaymentMethods | Activate the accepted terms |
| 3 Prepare the billing interval | BillingRunsUsageAggregatesInvoiceLines | Freeze the billing calculation |
| 4 Review and issue billing | BillingRunsInvoicesInvoiceLines | Issue the approved invoice once |
Explain additions, accepted plan changes, pauses and cancellations on a consistent as-of basis.
Normalise accepted recurring commitments by currency and stated inclusion policy; this is not recognised revenue.
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.
Separate pending, authorised, settled, refunded, disputed and unknown provider results.
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.
Keep event identity, aggregation and pricing connected through the issued document.
3 stages · 1 approval
Explain changed subscription terms through proration and reviewed financial corrections.
4 stages · 2 approvals
Use the real invoice balance and observed provider outcome to guide collection and correction.
4 stages · 2 approvals
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.