Scope
1 area implies 2 topics across 1 module
The end-to-end
Cash & Treasury
Financial Accounting
Data in and out
What actually crosses the boundary, which way, how often, and what it costs when it stops.
Crosses your scope boundary
Cash position and forecast→Business Intelligence
Daily
Cash Management · without it: Treasury decisions are made on yesterday's balance.
Matched and unmatched items→General Ledger
Daily
Bank Reconciliation · without it: The ledger and the bank never agree.
Interfaces outside the ERP
Bank statements←Banking platform
Daily
Cash Management · without it: The cash position is a guess and reconciliation stalls.
The order to do it in
Cash & Treasury
Nothing in scope blocks these — they can start together.
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, 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 — 2 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 — 1 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.