Skip to content
W
GoBD-compliant §203 StGB-compliant Q2-Q3

Intercompany Agent

Match IC balances, clarify timing differences, prepare elimination entries.

Matches intercompany balances between group entities, identifies timing differences and currency differences.

Analyse your process
Airbus Volkswagen Shell Renault Evonik Vattenfall Philips KPMG

Rule-based IC balances and timing differences, transfer-pricing judgement stays with humans

The agent validates intercompany balances per entity pair deterministically, identifies timing and currency differences by rules, and hands transfer-pricing conformity and unexplained differences to the group-tax owner.

Outcome: IC reconciliation rate automated from 60 to 90 percent, differences detected daily rather than monthly, and consolidation backlog reduced by 3 to 4 days.

80% Rules Engine
0% AI Agent
20% Human

The 10 steps make clear where IC differences are purely arithmetic and where they raise transfer-pricing questions:

435 entity pairs, five days of matching block the close

No consolidated close is faster than its slowest intercompany reconciliation. As long as entity pairs match their balances manually, every unresolved difference blocks the consolidation. In practice that means: five to six days of data collection, matching and clarification rounds before elimination entries can even begin. The Intercompany Agent reduces this bottleneck to hours by classifying differences rule-based and routing only the genuinely unclear cases to the human.

IC Differences Delay the Consolidated Close by Days

A group with 30 entities generates up to 435 possible entity pairs. Even if only a third maintain active IC relationships, hundreds of reconciliation processes arise each month across country, currency and system boundaries. Every single difference demands attention: who posted, who has not yet? Which exchange rate was applied? Does the transfer price match the agreement?

Manually, this process consumes five to six full working days per month-end close according to industry analyses. Not because the individual check is complex, but because the volume exceeds team capacity. Small unresolved differences accumulate into material consolidation variances that further delay the close. According to the PwC Best-in-Class Intercompany Reconciliation Report 2024, automated IC reconciliation typically reduces the time effort by 50 to 70 percent while raising the match rate above 90 percent.

90 Percent of Differences Follow Three Predictable Patterns

Most IC differences appear complex in individual cases but reduce to three causes that a rule engine reliably identifies.

Timing differences arise when one entity posts on the 30th and the counterparty not until the 2nd of the following month. The agent compares posting dates on both sides and automatically classifies the difference as timing-related. At the next reconciliation, it checks whether the counterpart entry has arrived.

Currency differences result from different conversion rates or reporting dates. The agent converts both sides to the agreed reporting-date rate and separately reports the currency difference.

Transfer pricing discrepancies occur when the posted amount diverges from the contractually agreed transfer price. The agent identifies the discrepancy and maps it to the relevant agreement.

Automated matching achieves the highest hit rates on these three patterns - in practice, most recurring differences are cleared without human intervention. Only the remaining cases - unassignable differences, missing documents, disputed charges - reach the human.

Elimination Entries Emerge as a By-Product of Reconciliation

In many groups, IC reconciliation and consolidation are two separate work steps with their own teams and time windows. The agent eliminates this separation. Once an entity pair is reconciled, the offset entries for debt consolidation and revenue/expense consolidation are ready. They are no longer created separately but follow directly from the matching result.

This shortens more than just the close. It also eliminates the error source of manual transfer: when reconciliation and elimination come from the same data base, there are no transcription differences. The reconciliation report per entity pair - with balances, difference classification and clarification history - simultaneously serves as audit evidence under IFRS 10 and comparable consolidation standards.

Transfer Pricing Conformity Remains a Human Decision

The agent identifies TP discrepancies automatically. It establishes that entity A posted a price of 102 while the agreement stipulates 100. But whether this discrepancy is acceptable from a tax perspective, whether the transfer price remains arm’s-length-compliant, whether an adjustment constitutes a constructive dividend under applicable tax law - these are assessments requiring human judgement.

The Decision Layer draws a clear line here: eight of ten decision steps in the IC process are rule-based. Balance matching, timing recognition, currency conversion, elimination entries and escalation follow defined rules. The two steps with a human decider - unexplainable differences and TP conformity - are deliberately chosen because they carry tax and financial reporting consequences that no rule engine can conclusively assess.

The result: the month-end close no longer waits for IC reconciliation. Consolidation receives ready-made elimination entries. And the tax audit finds complete documentation per entity pair - not because someone created it after the fact, but because it emerged within the process.

Micro-Decision Table

Who decides in this agent?

10 decision steps, split by decider

80%(8/10)
Rules Engine
deterministic
0%(0/10)
AI Agent
model-based with confidence
20%(2/10)
Human
explicitly assigned
Human
Rules Engine
AI Agent
Each row is a decision. Expand to see the decision record and whether it can be challenged.
Match IC balances Do balances between entity pairs agree? Rules Engine

Numerical matching

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Identify timing differences Is the difference explainable by different posting dates? Rules Engine Auditor

Date-based = R, interpretation = A

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Challengeable by: Auditor

Calculate currency differences What amount results from conversion at reporting date rate? Rules Engine

Reporting date rate calculation

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Identify transfer pricing discrepancies Does the posted price differ from the contractual price? Rules Engine Auditor

Contractual price vs. posting - exact = R, interpretation = A

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Challengeable by: Auditor

Prepare elimination entries What is the correct offsetting entry? Rules Engine

Mirroring the IC transaction

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Escalate unresolved differences Must a clerk clarify the difference? Human Auditor

Clarification between entities requires human communication

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Challengeable by: Auditor

Trigger clarification communication How is the sister entity informed? Rules Engine

Template = R, context-specific wording = A

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Create reconciliation report Is the reconciliation status documented? Rules Engine

Formatted report per template

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Escalation on deadline breach Is escalation triggered when clarification deadline is breached? Rules Engine

Deadline plus amount threshold

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

TP conformity assessment Are transfer prices conformant with OECD guidelines? Human Auditor

Transfer pricing law requires human assessment

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Challengeable by: Auditor

Decision Record and Right to Challenge

Every decision this agent makes or prepares is documented in a complete decision record. Affected parties (employees, suppliers, auditors) can review, understand, and challenge every individual decision.

Which rule in which version was applied?
What data was the decision based on?
Who (human, rules engine, or AI) decided - and why?
How can the affected person file an objection?
How the Decision Layer enforces this architecturally →

Does this agent fit your process?

We analyse your specific finance process and show how this agent fits into your system landscape. 30 minutes, no preparation needed.

Analyse your process

Governance Notes

GoBD-compliant §203 StGB-compliant

GoBD-relevant: intercompany transactions are tax-relevant and subject to retention obligations per AO Paragraph 147. Transfer prices must comply with OECD guidelines and national regulations. The documentation obligation per Paragraph 90 Abs. 3 AO requires traceable records of IC transactions.

Tax audits regularly focus on IC transactions. Complete reconciliation reports and elimination documentation significantly shorten audit duration.

§203 StGB-relevant data is encrypted end-to-end and never passed to AI models in plain text.

Process Documentation Contribution

The Intercompany Agent documents for the GoBD procedural documentation: which IC pairs were reconciled, how timing differences were identified and resolved, which elimination entries were made and which transfer pricing discrepancies were escalated.

Assessment

Agent Readiness 66-73%
Governance Complexity 36-43%
Economic Impact 68-75%
Lighthouse Effect 34-41%
Implementation Complexity 44-51%
Transaction Volume Monthly

Prerequisites

  • Multi-entity ERP with cross-entity access (SAP S/4HANA, Oracle or equivalent)
  • Defined IC entity pairs with account mapping
  • Access to reporting date exchange rates (ECB, Reuters or equivalent)
  • Transfer pricing agreements as reference data

Infrastructure Contribution

The Intercompany Agent builds the multi-entity reconciliation logic that the Consolidation Agent uses directly. The clarification communication pattern (structured request to other entities) becomes the standard for all cross-entity processes. The transfer pricing monitoring delivers data to the Transfer Pricing Agent.

Builds Decision Logging and Audit Trail used by the Decision Layer for traceability and challengeability of every decision.

What this assessment contains: 9 slides for your leadership team

Personalised with your numbers. Generated in 2 minutes directly in your browser. No upload, no login.

  1. 1

    Title slide - Process name, decision points, automation potential

  2. 2

    Executive summary - FTE freed, cost per transaction before/after, break-even date, cost of waiting

  3. 3

    Current state - Transaction volume, error costs, growth scenario with FTE comparison

  4. 4

    Solution architecture - Human - rules engine - AI agent with specific decision points

  5. 5

    Governance - EU AI Act, GoBD/statutory, audit trail - with traffic light status

  6. 6

    Risk analysis - 5 risks with likelihood, impact and mitigation

  7. 7

    Roadmap - 3-phase plan with concrete calendar dates and Go/No-Go

  8. 8

    Business case - 3-scenario comparison (do nothing/hire/automate) plus 3×3 sensitivity matrix

  9. 9

    Discussion proposal - Concrete next steps with timeline and responsibilities

Includes: 3-scenario comparison

Do nothing vs. new hire vs. automation - with your salary level, your error rate and your growth plan. The one slide your CFO wants to see first.

Show calculation methodology

Hourly rate: Annual salary (your input) × 1.3 employer burden ÷ 1,720 annual work hours

Savings: Transactions × 12 × automation rate × minutes/transaction × hourly rate × economic factor

Quality ROI: Error reduction × transactions × 12 × EUR 260/error (APQC Open Standards Benchmarking)

FTE: Saved hours ÷ 1,720 annual work hours

Break-Even: Benchmark investment ÷ monthly combined savings (efficiency + quality)

New hire: Annual salary × 1.3 + EUR 12,000 recruiting per FTE

All data stays in your browser. Nothing is transmitted to any server.

Intercompany Agent

Initial assessment for your leadership team

A thorough initial assessment in 2 minutes - with your numbers, your risk profile and industry benchmarks. No vendor logo, no sales pitch.

30K120K
1%15%

All data stays in your browser. Nothing is transmitted.

Frequently Asked Questions

Does the agent work with different ERP systems across entities?

Yes. The agent works with standardised interfaces. Whether both entities use SAP or one uses SAP and the other Oracle - matching runs via configured data exports. The account mapping is configured once.

How are transfer pricing discrepancies handled?

The agent identifies discrepancies between posted and agreed price and escalates them to the responsible clerk. The TP conformity assessment always remains with the human - the agent delivers the data basis, not the judgement.

What happens with entities in different time zones with differing close dates?

Timing differences from different posting dates are automatically recognised and classified as such. The agent distinguishes between real differences and time-related discrepancies that resolve in the following month.

What Happens Next?

1

30 minutes

Initial call

We analyse your process and identify the optimal starting point.

2

1 week

Discover

Mapping your decision logic. Rule sets documented, Decision Layer designed.

3

3-4 weeks

Build

Production agent in your infrastructure. Governance, audit trail, cert-ready from day 1.

4

12-18 months

Self-sufficient

Full access to source code, prompts and rule versions. No vendor lock-in.

Implement This Agent?

We assess your finance process landscape and show how this agent fits your infrastructure.