Sign in Start free trial
Finance

Billing, Subscriptions & Revenue

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.

76 features available 1 planned 11 capability areas
Highlights

What stands out

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.

Variable consideration with the constraint

Estimated rebates and bonuses are held back by a visible constraint and need a second person to change, which protects the audit position.

Safe bill runs

Preview, schedule, separate duties and approvals mean the right invoices go out once.

Selling price suggestions from your own sales

Standalone prices are proposed from observed sales or the price book, then accepted by a person.

Disclosure pack

Disaggregation, contract balances and remaining obligations are ready at period end.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Plans, products and charge models

Define what you sell once, with the charge shapes recurring businesses actually use, and reuse it across every subscription.

7 features
  • Plan cataloguePlans carry one or more charges, a billing period and a currency, so a subscription is built from a plan rather than typed line by line.
  • Flat, per-unit and one-time charges
  • Graduated tier pricingPrice each band of quantity at its own rate and bill the sum of the bands.
  • Volume pricingPrice the whole quantity at the rate of the band it falls in.
  • Usage charges with included allowanceInclude a quantity in the plan and bill only the usage above it, flat or in tiers.
  • Tier editor on the plan formAdd, reorder and check price bands visually on the plan form instead of editing raw numbers.
  • MetersDefine the usage meters a plan rates against, with the aggregation rule for the period.

Subscriptions and mid-term changes

Create subscriptions by hand or from an accepted quote, then change them mid-term without losing the history.

8 features
  • SubscriptionsEach subscription has a customer, entity, term, seats and auto-renew choice, and is built from plan charges.
  • Effective-dated subscription linesA line is never edited. It is closed once and a new line takes over, so every past invoice can be explained.
  • Smart defaults on the new-subscription formEntity, start date, tenant default term, seats and auto-renew are filled in for you and checked again on the server.
  • Change preview before applyingSee the proration and the effect on the next bill before a seat, plan or price change is applied.
  • Proration of mid-term changesAdd or remove seats or switch plans mid-period and the bill reflects the exact days owed, with credit for unused time on by default.
  • Anchored billing periodsPeriods follow the billing anchor day, clamped for short months.
  • Subscription hand-off from quotesAn accepted quote creates the subscription and its billing schedule without re-keying.
  • Standalone use without the ledgerBilling and revenue run without a general ledger licence. Journals queue for export until a ledger is connected.

Usage metering and rating

Take usage in from your product and turn it into charges with the same engine that rates everything else.

5 features
  • Usage ingest APIPost usage events from your product. Each event is unique per meter and event id, so retries never double count.
  • Usage CSV uploadLoad usage from a file when no API is available, with the same duplicate protection.
  • Rated usage viewSee each event rated against its tiers and allowance, per subscription and period.
  • Late usage and re-runsUsage that arrives after a period was billed is picked up in the next run as owed minus billed, never billed twice.
  • Unbilled usage revenue (optional)Turn on recognition of rated but unbilled usage as a contract asset at period end. Off by default.

Renewals

Renew on schedule, with the notice, uplift and quote your contract terms require.

4 features
  • Auto-renew and evergreen termsSubscriptions renew automatically or run evergreen, according to the choice on the subscription.
  • Renewal notice periodA renewal-due event fires ahead of the term end (30 days by default) so teams and customers are warned in time.
  • Price uplift on renewalApply a percentage uplift at renewal. The default is 0 percent and it is a tenant setting.
  • Renewal quote hand-back to quotingThe renewal draws up the renewal quote in the quoting hub, owned by the original quote owner, and billing shows the quote number on the subscription. You can also ask for one on demand.

Bill runs and invoices

Prepare, approve and run billing for the whole book with four eyes, then hand clean invoices to receivables.

9 features
  • Bill runsA run goes prepare, authorize, execute, reconcile. It picks up everything owed minus what was already billed, per line and period.
  • Separation of duties on runsWith segregation on (default), the person who prepared a run cannot authorize or execute it. The database enforces it.
  • Billing previewPreview an invoice run in a safe sandbox. Nothing is saved.
  • Scheduled bill runsSet weekly or monthly runs, optionally per entity. Each period prepares one run, a different person authorizes it, and it is skipped if a run is open or nothing is billable.
  • Approval routing for runsBill run preparation and authorization can wait for approval in Workflow under your own policy, with withdraw supported.
  • One draft invoice per billing requestReceivables creates one draft invoice (or a credit note for a net credit) per request. A person posts it.
  • Explain an invoice lineAsk why a bill line has the amount it has: the period, the proration, the tier and the usage behind it.
  • Credit notes, refunds and write-offs from billingIssue credits, refunds and write-offs from the billing screens and see them against the invoice.
  • Card retry and payment account updaterPlannedAutomatic retry of failed card payments and refreshed card details need a live payment provider account. Planned: not built.

Recurring revenue analytics

Know the health of the recurring book at any moment.

6 features
  • MRR and ARRMonthly and annual recurring revenue by subscription, plan and period.
  • MRR movementNew, expansion, contraction and churn each month, from the same ledger of changes that billing uses.
  • Net and gross revenue retentionNRR and GRR computed from the movement view.
  • Cohort analysisSee retention by the month a customer started.
  • Billing report packFourteen ready reports across billings, MRR movement, revenue by month, deferred revenue and disclosures, runnable and cloneable.
  • Role dashboardsDashboards for the billing specialist, billing manager, revenue accountant and CFO, plus a revenue disclosures dashboard.

Revenue contracts and performance obligations

Identify the contract, split it into what you promised, and price each part fairly under ASC 606 and IFRS 15.

10 features
  • Contract identificationRevenue contracts come from subscriptions, orders and quoting contracts, or are created manually. Each source is only counted once.
  • Contract combinationWhat one accepted quote sold is combined into one contract by default.
  • Performance obligationsEach contract is split into obligations with their own pattern and price.
  • Standalone selling price bookKeep standalone selling prices with effective dates. Entries wait in Workflow for approval.
  • Relative allocationThe transaction price is allocated across obligations by relative standalone price, with discounts and residual handled, and usage-only items kept variable.
  • Selling price suggestionsRun suggestions from observed standalone sales (median and interquartile range) or from the quoting price book less the usual discount. A person accepts, dismisses or ignores them.
  • Selling price range testOptionally flag prices outside the tenant range (15 percent either side by default, off by default).
  • Contract modificationsModifications are classified automatically as separate contract, termination and new, or part of the existing contract, with cumulative catch-up or prospective treatment.
  • Prospective treatment of subscription changesSubscription changes are handled prospectively by default.
  • Item rulesSet rules by item for how obligations are treated.

Recognition schedules and runs

Recognise revenue on the pattern that matches delivery, and post it with the same discipline as billing.

12 features
  • Point in time recognitionRecognise on the delivery date.
  • Ratable by day or monthSpread revenue evenly over the service period. Daily is the default.
  • Usage-based recognitionRecognise as usage is billed.
  • Milestone recognitionRecognise as milestones are achieved and recorded.
  • Percentage of completionRecognise by measured progress recorded against the obligation.
  • As billed and manual patternsFollow billing, or set a manual schedule that waits for approval.
  • Schedule override with approvalOverride a schedule by hand. The override waits in Workflow, and a rejection closes it.
  • Recognition runsPrepare, authorize, post and reconcile once per entity, period and book, with segregation of duties on by default.
  • Ledger posting and close checklistPosting goes through the ledger's posting service, and the close checklist gains a revenue recognition task that checks itself.
  • Deferred revenue and contract assetsAsset and liability are netted per contract so each contract shows one position.
  • Contract cost capitalisationCommissions from incentive payouts are capitalised and amortised (36 months by default, with the one-year expedient on).
  • Explain a revenue scheduleAsk for a plain-language explanation of why a schedule recognises what it does.

Variable consideration

Estimate discounts, rebates, penalties and bonuses and constrain them so revenue is never overstated.

7 features
  • Elements of variable considerationRecord discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties and usage-based fees against a contract.
  • Expected value and most likely amountEstimate each element from scenarios and history by either method.
  • The constraintApply the constraint with the five risk factors and a tenant tail. The constrained amount is never above the unconstrained one, and the database checks it.
  • Allocation including the exceptionAllocate general variable consideration by relative price, with the exception to a single obligation when a documented reason exists.
  • Re-estimation with cumulative catch-upA new estimate is a new revision. The catch-up flows through the next recognition run and its ledger journal.
  • Four eyes on estimate changesChanges at or above a tenant threshold (5,000 by default) need a different person to approve. Assistant proposals always do.
  • Changes-in-estimates disclosure and tie-outOpening plus new plus increases plus decreases plus settled equals closing, and the schedule change ties to the run's catch-up lines.

Disclosures and accounting policy

Produce the numbers the notes to the accounts ask for, under the standard you report in.

6 features
  • IFRS 15 and ASC 606 as settingsChoose the primary standard as a tenant setting. A second book can be queued for export.
  • Revenue waterfallSee revenue recognised, billed and remaining by period.
  • Disaggregation of revenueBy timing, pattern and segment.
  • Contract balances roll-forwardNet closing equals opening plus recognised minus billed.
  • Remaining performance obligations by time bandBands are a tenant setting (12, 24 and 60 months by default).
  • Significant judgements placeholderA text widget on the disclosures dashboard holds your judgements narrative.

Workflow, decisions and AI

Approvals are real policy on real records, and the assistant prepares work without approving it.

3 features
  • Decisions feedOne feed of bill-run, price and schedule requests: waiting, approved, in use, turned down and taken back.
  • Approve, reject and withdraw pathsEach path is proved with real policies, and withdrawing a request cleans up what it created.
  •  AI billing and revenue actions AI can list, preview, explain, identify contracts, suggest prices, prepare runs and draft estimates. Approvals and posting stay with people.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Preview a billing run and explain an invoice line
  • List, preview and prepare bill runs for a person to authorize
  • Record usage and show rated usage for a subscription
  • Identify revenue contracts and draft contract changes
  • Explain a revenue schedule or the revenue waterfall
  • Suggest standalone selling prices and list suggestions
  • Draft and re-estimate variable consideration with a preview and a tie-out
  • Ask quoting for a renewal quote
  • Run or clone a report from the billing report pack
  • Summarise abuse signals on usage and explain the credit liability roll-forward
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to Billing, Subscriptions & Revenue.

Workflow

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.

  • A monthly bill run above a value you set needs the billing manager to approve before it executes.
  • A new standalone selling price waits for the revenue accountant to approve.
  • A manual recognition schedule override needs the controller.
  • A change to a variable consideration estimate above the tenant threshold needs a different person to approve.

Reporting and analytics

Recurring revenue and revenue recognition datasets feed a fourteen-report pack and four role dashboards, plus a revenue disclosures dashboard.

Datasets

MRR and movementBillingRevenueRevenue balancesContract roll-forwardRemaining obligations by bandVariable consideration changes and elements

Dashboards

Billing specialistBilling managerRevenue accountantCFORevenue disclosures

Integration

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

subscriptions.subscription.changedsubscriptions.plan.changedsubscriptions.invoice.requestedsubscriptions.bill_run.changedsubscriptions.usage.receivedsubscriptions.renewal.duesubscriptions.revenue_run.changedsubscriptions.revenue_contract.changed

Connectors

Inbound: quoting contracts and billing schedules, orders, incentive payoutsOutbound: receivables invoice requests and ledger journalsPayment provider for card retry is planned and needs a provider account

Migration

Moving from an ERP: the finance packs below read the ledger history that revenue schedules rely on.

  • Zuoraplanned
  • Chargebeeplanned (Migrate tracker row MG-PK-SUB-CHARGEBEE is OPEN.)
  • Recurlyplanned (Migrate tracker row MG-PK-SUB-RECURLY is OPEN.)
  • Maxio (Chargify, SaaSOptics)planned (Migrate tracker row MG-PK-SUB-MAXIO is OPEN.)
  • SAP ERP familyavailable (Migrate packs are ON TST (tracker MG-22, verified 2026-11-04). Live runs against a customer system are external.)
  • Oracle ERP familyavailable (Migrate packs are ON TST (tracker MG-23).)
Mobile

On the phone

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.

Who uses it

Billing specialistBilling managerRevenue accountantControllerCFOAccountant (read)

Industries

  • Software and subscription businesses
  • Services with usage-based charges
  • Businesses that report under ASC 606 or IFRS 15
Questions

Frequently asked

Do I need the general ledger to use billing and revenue recognition?

No. Billing and revenue run on their own and queue journals for export. When the ledger is licensed, runs post through it.

Which revenue recognition patterns are supported?

Point in time, ratable by day or month, usage, milestone, percentage of completion, as billed and manual schedules.

Can the same person prepare and approve a bill run?

Not with segregation on, which is the default. The database enforces it.

Does it support both IFRS 15 and ASC 606?

Yes. The primary standard is a tenant setting, and a second book can be queued for export.

Is card retry and payment recovery included?

Not yet. It needs a live payment provider account and is planned.

How are variable amounts such as rebates handled?

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.

Can the assistant approve or post?

No. It prepares, previews and explains. Approvals and posting stay with people.

See Billing, Subscriptions & Revenue on  AI

Talk to us