UC64: Intercompany Netting & Settlement Reconciliation

The Problem

Multi-entity intercompany (IC) transactions create thousands of reconciling items across entities. Entity A invoices Entity B; Entity B receives and matches invoice. But timing differences (goods in transit, invoice in process) create temporary mismatches. Manual reconciliation between entity subledgers is tedious and error-prone. IC netting schedules require manual compilation. Month-end closes are delayed waiting for IC reconciliation completion.

What the Agent Does

Ingests IC sub-ledgers from all legal entities (invoices, credits, payments)
Ingests from centralized IC system (if available) or pulls from individual entity ERP systems via APIs
Matches IC transactions between entities:
Invoicing entity: "sold goods to Entity B for $100k"
Receiving entity: "purchased from Entity A for $100k"
Agent matches on amount (±2%), date (±5 days), and transaction reference
Identifies unmatched IC items:
Timing differences: invoice in process, goods in transit, payment not yet received
Quantity/amount variance: pick-pack-ship errors, freight charges unreconciled
Missing entities: IC invoice without corresponding entry in counterparty books
Calculates aging: items matched, timing items by age, unmatched items by age
Analyzes timing differences:
Goods in transit: analyzes invoice date vs. expected delivery date, flags if overdue
Pending receipt: analyzes invoice date vs. receipt date, suggests reversing entry if timing exceeds threshold
Generates IC netting settlement schedule showing:
Entity A → Entity B: $500k payable (net of credits/payments)
Entity B → Entity C: $200k receivable
Recommended settlement amounts and cash flow timing
Auto-posts timing reversal entries (if policy allows)
Produces IC reconciliation report: matched items, timing differences, netting recommendations, exception items

Data Requirements

Data Sources:

IC sub-ledgers from all entities (AP, AR modules) , IC invoices, credits, payment records
Centralized IC system (if available) , IC master records, netting schedules, authorization records
Intercompany pricing master , IC transfer prices, terms
FX rates , Current and historical rates for IC transactions in multiple currencies
Cost center and GL master , IC GL accounts, netting procedures

Data Classification:

Public: None
Internal Structured: IC transaction subledgers, IC master, netting schedules, FX rates
Internal Unstructured: IC authorization records, pricing agreements
External Third-Party: None
Sensitive/Regulated: IC transaction balances (intercompany accounts on balance sheet); transfer pricing documentation (potentially tax-sensitive)

Data Quality Requirements:

Timeliness: Weekly or daily
Completeness: 100% of IC transactions must exist in both entities' books
Accuracy: IC amounts must be identical between entities (before timing differences); FX rates must be consistent

Integration Complexity: High , Requires APIs to multiple entity ERP systems, IC master system integration, IC transaction matching logic, FX rate lookups, and netting calculation

Score Breakdown

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

Why It Scores Well

Month-end close acceleration: automated IC matching eliminates last-minute sub-ledger chasing. Netting schedule automation reduces manual compilation time. Timing difference analysis prevents unnecessary GL entries. Error reduction: fewer manual IC entries = fewer IC balance discrepancies.

Regulatory Alignment

SOX 404: Intercompany transaction controls and reconciliation
Transfer Pricing: IC pricing and transaction documentation for tax compliance
IFRS/GAAP: Intercompany transactions must be properly recorded and consolidated

Sprint Factory Fit

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

Fits Sprint 1 because multi-entity coordination and IC matching logic are complex. Discovery focuses on IC transaction data structure across entities and netting schedule format. Build sprint (2 weeks) focuses on cross-entity transaction matching algorithms, timing difference analysis, and netting calculation.

Comparable Implementations

BlackLine Intercompany Hub , Intercompany transaction matching and netting automation
SAP Intercompany Reconciliation Module , IC transaction reconciliation and settlement

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 Reconciliation

Bank Reconciliation Automation

Score: 4.3/5.0

Batch Reconciliation

Suspense & Clearing Account Resolution

Score: 4.1/5.0

Batch Accounts Payable

3-Way Match Exception Resolver

Score: 4.35/5.0

Governance Risks to Consider

Before deploying this use case, review these agentic AI risks from the Corvair Risk Catalogue. Each is scored on the DAMAGE framework and mapped to regulatory expectations.