Main site

Finance AI agent · Intercompany accounting

Intercompany Accounting AI Agent

One charge is two entries in two jurisdictions, so the agent drafts it, records the documentation that must exist before the return is filed, and holds both for the officer who signs.

Typical delivery
4–6 weeks
Deployment
Your stack
Signing officer
Evidence first
After launch
Agent Care

What this agent does

Drafts the charge, never prices it

In

  1. 01

    A charge is raised, and under 6662(e)(3)(B)(i) its documentation exists before the return is filed.

  2. 02

    The first GloBE return fell due 30 June 2026 and held, so the rule vintage rides each charge.

Reason

  1. 03

    A method is settled under 1.482-1(c)(1), and the methods set aside are recorded beside it.

  2. 04

    An examiner asks years later, and the file must be produced complete within thirty days.

  3. 05

    A pool position persists year on year, and OECD Chapter X asks what it has turned into.

Decide

  1. 06

    A loan sits unsettled, and the ASC 830 evidence is laid out for a person to classify.

  2. 07

    A charge-out reaches the Country-by-Country Report, filed under 1.6038-4 with the return.

Out

  1. 08

    Two ledgers agree and neither is defensible, and that is recorded as the finding.

  2. 09

    Execute write actions only inside the approval boundaries fixed at implementation.

Product statement

Drafting, documentation and the charge trail belong to the agent. The price belongs to a named officer, who signs under 26 U.S.C. 6062 and 6065 and owns it there.

Example workflow

One charge, both sides to signature

  1. 1Documents receivedIntercompany agreements, cost pools, functional analyses, the master file and the local file
  2. 2Transaction characterised and versionedThe counterparties, the jurisdictions, the tested party and the tier it sits in under Action 13
  3. 3Both sides raised apartThe charge as raised, the charge as received, and the entry eliminating both under ASC 810
  4. 4Checks and controls appliedAgreement checks, document checks, elimination in full under IFRS 10 B86 and drafting confidence

No human action required

Stages 1 to 4 run unaided, and no price is fixed at any of them — the agent is assembling evidence, and the officer lane opens at the documentation gate.

5DecisionSplits at the documentation gate
File complete against the method

Goes to the named signing officer to approve.

Anything undocumented

Adds a transfer-pricing counsel read first.

Signing-officer review

The charge is held with its method file, its agreement and the ledger on each side of it.

Approve · Append document · Send for counsel review

Approved — by the named signing officer

  1. 6Ledger and consolidation records updatedOnly where write access and the group records policy allow it
  2. 7Charge evaluatedDocument completeness, method stability, officer corrections and what counsel review found

Corrections entered

Each correction the officer enters is weighed in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Setting the price on an intercompany charge.
    • Signing the return under penalties of perjury.
    • Deciding a balance is long-term investment.
    • Electing the side-by-side safe harbour.

  • Automation boundary

    Agent acts unaided

    • ✓Draft each intercompany charge against the agreement that governs it.
    • ✓Record the method chosen and the ones set aside.
    • ✓Show the counterparty ledger beside the one that raised the charge.
    • ✓Hold the charge, its file and both ledgers as one.

    No price is set except by a named officer, who signs under penalties of perjury.

    • Judging whether a service conferred a benefit.
    • Telling an examiner the method was reasonable.
    • Choosing the tested party and the comparables.
  • Changes to the charge, the ledger or the file.

Example output

One intercompany charge, annotated

This serves a group finance team whose charge-out is read from two sides and whose first Australian public report fell due on 30 June 2026; below is one charge exactly as the agent leaves it.

Intercompany charge · one service recharge

Illustrative example
Charge
Service recharge, two jurisdictions
Recorded as
Documented before filing
Method
Method file, versioned
Evidence of record
Agreement, 6 August 2026
Confidence
Held unpriced
Held for
The signing officer, by name

As received

In existence under 1.6662-6(d)(2)(iii)(A) before the return was filed, and producible within thirty days.

What the charge record holds

  • Intercompany agreement
  • Cost pool schedule
  • Counterparty ledger

Why no price here

Setting an arm's-length price is a judgement a named officer makes.

What the score decides

Below the configured threshold a charge gets a counsel read before the officer sees it.

Action

ApproveAppend documentSend for counsel review

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

Each charge raised

From the document that supports it

03Evidence

Where that evidence lands

The agent does not vouch for a price, only for the document behind it and the day it existed: eight of the ten principal documents must pre-exist filing, and only items (B)(9) and (10) may follow.

01Approved path

One deal, two sets of books

It is a deduction in one country and income in the other, and agreement between the two ledgers proves only that management booked one number twice.

02Human review

Looked for, and not found

No current independent measure of intercompany failure was found; the recent material is vendor-published, and the best survey located is over a decade old. The newest hard evidence is public country-by-country data: under the early Romanian regime, about a fifth of the groups in scope published.

04

Build an evidence trail

The charge, the side that raised it and the officer who signed the return stay together.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • Group ledgers on both sides

    • ERP entities
    • subsidiary ledgers
    • Charges raised and received

  • Agreements and cost pools

    • Contract store
    • cost-pool data
    • Terms and allocation keys

  • Transfer-pricing documentation

    • Method files
    • comparables sets
    • Rationales and the methods set aside

Agent

Intercompany accounting

  • Reads both sides
  • Drafts the charge
  • Holds for the signer

  • Filings and public reporting

    • Form 8975
    • public CbCR lodgments
    • Jurisdiction lines once published

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six clamps between the model and the return

Six clamps around one beam, the last the tightest. What holds is drawn in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modeNarrow the agent to document assembly when evaluation or production signals degrade.Roll back
L5Version registerTrack model, prompt and charge-out rules, and note the rule vintage each charge was drafted under.Track
L4Charge trailRecord each charge, the documents beneath it, both ledger entries and each read of the file.Record
L3Officer approvalHold the charge for a named officer; the hold governs posting, not whether the price is right.Gate
L2Document guardrailsTest each charge against the agreement on file, and refuse one whose method file is not complete.Restrict
L1Confidence gatingRoute a thin method file, or an unsettled balance under ASC 830, to a counsel read first.Require review
Model coreCharge drafted — the agreement, both entries, the method file and its sources
L1 – L2
Test whether a charge may stand
L3
Leaves the price to a named officer
L4 – L5
Keep the charge and the documentation behind it
L6
Books nothing cross-border when signals degrade

How Nestack evaluates it

Evaluate the whole charge-out run — not only the charge that comes out.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the charge a return carries

  1. E1Final-output evaluationDid the charge record the method it was actually drafted under?
  2. E2Step-level evaluationDid the agent read the live agreement, the right period and both ledgers?
  3. E3Tool evaluationDid it read and write the correct entity and the correct charge?
  4. E4Confidence calibrationDo low-confidence charges actually attract more officer corrections?
  5. E5Slice evaluationHow does performance change across specific charge classes?
  6. E6Business outcomeHow many charges needed a correction before the officer approved?

Floor — the agreement a charge rests on

Failure modes

Where each failure originates in the agent

Seven failure modes, each shown where it first becomes visible.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • VK-04

      Pool balance read one year deep

      A position that persists reads as short-term.

    Stage gathers

    The ledgers, the terms, the pools and the dates

  2. 02 · Reasoning

    2 modes

    • VK-01

      Method chosen, none recorded

      The price is in range and the reasoning is gone.

    • VK-02

      Balance classed as trading

      Currency movement lands in earnings, not in CTA.

    Stage proposes

    The agreement, the method, both entries and confidence

  3. 03 · Tool / write

    2 modes

    • VK-03

      Both sides agree, both wrong

      The match proves consistency, never correctness.

    • VK-05

      Difference plugged, not resolved

      The elimination clears and the break survives.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • VK-06

      A line nobody can explain

      Directive 2021/2101 publishes it, with no draft stage.

    Stage returns

    The charge both books carry and a public file shows

  5. 05 · Change / Version

    1 mode

    • VK-07

      Side-by-side read as full relief

      The IIR and the UTPR lift; the QDMTTs do not.

    Stage tracks

    Model, prompt, charge rules and filing dates

  • Sev-1 · a charge filed on no document
  • Sev-2 · a stale method reaches the return
  • Sev-3 · signals degrade, charge held back
See the complete Finance failure-mode catalogue

Affected slices

Cross-border charges absorb the corrections

A group-level correction figure can read clean while cross-border service charges carry most of the rework. Nestack reports the correction rate by charge class, not only across the group.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Cross-border service charges9.8%3.7×Review
Cash pool positions6.9%2.6×Review
Intercompany loan balances4.3%1.6×Watch
Settled recharge routines2.1%0.8×Normal

Bar: correction-rate lift vs. settled-recharge baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

What an undocumented charge costs

A loop closes when the charge filed without its documentation is a standing case. That suite is what the next period consolidated is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Correction rate rises on cross-border service charges.

  2. 02

    Diagnose

    The charge that posts quietly each period and surfaces eighteen months later on a public register is worked backwards until one cause is left standing.

  3. 03

    Improve

    Number the elimination; the charges that drove it are filed beneath it.

  4. 04

    Verify

    A single unmatched counterparty case stops the whole consolidation.

  5. 05

    Learn

    One case joins the suite, and one line joins the charge-out rules.

  6. Learn → Detect

    The return edge. The next charge is measured against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, charge-out logic, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Charge classification and automation-boundary work.Week 1
  2. 02Ledger, agreement and cost-pool sources.Week 1, Week 2
  3. 03Documentation and counterparty-ledger trail mapping.Week 1, Week 2
  4. 04Charge and agreement intake.Week 2
  5. 05Entity, method and period binding.Week 2, Week 3
  6. 06Document scoring and review routing.Week 3
  7. 07Officer approval workflow.Week 3, Week 4
  8. 08Consolidation-system integration.Week 5
  9. 09Documentation and matching cases.Week 4, Week 5
  10. 10Guardrails and elimination controls.Week 4
  11. 11Charge-trail instrumentation.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne entity pair, one cycleProductionProduction consolidation workflowAdvancedMultiple entities / jurisdictions
Introduced at Pilot
Charge drafting to your agreements✓✓✓
Named officer approval✓✓✓
Entity-and-jurisdiction baseline✓✓✓
Introduced at Production
Reporting by counterparty class—✓✓
Counsel review workflow in your systems—✓✓
Approved ledger write-back—✓✓
Ledger-and-consolidation integration—✓✓
Introduced at Advanced
Multi-method documentation——✓
Cross-entity charge packs——✓
Dense entity structures——✓
Multi-jurisdiction charge-out controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, entity volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your live entity pairs and the agreement each charge runs under

    Agreement capture and method versioning

    Week 1

  2. 02Representative agreements, cost pools and both-side ledgers

    Source binding, charge-out logic and the documentation baseline

    Week 2

  3. 03Your filing calendar and the officers it names

    Charge-out mapping, document binding and the automation boundary

    Week 1

  4. 04Access to the relevant ledgers, feeds or exports

    Ledger, agreement and cost-pool assessment, then integration setup

    Week 2

  5. 05Charges you would not want published

    Matching cases and the failure round

    Week 4

  6. 06What no charge may be called

    Document scoring, review routing, guardrails and release controls

    Week 3

  7. 07A named officer who signs the return

    Officer approval, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Week five carries two bands here because those two phases coincide, not because the column looks better.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Charge-out discovery, method versioning and the automation boundary

W2Ledger and agreement integration, and the entity-and-jurisdiction baseline

W3Charge-out logic, documentation checks and release controls

W4Evaluation suite, matching cases and failure-mode testing

W5Consolidation integration, pilot charges and targeted corrections

W6One filing cycle run under the tax director, then Agent Care handover

Reading the band
Each bar runs only across the weeks its own work is named for, and week five is shared by design.
At the end of W6
Once the charge record validates, Agent Care picks the agent up.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Finance AI agent

Build an intercompany accounting agent around the document your last charge-out never produced.

Show us one intercompany charge you raise each period and the documentation behind it. If that file was written after the return went in, it was no defence when the officer signed. Under 7206(1) a false return is a felony; a charge nobody can document comes back as a finding.

Typical delivery
4–6 weeks
Deployment
Your entity structure
Signing officer
Evidence first
After launch
Agent Care available

Nestack Agents · Intercompany accounting

AGT-FIN-03 · Agent Care available after launch

Build an intercompany accounting agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your entities

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.