Small and medium business | Business Central, N...

Journal Posting Error: CONSISTENT Function Causing G/L Entry Inconsistency

(9) Share

Report

Posted on by CU29041010-0

Hi All,

I need some help understanding and resolving an error I’m encountering. The issue only occurs when I try to post a journal transaction. However, when I use Preview Posting, everything looks fine and the journal entries are displayed correctly.

Error Message: The transaction cannot be completed because it will cause inconsistencies in the G/L Entry table. Check where and how the CONSISTENT function is used in the transaction to find the reason for the error. Contact your system administrator. Tables can be marked as inconsistent during comprehensive tasks, such as posting. This prevents data from being updated incorrectly.

This makes the situation a bit confusing, as there doesn’t seem to be any issue during the preview stage. Any insights or suggestions on what might be causing this would be greatly appreciated.

Thank you in advance for your help.

Best regards,
Alexander Adinata

Categories:

Dynamics 365 Business Central

I have the same question (2)

All responses (12)

Answers (0)

Alex A 2,980 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Try deleting the line and enter it again anew..?

Which journal is it?

Was this reply helpful? Yes No
CU29041010-0 26 on at

Like (1)

Report
Copy link

Link copied!

I tried to re-enter the journal, but it did not work.
It's related to Payment and Cash Receipt Journal for foreign currency.

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,040 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Namaste @CU29041010-0

This bug occurs when debit and credit amount is not matching . In NAV version , we used to do commit transaction for gl entry to know what is calculating or entries getting generated at the run tme But this i would not recommend as might be production issue . IF there is difference in 0.01 then also it will give error . Can you check any additonal entries or any roudning precision set in General LEdger Setup or any payment tolerance

Warm Regards

Pallavi Phade

www.linkedin.com/in/pallaviphade131116

Was this reply helpful? Yes No
Suggested answer

KasparsSemjonovs 4,807 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

This error happens in some specific calculations/cases. Only way to solve it is to try to make the posting in a different way.
Most likely in the line You have the account, balancing account and application link set.
What You can try is:
1) Remove the application and post the journal line. Then do the application from Ledger entries

2) Remove the Bal.Account No. from the line and create a second line with the opposite amount.
3) as last resort is you can try to decrease/increase the amount by 0.01 and add additional line of this 0.01 with the same document number (might not be possible if the document type is invoice)

Hope You manage to post it!

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 1,921 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hi,

This happens when there is a customization around posting of G/L entries may be from your side or a bug from Microsoft.

You can check what is wrong by doing a preview posting and checking the G/L entries. Either G/L entry may not be totalling to 0 or if matching it may be with different G/L register and hence this error comes.

The error will not show during preview posting but only during posting, so that you can analyze the issue on preview posting level.

So check G/L entries and see if there is any customization around G/L posting then that must be the issue which you need to solve.

Regards,

Dhiren.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 21,537 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Please check these:https://tech-lucky.in/blogs/f/%F0%9F%94%8E-debugging-gl-inconsistencies-in-business-central-using-al

https://www.dynamicsuser.net/t/inconsistencies-error-in-the-g-l-entry-table/64947

https://community.dynamics.com/forums/thread/details/?threadid=c7deeea1-607e-45e6-854a-bb823cb86cc1

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 2,938 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi,

This error doesn't show in the Preview Posting, reason being Preview Post doesn't actually make changes to your Ledgers. But actual posting does make changes in your ledgers. And this error comes up while the data in the backend is being written into the Ledgers tables.

This error generally comes up when your debit and credit amounts does not match. It can come either from customizations when you are creating and posting additional Ledgers entries along with the standard entries while posting the Journals, or if there is any round issue which can make a difference of around 0.01 or so because of the currency exchange rates or VAT.

You can check this post for more information - Inconsistencies error in the G/L Entry table - Business Central/NAV / Developers Forum - Dynamics User Group

Hope this helps.

Aman K

Was this reply helpful? Yes No
Suggested answer

RockwithNav 8,802 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Is there any custom code or extension installed?
You may try uninstalling uninstalling that and see the behavior.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 9,762 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hello Alexander,

In short, this happens because Preview Posting does not execute the full database consistency checks, while real posting does, so a journal can preview fine but fail on post when G/L Entry is marked inconsistent. In practice, this error almost always comes from custom code or extensions interfering with posting—typically event subscribers on posting codeunits or G/L Entry that modify posted records, write after insert, or misuse CONSISTENT, which BC strictly enforces during posting. It’s rarely a journal setup issue; the right way to isolate it is to test posting with extensions disabled, review any custom logic touching G/L Entry or posting events, and look specifically for improper Modify() or CONSISTENT usage, since Microsoft’s base app alone doesn’t normally trigger this error.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 97,376 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

I suggest you debug it.
This appears to be a data issue caused by customization. This error wouldn't occur if it were just a standard function.

Thanks.

ZHU

Was this reply helpful? Yes No