FOUNDATION 06 · INTEGRATION & ACCOUNTING

When does operational work become financial truth?

A business document describes intent or execution. A journal entry records an accounting consequence. Integration connects them, but not every operational step posts—and different events recognize inventory, expense, revenue, receivables, payables, assets, and cash at different times.

BUSINESS EVENTWhat changed?

Goods moved, service was accepted, value was billed, production consumed resources, an asset entered use, or cash was identified.

VALUATIONHow much is it worth?

Quantity, price, currency, valuation, tax, account assignment, and accounting principle shape the amount.

POSTINGWhere is it recorded?

Company code, ledger, G/L account, subledger, profit center, cost object, segment, and other dimensions carry the entry.

EVENTS, NOT MODULES

One process creates several accounting moments

Illustrations show common patterns; actual entries depend on configuration, valuation, tax, accounting standards, and process variant.

EVENTOPERATIONAL EVIDENCETYPICAL FINANCIAL EFFECT

Goods receipt for stock POPurchase order history and material documentDebit inventory; credit GR/IR clearing account

Supplier invoiceSupplier invoice referencing PO and receipt where applicableDebit GR/IR and tax or variance as relevant; credit supplier payable

Post goods issue for saleOutbound delivery and material documentDebit cost of goods sold; credit inventory

Customer billingBilling document and accounting statusDebit customer receivable; credit revenue and output tax as relevant

Incoming payment and clearingBank statement or payment document plus clearing referenceDebit bank or bank clearing; credit customer receivable

Asset capitalizationAsset acquisition, settlement, or capitalization documentDebit fixed asset; credit supplier, clearing, or originating cost object

THE UNIVERSAL JOURNAL

S/4HANA integrates financial and management dimensions

The Universal Journal is the book of original entry for accounting-relevant FI and CO transactions. It supports a shared line-item foundation, but “single source of truth” does not mean every operational record lives in one table or that all reconciliation work disappears.

JEBalanced journal entry

Debit and credit line items record the accounting effect in company-code, ledger, currency, account, and relevant reporting dimensions.

COManagement dimensions

Cost center, profit center, project, internal order, market segment, and other account assignments explain responsibility and purpose.

SLSubledger detail

Customers, suppliers, assets, and materials retain operational detail while reconciliation accounts connect relevant balances to the general ledger.

SRCSource-document relationship

Material, billing, asset, settlement, and other documents remain essential evidence and should be traceable to their journal entries.

ACCOUNT DETERMINATION

The account is an outcome of several determinants

Exact rules differ by business event. Diagnose the combination rather than hard-coding a familiar account.

TRANSACTIONWhat kind of event?

Movement type, billing condition, asset transaction, posting key, account assignment category, or business transaction narrows the rule.

OBJECT CLASSIFICATIONWhat is being posted?

Valuation class, account-assignment group, tax classification, asset class, and material or service attributes contribute meaning.

ORGANIZATIONWhere does it belong?

Chart of accounts, valuation area, company code, sales organization, plant, ledger, and controlling context influence the result.

WHEN INTEGRATION BREAKS

Find the last completed business event

NO SOURCE DOCUMENT

Check eligibility, due status, block, workflow, job or interface execution, and whether the predecessor is complete.

SOURCE EXISTS, NO JOURNAL

Check accounting status, posting period, master data, account determination, tax, currency, balancing dimensions, and application log.

JOURNAL EXISTS, WRONG VALUE

Trace quantity, price, exchange rate, valuation, condition values, tax base, account assignment, and any manual override.

BALANCES DO NOT RECONCILE

Define the two populations, key date, currency, ledger, reversal logic, clearing status, interface timing, and accepted reconciliation rule.

WORKED EXAMPLE

Goods arrived, but GR/IR remains open at month-end

An open GR/IR item is not automatically an accounting defect. It can be valid timing evidence—or an exception requiring ownership.

Trace the purchase-order item’s goods receipts, reversals, invoice receipts, credit memos, quantities, values, currencies, and clearing status.
Separate missing invoice, missing receipt, quantity mismatch, price variance, delivery cost, and incorrect reference scenarios.
Confirm cut-off: was the economic event recorded in the correct period and is the unmatched item expected at the key date?
Assign the exception to procurement, receiving, accounts payable, supplier, or system support based on the missing evidence.
Use approved correction and clearing procedures; do not force a manual G/L posting that breaks subledger traceability.

RECONCILIATION DISCIPLINE

A report total is the start of a question

Population

Define company code, ledger, account, object type, status, key date, posting date, and any inclusion or exclusion rule.

Valuation

Align currency type, exchange-rate date, quantity unit, sign, tax treatment, and aggregation level.

Timing and lineage

Account for asynchronous processing, reversals, clearing, late postings, summarized interfaces, and archived or replicated data.

Authoritative reference pointsSAP Help — Universal Journal SAP Help — Reconciliation Accounts SAP Help — GR/IR Account Reconciliation

Postings above are conceptual examples, not accounting advice. Validate the configured process, accounting principle, localization, and customer design.