Scope
1 area implies 7 topics across 2 modules
You did not pick these
Supply Chain Management
Your streams cross into this module, so the work happens there too. That is the part most scoping exercises miss.
The end-to-end
Procure-to-Pay
Supply Chain Management → Financial Accounting
- 01Source-to-Contractimplied
- 02Requisition-to-Receiptimplied
- 03Invoice-to-Pay
Data in and out
What actually crosses the boundary, which way, how often, and what it costs when it stops.
Crosses your scope boundary
Sub-ledger postings←Accounts Payable
Continuous
General Ledger · without it: Payables detail and the control account disagree.
Net pay file→ABA
Per pay run
Payroll · without it: Staff are not paid.
Interfaces outside the ERP
Supplier invoices←Supplier e-invoicing, email and portals
Continuous
Accounts Payable · without it: Invoices arrive by exception and are keyed by hand.
Remittance advice→Suppliers
Per payment run
Accounts Payable · without it: Suppliers cannot reconcile and call the finance team instead.
Purchase orders→Suppliers, EDI and supplier portals
Continuous
Procurement · without it: Suppliers work from email and there is no commitment record.
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.
Supply Chain Management→Financial Accounting
Procure-to-Pay
One side of this is outside your scope
Supply Chain Management→Financial Accounting
Requisition-to-Receipt
One side of this is outside your scope
The order to do it in
Procurement
Nothing in scope blocks these — they can start together.
Accounts Payable
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 General Ledger without including it. Fine if it is already standing and staying as it is — a gap in the plan otherwise.
Concerns raised
Australian obligations in scope
Everything in scope — 7 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 — 6 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.