R2R 606 · PRODUCTION SUPPORT
How do you support Record to Report when something goes wrong?
Restore financial processing while identifying where the accounting chain broke and why. Work backward from a balance, report, reconciliation, or close symptom to the journal and originating business transaction—not merely the final financial statement.
ACCOUNTING CHAIN
Follow the financial consequence back to the source
R2R often exposes problems created by another ERP process. A reporting difference can originate in an O2C, P2P, payroll, asset, banking, or integration posting; establish where the accounting result was last known to be correct.
- 01Business transactionOrigin
- 02Accounting documentEntry
- 03G/L and ledgerBalance
- 04ReconciliationProof
- 05CloseCertification
- 06Financial reportAction
SUPPORT OPERATING LOOP
Protect evidence before changing the accounting result
Establish financial impact
Identify the company code, ledger, account, period, document, source transaction, scope, close impact, and potential financial-statement impact. Preserve a reproducible example.
Find the failed transition
Trace business transaction → journal → G/L → ledger → reconciliation → close → report. Locate the last correct accounting result and the observed difference.
Choose the right cause family
Separate transaction or journal data, master data, configuration, custom logic, integration, authorization, jobs, workflow, period control, and close sequencing.
Correct with audit integrity
Correct an individual transaction or reverse and repost when required. Correct master data, configuration, code, or integration only at the layer that consistently caused the result.
Retest transaction and reporting
Validate debit equals credit, account, amount, currency, tax, assignments, reconciliation, period, ledger, P&L, balance-sheet, and cash-flow effects where relevant.
Make recurrence visible
Capture symptom, scope, root cause, resolution, validation, and prevention. Turn recurring issues into validation, monitoring, close controls, approvals, master-data governance, or regression tests.
FIRST R2R DECISION
Separate source accounting from reporting interpretation
The journal can be correct while the report is wrong; a balance can be wrong because of a source transaction. Diagnose the evidence layer that first diverged.
Move from a balance to period movements, accounting documents, and source transactions. A balance is a result, not an isolated object.
When AR, AP, or Asset Accounting differs from G/L, find the posting that broke the reconciliation relationship.
Closed periods, approval, blocked accounts, validations, imbalance rejection, and incomplete close activities can be intended controls.
R2R DIAGNOSTIC PLAYBOOKS
Follow the path that matches the financial symptom
Each case identifies the accounting relationship and determination evidence to understand before correction.
01 · Accounting document cannot be posted
Trace: Business transaction → company code → posting period → document type → G/L account → posting rules → tax and currency → account assignment. Confirm that the document satisfies the required accounting controls.
02 · Wrong G/L account
Trace: Source transaction → transaction or account key → account determination → valuation or business context → G/L → accounting document. Establish whether the source or the determination rule was wrong.
03 · Subledger does not match G/L
Trace: Customer, supplier, or asset transaction → subledger posting → reconciliation account → G/L balance. Check missing postings, manual entries, migration, interfaces, timing, and periods.
04 · Trial balance does not look right
Trace: Journal → G/L account → debit and credit → period → ledger → trial balance. Investigate duplicate or missing postings, wrong periods or ledgers, reversals, and foreign-currency effects.
05 · Period close cannot proceed
Trace: Open transactions → reconciliations → accruals → allocations → depreciation → valuation → close activities → period lock. Look for unfinished upstream processing and failed jobs.
06 · Foreign-currency result is wrong
Trace: Transaction currency → exchange rate → local or group currency → valuation → gain/loss account → accounting document. Separate original conversion from period-end valuation.
07 · Financial report is wrong
Trace: Accounting document → G/L balance → ledger → reporting hierarchy or mapping → P&L, balance sheet, or cash flow. Decide whether the accounting data or reporting interpretation is wrong.
R2R SUPPORT MOMENT
The balance sheet does not reconcile
Do not start with reporting configuration. Identify the account, company code, ledger, period, source transactions, and when the difference first appeared. Determine whether a journal is wrong or the report is reading correct journals incorrectly.
- Record the known-good step and observed accounting difference.
- Preserve journals, balances, mapping, filters, statuses, and expected result before changing anything.
- Avoid direct balance adjustments that merely make the report reconcile.
Use 101 for process language, 202 for accounting capabilities, 303 for the operating close, 404 for design and configuration, and 505 for implementation context.