Everything published
31 publications
Guides, field notes, patterns and use cases — newest first.
2026-10-13GuideIndexing renewals without code: the Renew flow we should have built firstApplying a published index to renewals in Revenue Cloud, starting from the native asset-button flow. The flow, the renewal term that produced twelve years, and what the flow cannot do on its own.2026-10-13GuideNegative amendment at zero: the line that does not know it has a priceRemoving licences by amendment produces a line at zero, so no credit note. Three weeks of dead ends, a dead branch inside the standard procedure, and the Map Line Item step that was missing.2026-10-13GuideMigrating from CPQ to Revenue Cloud: carry the active book, not the historyA few hundred CPQ contracts to turn into Revenue Cloud assets without re-billing what the legacy engine already invoiced. The method, the seven traps found in rehearsal, and the one control that settles it.2026-10-13GuideRenewal at list price: when the pricing procedure ignores your Renew linesA native renewal coming out at full list price — no bundle discount, no included components, no indexation. Four causes stacked inside the procedure, and the tool that makes them visible.2026-10-05Use caseMigrate from Salesforce CPQ to Revenue CloudWhat transfers, what does not, and the distinction that makes most CPQ material inapplicable.2026-10-05Use caseGenerate the quote document automaticallyA branded PDF from a quote, without building a data-extraction layer to feed it.2026-10-05Use caseMove pricing configuration between orgsWhy a pricing procedure that works in one org returns nothing in the next, and what has to travel together.2026-10-05Use casePrice a setup fee by volume tierA setup fee that steps at a threshold, plus adders that scale with a count — without filling the pricing procedure.2026-10-05Use caseA bundle catalog that survives contact with sellersModel bundles, options and regional variants without producing a catalog nobody can maintain.2026-10-05Use caseSell through several legal entitiesOne org, several selling entities, and tax rules that must not leak between them.2026-10-05Use caseBring in invoices produced elsewhereGet invoices that were produced elsewhere into Revenue Cloud Billing without pretending the engine made them.2026-10-05Use caseCalculate due dates on fixed days of the monthDue dates that fall on fixed days of the month rather than a number of days after the invoice.2026-10-05Use caseIntra-EU VATCharge the right VAT across EU borders, including the zero-rated cases, and be able to explain any rate on any invoice.2026-10-05Use caseSubscription businessTerm subscriptions, amendments, renewals — and the billing schedule that has to hold it all together.2026-10-05PatternKeeping the ERP boundary cleanDecide what Revenue Cloud owns and what the ERP owns, before the integration decides for you.2026-10-05PatternDocument generation on the pricing contextGenerate a quote document without building a data-extraction layer, by reusing the context the pricing engine already uses.2026-10-05PatternScaling past the procedure ceilingWhat to do when one pricing procedure can no longer hold the logic of every offer.2026-10-05PatternIncluded allowances and overageExpress “the first N hours are included, beyond that you pay” natively — and find out why only one of your allowances applies.2026-10-05PatternRouting invoice lines to the ledgerGet invoice lines into the right accounting account when the invoice carries almost none of the information you need to route on.2026-10-05PatternThe Apex tax engine adapterWhen 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.2026-10-05PatternCountry-driven tax code, without ApexVary the tax code — not just the rate — by customer country, using only configuration and a flow.2026-10-05PatternBill-To driven taxationMake 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.2026-10-05Field noteProducts created by API can behave differently from identical ones created in the UIA bundle built by bulk API refused to open the configurator. A hand-built equivalent worked. The records looked the same.2026-10-05Field note“No such column” when the column existsAn Apex class pinned to an older API version cannot see fields added in a later one — even through dynamic SOQL.2026-10-05Field noteA flow criterion written in English fails silently on a localised orgBilling schedules were never created because a flow filtered on a status value that the org renders in another language.2026-10-05Field noteLedger assignment criteria are insert-only, and nothing warns youA mistake in a ledger routing criterion is permanent. The object accepts field names that do not exist, and only tells you at posting.2026-10-05Field noteThe billing prerequisites that fail without an errorFour pieces of org configuration decide whether billing schedules exist at all. None of them reports anything when missing.2026-10-05Field noteWhy a pricing procedure that works in one org returns nothing in the nextPricing is not one artefact but five, and moving a subset produces a procedure that runs and prices nothing.2026-10-05GuideA genuinely complex offer: tiered setup, adders, and twenty-one hardware variantsWhat it takes to model a managed-services offer where the setup fee steps at a headcount threshold, adders scale on a quantity that is not the seat count, and one bundle carries twenty-one appliance variants in three roles.2026-10-05GuideFrom order to invoice: where billing actually starts, and why it silently does notBetween 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.2026-10-05GuideProcedure Plans: what to do when one pricing procedure is fullA pricing procedure has a ceiling. We hit it at 128 elements with another offer still to build. Here is what the ceiling actually is, why counting it is harder than it looks, and what splitting the procedure costs you.