Solution patterns
Reusable answers, taken from real projects.
Each pattern follows the same shape: the problem, the context it came from, the architecture we recommend, how to build it, and what it costs you. Anonymised — never generalised into uselessness.
Bill-To driven taxation
Make the tax rate follow the billing profile rather than the order address — and know why that is the correct reading of the model, not a workaround.
TaxCountry-driven tax code, without Apex
Vary the tax <em>code</em> — not just the rate — by customer country, using only configuration and a flow.
TaxThe Apex tax engine adapter
When the shipped engine returns nothing, what a working adapter actually has to implement — and the eight failures that stand between you and a taxed invoice.
BillingRouting 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.
PricingIncluded allowances and overage
Express “the first N hours are included, beyond that you pay” natively — and find out why only one of your allowances applies.
PricingScaling past the procedure ceiling
What to do when one pricing procedure can no longer hold the logic of every offer.
IntegrationDocument generation on the pricing context
Generate a quote document without building a data-extraction layer, by reusing the context the pricing engine already uses.
IntegrationKeeping the ERP boundary clean
Decide what Revenue Cloud owns and what the ERP owns, before the integration decides for you.