FUTURE STATE DESIGN
You Know What a Clean Ledger Looks Like. That Knowledge Designs the To-Be.
After audit season you have looked at ledgers in every condition.
The clean one: every transaction coded correctly, every balance reconciled, every accrual supported, every intercompany agreed.
The messy one: miscoded expenditure, unsupported accruals, unreconciled balances sitting open since last quarter, intercompany disputes that have been open since the previous Finance Director left.
You know — instinctively — what a clean ledger looks like.
That instinct is your To-Be design capability.
When an ERP Business Analyst runs a To-Be design workshop, they are asking:
"What does the perfect version of this process look like?"
You already know.
Because you have seen the clean version and the messy version.
You know that the clean version has automated bank feeds, not manual import. Three-way matching, not manual invoice approval. System-generated accruals based on goods receipt, not manual estimation. Auto-cleared intercompany, not monthly dispute calls.
The To-Be is not an aspiration.
It is the clean ledger. Designed into the system. Enforced by configuration. Not dependent on the right person being in post.
Discussion question: What is the single biggest difference between your cleanest period close and your messiest? That difference is your To-Be design priority.
Fall4U FCA FCCA — Future Defined Academy
0
0 comments
FUTURE STATE DESIGN
powered by
skool.com/future-defined-academy-2168
FDA teaches accounting students and finance professionals how to translate their finance knowledge into ERP, systems and transformation careers.
Suggested communities
Powered by