E ERP Atlas
404
CONFIGURATION WORKBENCHPolicy, IMG, apps, transport, proof

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.

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
01

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.

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 parameters
OB13Maintain chart of accounts
OB29 / OB37Maintain and assign fiscal year variant
OBBO / OB52Maintain posting-period variant assignment / period intervals
OKKPMaintain controlling area
Configuration and evidence objectsT001T004T009T009BT001BTKA01

Maintain in this order

  1. Confirm the legal entity, country, local currency, language, chart of accounts, fiscal year, and tax/localization boundary before copying company-code settings.
  2. Assign a fiscal-year variant whose periods and year-shift logic match statutory and management requirements; do not assume calendar year.
  3. Assign the posting-period variant and design the normal period, adjustment-period, and authorization-group approach before opening intervals.
  4. Assign the company code to the intended controlling area only after chart-of-accounts, fiscal-year, and currency compatibility is proven.
RUNOBY6, OKKP, OB52, then post a controlled journal using Manage Journal Entries or FB50
EXPECTED PROOF

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.
02

CONFIGURATION WORKBENCH

Design ledgers, principles, and currencies

Every journal reaches the intended accounting principle and carries the currencies required for entity and group reporting.

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 types
OB22Display or maintain company-code currency settings where applicable to the target release
OB07 / OB08Maintain exchange-rate types / exchange rates
FB50LPost a ledger-group-specific G/L document where supported
Configuration and evidence objectsFINSC_LEDGERFINSC_LD_CMPT881TCURRTCURFACDOCA

Maintain in this order

  1. Document the purpose of the leading ledger, each non-leading or extension ledger, every ledger group, and the accounting principle assigned to it.
  2. Use separate ledgers for parallel accounting when that design fits the policy; treat account-based differences as a deliberate exception, not the inherited default.
  3. Configure company-code and group currency plus only the additional currency types that have a proven reporting or valuation use.
  4. Set exchange-rate types, source currencies, translation rules, and ownership, then test common and ledger-specific postings with non-trivial rates.
RUNPost one common journal and one ledger-group-specific adjustment; inspect ACDOCA and ledger-aware reports
EXPECTED PROOF

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.

03

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.

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

FS00 / Manage G/L Account Master DataMaintain or inspect G/L accounts by chart and company code
OBA7 / FBN1Maintain document types / accounting document number ranges
OB41 / OBC4Maintain posting keys / field-status variants and groups
GGB0 / GGB1 / OB28 / OBBHDefine and activate validations and substitutions
FB50 / Manage Journal EntriesPost and inspect controlled journal entries
Configuration and evidence objectsSKA1SKB1T003TBSLT004FBKPFACDOCA

Maintain in this order

  1. Design account groups and G/L accounts with explicit account type, financial-statement treatment, open-item behavior, tax category, field status, currency, and posting restrictions.
  2. Define document types and number ranges by business purpose; decide permitted account types, negative postings, reversal type, and whether the source should post directly.
  3. Align posting-key, account, and field-status requirements so mandatory dimensions are collected without conflicting suppressions.
  4. Add validations or substitutions only for a demonstrated control need, assign clear messages, document prerequisites, and test positive, negative, reversal, and interface cases.
RUNPost, approve where applicable, display, and reverse one manual journal; repeat one negative test
EXPECTED PROOF

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.
  • Document posts to an unintended account type or ledger: inspect G/L master, document type, account determination, ledger group, and source application.
04

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.

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 accounts
OBYCMaintain materials-management automatic postings
VKOAMaintain sales revenue account determination
AO90Assign Asset Accounting G/L accounts
FB03 / Manage Journal EntriesInspect the resulting accounting document and source reference
Configuration and evidence objectsBUT000KNB1LFB1T030VKOAT095ACDOCA

Maintain in this order

  1. Assign customer, supplier, and asset reconciliation accounts through master-data and asset-account-determination rules; prevent unsupported direct posting.
  2. Test MM account determination with the actual chart, valuation grouping, valuation class, transaction key, account modifier, and movement that the business will use.
  3. Test SD account determination with the actual chart, sales organization, account-assignment groups, account key, and pricing conditions.
  4. 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.
RUNExecute one controlled source event from P2P, O2C, inventory, or assets and trace it to ACDOCA
EXPECTED PROOF

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.
05

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.

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 parameters
F110 / Manage Automatic PaymentsCreate and review payment proposals and runs
Manage Bank AccountsMaintain governed bank-account master data where activated
OT83Maintain electronic bank statement transaction types and posting rules
Manage Bank Statements / Reprocess Bank Statement ItemsImport, post, clear, and resolve bank-statement items
Configuration and evidence objectsT042*BNKAT012T012KFEBKOFEBEPREGUHREGUPACDOCA

Maintain in this order

  1. Design open-item accounts, payment methods, company-code and country parameters, house banks, bank selection, value dates, payment media, and maker-checker ownership together.
  2. Maintain bank main and interim/clearing accounts with explicit purpose, currency, account ownership, and statement-processing relationship.
  3. Configure statement formats, transaction types, external transaction codes, posting rules, interpretation or processing rules, and duplicate protection.
  4. Test proposal exclusions, payment posting, bank confirmation, automatic clearing, unmatched fees, rejected payments, reversal, and reprocessing evidence.
RUNCreate a controlled payment proposal, post without transmitting live funds, import a test statement, and reprocess one unmatched item
EXPECTED PROOF

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.

06

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.

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 defaults
AFAMAMaintain depreciation keys
AO90Maintain Asset Accounting account determination
AS01 / Manage Fixed AssetsCreate or inspect the controlled asset
AFAB / Schedule Asset Accounting JobsExecute depreciation posting run
Configuration and evidence objectsT093T093BT090NAT095ANLAANLBANLCACDOCA

Maintain in this order

  1. Assign a country-appropriate chart of depreciation and document the purpose, ledger group, currency, and posting behavior of each active depreciation area.
  2. Define asset classes, number ranges, screen layout, account determination, default useful life, and depreciation keys by asset purpose.
  3. Maintain account assignments for acquisition, accumulated depreciation, depreciation expense, retirement, gain or loss, and clearing using project-owned accounts.
  4. Create one asset, post acquisition, inspect planned values, execute depreciation in test mode and update mode, and reconcile asset and G/L views.
RUNCreate asset -> post acquisition -> inspect Asset Explorer -> run depreciation -> inspect journal entry
EXPECTED PROOF

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.
07

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.

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 -> Periodic Processing -> Allocation

Financial Accounting -> General Ledger Accounting -> Business Transactions -> Open Item Clearing

Transactions and apps

ACEIMGConfigure Accruals Management
FAGL_FCVExecute foreign-currency valuation for the target release path
Manage Allocations / Run AllocationsMaintain, simulate, execute, and inspect Universal Allocation where activated
F.13Execute automatic clearing for eligible open items
FAGLGVTRCarry forward G/L balances for year-end where applicable
Configuration and evidence objectsACDOCABKPFTCURRT030HACE*FAGL*T811*

Maintain in this order

  1. Define accrual item types, methods, calculation rules, account determination, ledger-group behavior, review/approval thresholds, and reversal or utilization behavior.
  2. Define foreign-currency valuation methods, areas, exchange-rate types, document types, adjustment accounts, and unrealized gain/loss accounts by policy.
  3. Configure allocation contexts, cycles, segments, senders, receivers, tracing factors, ledger or version scope, and reversal behavior; use simulation before update.
  4. Define clearing criteria and account eligibility, then test items that should clear and near-matches that must remain open.
RUNSimulate and post one accrual, one foreign-currency valuation, one allocation, and one automatic clearing run
EXPECTED PROOF

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.

08

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.

SPRO / IMG path

Financial Accounting -> General Ledger Accounting -> Master Data -> G/L Accounts -> Define Financial Statement Versions

Use Manage Global Hierarchies for new financial statement versions where supported by the target release

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 HierarchiesCreate governed financial-statement hierarchies; SAP recommends this route for new FSVs
F0708 Balance Sheet/Income StatementReport and drill from statements to account and line-item detail
OB52Open or close periods by interval, account type, and authorization group
Manage Reconciliation CloseApprove ICMR reconciliation close where that extension is activated
Manage Closing Task ListsMaintain AFC task templates where the separately licensed extension is approved
Configuration and evidence objectsFINSC_FAGL_FSVHRRP_NODEHRRP_DIRECTORYACDOCAT001BACDOCU

Maintain in this order

  1. Create the financial statement hierarchy, assign all relevant accounts, govern validity and ownership, and make unassigned-account review a close control.
  2. Run balance sheet and income statement by company, ledger, currency, period, profit center, and segment; prove drill-down to the source journal.
  3. Define the close calendar, dependencies, evidence, review, late-journal process, and reopen authority whether orchestration is manual or tool-supported.
  4. Close the period only after reconciliations, adjustments, statements, exceptions, and group hand-off are approved; retain the before-and-after period-access evidence.
RUNRun F0708, drill to journal lines, verify unassigned accounts, close the normal period, and execute positive/negative posting tests
EXPECTED PROOF

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.

CURATED SOURCE REGISTER

R2R implementation register

A curated, release-labelled register derived from the supplied FI/CO implementation inventory. Use it to locate the setting, identify its ownership and transport boundary, and define proof. It is a planning aid, not a substitute for the IMG and activated scope in the target system.

Core

Part of the minimum S/4HANA 2025 R2R accounting spine.

Confirm

Relevant only when the approved design requires it; confirm the target-release access path and behavior.

Optional / localized

Country, product, or scenario-specific; keep outside the minimum spine until approved.

Legacy

ECC, classic, compatibility, or deprecated content; retain only for transition analysis.

57 of 57 entries shown

Transport rule: Move only approved project-owned entries and their known dependencies. Customizing, master data, number-range intervals, exchange rates, operational jobs, workflow content, and migration data do not share one deployment mechanism.

01

IMPLEMENTATION REGISTER

Establish legal and fiscal scope

7 of 7 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core ClientFinance organization Create the operational chart of accounts and define the G/L account-number lengthDepends on: Approved account architecture and group-account mappingProof: Display the chart definition and create or validate a governed test account. OB13T004 Customizing
Core Company codeFinance organization Assign the chart of accounts to the company codeDepends on: Company code and chart of accounts existProof: Company-code parameters show the intended operational chart. OB62T001 / T004 Customizing
Core Client / company codeFiscal calendar Define and assign the fiscal-year variantDepends on: Statutory calendar and special-period policyProof: Posting dates derive the expected normal and special periods. OB29 / OB37T009 / T009B / T001 Customizing
Core Client / company codePeriod control Define and assign the posting-period variantDepends on: Company code and period-control ownershipProof: The company code resolves to the approved posting-period variant. OBBO / OBBPT010O / T001 Customizing
Core Company codePeriod control Maintain controlled posting-period intervalsDepends on: Posting-period variant, account types, authorization groups, close calendarProof: Positive and negative postings prove open, closed, and adjustment-period behavior. OB52T001B Operational control data; handle through cutover and restricted access
Core Controlling areaManagement accounting Define the controlling area and assign the company codeDepends on: Compatible chart, fiscal year, and currency designProof: A journal accepts the intended cost object and rejects an invalid assignment. OKKP / OX19TKA01 / TKA02 Customizing
Confirm Client / company codeReporting dimensions Define segments and govern profit-center assignmentsDepends on: Segment-reporting policy and responsibility modelProof: Journal lines derive valid profit center and segment values and report correctly. SPRO / Manage Profit Centers / KE51 where availableFAGL_SEGM / CEPC / CEPC_BUKRS Customizing for design; master data for profit centers
02

IMPLEMENTATION REGISTER

Design ledgers, principles, and currencies

7 of 7 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core Client / company codeLedgers and currencies Define leading-ledger and company-code currency settingsDepends on: Accounting principles, local and group reporting currenciesProof: A posting creates the expected ledger and currency-type values in ACDOCA. FINSC_LEDGERFINSC_LEDGER / FINSC_LD_CMP Foundational Customizing; architecture approval required
Confirm Ledger / company codeParallel accounting Define and assign non-leading ledgers and ledger groupsDepends on: Approved parallel-accounting designProof: Ledger-specific test postings and reports isolate the intended accounting principle. FINSC_LEDGERFINSC_LEDGER / FINSC_LD_CMP Foundational Customizing
Confirm LedgerExtension ledger Define an extension ledger only for an approved delta-posting use caseDepends on: Underlying ledger, accounting use case, reporting and reversal designProof: Inherited and delta values reconcile to the base ledger without double counting. FINSC_LEDGERFINSC_LEDGER Customizing
Core ClientExchange rates Define exchange-rate types and translation ratiosDepends on: Treasury rate policy and currency-pair conventionsProof: A controlled translation uses the approved rate type and ratio. OB07 / OBBSTCURV / TCURF Customizing
Core ClientExchange rates Maintain governed exchange-rate valuesDepends on: Approved source, effective date, quotation and workflowProof: Rate display and a valuation test agree to the approved source. OB08 / TCURMNTTCURR Operational reference data; govern separately from design transports
Core ClientCurrency precision Verify currency decimal-place settings before transactional useDepends on: ISO/local currency definition and conversion assessmentProof: Document entry, storage, and reporting preserve the intended precision. OY04TCURX Foundational Customizing; high-risk after postings
Legacy Company codeLedger configuration Treat direct maintenance of classic ledger views as transition evidence onlyDepends on: Source-system assessmentProof: Target design is recreated and proven in FINSC_LEDGER rather than copied blindly. SM30 views for T881 / T882GT881 / T882G Legacy release-dependent Customizing
03

IMPLEMENTATION REGISTER

Control accounts and journal entries

8 of 8 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core Chart / company codeG/L master Create and extend governed G/L accountsDepends on: Chart, account group, field status, tax and open-item policyProof: The account posts only with the intended field, currency, tax, and open-item behavior. Manage G/L Account Master Data / FS00SKA1 / SKB1 Master data; deploy through the approved master-data process
Core ChartG/L master controls Define account groups and G/L master field statusDepends on: Account architecture and master-data governanceProof: Create/change tests show mandatory, optional, suppressed, and display-only fields. OBD4T077S Customizing
Core ClientJournal controls Define document types and number-range assignmentsDepends on: Journal taxonomy, ledger scope, reversal and audit policyProof: Posted documents use the expected type, interval, year behavior, and audit trail. OBA7 / FBN1T003 / NRIV Document-type Customizing; number-range intervals need separate handling
Core ClientJournal controls Review posting keys and field-status interactionDepends on: Account type, debit/credit and field-status designProof: Positive and negative journal tests demonstrate the intended field controls. OB41TBSL Customizing; change only with explicit design need
Core Company code / employee groupTolerances Define posting and clearing tolerancesDepends on: Delegation of authority and difference policyProof: Boundary-value tests accept permitted differences and reject amounts above authority. OBA4 / OBA3 / OBA0T043S / T043G / T043T Customizing
Core Client / company codeValidation and substitution Define and activate journal validations and substitutionsDepends on: Control requirement, call-up point, message and exception designProof: Positive, negative, reversal, interface, and background-posting tests behave consistently. GGB0 / GGB1 / OB28 / OBBHGenerated rules / T001D / T001Q Workbench and Customizing content; verify generated objects and activation
Confirm Client / company codeDocument splitting Configure document splitting only when balanced reporting dimensions require itDepends on: Segment/profit-center balance-sheet policy and zero-balance designProof: Simulation and live tests produce balanced dimensions without unexplained clearing lines. SPRO document-splitting activities / FINS_SIS_SIM_SPLT8G17 / T8G20 / FAGL_SPLIT_FIELD Cross-dependent Customizing; sequence and simulate before activation
Legacy Controlling areaCost elements Treat KA01/KA06 cost-element creation as legacy for S/4HANA primary accountsDepends on: ECC transition assessmentProof: S/4HANA G/L account category supplies the required cost-element behavior. KA01 / KA06CSKA / CSKB Legacy master-data process
04

IMPLEMENTATION REGISTER

Connect source processes and subledgers

7 of 7 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core Sales organization / chartSD integration Define SD revenue and related account determinationDepends on: Chart, account keys, customer/material classifications, tax and pricing designProof: Billing posts to the expected revenue, discount, tax and reconciliation accounts. VKOACondition tables / KONP / resulting ACDOCA Customizing
Core Valuation area / chartMM integration Define inventory and GR/IR account determinationDepends on: Valuation grouping, valuation class, transaction and account modifierProof: Goods receipt and invoice receipt reconcile inventory, GR/IR, liability and price differences. OBYCT030 keys BSX / WRX Customizing
Core Valuation area / chartMM integration Define consumption, physical-inventory and price-difference accountsDepends on: Movement types, modifiers, valuation classes and currency designProof: Controlled movements post to the expected expense, variance and exchange-difference accounts. OBYCT030 keys GBB / PRD / KDM Customizing
Core Client / Business PartnerSubledger master data Align Business Partner roles and number ranges with customer/supplier integrationDepends on: Customer/supplier account groups, number strategy and synchronization directionProof: A Business Partner creates or synchronizes the intended customer/supplier roles without number collision. BP / BUCF / CVI CustomizingTB003 / TB001 / CVI mapping views / BUT000 Customizing for roles and mappings; Business Partners are master data
Core Customer / supplier account groupReconciliation accounts Govern reconciliation-account determination and sensitive master fieldsDepends on: Account groups, reconciliation-account and four-eyes policyProof: Subledger postings update the correct reconciliation account and direct G/L posting is blocked. BP / account-group and sensitive-field CustomizingKNB1 / LFB1 / reconciliation G/L Customizing plus master-data governance
Confirm Client / company codeCO integration Confirm CO document-type and ledger mapping for integrated postingsDepends on: Ledger, controlling version and document-type designProof: Primary and secondary cost postings reach the expected ledger, account and dimensions. FINSC_VERSN_LD / FINS_CO_DOCT_CC views where applicableFINSC_VERSN_LD / FINS_CO_DOCT_CC Release-sensitive Customizing
Legacy Company code / credit control areaCredit management Keep classic FI credit-management settings outside the R2R S/4HANA spineDepends on: Decision between classic credit management and SAP Credit ManagementProof: Approved target credit solution owns limits and exposure; no hybrid control is assumed. FD32 / classic OB45 and SD credit settingsKNKK / S066 ECC transition content
05

IMPLEMENTATION REGISTER

Configure open items, payments, and bank statements

7 of 7 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core Chart / company codeAutomatic clearing Define automatic-clearing criteria and difference accountsDepends on: Open-item accounts, matching fields, tolerances and reason-code policyProof: A clearing run matches only eligible items and posts approved differences transparently. OB74 / OBXZ / OBXLV_TF123 / T030 Customizing
Core Company codePayment differences Define reason codes for payment differencesDepends on: Residual-item, partial-payment, charge and write-off policyProof: Incoming-payment tests create the expected residual item or difference posting. OBBET053R Customizing
Core Country / company codeAutomatic payments Configure payment methods, paying company codes and bank selectionDepends on: House banks, payment policy, supplier data, formats, approvals and securityProof: F110 proposal selects eligible items and bank accounts; blocked or ineligible items remain excluded. FBZPT042 / T042A / T042B / T042E / T042Z Customizing
Core Company codeHouse banks Create and govern house banks and bank accountsDepends on: Bank keys, account IDs, G/L accounts, signatories and workflowProof: Payment and statement scenarios resolve the correct bank account and clearing path. Manage Banks / Manage Bank Accounts; FI12 only where applicableBank and bank-account master data / T012 compatibility objects Master or application data with product-specific deployment
Core Company codeElectronic bank statement Define account symbols, posting rules and external-transaction mappingDepends on: Bank format, transaction codes, G/L design and clearing referencesProof: A representative statement imports, posts and clears with traceable exceptions. OT83T033I / T033G / T033F / T028G Customizing
Confirm Company codePayment media Configure payment-medium formats and variants for the approved bank channelDepends on: Bank specification, security, approvals and file-transfer ownershipProof: A non-production payment file validates to the bank specification and ties to the payment run. OBPM1 / OBPM4 / Manage Payment FormatsPayment-medium format and variant objects Customizing plus governed variants; external connectivity is separate
Optional / localized Company code / workflowBank communication Implement BCM, Multi-Bank Connectivity, or payment approval only when separately approvedDepends on: License, bank onboarding, security, retention and operating modelProof: Maker-checker, rejection, resubmission and audit evidence work without live transmission during testing. Product-specific Fiori apps and workflowProduct-specific Product, workflow, role and connector boundary
06

IMPLEMENTATION REGISTER

Configure Asset Accounting and depreciation

6 of 6 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core Chart / company codeAsset Accounting Define chart of depreciation and assign it to the company codeDepends on: Valuation principles, ledgers, currencies and fiscal yearProof: Asset values update the intended depreciation areas and ledger groups. SPRO Asset AccountingT093 / T093B and current Asset Accounting objects Foundational Customizing
Core Chart of depreciationDepreciation areas Define depreciation areas, posting behavior and ledger-group assignmentDepends on: Book, tax and group valuation designProof: Acquisition and depreciation post only to the intended accounting principles. SPRO Asset AccountingT093A and current ledger-assignment objects Customizing
Core Chart / asset classAsset master Define asset classes, number ranges and screen layoutDepends on: Asset taxonomy, capitalization policy and ownershipProof: Asset creation enforces the correct account determination and required master fields. OAOA / AS08 / SPROANKA / NRIV / screen-layout objects Customizing; asset records are master data
Core Chart of accountsAsset integration Define Asset Accounting account determinationDepends on: Asset classes, transaction types, depreciation areas and G/L accountsProof: Acquisition, retirement, transfer and depreciation hit the expected balance-sheet and P&L accounts. AO90T095 / T095B and resulting ACDOCA Customizing
Core Company codeDepreciation run Schedule and prove depreciation postingDepends on: Open periods, complete asset values and depreciation keysProof: Planned depreciation, posted journal values and Asset Accounting reports reconcile. AFAB / Schedule Asset Accounting JobsAsset values / ACDOCA / job log Run parameters and job instances are operational data
Confirm Company codeLegacy asset migration Load legacy asset values only through a reconciled migration designDepends on: Transfer date, takeover values, accumulated depreciation and reconciliationProof: Asset history sheet, G/L control accounts and approved source totals agree. Migration Cockpit / approved Asset Accounting migration toolsAsset master and value objects / ACDOCA Migration data, not ordinary Customizing
07

IMPLEMENTATION REGISTER

Configure accruals, valuation, allocation, and clearing

7 of 7 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core Client / valuation areaForeign-currency valuation Define valuation methods, areas and accounting-principle assignmentDepends on: Ledger groups, accounting principles, rate types and valuation policyProof: A controlled FCV run uses the intended method, key date, rate and ledger scope. OB59 and current FCV CustomizingT044A / valuation-area and principle assignment objects Customizing
Core Chart of accountsForeign-currency valuation Define unrealized gain/loss and adjustment account determinationDepends on: Valuation method, account types and chartProof: Valuation and reversal journals reconcile to the valued population and configured accounts. OB09 / OBA1 as applicableT030H / T030HB Customizing
Core Company codeAccruals Configure and operate governed accrual/deferral processingDepends on: Accrual policy, approval, calculation, reversal and evidenceProof: Population, calculation, journal, reversal and reviewer approval are reproducible. Manage Manual Accruals / Accrual Engine apps; FBS1 only for approved simple casesAccrual objects / ACDOCA Methods are configuration; objects and runs are operational data
Core Company codeRecurring journals Use recurring entries only for stable, approved posting patternsDepends on: Validity, frequency, amount logic, review and end dateProof: Scheduled posting matches the approved template and stops at expiry. FBD1 / recurring-entry processingRecurring document / resulting ACDOCA Operational document data
Core Company code / chartRegrouping Configure receivable, payable, and GR/IR regrouping where policy requires itDepends on: Maturity, changed-reconciliation-account and balance-sheet presentation policyProof: Close postings and reversals reclassify the correct population and reconcile to source open items. OBBU / OBBV / OBBW / OBYP and close appsT030U / T030 keys BNG and GNB Customizing
Confirm Controlling areaAllocations Define allocation cycles and tracing factors for approved close allocationsDepends on: Sender/receiver population, driver, version, ledger and reversal designProof: Run log, tracing factors, sender credit, receiver debit and totals reconcile. Manage Allocations / KSV1 / KSU1 where applicableUniversal Allocation objects or T811* compatibility objects Configuration or governed application content; cycles require ownership
Legacy Company codeG/L planning Exclude deprecated classic G/L planning transactions from the S/4HANA core pathDepends on: Transition assessment and approved replacementProof: Planning need is met through the selected current planning product or explicitly documented as out of scope. GLPLINST / GLPV / GLP2 / GLPADMFINS_DEPR_OBJECT / classic planning tables Deprecated compatibility content
08

IMPLEMENTATION REGISTER

Build statements and protect the close

8 of 8 entries shown

StatusScope / areaTask, dependency, and proofAccess / objectsTransport handling
Core Client / chartFinancial statements Define and govern the financial statement hierarchyDepends on: Chart, reporting policy, retained earnings and ownershipProof: All in-scope accounts are assigned once and statements drill to journal detail. Manage Global Hierarchies / OB58 where applicableFINSC_FAGL_FSV / hierarchy repository objects Tool- and release-dependent hierarchy deployment
Core ChartRetained earnings Define retained-earnings account determinationDepends on: P&L account types and year-end carry-forward designProof: Balance carryforward closes P&L accounts to the expected retained-earnings account. OB53T030 key BIL Customizing
Confirm HierarchySemantic reporting Assign semantic tags only for reports that consume themDepends on: Selected analytical report and KPI definitionProof: The target report derives the intended semantic measure from the assigned hierarchy nodes. FINSC_SEM_TAG / FINSC_FAGL2SEMTAFINSC_SEM_TAG / FINSC_FAGL2SEMTA Customizing or governed hierarchy content
Core Company / ledger / periodClose reporting Run balance sheet and income statement and reconcile to the trial balanceDepends on: Complete hierarchy, approved ledger/currency and posted close adjustmentsProof: Statements reconcile by company, ledger, currency and period and drill to source documents. F0708 / Display Financial Statements; F.01 where applicableACDOCA / hierarchy objects Report parameters and variants are governed separately
Confirm Company pairs / group unitsIntercompany reconciliation Use ICMR when activated; do not substitute classic ICR assumptionsDepends on: Activated scope, matching rules, data sources, ownership and close processProof: Matched, unmatched, adjusted and approved populations reconcile between counterparties. ICMR Fiori appsICMR matching and reconciliation objects Product-specific configuration and operational cases
Legacy Company codeIntercompany reconciliation Treat FBIC3 and classic ICR tables as legacy transition referencesDepends on: Source-system assessmentProof: Target reconciliation is designed and proven in the selected S/4HANA capability. FBIC3FBICRC* ECC/classic application content
Optional / localized Country / company codeTax and statutory reporting Keep tax procedures, tax codes, statutory forms, e-reporting and local branches in a localization workstreamDepends on: Country scope, legal advice, localization activation and tax ownershipProof: Country acceptance tests reconcile tax base, calculated tax, postings, return and audit evidence. FTXP / OB40 / localization-specific apps and activitiesT007* / T030K / localization-specific objects Localized Customizing plus governed certificates, forms and interfaces
Optional / localized GroupClose orchestration and consolidation Implement Advanced Financial Closing or Group Reporting only as approved extensionsDepends on: License, group design, tasks, roles, data mapping and operating modelProof: Task evidence or consolidated values reconcile to the approved entity close without changing the core R2R proof. Product-specific Fiori appsProduct-specific close and consolidation objects / ACDOCU where applicable Separately licensed product and content boundary

CLOSE PROOF

One company-code close, fully reconciled

Configuration values are not completion evidence. Run the accounting cycle and reconcile every population, journal, report, and access decision.

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
  1. 01
    Source posting -> journal display

    The source event, account determination, reconciliation account, dimensions, ledgers, currencies, and ACDOCA lines are connected and explainable.

  2. 02
    Open item -> payment/statement or controlled clearing

    Selection, posting, clearing, bank or matching evidence, residual items, and exception ownership reconcile.

  3. 03
    Asset acquisition -> depreciation

    Asset values, depreciation area, ledger, expense, accumulated depreciation, and journal entries agree.

  4. 04
    Accrual + foreign-currency valuation + allocation

    Populations, methods, rates or drivers, approvals, run logs, postings, reversals, and ledger scope are reproducible.

  5. 05
    Reconciliation -> 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.

READY FOR THE PROJECT?Continue to R2R 505

Apply the accounting spine inside policy workshops, mock closes, migration reconciliation, cutover, first live close, and stabilization.

Enter the live project →