bank statement in EUR, books in USD: "translation not run" error on the reconciliation report

TL;DR

The rec cannot compare a EUR statement to USD books until the statement side is translated at defined rates. Run the account's currency translation for the statement period using the closing rate for balances and transaction-date or average rates per your policy for activity, then regenerate the report. If translation was run but the report still complains, the translation was for a different period, entity, or rate set than the report expects.

bank statement in EUR, books in USD: "translation not run" error on the reconciliation report

Use this when

• The rec report errors or warns translation not run for a foreign-currency account.
• The bank account is denominated in EUR while the ledger base is USD.
• Statement lines show in EUR and book lines in USD with no converted view.

Not for this skill when

• The account is actually a USD account and the statement was issued in EUR by bank error. Resolve the statement with the bank first.
• Translation ran correctly and differences remain. Those are real rec differences to work, not a translation gap.

Steps

1. Confirm the account currency, the book base currency, and the report's expected translation basis from policy. Verify: you know which rates the report needs for balance and for activity
2. Check translation run history for this account and period and note whether it ran, failed, or ran for a different rate set. Verify: the run state explains the report message
3. Verify the needed EUR rates exist for the period: closing and any transaction-date rates in scope. Verify: no missing rate will stall the translation
4. Run translation for the account and period and record the run id and rates used. Verify: translated statement and book views now exist in a common currency
5. Regenerate the reconciliation report and confirm the translation warning is gone and remaining differences are genuine items. Verify: the rec proceeds on translated figures

Variant phrasings

bank statement EUR books USD translation not run reconciliation

The untranslated-rec phrasing.

foreign currency bank account reconciliation translation

When setting up the translated rec.

Compatibility: Foreign currency bank accounts and translation in NetSuite, SAP, Dynamics 365, and Oracle cash management.

Why it happens

A foreign currency bank account lives in two currencies at once: the bank's and the ledger's. Reconciliation needs a single comparison currency, so translation is a precondition, not an enhancement. Reports check for it and refuse to present a misleading mixed-currency comparison. When translation jobs are scheduled separately from rec generation, a late or failed translation surfaces exactly as this error at report time.

Edge cases / pitfalls

• Policy must state whether rec differences from rate movement between transaction and closing are expected and where they post; otherwise every month re-litigates them.
• If the account is swept or valued daily, translation timing matters: run translation after the last statement import of the period.
• A bank account that should be reclassified as USD-functional needs an accounting decision, not monthly translation workarounds.

Provenance

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

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

Thread query: bank statement in EUR, books in USD: "translation not run" error on the reconciliation report

TL;DR: The rec cannot compare a EUR statement to USD books until the statement side is translated at defined rates. Run the account's currency translation for the statement period using the closing rate for balances and transaction-date or average rates per your policy for activity, then regenerate the report. If translation was run but the report still complains, the translation was for a different period, entity, or rate set than the report expects.