Bill and collect

How claims are labelled

Salesforce docsdocumented by SalesforceField experienceobserved on a real orgRecommended patternwhat we recommendTo verifyunverified

Billing takes three days a month, it goes out late the moment someone is away, and the mistakes are found by the customer.

The architecture

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.

Use case

Calculate due dates on fixed days of the month

Due dates that fall on fixed days of the month rather than a number of days after the invoice.

Bring in invoices produced elsewhere

Get invoices that were produced elsewhere into Revenue Cloud Billing without pretending the engine made them.

Guide

From order to invoice: where billing actually starts, and why it silently does not

Between an activated order and a posted invoice sit an orchestrator, a context definition, four org settings and a set of order-line fields nobody tells you are required. Each one fails without an error.

Pattern

Routing invoice lines to the ledger

Get invoice lines into the right accounting account when the invoice carries almost none of the information you need to route on.

Field note

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.

Ledger 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.