An RFP says “25 forms”, “around 40 roles”, “integration with 12 systems”. The bid prices 25, 40 and 12. Delivery then discovers that each form exists in four countries and two languages and must also travel as a structured e-invoice; that each role must be restricted by company code and re-checked for segregation of duties; that each system carries several messages in both directions, on new APIs, tested four times.
None of that is scope creep. It is multiplication the estimate never did. We call it the Scope Multiplier, and it is why so many S/4HANA programmes run long: Horváth found transformations take on average 30% longer than planned, and ISG found only 15% of SAP migrations on time and on budget.
Three multipliers we see in almost every S/4HANA bid
| Multiplier | The RFP says | Delivery builds |
|---|---|---|
| The Output Iceberg | “25 forms” | Types × countries × languages × channels, plus structured e-invoice mappings for every mandated country |
| Roles Debt | “About 40 roles” | Roles × organisational restrictions, mapped to Fiori catalogs and re-proved against SoD rules |
| The Interface Multiplier | “12 systems” | Systems × business objects × directions, many rebuilt on standard APIs, each tested in every cycle |
Why now: the e-invoicing wave
The Output Iceberg is getting bigger. Belgium has required structured B2B e-invoices since January 2026; Poland’s KSeF phased in from February 2026; France requires all companies to receive e-invoices from September 2026; Germany requires issuing from 2027 for larger businesses and 2028 for all; Ireland’s first phase starts on 1 November 2028; and EU-wide intra-community e-invoicing follows in July 2030. Every one of those turns an invoice from a layout into a compliance integration, and any S/4HANA programme running through 2027–2030 will meet several of them.
Turn the change request into a unit rate
- Multiply what you can: ask the clarification questions that expose countries, languages, org units and the integration inventory.
- State the base in units, not words: “72 output deliverables”, not “standard forms”.
- Attach a unit rate to every multiplier: per extra layout, e-invoice mapping, derived role, message flow and test cycle. When the number grows, the price grows by an agreed amount.
Run the multiplier on your RFP
Enter what the RFP says, then the dimensions you know. Nothing you type leaves your browser.
A multiplier above 2× (shown in red) is a pricing decision, not an assumption. Put a unit rate on it before you submit. Default values are the illustrative example from the whitepaper.
The surveys show S/4HANA programmes overrun because of scope and complexity; they don’t measure outputs, roles or interfaces separately. Linking change requests to these three areas is our own model, from bid and delivery experience. The examples are illustrative.
The Scope Multiplier
10 pages: the model, a formula and worked example for each multiplier, the unit-rate method, the multiplier sheet and twelve clarification questions. No sign-up.
Want the multiplier run on your live bid? Our Orange Team review stress-tests assumptions, scope lines and staffing before you freeze scope and price. Book a free discovery call.
Sources: Horváth, March 2025; ISG, March 2026; KPMG Belgium; KPMG Poland; service-public.gouv.fr; IHK Stuttgart; Revenue.ie (updated 20 Oct 2026); Deloitte on ViDA. Full references in the whitepaper. E-invoicing dates change; check the current rules for each country. General information, not tax or legal advice.