Business Central bank rec statement ending balance was typed in the wrong cu

Not specified by the original author.

TL;DR

Correct the bank rec statement ending balance in Business Central to the EUR amount from the statement (not the typed figure in the old currency) and redo the rec in the account's currency, because a balance typed in the wrong currency after migration can never tie. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Business Central bank rec statement ending balance was typed in the wrong currency after the account migrated to EUR

Use this when

• You see this exact error or symptom: Business Central bank rec statement ending balance was typed in the wrong currency after the account migrated to EUR.
• The failure is in the accounting or ERP system named in the title and its bank or processor feed, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one affected transaction first and capture the evidence before changing anything: check the system's own error detail and the underlying transaction record (journal, bill, payout or statement line) for one affected item, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Correct the bank rec statement ending balance in Business Central to the EUR amount from the statement (not the typed figure in the old currency) and redo the rec in the account's currency, because a balance typed in the wrong currency after migration can never tie. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Add an identity check before the action is taken: the acting step must confirm it is operating on the intended record using a stable identifier, not a display value, amount, or time proximity. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: repost or rematch that single item and confirm the reconciliation balance moves by exactly that item and then ties. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of items in the period close in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

Business Central bank rec statement ending balance was fix

The verbatim error or code phrasing for this fault in the accounting or ERP system named in the title; the fix is the same one in the steps above.

Business Central bank rec statement ending balance was typed in the

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix Business Central bank rec statement ending balance was

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: SAP, NetSuite, QuickBooks and QuickBooks Online, Xero, Sage 50 and Sage Intacct, Dynamics 365 Finance, Business Central, Oracle EBS, Workday, BlackLine, FloQast, Coupa and Stripe, PayPal, Square, Bill.com, Ramp and Brex as named in the title.

Why it happens

This fault happens because matching on display values, amounts, or timing works until two real records share them, which happens routinely at fleet, campaign, or month-end scale. In this case the condition is the one named in the title, in the accounting or ERP system named in the title and its bank or processor feed: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

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

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

Thread query: Business Central bank rec statement ending balance was typed in the wrong currency after the account migrated to EUR

TL;DR: Correct the bank rec statement ending balance in Business Central to the EUR amount from the statement (not the typed figure in the old currency) and redo the rec in the account's currency, because a balance typed in the wrong currency after migration can never tie. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Not specified by the original author.

TL;DR

Reopen the bank account ledger entry in Business Central through the undo from the bank reconciliation itself (or reverse the payment properly), because an already-closed ledger entry cannot be undone directly once its statement line is reconciled. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Business Central bank account ledger entry is already closed error when undoing a reconciled payment

Use this when

• You see this exact error or symptom: Business Central bank account ledger entry is already closed error when undoing a reconciled payment.
• The failure is in the accounting or ERP system named in the title and its bank or processor feed, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one affected transaction first and capture the evidence before changing anything: check the system's own error detail and the underlying transaction record (journal, bill, payout or statement line) for one affected item, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Reopen the bank account ledger entry in Business Central through the undo from the bank reconciliation itself (or reverse the payment properly), because an already-closed ledger entry cannot be undone directly once its statement line is reconciled. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Make the operation idempotent: look the record up by its stable key before creating, adopt or update the existing record when it is the same entity, and log which path was taken. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: repost or rematch that single item and confirm the reconciliation balance moves by exactly that item and then ties. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of items in the period close in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

Business Central bank account ledger entry is already fix

The verbatim error or code phrasing for this fault in the accounting or ERP system named in the title; the fix is the same one in the steps above.

Business Central bank account ledger entry is already closed error when

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix Business Central bank account ledger entry is already

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: SAP, NetSuite, QuickBooks and QuickBooks Online, Xero, Sage 50 and Sage Intacct, Dynamics 365 Finance, Business Central, Oracle EBS, Workday, BlackLine, FloQast, Coupa and Stripe, PayPal, Square, Bill.com, Ramp and Brex as named in the title.

Why it happens

This fault happens because create-style operations are not idempotent in most of these systems, so a retry or a pre-existing record surfaces as a hard conflict instead of a no-op. In this case the condition is the one named in the title, in the accounting or ERP system named in the title and its bank or processor feed: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

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

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

Thread query: Business Central bank account ledger entry is already closed error when undoing a reconciled payment

TL;DR: Reopen the bank account ledger entry in Business Central through the undo from the bank reconciliation itself (or reverse the payment properly), because an already-closed ledger entry cannot be undone directly once its statement line is reconciled. Prove it on one affected transaction before rolling it to the rest of items in the period close, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Not specified by the original author.

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.