Parallel Ledgers for US GAAP and IFRS Revenue

Many US companies report under more than one framework. A US subsidiary of a European group reports US GAAP locally and IFRS to the parent. A US parent with foreign subsidiaries may need IFRS or local GAAP abroad. For revenue, ASC 606 and IFRS 15 are largely converged, but not identical. SAP S/4HANA and SAP RAR handle this with parallel accounting. This article explains how the pieces fit and where the design decisions are.

Parallel Accounting in S/4HANA

S/4HANA supports parallel accounting primarily through the ledger approach:

• One leading ledger (0L) represents the main accounting principle from a group perspective. Many large US companies use US GAAP here; groups headquartered elsewhere often use IFRS.

• Additional standard ledgers hold other principles, such as IFRS, US GAAP, or local GAAP. In S/4HANA, these non-leading ledgers are fully integrated and post in real time.

• Extension ledgers build on a standard ledger and are used for adjustments specific to one principle, typically manual ones.

• Accounting principles are configuration objects that are assigned to ledger groups. A ledger group usually contains one ledger.

An alternative, the account approach with parallel G/L accounts, exists but is rarely used in S/4HANA.

How RAR Uses Accounting Principles

RAR is built around the same concept. Revenue accounting requires defined accounting principles and company codes enabled for revenue accounting. Several key settings are maintained per company code and accounting principle, including revenue accounting periods and account determination. When RAR posts, the accounting principle determines the ledger group that receives the entries.

Account determination supports a base accounting principle: for several accounts, such as recognized revenue, receivable adjustment, unbilled receivable, contract liability, and contract asset, the target account for another principle can be derived from a reference account under the base principle. This keeps the chart of accounts consistent across ledgers and reduces maintenance.

The reconciliation reports between revenue accounting and the general ledger also run per accounting principle, so each framework can be reconciled on its own.

Where ASC 606 and IFRS 15 Actually Differ

The five-step model is the same. Differences sit in specific areas, including:

• Collectibility. ASC 606 uses "probable" in the US GAAP sense, a higher threshold than IFRS 15's "more likely than not," and assesses whether collection of substantially all of the consideration is probable.

• Shipping and handling. ASC 606 allows a policy election to treat shipping after control transfers as a fulfillment activity. Under IFRS 15, it may be a separate performance obligation.

• Sales and similar taxes. ASC 606 offers an election to exclude such taxes from the transaction price. IFRS 15 requires a principal-versus-agent judgment.

• Contract cost impairment. US GAAP does not permit reversal of impairment losses on capitalized contract costs; IFRS does when the indicators no longer exist.

• Licenses of intellectual property. The standards apply different approaches to timing and to license renewals.

• Interim disclosures. ASC 606 requires more extensive interim disclosures for public business entities.

For many companies, these differences affect only a subset of contracts. That is useful: it means the system design should focus on where results actually diverge.

Design Choices

Which principle leads? The leading ledger should reflect the primary reporting framework. For SEC registrants, US GAAP usually leads. For a US subsidiary of a foreign group, it depends on which framework drives management reporting and the close calendar.

Same result or different result? For each revenue stream, decide whether the ASC 606 and IFRS 15 outcome is the same. Where it is the same, a single set of RAR rules with base-principle account derivation keeps maintenance low. Where it differs, the difference has to be modeled explicitly, and the reason documented.

System logic or manual adjustment? If differences are rare and immaterial, a controlled manual adjustment in an extension ledger may be adequate. If they are recurring, configure them so they are calculated consistently every period. Manual top-side entries are a frequent source of SOX findings.

Period and close alignment. Revenue accounting periods are maintained per company code and accounting principle. Keep them aligned with the G/L period close for each ledger, or the posting run will fail at the worst possible moment.

Pitfalls

• Assuming convergence means identical. Review each revenue stream against the known differences rather than assuming one ledger is a copy of the other.

• Ledger-specific manual postings to RAR accounts. These break the subledger-to-ledger reconciliation for that principle.

• Missing ownership. Each accounting principle needs an accountable owner who signs off on its revenue result and reconciliation.

The Bottom Line

S/4HANA parallel ledgers and RAR accounting principles let one revenue process feed both US GAAP and IFRS reporting. The technology is mature; the work is in identifying where ASC 606 and IFRS 15 genuinely differ and modeling only those differences. At Revident, we pair this with human-governed automation that prepares per-ledger reconciliations and flags divergences for review, so the people accountable for each framework can approve with confidence.

Related terms: Parallel Accounting · ASC 340-40 · IFRS 15

Related articles: IFRS 15 vs. ASC 606: Where the Standards Still Differ · SAP RAR vs. Legacy SD Revenue Recognition

Planning parallel revenue reporting for US GAAP and IFRS? Talk to our experts.