SAP Record to Report Process:
R2R Steps, T-Codes and Financial Close

Record to Report (R2R) is the end-to-end financial accounting process in SAP FICO covering everything from recording a financial transaction to producing a financial statement. It starts when a business event occurs and ends when that event appears correctly in the balance sheet and P&L. In SAP S/4HANA, R2R runs on the Universal Journal (ACDOCA) which stores every FI and CO posting in one table, eliminating the FI/CO reconciliation steps that SAP ECC required at every period-end.

R2R stands for Record to Report. It is one of three core financial processes in enterprise organisations alongside Procure to Pay (P2P) and Order to Cash (O2C). R2R covers the general ledger accounting cycle: recording transactions, reconciling accounts, closing periods, and producing financial statements for management reporting and external reporting to auditors and regulators.

The nine steps are: (1) Record all source transactions — FB50, FB60, MIRO; (2) Process accruals and deferrals — FBS1, FBD1/F.14; (3) Bank reconciliation — FEBAN, FF67; (4) Asset depreciation — AFAB; (5) Foreign currency revaluation — FAGL_FC_VAL in S/4HANA or F.05 in ECC; (6) CO allocations — KSU5 assessment and KSV5 distribution; (7) Period close — OB52 and MMPV; (8) Financial statements — F.01 or Fiori; (9) Year-end balance carryforward — FAGLGVTR (once per year only).

Key R2R T-codes: FB50 (GL journal entry), FB60 (vendor invoice), MIRO (logistics invoice), FBS1 (accrual document), FBD1/F.14 (recurring entries), FEBAN (bank reconciliation), AFAB (asset depreciation), FAGL_FC_VAL (FX revaluation S/4HANA), KSU5/KSV5 (CO allocations), OB52 (FI period control), MMPV (MM period close), FAGLGVTR (balance carryforward), F.01 (financial statements), FS10N (GL balances), FBL3N (GL line items), MB5S (GR/IR analysis).

FAGLGVTR is the SAP transaction for year-end balance carryforward in the New General Ledger. It closes all income statement accounts — revenue, cost of sales, overheads — to the retained earnings account, and carries balance sheet account balances forward to the new fiscal year. It runs once per year only, after all period-12 postings and audit adjustments are finalised. In S/4HANA, profit centre balances also carry forward automatically. Always simulate first — this step is very difficult to reverse once executed in update mode.

The Universal Journal is the single database table in SAP S/4HANA (table name: ACDOCA) that stores every accounting posting including FI, CO, ML, AA, and PCA in one unified entry. It replaces the separate tables — BSEG for FI, COEP for CO — that existed in SAP ECC. Because every posting goes to one table, FI and CO are always in sync, FI/CO reconciliation is eliminated, and financial reporting is real-time. This is the single most important architectural change in S/4HANA for the R2R process.

Three key differences: (1) Universal Journal — all postings go to ACDOCA eliminating FI/CO reconciliation that typically took 1–2 days in ECC; (2) New Asset Accounting — depreciation posts directly to ACDOCA with no separate GL reconciliation step; (3) Real-time reporting — Fiori financial reporting apps run from live ACDOCA data rather than from aggregated totals tables that required batch updates. The nine-step sequence is identical but the effort in S/4HANA is significantly reduced.

Foreign currency revaluation adjusts all open items and GL account balances denominated in foreign currency to the period-end exchange rate. In S/4HANA use FAGL_FC_VAL; in ECC use F.05. The adjustment posts an unrealised exchange gain or loss. At the start of the next period, this posting automatically reverses — because the gain or loss is only realised when the item is actually paid or cleared. Skipping FX revaluation at period-end produces a materially misstated balance sheet and is an audit finding.

Period close happens every month: post accruals, run depreciation and FX revaluation, lock the period with OB52 and MMPV, and run financial statements. Year-end close includes all monthly steps plus: final audit adjustments, GR/IR reconciliation with MB5S, and the balance carryforward with FAGLGVTR. FAGLGVTR is the only step unique to year-end — it resets income statement account balances to zero and carries balance sheet balances into the new fiscal year.

Key R2R tables: ACDOCA (Universal Journal — primary table in S/4HANA), BKPF (accounting document header), BSEG (document segment in ECC, compatibility view in S/4HANA), FAGLFLEXT (GL totals table in ECC New G/L), SKA1 (GL account chart of accounts), SKB1 (GL account company code data), ANEK/ANEP (asset accounting documents), T001 (company codes).

GR55 is the SAP transaction for executing Report Writer report groups. It runs financial statement reports — balance sheet, P&L, and custom management reports — defined in Report Painter or Report Writer. The report group references a financial statement version (FSV) and chart of accounts to determine which GL accounts appear in each report line. In S/4HANA, many organisations use Fiori-based financial reporting apps instead, but GR55 remains available and widely used for custom reporting.

Accruals are postings for costs incurred during the current period but not yet invoiced — for example, October electricity that will be invoiced in November. You post the accrual in October so it appears in October's P&L. Deferrals are for amounts already paid or received that relate to future periods — for example, an annual insurance premium paid in January. In SAP, use FBS1 to create an accrual or deferral document with a specified reversal date. The document automatically reverses at the start of the next period, so no manual reversal is needed.

Document splitting distributes accounting line items across reporting dimensions — typically profit centre or segment — so that a balance sheet can be produced by segment. When active, every posting must balance to zero for each splitting dimension, not just overall. If a line item has no profit centre assigned — for example a vendor line where profit centre derivation fails — the posting is rejected. This is one of the most common causes of period-end posting failures in organisations where document splitting is active. The fix is correct profit centre derivation configuration and a zero-balance clearing account.

OB52 is the transaction for maintaining posting period variants — controlling which fiscal periods are open and closed for FI posting. At period-end, use OB52 to close the month just ended (preventing backdated postings) and open the next period simultaneously. Typically two periods are kept open at any time. Access to OB52 in production must be tightly controlled — unrestricted access allows any user to reopen closed periods and post backwards, which undermines the integrity of closed financial statements.

SAP FICO consultants design and implement R2R at two levels. In implementation projects, they set up the chart of accounts, financial statement versions, document types, posting period variants, and closing cockpit tasks. In production support roles, they handle period-end issues: fixing failed accruals, clearing GR/IR, troubleshooting posting errors, running depreciation, and generating period-end reports. R2R end-to-end knowledge is tested in every FICO interview and is a daily requirement in both implementation and support roles.

The Financial Closing Cockpit (transaction FCCX or the Fiori Close Cockpit app) organises and monitors all period-end close tasks in a structured, dependency-aware checklist. Each task — depreciation run, FX revaluation, CO allocations, balance carryforward — is defined with a responsible user, a deadline, and automated execution capability. The cockpit shows which tasks are complete, in progress, or failed. In S/4HANA, it integrates with ACDOCA for automatic task completion tracking and is the standard close management tool in large SAP organisations.

AFAB posts periodic asset depreciation. It calculates the depreciation amount for all fixed assets in a company code and depreciation area based on the depreciation key, useful life, and acquisition value defined in the asset master (AS03). It posts a debit to the depreciation expense account and a credit to accumulated depreciation. Always run AFAB in test mode first to verify amounts against prior periods adjusted for acquisitions and disposals. In S/4HANA with New Asset Accounting, AFAB posts directly to ACDOCA — no separate GL reconciliation step is needed.

Both are CO period-end allocation methods that move costs between cost centres. Distribution (KSV5) moves costs keeping the original primary cost element — receivers see exactly which cost type they received (electricity, rent, etc.). Assessment (KSU5) moves costs using a secondary cost element — the original cost breakdown is collapsed into a single assessment element on the receiving side. Use distribution when receiver cost centres need to see the source cost detail. Use assessment for overhead allocations where that level of detail on the receiver side is not required or appropriate.

Every step in R2R directly determines reporting accuracy. If accruals are missed, costs are understated in that period. If FX revaluation is skipped, balance sheet values are misstated. If depreciation is not posted, both asset net book values and period expenses are incorrect. If CO allocations do not run, overhead remains on service cost centres rather than on the business cost objects where it belongs. The balance sheet and P&L produced at the end of R2R are exactly as reliable as the quality of each preceding step — which is why the close sequence is a control structure, not an optional checklist.

Yes — VoiSAP's SAP FICO training covers the entire R2R process end-to-end with hands-on practice on a live SAP S/4HANA system. You post journal entries, run depreciation with AFAB, execute FX revaluation with FAGL_FC_VAL, run CO allocations with KSU5 and KSV5, carry forward balances with FAGLGVTR, and generate financial statements yourself — not watching someone else do it. Gourav has 18 years of enterprise SAP FICO delivery experience across UK, India, and Canada, and has trained students who went on to FICO roles at major Canadian and US employers. Book a free demo to discuss your background and how the training is structured.