Billing·Reference·6 min·Updated 2026-10-05
Non-standard payment terms
Due dates that fall on fixed days of the month rather than a number of days after the invoice.
Business requirement
Customers pay on the next 1st, 11th or 21st after the invoice date — not “30 days net”. The due date has to be correct on the document and in the ledger.
Why it is not trivial
Standard payment terms express a duration. This rule expresses a calendar. The gap is small and the consequences are not: every ageing report and every dunning rule reads the due date.
Recommended architecture
Keep the payment term as the carrier of the rule and compute the date at invoice time through a billing extension point, rather than trying to express a calendar as a duration.
Salesforce components
Select one to open its detail.
Flow
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
Model the three fixed days as data, not as code branches, so finance can change them without a deployment. Compute the next occurrence from the invoice date and write it to the due date.
Watch out
- The payment term lives on the order, not on the billing profile. The field the documentation suggests on the profile did not exist on the object when checked by describe.
- No payment term on the order means no billing output at all — not a wrong date, no output.
Alternatives
Approximating with a fixed number of days is tempting and wrong by up to ten days per invoice. Where the customer base is small, a manual override is honest; at volume it is not.