Scope
1 area implies 3 topics across 2 modules
You did not pick these
Data & Analytics
Your streams cross into this module, so the work happens there too. That is the part most scoping exercises miss.
The end-to-end
Record-to-Report
Financial Accounting → Data & Analytics
Data in and out
What actually crosses the boundary, which way, how often, and what it costs when it stops.
Crosses your scope boundary
Payroll journal←Payroll
Per pay run
General Ledger · without it: Labour cost is missing from the period and the month cannot close.
Sub-ledger postings←Accounts Payable
Continuous
General Ledger · without it: Payables detail and the control account disagree.
Revenue postings←Accounts Receivable
Continuous
General Ledger · without it: Revenue is recognised late or not at all.
Depreciation journal←Asset Management
Monthly
General Ledger · without it: Asset carrying values drift from the ledger.
Trial balance extract→Business Intelligence
Daily
General Ledger · without it: Reporting runs on stale numbers.
Payroll journal→General Ledger
Per pay run
Payroll · without it: Labour cost is missing from the period.
Depreciation journal→General Ledger
Monthly
Asset Management · without it: Carrying values drift from the ledger.
Stock movements→General Ledger
Continuous
Inventory Management · without it: Inventory value in the ledger stops matching the warehouse.
Opening balances and master data→General Ledger
At cutover
Data Migration · without it: The new ledger opens on numbers nobody can reconcile to the old one.
Reporting extracts←General Ledger
Daily
Business Intelligence · without it: Management reporting diverges from the ledger.
Interfaces outside the ERP
Statutory and management reporting→Regulator and board reporting
Monthly and annually
General Ledger · without it: Statutory deadlines are missed.
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.
Financial Accounting→Data & Analytics
Record-to-Report
One side of this is outside your scope
The order to do it in
General Ledger
Nothing in scope blocks these — they can start together.
Cash & Treasury
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 Accounts Payable, Accounts Receivable 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 — 3 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 — 2 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.