Billing
From an order to a posted invoice
Billing schedules, invoices, credit memos, payments, ledger
Billing is the part of Revenue Cloud that fails most quietly. Billing schedules, invoices and invoice lines are outputs of the engine — they cannot be created by hand or by API. When the org prerequisites are not in place they are simply never produced, and nothing reports it.
The invoice itself carries far less than people expect: no country field, a null billing-profile reference, and a tax code on the line that stays empty even after posting.
The objects
Select any object to open its detail — purpose, the fields that matter, what it relates to, and what to watch for.
The architecture
Scroll the diagram sideways
Every box on the top row is a prerequisite that produces no error when it is missing — the schedules simply never appear. The order line is the other silent failure: it needs period boundary and billing frequency fields that are not surfaced as required, so a data import passes cleanly and nothing ever bills.
Implementation guides
Solution patterns
Use cases
Non-standard payment terms
Due dates that fall on fixed days of the month rather than a number of days after the invoice.
IntegrationBringing in externally produced invoices
Get invoices that were produced elsewhere into Revenue Cloud Billing without pretending the engine made them.
Field notes
The billing prerequisites that fail without an error
Four pieces of org configuration decide whether billing schedules exist at all. None of them reports anything when missing.
BillingLedger assignment criteria are insert-only, and nothing warns you
A mistake in a ledger routing criterion is permanent. The object accepts field names that do not exist, and only tells you at posting.