The billing prerequisites that fail without an error

A billing schedule is produced by the engine from an order. When the prerequisites are not in place, no schedule is produced — and nothing anywhere says so. The order looks fine, the invoice run finds nothing to invoice, and the investigation starts in the wrong place.

What has to be true, all of it invisible until the first invoice fails:

• The order save behaviour release update — found under the archived tab, which is not where anyone looks.
• The billing context definition extended and activated, then declared in the billing settings as a context service mapping.
• The correct intra-context mapping. The schedule-group mapping, not the order mapping. Choosing the wrong one produces no schedules and no error.
• The billing defaults: legal entity, billing treatment, tax treatment.

And then the data. A billing profile produces nothing without a bill-to contact, a payment term on the order, and a delivery address. The order line needs period boundary, boundary start month, boundary day and billing frequency — none of which is surfaced as required.

This last point is the one that matters at scale. A data migration of thousands of accounts will import cleanly and bill nothing. Check it on one record before loading the rest.