Revenue is not billing. Billing is not a receivable.
And a receivable is not cash. Four quantities that sit in one bucket in many organisations and therefore run against each other on a regular basis. FinanceOS keeps them apart and connects them.
What each of them is — and what it is not.
The principle sounds academic until a recurring billing run, a credit note and a partial payment meet in the same month.
The performance recognised
By contract component, in the right period, regardless of whether an invoice has been issued.
The billing run
Price, terms, tier, consumption. It can run ahead of recognition or behind it — both are normal, and both have to be explainable.
The open item
Created with the invoice, carrying a due date and payment behaviour, and from there it belongs to working capital.
The receipt
Applied, not estimated. Between a receivable and cash lie a payment promise, a dispute and a deduction.
Confusing these four means arguing at quarter end about figures that are all correct and still do not add up.
What this domain is responsible for.
From contract to evidence, eight stations.
The same chain carries tax: one contract clause determines revenue recognition, billing date, tax consequence and liquidity at once.
01 · Contract
Clause, term, consideration
02 · Price and terms
Discount, tier, indexation
03 · Delivery
Performed, accepted, documented
04 · Billing
Billing run and invoice
05 · Revenue recognition
By contract component
06 · Accrual
In the right period, with a reason
07 · Tax effect
Visible before it is reported
08 · Close and evidence
The evidence chain for the audit
Where this domain appears on the horizontal axis.
A domain on its own is a responsibility. It becomes visible where a business record runs through it.
The invoice still goes out from your system.
FinanceOS replaces neither your billing system nor your ERP. It holds the connection between the four quantities and makes it evidenceable.
Your ERP
Invoice output, posting, customer account.
Your billing system
Tariffs, usage data, billing run.
Your legal team
Contract work and clause drafting.
FinanceOS
Recognition, accrual, handover, evidence.
The principle holds internally too: FinanceOS does not invent a second revenue truth. It makes visible where the four quantities diverge in your organisation, and why.
What is verified in the product in this domain today
Handover into close and receivables
Verified in the product
The transition from recognised revenue into accrual and open items, with evidence.
Recognition by contract component
Pilot or validation
The split by component on multi-element contracts.
Consumption-based models
In active development
Usage-driven and recurring billing in full depth.
What is not marked, we do not claim.
Maturity per capability is stated on the product status page. What we can evidence today
How long does it take you to reconcile billing to revenue?
If the answer is “until the close is done”, that is the entry point. Thirty minutes on one of your contract models.