Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 5

Scope and coverage

7 min

Record-to-report is the end of every process chain in the company. Sales, purchasing, production, payroll and treasury all end up as journal entries, and R2R turns those entries into a closed period and a set of financial statements. That makes R2R testing different from testing one process: you need coverage of finance's own transactions and of everything that feeds them. A good R2R test plan starts with a scenario catalogue that makes that coverage visible.

Financial statements and disclosuresBalance sheet, P&L, segment reporting, statutory and group packs
CloseAccruals, valuation, GR/IR, regrouping, allocations, carryforward
SubledgersAccounts payable, accounts receivable, Asset Accounting, bank
General ledgerJournal entries, master data, ledgers, document splitting
FeedersLogistics, payroll, treasury and interface postings
The layers of R2R scope.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-305

Building the catalogue

Start from SAP Best Practices. The SAP Signavio Process Navigator lists scope items for finance, each with a process flow and test script. Commonly used ones include Accounting and Financial Close (J58), Accounts Payable (J60), Accounts Receivable (J59) and Asset Accounting (J62), plus bank integration and cash scope items. Scope item IDs and titles change between releases and editions, so confirm each one in Process Navigator for SAP S/4HANA 2025 before you cite it. Then add Contoso's own company variant: the documents, accounts, ledgers and approval steps Contoso actually uses, which the standard scripts do not know.

AreaBest Practices referenceContoso variants to add
General ledgerAccounting and Financial Close (J58)Ledger-specific IFRS postings in 2L; recurring entries; segment splitting
Accounts payableAccounts Payable (J60)Lakeside Components invoices with GR/IR; payment run; central payment for 1810
Accounts receivableAccounts Receivable (J59)Great Lakes Fleet Services invoices, incoming payments, residual items, dunning
AssetsAsset Accounting (J62)CNC machine acquisition, depreciation in 0L and 2L, retirement
BankBank integration scope items (check IDs for your release)Bank statement import, automatic clearing rules
CloseAccounting and Financial Close (J58)Contoso close calendar tasks for 1710 and 1810
IntercompanyIntercompany scope items (check IDs for your release)1710 to 1810 stock transfers and recharges

Extract from Contoso's R2R scenario catalogue.

Coverage you can show

Coverage is not the number of test cases. It is whether every account that will carry a balance, every document type and every close task is touched by at least one scenario. Build a coverage matrix with scenarios as rows and these objects as columns. Gaps jump out: a balance sheet account nobody posts to in testing, a document type used only by an interface, a close task listed in the calendar but missing from the plan.

MeasureWhat it showsWeakness
Test cases per processEffort spentSays nothing about what was missed
Scope items coveredAlignment with SAP Best PracticesMisses company-specific variants
Accounts, document types and close tasks touchedWhat the financial statements depend onTakes effort to build; worth it
Three ways to measure R2R coverage.
The Sign-Off Table · thesignofftable.com/academy/sap-fin-305

Do not forget the scenarios that are not transactions. Master data changes (a new G/L account, a changed reconciliation account on a supplier, a new profit center), authorization checks (can an AP clerk post a manual journal entry to a revenue account?), interfaces (bank statements, payroll postings, any external system that posts journal entries) and reports (the financial statement version, segment reports, the statutory pack) all affect R2R. Each belongs in the catalogue with its own expected result. Interfaces in particular are often owned by an integration team and tested for "message processed"; finance must add the accounting check: the right accounts, amounts, periods and characteristics in the Universal Journal.

What would you do?

Grace asks why the R2R test plan needs more than the SAP Best Practices test scripts for the finance scope items. What is the best answer?

Key points
  • R2R scope covers the general ledger, subledgers, bank, close, reporting and every feeder process.
  • Start from SAP Best Practices scope items and add Contoso's company variants.
  • Measure coverage by accounts, document types and close tasks touched, not by test case counts.
  • Confirm scope item IDs in Process Navigator for your release.

Check your understanding · not graded

Lesson check

  1. 1. What is the best measure of R2R test coverage?

  2. 2. Where do you find SAP Best Practices finance scope items and their test scripts?

  3. 3. Why add company variants to standard scope items?