R2R 404 · AT THE KEYBOARD
R2R Configuration Workbench
Configure and prove one controlled company-code close from source-integrated journal entries through reconciliation, period-end adjustment, financial statements, and posting-period protection.
IMPLEMENTATION CONTEXT
R2R Implementation Context
This guide starts after the accounting policy and Fit-to-Standard direction are understood. It focuses on the configuration, execution and reconciliation spine required to operate and close one company code.
Group Reporting, Treasury, Advanced Financial Closing, complex localization and enterprise-wide consolidation design are outside the minimum scope of this guide.
- Business / Accounting Policy
- Fit-to-Standard
- Confirm Accounting Design
- Configure
- Close
- Reconcile
PREREQUISITE AND OUTCOME
Configure only after you can explain the accounting result
Enter with: the 101/202 accounting concepts and the 303 close dependency map. Leave able to: locate and reason about the minimum R2R configuration spine, its dependencies, transport boundary, and proof obligations. The workbench is a guided reference—not authorization to change a customer system or evidence of independent FI configuration competence.
WORKBENCH ENVELOPE
One minimum company-code close
Optional platforms, country localization, and specialist accounting stay outside the spine until the essential accounting cycle posts, reconciles, reports, and locks.
Essentials included
- One company code, operational chart of accounts, fiscal year, posting-period variant, leading ledger, company-code currency, and group currency
- G/L master controls, journal document controls, open-item management, validation, substitution, and period access
- One source-integrated posting, one bank/open-item example, one asset/depreciation example, one accrual, and one foreign-currency valuation
- Financial statement hierarchy, balance sheet and income statement proof, close evidence, transport boundaries, and current S/4HANA persistence
Extensions - not included yet
- Country-specific statutory reporting, tax procedure design, withholding tax, e-invoicing, and localization beyond identifying their boundary
- Full Group Reporting implementation, consolidation of investments, planning, disclosure management, and external consolidation platforms
- Treasury, financial instruments, revenue accounting, lease accounting, Central Finance, and industry solutions
- SAP Advanced Financial Closing, Multi-Bank Connectivity, and SAP Cash Application implementation because they are optional or separately licensed extensions
- Custom code, interfaces, security-role build, production migration, and irreversible production period changes
THE R2R CLOSE SPINE
Foundation → Post → Reconcile → Adjust → Report → Lock
Use this as the mental model for one controlled company-code close; the eight technical sections below provide the configuration depth.
Foundation
Where and under which accounting rules do we keep the books?
Post
Can valid journals and source transactions post correctly?
Reconcile
Do subledgers, open items, banks, and assets agree with the G/L?
Adjust
What period-end entries are needed before reporting?
Report
Do the financial statements show the intended result?
Lock
Can the period now be closed safely?
CONFIGURATION WORKBENCH
Establish legal and fiscal scope
The company code has a coherent country, currency, chart of accounts, fiscal year, posting-period variant, and controlling relationship.
Plain-language meaning: Where and when do we account?
SPRO / IMG path
Enterprise Structure -> Definition -> Financial Accounting -> Define, copy, delete, check Company Code
Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fiscal Year and Posting Periods
Financial Accounting -> General Ledger Accounting -> Master Data -> G/L Accounts -> Preparations -> Edit Chart of Accounts List
Controlling -> General Controlling -> Organization -> Maintain Controlling Area
Transactions and apps
OX02 / OBY6Define company code / maintain global company-code parametersOB13Maintain chart of accountsOB29 / OB37Maintain and assign fiscal year variantOBBO / OBBP / OB52Define posting-period variant / assign it to the company code / open or close posting periodsOKKPMaintain controlling areaT001T004T009T009BT001BTKA01Maintain in this order
- Confirm the legal entity, country, local currency, language, chart of accounts, fiscal year, and tax/localization boundary before copying company-code settings.
- Assign a fiscal-year variant whose periods and year-shift logic match statutory and management requirements; do not assume calendar year.
- Assign the posting-period variant and design the normal period, adjustment-period, and authorization-group approach before opening intervals.
- Assign the company code to the intended controlling area only after chart-of-accounts, fiscal-year, and currency compatibility is proven.
The journal accepts the intended company, fiscal period, currency, accounts, and controlling assignments and rejects a deliberately closed or unauthorized period.
If it fails, check here first
- Period rejected: inspect posting date, fiscal-year period derivation, T001B interval, account type, authorization group, and user authorization.
- Controlling object rejected: inspect company-code assignment, chart of accounts, fiscal year, controlling-area currency, and validity dates.
- Unexpected local currency or tax behavior: inspect company-code country and currency before changing posting logic.
CONFIGURATION WORKBENCH
Design ledgers, principles, and currencies
Every journal reaches the intended accounting principle and carries the currencies required for entity and group reporting.
Plain-language meaning: Which books and currencies do we maintain? A ledger is a set of books; an accounting principle tells SAP which rules apply to that view.
SPRO / IMG path
Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Ledger -> Define Settings for Ledgers and Currency Types
Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Parallel Accounting -> Assign Accounting Principle to Ledger Groups
Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Ledger -> Define Ledger Group
SAP NetWeaver -> General Settings -> Currencies -> Check Exchange Rate Types / Define Translation Ratios / Enter Exchange Rates
Transactions and apps
FINSC_LEDGERMaintain ledger and company-code settings including currency typesOB22Display or maintain company-code currency settings where applicable to the target releaseOB07 / OB08Maintain exchange-rate types / exchange ratesFB50LPost a ledger-group-specific G/L document where supportedFINSC_LEDGERFINSC_LD_CMPT881TCURRTCURFACDOCAMaintain in this order
- Document the purpose of the leading ledger, each non-leading or extension ledger, every ledger group, and the accounting principle assigned to it.
- Use separate ledgers for parallel accounting when that design fits the policy; treat account-based differences as a deliberate exception, not the inherited default.
- Configure company-code and group currency plus only the additional currency types that have a proven reporting or valuation use.
- Set exchange-rate types, source currencies, translation rules, and ownership, then test common and ledger-specific postings with non-trivial rates.
The common entry appears in all intended ledgers, the adjustment only in its ledger group, and every configured currency is populated using the documented rule.
If it fails, check here first
- Ledger-specific posting reaches the wrong books: inspect ledger group, accounting-principle assignment, document input, and extension-ledger relationship.
- Currency is blank or inconsistent: inspect FINSC_LEDGER company-code settings, currency source, exchange-rate type, rate validity, and conversion date.
- FI and controlling views disagree: verify whether the process is integrated in the Universal Journal and whether a compatibility or costing-based view is being compared.
Release-sensitive: SAP S/4HANA supports up to ten currency fields in the Universal Journal: two preconfigured fields and up to eight freely defined currencies. Confirm the exact supported currency roles and conversion restrictions for the installed release before design freeze.
CONFIGURATION WORKBENCH
Control accounts and journal entries
G/L accounts and journal document controls permit valid entries, prevent prohibited use, retain source evidence, and support controlled reversal.
Plain-language meaning: What makes a valid accounting document?
SPRO / IMG path
Financial Accounting -> General Ledger Accounting -> Master Data -> G/L Accounts -> Preparations
Financial Accounting -> Financial Accounting Global Settings -> Document -> Document Types / Document Number Ranges / Posting Keys / Field Status
Financial Accounting -> Financial Accounting Global Settings -> Tools -> Validation and Substitution
Financial Accounting -> General Ledger Accounting -> Business Transactions -> Closing -> Opening and Closing Posting Periods
Transactions and apps
Migration CockpitMigrate governed G/L accounts and validate chart/company-code extensionsOBA7 / FBN1Maintain document types / accounting document number rangesOB41 / OBC4Maintain posting keys / field-status variants and groupsGGB0Define validations; assign and activate them separately through the approved pathGGB1Define substitutions; assign and activate them separately through the approved pathFB50Post and inspect controlled journal entriesSKA1SKB1T003TBSLT004FBKPFACDOCAMaintain in this order
- Design account groups and define G/L master-data requirements: account type, financial-statement treatment, open-item behavior, tax category, field status, currency, and posting restrictions.
- Define document types and number ranges by business purpose; decide permitted account types, negative postings, reversal type, and whether the source should post directly.
- Align posting-key, account, and field-status requirements so mandatory dimensions are collected without conflicting suppressions.
- For validation: define the GGB0 rule, assign or activate it through the approved call-up point and company scope, then run positive and negative posting tests.
- For substitution: define the GGB1 rule, assign or activate it separately, then post a test document and verify the substituted value without weakening the original posting control.
The valid journal balances and contains required dimensions and evidence. The invalid journal is blocked for the intended reason, and reversal retains a linked audit trail.
If it fails, check here first
- Field is unexpectedly required or hidden: compare posting-key, account, and field-status settings plus screen or app behavior.
- Validation does not trigger: inspect call-up point, prerequisite, activation level, company assignment, Boolean logic, and source posting route.
- Substituted value is missing or wrong: inspect GGB1 rule order, prerequisite, substituted field eligibility, activation, and whether the posting route calls the substitution.
- Document posts to an unintended account type or ledger: inspect G/L master, document type, account determination, ledger group, and source application.
CONFIGURATION WORKBENCH
Connect source processes and subledgers
Customer, supplier, asset, material, revenue, payroll, and controlling events produce explainable G/L accounts and dimensions without direct posting to reconciliation accounts.
Plain-language meaning: Where should a business transaction post in the G/L?
SPRO / IMG path
Financial Accounting -> Accounts Receivable and Accounts Payable -> Customer/Supplier Accounts -> Master Data -> Preparations
Materials Management -> Valuation and Account Assignment -> Account Determination -> Configure Automatic Postings
Sales and Distribution -> Basic Functions -> Account Assignment/Costing -> Revenue Account Determination
Financial Accounting -> Asset Accounting -> Integration with General Ledger Accounting -> Assign G/L Accounts
Transactions and apps
BPMaintain customer and supplier company-code roles and reconciliation accountsOBYCMaintain materials-management automatic postingsVKOAMaintain sales revenue account determinationAO90Assign Asset Accounting G/L accountsFB03 / Manage Journal EntriesInspect the resulting accounting document and source referenceBUT000KNB1LFB1T030VKOAT095ACDOCAMaintain in this order
- Assign customer, supplier, and asset reconciliation accounts through master-data and asset-account-determination rules; prevent unsupported direct posting.
- Read integration as Business Source -> Account Determination -> Operational / Subledger Document -> Universal Journal -> Reconcile.
- Test MM account determination with the actual chart, valuation grouping, valuation class, transaction key, account modifier, and movement that the business will use.
- Test SD account determination with the actual chart, sales organization, account-assignment groups, account key, and pricing conditions.
- Map payroll, settlement, tax, bank, and other integration points only through the responsible process design, then reconcile each source quantity or population to its journal. Use dedicated O2C and P2P configuration guides for source setup detail; R2R owns the accounting result and reconciliation.
The source document and journal are linked; the account determination can be reproduced; quantities, amounts, currencies, reconciliation account, and controlling dimensions agree.
If it fails, check here first
- Account cannot be determined: capture the actual rule inputs and access sequence before adding a broader fallback.
- Subledger does not reconcile: inspect posting status, reversal timing, company/ledger/currency scope, reconciliation account assignment, and direct-posting violations.
- Profit center or segment is missing: inspect source master data, derivation, document splitting where used, substitution, and balancing rules.
CONFIGURATION WORKBENCH
Configure open items, payments, and bank statements
Due items can be selected and cleared through a governed payment path, while bank statements confirm settlement and leave unmatched items visible.
Plain-language meaning: Prove the R2R cash path: open item → payment → bank clearing → bank statement → reconciled cash.
SPRO / IMG path
Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments
Financial Accounting -> Bank Accounting -> Bank Accounts -> Define House Banks
Financial Accounting -> Bank Accounting -> Business Transactions -> Payment Transactions -> Electronic Bank Statement
Financial Accounting -> General Ledger Accounting -> G/L Accounts -> Master Data -> Preparations -> Open Item Management
Transactions and apps
FBZPConfigure automatic payment program parametersF110Create and review payment proposals and runsManage Bank AccountsMaintain governed bank-account master data where activatedOT83Maintain electronic bank statement transaction types and posting rulesFEBANPostprocess/reprocess bank-statement items and resolve exceptionsT042*BNKAT012T012KFEBKOFEBEPREGUHREGUPACDOCAMaintain in this order
- Keep the accounting completion path visible: Open Supplier / Customer Item -> Payment -> Bank Clearing -> Bank Statement -> Cash Reconciliation.
- Design open-item accounts, payment methods, company-code and country parameters, house banks, bank selection, value dates, payment media, and maker-checker ownership together.
- Maintain bank main and interim/clearing accounts with explicit purpose, currency, account ownership, and statement-processing relationship.
- Configure statement formats, transaction types, external transaction codes, posting rules, interpretation or processing rules, and duplicate protection.
- Test proposal exclusions, payment posting, bank confirmation, automatic clearing, unmatched fees, rejected payments, reversal, and reprocessing evidence.
Only eligible items are selected, the payment clears the subledger item, the statement clears the intended bank interim account, and the unmatched item retains a reason and owner.
If it fails, check here first
- Item is excluded from payment: inspect due date, block, method, currency, minimum amount, bank data, proposal log, and competing run.
- Statement does not post or clear: inspect format, transaction type, external code mapping, sign, posting rule, account symbol, reference, and open-item availability.
- Bank balance differs: reconcile statement completeness, opening/closing balance, value dates, main and interim accounts, rejected payments, fees, and manual postings.
Release-sensitive: Multi-Bank Connectivity and SAP Cash Application are separate capabilities with licensing and integration implications. Keep their setup outside the essential workbench until approved.
CONFIGURATION WORKBENCH
Configure Asset Accounting and depreciation
An asset class and depreciation-area design create explainable acquisition and periodic depreciation postings in the Universal Journal.
Plain-language meaning: Prove asset acquisition → asset value → depreciation → G/L reconciliation, without expanding into the full asset lifecycle.
SPRO / IMG path
Financial Accounting -> Asset Accounting -> Organizational Structures -> Copy Reference Chart of Depreciation / Assign Chart of Depreciation to Company Code
Financial Accounting -> Asset Accounting -> Valuation -> Depreciation Areas / Depreciation Keys
Financial Accounting -> Asset Accounting -> Master Data -> Asset Classes
Financial Accounting -> Asset Accounting -> Integration with General Ledger Accounting -> Assign G/L Accounts
Transactions and apps
OADB / OAYZMaintain depreciation areas / asset-class depreciation-area defaultsAFAMAMaintain depreciation keysAO90Maintain Asset Accounting account determinationAS01 / AS03Create or display the asset masterAFABExecute depreciation posting runT093T093BT090NAT095ANLAANLBANLCACDOCAMaintain in this order
- Assign a country-appropriate chart of depreciation and document the purpose, ledger group, currency, and posting behavior of each active depreciation area.
- Define asset classes, number ranges, screen layout, account determination, default useful life, and depreciation keys by asset purpose.
- Maintain account assignments for acquisition, accumulated depreciation, depreciation expense, retirement, gain or loss, and clearing using project-owned accounts.
- Create one asset, post acquisition, inspect planned values, execute depreciation in test mode and update mode, and reconcile asset and G/L views.
Acquisition and depreciation update the intended asset, depreciation area, ledger, accounts, cost assignment, periods, and ACDOCA lines and reconcile to the asset values.
If it fails, check here first
- Depreciation is zero or starts incorrectly: inspect capitalization and asset value dates, depreciation key, useful life, period control, and area activation.
- Posting account missing: inspect chart, account determination, asset class, depreciation area, transaction type, and G/L extension.
- Asset and G/L differ: inspect posting status, ledger/area mapping, prior-year correction, depreciation rerun requirement, migration values, and reconciliation scope.
CONFIGURATION WORKBENCH
Configure accruals, valuation, allocation, and clearing
Period-end jobs calculate, review, post, reverse or utilize, and reconcile adjustments using explicit populations and accounting policies.
Plain-language meaning: Accrual puts income or expense into the correct period. Foreign-currency valuation revalues balances at the period-end rate. Allocation distributes costs to the objects that should carry them. Clearing matches items that offset each other.
SPRO / IMG path
Financial Accounting -> General Ledger Accounting -> Business Transactions -> Accruals Management
Financial Accounting -> General Ledger Accounting / Accounts Receivable and Accounts Payable -> Business Transactions -> Closing -> Valuating -> Foreign Currency Valuation
Financial Accounting -> General Ledger Accounting -> Business Transactions -> Open Item Clearing
Transactions and apps
ACEIMGConfigure Accruals ManagementFAGL_FCVExecute foreign-currency valuation for the target release pathF.13Execute automatic clearing for eligible open itemsACDOCABKPFTCURRT030HACE*FAGL*T811*Keep these technically different close processes in the same high-level phase, but prove each with its own population, run, posting, and reversal or clearing evidence.
ACCRUE
Recognize expense or income in the correct accounting period.
- Manual accruals
- Recurring accrual logic
- Accrual engine where applicable
VALUE
Revalue foreign-currency balances at period-end.
- Open foreign-currency balance
- Valuation rule
- Exchange rate
- Valuation posting
- Reversal / subsequent period treatment
ALLOCATE
Move or distribute costs based on defined rules and drivers.
- Universal Allocation where selected
- Classic allocation where retained
CLEAR
Match and clear offsetting open items.
- Customer/vendor clearing
- G/L open-item clearing
- GR/IR account maintenance where relevant
Maintain in this order
- Define accrual item types, methods, calculation rules, account determination, ledger-group behavior, review/approval thresholds, and reversal or utilization behavior.
- Define foreign-currency valuation methods, areas, exchange-rate types, document types, adjustment accounts, and unrealized gain/loss accounts by policy. Prove Open Foreign Currency Balance -> Valuation Rule -> Exchange Rate -> Valuation Posting -> Reversal / Subsequent Period Treatment.
- Configure allocation contexts, cycles, segments, senders, receivers, tracing factors, ledger or version scope, and reversal behavior; use simulation before update. Choose Universal Allocation or Classic Allocation according to the installed release and approved design; do not imply both must be configured.
- Define clearing criteria and account eligibility, then test items that should clear and near-matches that must remain open. Include customer/vendor clearing, G/L open-item clearing, and GR/IR account maintenance only where relevant.
Each run uses the intended population and ledger scope, produces explainable accounts and dimensions, retains logs and approvals, and supports the designed reset, reversal, utilization, or reconciliation.
If it fails, check here first
- Population is incomplete: inspect company, ledger, account, open-item status, key date, currency, source selection, and exclusion logs.
- Unexpected amount: inspect method, rate, date, planned/actual source, tracing factor, manual adjustment, prior run, and parallel valuation.
- Duplicate or residual posting: inspect run identity, update status, cancellation, reversal date, clearing status, delta logic, and rerun parameters.
Release-sensitive: Universal Allocation received new private-edition apps in SAP S/4HANA 2025 FPS01. Confirm app availability, migration notes, and the correct classic or Universal Allocation route in the installed system.
CONFIGURATION WORKBENCH
Build statements and protect the close
Approved ledger balances map to governed financial-statement hierarchies, drill to source journals, and remain protected by controlled period access.
Plain-language meaning: Where document splitting is used, it can support balanced reporting by dimensions such as profit center or segment. Balance-sheet balances carry forward; the annual P&L result closes into retained earnings.
SPRO / IMG path
Manage Global Hierarchies (Fiori App F2918) -> Create / Maintain FSV -> Activate -> Use in Financial Reporting
OB58 / FSE2 -> Maintain Classic Financial Statement Version where the installed landscape still uses classic FSVs
Financial Accounting -> Financial Accounting Global Settings -> Ledgers -> Fiscal Year and Posting Periods -> Open and Close Posting Periods
For approved extensions only: configure Intercompany Matching and Reconciliation, Group Reporting, or SAP Advanced Financial Closing in their product-specific guides
Transactions and apps
Manage Global Hierarchies (Fiori App F2918)Preferred route for creating, maintaining, activating, and using FSV-compatible hierarchies in current S/4HANA landscapesOB58 / FSE2Maintain classic financial statement versions where relevant in installed landscapesOB53Define retained-earnings account determination for P&L closeFAGLGVTRCarry forward balances after retained-earnings logic and year-end close prerequisites are provenBalance Sheet / Income Statement (Fiori App F0708)Run financial statements and drill to accounting evidenceS_ALR_87012284Report and drill from statements to account and line-item detailOB52Open or close periods by interval, account type, and authorization groupManage Reconciliation CloseApprove ICMR reconciliation close where that extension is activatedManage Closing Task ListsMaintain AFC task templates where the separately licensed extension is approvedFINSC_FAGL_FSVHRRP_NODEHRRP_DIRECTORYACDOCAT001BT030ACDOCUMaintain in this order
- For current S/4HANA design, create or maintain the financial statement hierarchy in Manage Global Hierarchies, activate it, assign all relevant accounts, govern validity and ownership, and make unassigned-account review a close control. Retain OB58/FSE2 only as the classic route where the landscape still needs it.
- Configure retained earnings in OB53 and prove the year-end chain: P&L Accounts -> Retained Earnings Determination -> Year-End Balance Carryforward -> Opening Balances. Balance-sheet accounts carry forward their balances; P&L accounts close into retained earnings based on configured retained-earnings logic.
- Run balance sheet and income statement by company, ledger, currency, period, profit center, and segment; prove drill-down to the source journal.
- Define the close calendar, dependencies, evidence, review, late-journal process, and reopen authority whether orchestration is manual or tool-supported.
- Close the period only after reconciliations, adjustments, statements, exceptions, and group handoff are approved; retain the before-and-after period-access evidence.
Statements reconcile to the approved trial balance, reported values drill to ACDOCA, exceptions are documented, authorized adjustment access works as designed, and ordinary late posting is blocked.
If it fails, check here first
- Account is unassigned or misclassified: inspect hierarchy validity, chart, account range, retained-earnings treatment, node assignment, and report key date.
- Report differs from trial balance: align company, ledger, currency, period, hierarchy, comparison settings, eliminations, and document status.
- Closed period still accepts posting: inspect account type, both OB52 intervals, authorization group, special period, posting date, ledger-specific access, and technical user.
Release-sensitive: SAP Advanced Financial Closing is separately licensed. ICMR and Group Reporting also require activated scope and dedicated design. The essential R2R path works without representing any of these extensions as mandatory.
CLOSE PROOF
One company-code close, fully reconciled
Configuration is complete only when source postings, subledgers, adjustments, financial statements and closing controls can be reconciled into one explainable company-code result. Settings are not evidence.
Configure -> Post -> Reconcile -> Adjust -> Report -> Lock
- POST
Can we account?
- RECONCILE
Do we agree?
- ADJUST
Are we complete and correctly valued?
- REPORT
Can we explain the numbers?
- LOCK
Can we safely stop further posting?
Controlled test data and ownership
- Company code, chart, fiscal year, posting periods, leading ledger, accounting principle, company-code currency, group currency, controlling assignment, and governed G/L accounts
- Customer or supplier, material or service source, asset, bank and clearing accounts, exchange rates, financial statement hierarchy, and open test period
- Named preparer, reviewer, close owner, evidence location, test run IDs, expected accounts, expected currencies, and approved reversal or cleanup approach
- 01Source posting -> journal display
Operational Source -> Accounting Determination -> Accounting Document -> ACDOCA -> Reconciliation / Reporting is connected and explainable.
- 02Open item -> payment/statement or controlled clearing
Selection, posting, clearing, bank or matching evidence, residual items, and exception ownership reconcile.
- 03Asset acquisition -> depreciation
Asset values, depreciation area, ledger, expense, accumulated depreciation, and journal entries agree.
- 04Accrual + foreign-currency valuation + allocation
Populations, methods, rates or drivers, approvals, run logs, postings, reversals, and ledger scope are reproducible.
- 05Reconciliation -> balance sheet/income statement -> period lock
Subledgers and key accounts reconcile, unassigned accounts are resolved, statements drill to source, approvals are retained, and late posting is blocked.
CURRENT SAP REFERENCES
Verify against the installed release and scope
These SAP S/4HANA 2025 FPS01 product-assistance pages anchor the workbench. The IMG, Fiori content, activated scope, localization, simplification list, and licenses in the target system remain authoritative.
Apply the accounting spine inside policy workshops, mock closes, migration reconciliation, cutover, first live close, and stabilization.