Supply accepted plan terms, customer identities, meter definitions, tax treatment, provider access, recurring mandates, accounting mappings and billing-review authority.
Implementation
Configure and reconcile a complete subscription billing interval.
Implementation phases
- Agree commercial termsTeam and ERP.ai
- Reconcile identity and historyCustomer
- Connect usage and taxTeam and ERP.ai
- Exercise billing and correctionsTeam and ERP.ai
- Review collection and accessCustomer
Phase 1 · Team and ERP.ai
Agree commercial terms
Define products, intervals, quantity bases, tiers, included usage, proration, currencies and acceptance evidence.
Phase 2 · Customer
Reconcile identity and history
Import customer scope, active subscriptions, published prices, outstanding documents and settled receipts without repeating collection.
Phase 3 · Team and ERP.ai
Connect usage and tax
Validate event identity, aggregation, cutoff and tax-result handling against explicit examples.
Phase 4 · Team and ERP.ai
Exercise billing and corrections
Test one issue per interval, tier boundaries, effective changes, late usage, credits and separate refunds.
Phase 5 · Customer
Review collection and access
Test unknown provider outcomes, dispute holds, customer account isolation and revoked mandates through UI and API.
Publish a new price revision or record an accepted effective subscription change. Preserve old invoices and correct them with reviewed source-linked documents. Recheck the website, canonical specification and app skill together when changing supported billing behaviour.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.