## TL;DR
Translation can only be as good as the local trial balance it starts from. Prove each subsidiary TB balances in its own currency, confirm the rates used per balance type, equity at historic, income at average, assets and liabilities at closing, and rebuild the cumulative translation adjustment as the plug it mathematically is: if it does not foot, either a local TB moved after translation or a rate class was applied wrong.

```text
consolidation translation adjustment does not foot: "subsidiary TB mismatch" error
```

## Use this when
- Consolidation reports a translation adjustment that does not foot or a subsidiary TB mismatch.
- Local subsidiary books are reported as balanced in local currency.
- The mismatch appeared after a late local adjustment or a rate table change.

## Not for this skill when
- Subsidiaries' local TBs do not balance in local currency. Fix the local books first; translation is not the problem.
- The break is intercompany balances not eliminating. That is the pairing workflow, separate from translation.

## Steps
1. Pull each subsidiary TB in local currency for the period and confirm it balances and is the final version used by consolidation. Verify: local TBs balance and their timestamps match the consolidation run
2. List the rates applied by class: closing, average, and historic, with their sources. Verify: each class uses the rate type the policy prescribes
3. Retranslate one subsidiary by hand in a spreadsheet from its local TB and compare account by account with the consolidation output. Verify: the differing accounts are named, not just the total
4. Trace each differing account to its cause: a post-translation local change, a wrong rate class, or an equity account mapped to the wrong class. Verify: every differing account has a cause
5. Correct the cause, rerun translation and consolidation, and confirm the translation adjustment foots as the balancing figure. Verify: CTA equals the computed difference between translated net assets and historic equity plus income

## Variant phrasings
### consolidation translation adjustment does not foot CTA
The CTA footing phrasing.
### subsidiary trial balance mismatch consolidation translation
When isolating the subsidiary at fault.

Compatibility: Consolidation and currency translation in NetSuite OneWorld, SAP Group Reporting, Oracle FCCS, and Dynamics consolidation.

## Why it happens
Translation is a mechanical restatement: the same local numbers multiplied by prescribed rates. Its balancing figure, the CTA, absorbs the arithmetic of using different rates for different classes, so it always foots when the inputs are frozen and the rate classes are right. A footing failure therefore means the inputs moved, a manual consolidation journal interfered, or an account is classified into the wrong rate class. The hand retranslation of one subsidiary is the fastest way to see which.

## Edge cases / pitfalls
- Late local adjustments are the leading cause in practice. Freeze and version local TBs at consolidation start.
- Acquired subsidiaries bring opening equity at acquisition-date historic rates; using incorporation-date rates creates a permanent footing gap.
- If a subsidiary changed functional currency, translation history needs restatement per policy; do not force the old CTA to foot by plug.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_DwDguErwPGyNPRwec3Tplw