Enterprise system
Finance and accounting
Connect ledgers, subledgers, consolidation, intercompany activity, controls and operational evidence.
Page purpose
Define the responsibility and boundary of Finance and accounting before choosing extension, integration or replacement.
Finance and accounting systems turn operational events into subledger entries, journals, ledgers, consolidation, tax inputs, and management reporting. Their boundary must identify which system owns each source transaction, accounting event, posted journal, balance, exchange rate, chart value, and consolidation adjustment.
Accounting continuity is the governing constraint. The decision is sequenced by ledger and subledger, using posting lineage, period-state control, close dependencies, specialist-calculation fit, and historical-access needs to choose a safe transition boundary and the evidence required before that boundary moves.
Failure modes
How system failures surface in real work.
- Close depends on offline reconciliations and journals whose source evidence and approval are difficult to trace.
- Entity, account, cost-center, and intercompany definitions diverge across ledgers and reporting stores.
- Operational systems send incomplete or aggregated postings that cannot be reconciled back to source transactions.
System boundary
What the system owns and what remains outside it.
- Which ledger and subledger is authoritative for each accounting event and balance?
- For each specialist calculation, does control improve by keeping a governed posting interface or by moving the rule beside the ledger?
- What transaction history, open detail, and supporting evidence must migrate versus remain archived?
Target state
Clearer responsibilities and a target operating state.
- Traceable lineage from operational event through subledger and general ledger to reported balance.
- Governed financial dimensions and intercompany rules across entities and systems.
- A controlled close and consolidation process with visible exceptions and ownership.
System design
Models and contracts specific to the system boundary.
- Ledger, subledger, accounting-event, and financial-data authority map.
- Close, consolidation, intercompany, journal, and reconciliation process design.
- Posting contracts with control totals, error handling, replay, and period validation.
- Ledger-by-ledger transition and archive plan for open items, balances, comparative periods, specialist calculations, and supporting evidence.
Transition
Changing the system while operations continue.
- Trace representative source events to accounting rules, postings, adjustments, and statements.
- Profile charts, dimensions, open items, balances, and historical journals before target mapping.
- Separate core ledger integrity from specialist calculations and reporting extensions.
- Rehearse period close, opening balances, open-item migration, parallel reporting, and rollback.
Record and operating integrity
Protecting record integrity and continuity during transition.
- Loading opening balances that reconcile in total but lose entity, currency, account, or source detail.
- Allowing coexistence systems to post into different period states or use inconsistent exchange rates.
- Changing accounting rules and technology simultaneously without an attributable comparison baseline.
System measures
Measures that reveal improvement in real work.
- Control-total and balance reconciliation by source, ledger, entity, account, currency, and period.
- Close duration, aged reconciliation items, manual journal volume, and late adjustment count.
- Posting failure, duplicate, replay, and exception-resolution rates across financial interfaces.
Decision questions
System decisions a product alone cannot answer.
Can finance migration rely on opening balances alone?
Only if operational, reporting, audit, and service needs genuinely permit it. Open items, source lineage, comparative periods, and accessible historical evidence often require more.
Should reporting be modernized with the ledger?
Their boundaries should be designed together, but reporting can transition separately when ledger authority, definitions, lineage, and reconciliation remain explicit.