Inconsistencies error in the G/L Entry table

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

Is there a question involved here?

The CONSISTENT check is part of the primary posting routine and is done to ensure that your credit and debit are balancing.

The cause of this error is 99.9% customization’s done to your system, somewhere either in the posting routine or in the way you insert data into the table.
So you need to contact your partner or whoever created these changes and find the error.

yes, what is the message trying to say?

It’s trying to tell you that you have an error in the system. Which as written above is due to someone changing the system.

NO one has changes any system settings.
is it due to VAT Setup application? because that is the last thing we implemented in the system recently?

Hi mdhashmi -

You can write a single instance codeunit to trap this error. If you go to codeunit 12 and search for CONSISTENT, this function checks for your debit and credit in G/L entry table. In your case looks like the VAT has a rounding issue which is causing this error. Here is an example what is happening. In g/L entry table you have 3 transactions that will be created.
Debit say G/L account 1100 1000
Credit say G/L account 1200 -999
Credit say G/L account 1201 -2.35 (This is your VAT account)

do you see the inconsistency here, this is what is happening, some pennis in rouding. What you have to do write a single instance codeunit and trap the error. If you need to know how to write a single instance codeunit please let me know and I will help you out.