Scope
1 area implies 6 topics across 3 modules
You did not pick these
Customer Relationship Management, Supply Chain Management
Your streams cross into these modules, so the work happens there too. That is the part most scoping exercises miss.
The end-to-end
Order-to-Cash
Customer Relationship Management → Supply Chain Management → Financial Accounting
- 01Order-to-Fulfilimplied
- 02Fulfil-to-Invoice
- 03Invoice-to-Cashimplied
Data in and out
What actually crosses the boundary, which way, how often, and what it costs when it stops.
Crosses your scope boundary
Revenue postings←Accounts Receivable
Continuous
General Ledger \u00b7 without it: Revenue is recognised late or not at all.
Customer orders←Sales Force Automation
Continuous
Order Processing \u00b7 without it: Orders are rekeyed and differ from what was agreed.
Interfaces outside the ERP
Customer receipts←Bank statement feed
Daily
Accounts Receivable \u00b7 without it: Cash is unapplied and collections chase customers who have paid.
Invoices and statements→Customers and e-invoicing networks
Per billing cycle
Accounts Receivable \u00b7 without it: Payment terms start late, and days sales outstanding rises.
Integration points
Every module boundary a stream crosses is an interface. The ones marked straddle your scope — you are changing one side and not the other, which is the interface most often missed at scoping and found during testing.
Customer Relationship Management→Supply Chain Management
Order-to-Cash
Supply Chain Management→Financial Accounting
Order-to-Cash
One side of this is outside your scope
Supply Chain Management→Customer Relationship Management
Order-to-Fulfil
Supply Chain Management→Financial Accounting
Fulfil-to-Invoice
One side of this is outside your scope
The order to do it in
Order Management
Nothing in scope blocks these — they can start together.
Accounts Receivable
Unblocked once the phase above is standing.
Sequence is a delivery judgement rather than a fact about the taxonomy. These are proposals from common tier-1 ordering — argue with them.
Assumed already in place
This scope depends on Inventory, General Ledger without including them. Fine if they are already standing and staying as they are — a gap in the plan otherwise.
Concerns raised
Australian obligations in scope
Nothing AU-specific in this scope.
Everything in scope — 6 topics
The ones you chose, and the ones they brought with them. An implied topic cannot be dropped on its own — it is here because of a pick, and the pick is named.
You picked these — 1
Came with them — 5 you did not pick
Next
This is a diagnosis, not a plan
Build takes the same scope and turns it into the documents somebody has to write — the investment brief, the business case, the plans — starting with what each one needs as an input before its headings can be answered honestly.
Build it →Share this scope
The scope is in the address bar. Send the link and the other person sees the same picture.