202
MODULE TOPICExplore the capabilities that make R2R work

RECORD TO REPORT · INTEGRATE

How do operational processes reach the general ledger?

Sales, purchasing, inventory, production, assets, payroll, banking, and controlling create accounting consequences through governed master data and account determination.

GL ACCOUNTANT OUTCOME

Use this capability inside the complete close

Learn the business purpose, SAP record, controls, diagnostic evidence, and hand-offs for this capability. Complete all R2R 202 guides to form the role-level knowledge foundation; company policy, local procedures, system authorization, and supervised execution remain workplace requirements.

PROCESS ROLE

Integration preserves one business event across operational and accounting evidence

R2R does not begin with a manual journal. Most value originates in another process. The accounting entry must retain enough source reference and dimensional context for Finance to explain the balance without recreating the transaction.

OPERATIONAL FLOW

What happens in SAP

Read the sequence as one connected business event, not as isolated transactions.

01EVENT

Complete a consequential action

Billing, goods movement, supplier invoice, asset acquisition, payroll posting, settlement, or bank processing creates accounting relevance.

02DETERMINE

Resolve accounts and dimensions

Transaction keys, valuation classes, account keys, reconciliation accounts, asset classes, symbolic accounts, and settlement rules shape the entry.

03POST

Create the journal entry

The source document and accounting document remain linked while value reaches the Universal Journal.

04RECONCILE

Prove operational detail to ledger

Quantity, value, open items, subledger totals, clearing accounts, and source status must agree with the resulting accounts.

DESIGN & CONTROL

What shapes the result

These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.

Master-data readiness

Customer and supplier reconciliation accounts, material valuation, asset class, cost objects, tax, and organizational extensions must be complete before posting.

Account determination

MM, SD, Asset Accounting, payroll, bank, foreign-currency valuation, and settlement each use their own governed determination logic.

Reference integrity

Source document, accounting document, reversal, clearing, and follow-on status must remain traceable across application boundaries.

DIAGNOSTIC EVIDENCE

Reconcile the business fact, not only the debit and credit

A technically balanced posting is incomplete evidence if quantity, source status, organizational ownership, or account determination cannot be explained.

SOURCE

Operational document, item, quantity, status, organization, master data, transaction type, and posting trigger.

DETERMINATION

Rule inputs, selected account, account modifier or key, reconciliation account, tax logic, and derived dimensions.

LEDGER

Journal entry, ledgers, currencies, debit and credit lines, source reference, reversal, and reporting impact.

INTEGRATION STORY

One delivery creates quantity and value evidence

Post goods issue reduces the delivered material quantity and normally posts inventory credit and cost-of-sales debit. Finance can trace the accounting lines back to the delivery and material document and explain the determined accounts.

  • Source event is complete
  • Account determination is reproducible
  • Quantity and value agree
  • References remain connected
Technical referencesSAP Help - Universal Journal
CONTINUE THE PATHContinue to R2R 303

See how continuous accounting, operational cut-off, parallel subledger workstreams, GL close, reporting, group hand-off, and period control connect.

Open practitioner map