Architecture
Billing architecture
What has to be true before a single invoice exists — most of it invisible until the first one fails.
Salesforce docs documented by SalesforceField experience observed on a real orgRecommended pattern what we recommendTo verify unverified
Billing architecture
order → schedule → invoice
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.
The objects involved
Select one to open its detail.
Guide