Accruals, Reclassifications, and Intercompany Reconciliation in Period-End Close

Explanation

Beyond depreciation, foreign currency valuation, and standard clearing, a mature period-end close includes several advanced control activities that ensure the financial statements are complete, correctly classified, and free of unreconciled intercompany differences. These activities are typically owned by senior FI consultants and controllers because they require judgment about materiality, statutory classification rules, and cross-module data quality. Accruals and deferrals address the timing mismatch between cash movement and economic activity. Manual accrual postings using recurring entry templates or accrual documents record expenses incurred but not yet invoiced (e.g., utility costs) or revenue earned but not yet billed. These postings are typically reversed automatically in the following period once the actual invoice is received, avoiding double counting. In S/4HANA, some organizations use the Accrual Engine or Fiori-based accrual apps for more structured, auditable accrual management, though many mid-size implementations still rely on manual recurring entries configured through classic recurring document templates. Receivables and payables reclassification is a statutory requirement in many jurisdictions: balance sheet presentation must separate short-term from long-term amounts based on remaining term to maturity, and in some cases separate related-party balances from third-party balances. The reclassification program analyzes open items on customer and vendor accounts, groups them by due date bucket, and posts reclassification entries to designated balance sheet accounts (current portion vs non-current portion). These postings are also typically auto-reversed at the start of the next period since they are presentation-only, not economic transactions. GR/IR (goods receipt/invoice receipt) clearing account analysis is critical because unmatched GR/IR balances indicate either goods received but not yet invoiced, or invoices received but goods not yet receipted; large or aged balances distort both the balance sheet and vendor liability reporting. Period-end procedures typically include running a GR/IR analysis report, identifying aged items above a threshold, and either accruing for expected invoices or investigating stuck purchase orders. Intercompany reconciliation is one of the most labor-intensive advanced closing activities in a multi-entity group. Intercompany AR/AP balances and intercompany revenue/expense postings must match between the two trading partners' company codes before consolidation. Differences arise from timing (one side posted, the other hasn't), currency translation differences, or incorrect trading partner assignment on the document. Reconciliation is done using intercompany reports at the document or account level, and unresolved differences must be investigated and corrected, or explicitly documented as reconciling items for the consolidation team. From an architecture perspective, in S/4HANA these reconciliation processes benefit from the single Universal Journal and Fiori-based reconciliation apps that provide near-real-time intercompany matching visibility, whereas in ECC these processes typically rely on ALE/IDoc-based intercompany postings and separate ad hoc reports, requiring more manual reconciliation effort and longer close cycles.

Code example

* Reclassification bucket example (conceptual)* Customer open item due in 45 days   -> Current AR (no reclass needed)* Customer open item due in 400 days  -> Reclassify to Non-Current AR*   Dr Accounts Receivable (Current)       XXX*   Cr Accounts Receivable (Non-Current)   XXX  [reversed next period] * GR/IR aging check (conceptual selection logic)* SELECT items on GR/IR clearing account* WHERE posting_date < (period_end_date - 60 days)* AND clearing_status = 'OPEN'* -> flag for accrual review or PO investigation * Intercompany reconciliation check (conceptual)* Company Code 1000 IC Receivable balance vs* Company Code 2000 IC Payable balance (same trading partner)* Difference = 1000_balance - 2000_balance* IF difference <> 0 THEN flag for investigation before consolidation

Real project scenario

During quarterly close, the consolidation team reports a material intercompany mismatch between the US and German entities' intercompany balances. Investigation reveals that a cross-border service invoice was posted in the US entity's local currency but the corresponding entry in the German entity used a different exchange rate on a later posting date, and the trading partner field was missing on one of the line items, causing it to be excluded from the standard intercompany reconciliation report entirely. The FI lead must manually trace the transaction, correct the trading partner assignment, and document the timing difference as a reconciling item to allow consolidation to proceed on schedule.

Common mistakes

• Forgetting to set auto-reversal on reclassification postings, causing incorrect balance sheet presentation to persist into the next period • Missing or incorrect trading partner field on intercompany postings, which causes items to be excluded from reconciliation reports • Treating aged GR/IR balances as immaterial without investigating whether they represent real accrual or a stuck purchase order • Performing manual accrual reversals inconsistently, leading to duplicated or missing expense recognition • Reconciling intercompany balances only at the account total level instead of the document level, masking offsetting errors

Best practices

• Enforce mandatory trading partner field entry on intercompany transactions through validation rules • Maintain a materiality threshold and aging policy for GR/IR review so effort is focused on significant items • Standardize reclassification and accrual reversal settings across company codes to avoid inconsistent balance sheet presentation • Reconcile intercompany balances at the document or line-item level, not just account totals, before consolidation cutoff • Maintain a documented list of recurring reconciling items and their root causes to speed up investigation each period

Interview angle

Senior-level interviews often probe how candidates handle intercompany mismatches under close deadline pressure, whether they understand the statutory basis for current/non-current reclassification, and how they distinguish accrual reversals from valuation reversals. Discussing a real reconciliation investigation, the root cause analysis, and the control improvement implemented afterward demonstrates the kind of close-process ownership expected at advanced and architect levels.