BC Pro Tip: Don’t Double-Dip Your Local Currency!

Don’t Overdo It — Leave That Local Currency Blank!

When setting up Business Central, remember that your local currency (LCY) is already defined in the General Ledger Setup — no need to create it again on the Currencies page. Adding the same currency there can confuse the system, causing errors such as “Currency Code cannot be found in the related table.” It also leads to inconsistent setups where some records use a blank currency and others use the LCY code. To keep things clean and accurate, leave the Currency Code blank for your local currency in bank accounts, customers, and vendors. Business Central automatically treats blanks as your local currency — so keep it simple and let BC do its thing!

If you’ve ever run into this error in Business Central 👇You're not alone!

"The field Currency Code of table Gen. Journal Line contains a value (LCY) that cannot be found in the related table (Currency)."

This error pop-up when using Bank Account in General Journal:

The Root Cause:

In Business Central, your Local Currency (LCY) is already defined in the General Ledger Setup.

That’s your system’s base currency — everything revolves around it.

In Bank Account Setup, the local currency code PHP has been used.

How to Fix It:

1. Go to General Ledger Setup → check the LCY Code (example: PHP).

2. Go to Currencies → make sure you don’t have PHP listed there.

3. For bank accounts, customers, and vendors that use the local currency,
   leave the Currency Code blank — that’s how Business Central knows it’s LCY.

 Quick Reminder:

Blank means Local.  If your local currency is already set up in the General Ledger, Business Central’s happy place is blank — no extra currency code needed.

Microsoft Documentation:

https://learn.microsoft.com/en-us/dynamics365/business-central/finance-set-up-currencies