LATAM Intercompany Exception Register: A Practical Template for Regional Controllers

A regional finance team can reconcile dozens of intercompany balances and still arrive at the monthly close with no clear answer to three questions: What remains unmatched? Who is responsible for resolving it? Which issues are serious enough to affect headquarters reporting?

An intercompany exception register answers those questions in one controlled place. It does not replace the underlying reconciliations, local ledgers or consolidation procedures. It records only the differences that require investigation, judgment or an accountable next action. For groups operating across multiple Latin American countries, that distinction matters: Group Finance needs a reliable regional view without taking over every local accountant's job.

This guide provides a practical register format, a worked example and a review routine that a Controller can adapt to several entities, currencies and accounting providers. It builds on ASCG Americas' existing overview of why intercompany reconciliations break between U.S. and Latin American entities. The focus here is different: the operating tool used once a mismatch is identified.

What counts as an intercompany exception?

An exception is not simply any difference between two accounting systems. It is a difference or uncertainty that cannot be satisfactorily explained and cleared through the agreed routine by the reporting cutoff. Typical situations include:

• One company has recorded an invoice that its counterparty has not received or accrued.
• The same service charge appears in different reporting periods.
• Both entities agree on the source amount, but a currency translation or reporting mapping creates an apparent mismatch.
• A payment is in transit and the receivable and payable have different settlement dates.
• An allocation, loan, interest charge or credit note is disputed or lacks sufficient support.
• A related-party balance appears against the wrong legal counterparty.

Some are ordinary timing items; others require an accounting, tax or legal assessment. A good register keeps those categories separate. The goal is not to force equal balances with a plug entry. The goal is to explain and resolve each material difference on appropriate evidence.

The minimum register: fields Group Finance should standardize

Keep the regional register small enough that local teams will maintain it. Allow more detailed attachments outside the register, but make each exception identifiable, comparable and assignable.

Control point: compare balances in their transaction currency first, where possible, using the same transaction and cutoff. Record functional-currency and group-presentation-currency amounts separately. An unexplained difference should not be calculated by subtracting MXN, BRL and USD balances or by mixing translation rates. Where the appropriate accounting treatment is uncertain, the specialist must decide it—not the spreadsheet.

A starter register you can copy

Use this compact version for your first month. Add more columns only if they support a defined review or reporting requirement.

All examples, entity codes, dates and amounts in this guide are fictional. The dates illustrate an internal close workflow, not local legal or tax deadlines.

A register is useful only when a team can reproduce the balance. Store the reconciliations and source documents in a controlled repository; the table should link to that evidence rather than copy sensitive records into an unrestricted spreadsheet.

Worked example: a USD 8,000 mismatch across two LATAM entities

Consider a hypothetical group with a Mexican subsidiary (Entity MX), a Colombian subsidiary (Entity CO) and a regional Controller who reviews their October close.

Entity MX reports a USD 100,000 intercompany receivable under invoice INV-184. Entity CO reports only a USD 92,000 payable against the same invoice on the same comparable transaction-currency basis. The USD 8,000 unexplained difference is material under the group's illustrative internal review policy.

The two local teams should not book an automatic USD 8,000 adjustment just to obtain agreement. A defensible process would be:

1. Capture the exception. The Controller logs IC-001, both legal entities, the invoice, the reporting period, the common USD basis and the USD 8,000 variance.

2. Assign two investigators and one accountable owner. The MX accountant confirms the invoice and any related credit notes; the CO accountant traces the payable and cutoff entries. The CO Controller owns delivery of a consolidated explanation by the agreed date. Ownership of the register does not transfer the local entity's accounting responsibility.

3. Review the evidence. Suppose Entity CO has posted only part of the invoice while the remainder awaits a documented review. The supporting records must establish whether the difference represents an unrecorded liability, an actual dispute, or a legitimate difference in recognition. Each result could lead to a different treatment.

4. Document the decision. If the appropriate local reviewers determine that a posting is required, record its authorization, ledger reference and revised matching amounts. If the USD 8,000 remains disputed, preserve it as open with a decision owner and a documented effect on the regional report.

5. Close without deleting the history. Mark the exception resolved only after both sides are verified on the agreed basis, the evidence is saved and an independent reviewer has confirmed the disposition. Do not replace the original variance with zero without recording how it was cleared.

A separate example explains why the FX field is essential: if two teams agree that the underlying balance is USD 45,000 but their group-reporting extracts show different presentation-currency equivalents, there may be a translation or mapping issue rather than a missing USD transaction. The register should show zero difference in transaction currency alongside an open reporting-bridge question. IAS 21 is relevant when IFRS Accounting Standards apply, but the appropriate treatment depends on the transaction and each entity's functional currency.

Five reason codes are usually enough to begin

Avoid creating dozens of labels in the first version. Start with a few categories that drive different actions:

An item can have a primary code and a secondary tag, but it should have only one accountable owner for the next action. “Waiting for the other country” is not a useful status unless a person and response date are named.

Assign ownership across countries without taking over local accounting

A regional Controller should coordinate the flow of evidence and decisions; the local entities and appropriate advisers should retain their own recording and compliance responsibilities. One practical model is:

A group should name actual role holders rather than treat a service provider's generic inbox as an accountable person. Segregate preparation and review when resources allow, and record exceptions to that control where smaller entities cannot fully separate duties.

Aging, materiality and escalation: make the rules explicit

An unresolved USD 8,000 variance may be significant for one group and immaterial for another. There is no universal LATAM threshold that can be recommended for every company. The board or Group Finance team should approve internal thresholds appropriate to the group, separate from any accounting-standard or statutory materiality judgment.

An illustrative process might classify items as:

• Operational: explained timing item with evidence, next clearing event and no known material reporting impact.
• Management attention: aged beyond the agreed internal target, repeatedly recurring, or above an internally approved investigation threshold.
• Specialist / immediate escalation: suspected error affecting published numbers, potentially missed local obligation, material related-party dispute, fraud concern or a transaction requiring tax/legal judgment.

Track age from the first detection date rather than restarting the clock when the register is refreshed. Review both the nominal amount and the nature of the item; a small unresolved compliance issue can demand attention even when its value is below a financial threshold.

Fit the register into the close calendar

The best register is used before the regional report is approved, not assembled afterward for an audit request. A suggested sequence is:

Before close: confirm counterparty codes, recurring charge schedules, expected invoices and agreement references. Send the local teams a standard list of data fields and deadlines.

During local close: compare material transaction-currency balances, generate new exception IDs, assign owners and attach preliminary evidence. Keep cutoff and currency assumptions visible.

At the regional review: the Controller confirms whether each material variance is resolved, appropriately explained, or escalated with a documented impact. The reporting package should distinguish closed, open but assessed and unassessed items.

After reporting: review repeat causes with the affected providers. If three entities repeatedly send management-charge documents after cutoff, improving the billing and confirmation workflow may be more effective than adding another reconciliation spreadsheet.

A useful link exists between the exception register and the regional financial reporting process: the Controller should be able to show which unresolved items affect the figures and commentary headquarters receives.

What this register does—and does not—prove

A cleared intercompany match is not proof that a transaction complies with every tax, transfer-pricing, legal or financial-reporting requirement. For groups reporting under applicable IFRS standards, related-party disclosures, foreign-currency accounting and consolidation considerations arise under different requirements. The OECD transfer-pricing framework provides guidance on the arm's-length principle, but its application depends on the countries and transactions involved.

Likewise, a regional tracker is an operating control, not a substitute for appropriate accounting judgments, legally required documentation, a local tax filing or the formal consolidation process. Escalate these matters to the responsible qualified professionals rather than using a status label to imply technical sign-off.

Four indicators that tell you whether the process is improving

A Controller does not need a complicated dashboard to review the value of the register. Start with four measures, tracked consistently month to month:

Avoid adding different transaction currencies together without a clearly documented conversion methodology. An item count, an amount by currency and a separately defined reporting-currency view may be more transparent than one unsupported grand total.

A regional rollout that does not require replacing every ERP

For the first month, pick a controlled population: for example, balances among three entities that already exchange regular service fees or loans. Agree on counterparty IDs, the transaction-currency comparison method, reason codes and the person responsible for regional review. Run the register in parallel with the existing reconciliation process; retain evidence and correct fields that local teams cannot supply reliably.

In the second month, introduce agreed aging and escalation rules, add recurring counterparty pairs and measure how many issues were resolved before the reporting cutoff. Only then decide whether automation is justified. The objective is not to standardize every local system; it is to make regional exceptions visible, owned and reviewable.

When the same problems recur across several LATAM entities and local providers, multi-country accounting coordination can help define the close handoffs, ownership matrix and reporting inputs. ASCG Americas focuses on that regional coordination layer while country-level professionals remain responsible for their relevant local work.

Want to assess where intercompany issues are slowing your regional close? Discuss your regional finance structure with ASCG Americas. Sharing the countries involved, the number of legal entities and the types of unresolved differences is a useful starting point for an operational review.

---

Primary technical sources (for professional review)

These sources support the framework distinctions in this article. Their application to a specific entity, accounting basis or jurisdiction requires professional judgment.

1. IFRS Foundation — IFRS 10, Consolidated Financial Statements. Principles for consolidated reporting and the group as an economic entity.
2. IFRS Foundation — IAS 21, The Effects of Changes in Foreign Exchange Rates. Accounting for foreign-currency transactions and translation, when applicable.
3. IFRS Foundation — IAS 24, Related Party Disclosures. Related-party relationships, transactions, outstanding balances and required disclosures, when applicable.
4. OECD — Transfer Pricing Guidelines for Multinational Enterprises and Tax Administrations (2022). Framework for evaluating cross-border related-party transactions; verify country-specific application and updates before use.