Revenue recognition beside billing
Contracts, schedules and journals come from the same source as the invoice, so finance does not rebuild revenue from an export.
Bill recurring plans accurately and recognise the revenue under ASC 606 and IFRS 15.
Define plans, meter usage, bill on schedule and renew without spreadsheets. Revenue recognition sits beside billing, so every contract, obligation and schedule traces back to what was sold and what was billed. Approvals use four eyes by default and the assistant only prepares work.
Contracts, schedules and journals come from the same source as the invoice, so finance does not rebuild revenue from an export.
Estimated rebates and bonuses are held back by a visible constraint and need a second person to change, which protects the audit position.
Preview, schedule, separate duties and approvals mean the right invoices go out once.
Standalone prices are proposed from observed sales or the price book, then accepted by a person.
Disaggregation, contract balances and remaining obligations are ready at period end.
Search or filter. Planned items are labelled; everything else is available now.
Define what you sell once, with the charge shapes recurring businesses actually use, and reuse it across every subscription.
7 featuresCreate subscriptions by hand or from an accepted quote, then change them mid-term without losing the history.
8 featuresTake usage in from your product and turn it into charges with the same engine that rates everything else.
5 featuresRenew on schedule, with the notice, uplift and quote your contract terms require.
4 featuresPrepare, approve and run billing for the whole book with four eyes, then hand clean invoices to receivables.
9 featuresKnow the health of the recurring book at any moment.
6 featuresIdentify the contract, split it into what you promised, and price each part fairly under ASC 606 and IFRS 15.
10 featuresRecognise revenue on the pattern that matches delivery, and post it with the same discipline as billing.
12 featuresEstimate discounts, rebates, penalties and bonuses and constrain them so revenue is never overstated.
7 featuresProduce the numbers the notes to the accounts ask for, under the standard you report in.
6 featuresApprovals are real policy on real records, and the assistant prepares work without approving it.
3 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Billing, Subscriptions & Revenue.
Bill runs, standalone selling price entries, manual schedules and variable consideration estimates can route through approval policies you control. Preparers never approve their own work.
Recurring revenue and revenue recognition datasets feed a fourteen-report pack and four role dashboards, plus a revenue disclosures dashboard.
Datasets
Dashboards
Subscription, plan, usage, bill run and revenue resources are in the public API, with events for downstream systems. Usage can be posted from your product in real time.
/v1 subscriptions (with change commands), subscription_plans, subscription_usage, subscription_bill_runs, revenue_contracts, revenue_runs, variable_consideration
Events
Connectors
Moving from an ERP: the finance packs below read the ledger history that revenue schedules rely on.
Subscriptions (list and detail), bill runs (list and detail), the billing decisions feed and the MRR table work on the phone. Revenue schedule work is a desktop task.
Orders and quoting contracts create subscriptions, billing schedules and revenue contracts.
Billing schedules arrive from accepted quotes. Renewals hand a renewal quote back.
Bill runs create draft invoices and credit notes in receivables.
Recognition runs post revenue, deferred revenue and contract assets, and feed the close checklist.
Commission payouts become capitalised contract costs.
Recurring revenue informs the revenue plan.
Subscription payments reach cash.
Advisers read billing and revenue.
No. Billing and revenue run on their own and queue journals for export. When the ledger is licensed, runs post through it.
Point in time, ratable by day or month, usage, milestone, percentage of completion, as billed and manual schedules.
Not with segregation on, which is the default. The database enforces it.
Yes. The primary standard is a tenant setting, and a second book can be queued for export.
Not yet. It needs a live payment provider account and is planned.
As elements with an estimate and a constrained amount that is never above the estimate. Changes are revisions and large ones need a second person.
No. It prepares, previews and explains. Approvals and posting stay with people.