Layer 1 — Pricing
A Pricing Context defines the structure for one product or service line — the rate components, charge components, and usage inputs that can appear on a bill. It is the canvas. On top of the context, you build Pricing Modules — rate cards that set the actual prices, charges sets that define the rules, and plans that compose them into sellable offers. One context can support many plans without rebuilding the product structure.Layer 2 — Subscription
A Subscription enrolls a customer onto a specific plan. It captures the customer’s version of that plan — their contract terms, subscription inputs (SLA tier, seat count, region), and the usage that accrues each billing period. Every subscription links to a Billing Account, which is what actually gets invoiced. A billing account can hold just one subscription — the common shape for a B2C customer — or several, letting a B2B client’s multiple services roll up into a single consolidated bill instead of one per service. Same subscription mechanism either way; the billing account is what decides whether the customer gets one bill or many. Without a subscription, you have pricing but no one to bill.Layer 3 — Billing
A Bill Run processes all active subscriptions for a period. It ingests meter readings and usage, applies the plan’s pricing logic, and produces draft invoices for review. Drafts can be adjusted — meter corrections, manual line items, credits — before being posted and distributed to customers. Nothing is locked until you post.Layer 4 — AR Management
Once an invoice is posted, it enters AR. Payments are matched to open invoices, credits and adjustments post as formal entries to the customer’s subledger, and the AR Aging Report tracks what remains outstanding by how long it has been unpaid. Every transaction — invoice, credit note, payment, late fee — is recorded on the customer AR subledger. The balance is the sum of every entry, not a number someone edited.Layer 5 — Reporting
Reporting draws on everything upstream — pricing, subscriptions, billing, and AR — to show monthly sales and payments, aged receivables, what a bill run actually produced (bills generated, late payment charges applied, waived), and usage history by bill run or by subscription. These aren’t separate exports bolted on afterward; they read from the same records the other four layers already produced.For the full detail on each layer, use the navigation on the left.