UC17: Intercompany Reconciliation

The Problem

Matching due-to/due-from accounts across subsidiaries is a month-end bottleneck. Company A records $1M payable to Company B; Company B records $1M receivable from Company A,these should match, but timing differences (invoice in transit), FX differences (transaction vs. translation), and recording errors create mismatches. Manual reconciliation of 100+ intercompany balances can consume 3 to 5 days and often remains unresolved, blocking consolidation.

What the Agent Does

Retrieves due-to/due-from sub-ledgers for all subsidiaries (parent company + consolidated subs)
Matches intercompany balances using key fields:
Transaction date (within ±5 days tolerance for timing)
Amount (exact match or within FX tolerance threshold)
Counterparty entity (Company A's payable to B = Company B's receivable from A)
Auto-reconciles matched pairs
Flags mismatches with classification:
Timing differences (receipt timing, invoice in transit): suggests reversal/re-booking in following month
FX differences: calculates FX variance, suggests plug JE using standard FX rate
Missing counterparty record: flags for manual investigation
Amount discrepancy >tolerance: flags for review
Generates intercompany reconciliation report with automated vs. manual reconciling items
Proposes plug JEs to balance intercompany accounts

Data Requirements

Data Sources:

ERP GL module , Intercompany due-to/due-from sub-ledgers, all entities
ERP transaction detail , Due-to/due-from transaction dates and amounts
FX rate tables , Period-end FX rates for transaction currency conversion

Data Classification:

Public: FX rates
Internal Structured: Intercompany sub-ledgers, FX rate tables
Internal Unstructured: None
External Third-Party: None
Sensitive/Regulated: Intercompany balances (potentially sensitive)

Data Quality Requirements:

Timeliness: Daily (month-end: within 2 hours of close)
Completeness: 100% of intercompany transactions must have counterparty records
Accuracy: Due-to/due-from amounts must reconcile to underlying transactions

Integration Complexity: Medium , Requires ERP GL APIs to pull intercompany sub-ledgers for all entities, FX rate integration, JE generation

Score Breakdown

Criterion	Weight	Score (1-5)	Weighted
Time Recaptured	15%	5	0.75
Error Reduction	10%	4	0.40
Cost Avoidance	10%	2	0.20
Strategic Leverage	5%	3	0.15
Data Availability	15%	4	0.60
Process Clarity	15%	4	0.60
Ease of Implementation	10%	4	0.40
Fallback Available	10%	4	0.40
Audience (Internal)	10%	4	0.40
Composite	100%		4.20

Why It Scores Well

Time savings: Eliminating 3 to 5 days of manual monthly reconciliation × 10 close teams = 150 to 250 FTE hours/month. Error reduction: Systematic matching prevents reconciling items from flowing to parent-level financials. Audit efficiency improves with documented, mechanical reconciliation.

Regulatory Alignment

ASC 810 (Consolidation): Intercompany balances must be eliminated in consolidated statements
SOX 404: Intercompany reconciliation is a control point in consolidation process

Sprint Factory Fit

Sprint 0 (2 weeks) + 1 build sprint (2 weeks)

Sprint 0 + 1 build sprint. Discovery focuses on intercompany account structure and FX rate rules. Sprint 0 covers ERP GL API integration and basic matching logic. Build sprint focuses on FX treatment, timing-difference detection, and exception workflow.

Comparable Implementations

BlackLine Intercompany Hub , Centralized intercompany matching and reconciliation
Trintech Wdesk , Consolidation and intercompany workflows

Deploy This Use Case with the Sprint Factory

From zero to a governed, production agent in 6 weeks.

Sprint Factory Schedule a Briefing

Related Use Cases

Batch General Ledger & Close

Month-End Anomaly Detector

Score: 4.3/5.0

Batch General Ledger & Close

Account Reconciliation Automation

Score: 4.15/5.0

Batch General Ledger & Close

Fixed Asset Lifecycle Agent

Score: 3.75/5.0