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

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.

(0) Share

Report

Posted on by Mark Lawrence

Hi All,

I'm trying to create a WHT extension in Business Central W1 based on our previous WHT in NAV W1 CU20. I'm getting an error "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." when posting a Sales invoice transaction. I set the tax to non vat and I'm not using currency exchange rate to lessen the cause of error. I already check the debit and credit amount in debug mode and it was balance but I still getting the error. Please help me to solve this issue. Thanks in advance.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Olister Rumao 3,967 on at

Like (1)

Report

Hi Mark,

I have also got this error when I was trying to post a transaction with a same GL Account as debit and credit.

If possible make sure that the entries have some difference like a Dimension or different Account.

Let me know if the error still persists.

Was this reply helpful? Yes No
Mark Lawrence 30 on at

Like (0)

Report

Hi Mr. Olister,

Thank you for your reply.

Yes, the error still showing. I'm using different accounts in posting.

Here are the details from preview posting:

Posting Date Document Type Document No. G/L Account No. G/L Account Name Amount

01/23/2020 Invoice *** 6210 Sales, Raw Materials - Dom. -100.00

01/23/2020 Invoice *** 5610 Sales VAT 25 % -25.00

01/23/2020 Invoice *** 1124 Creditable WHT 1.00

01/23/2020 Invoice *** 2310 Customers Domestic 124.00

Thank you.

Was this reply helpful? Yes No
Suggested answer

John Ray Patajo 837 on at

Like (1)

Report

Hi Mark,

Check other related entries like making sure the Customer Ledger Entry is 124 not 125 based from your example.

Thanks.

Was this reply helpful? Yes No
Mark Lawrence 30 on at

Like (0)

Report

Hi Mr. John,

We already check the related entries and the amounts are same but the error still showing. Thanks for your suggestion.

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

If you are able to repro this scenario in standard Dynamics 365 BC (preferable in CRONUS), you may want to raise this as an issue to Microsoft via your CSP.

Was this reply helpful? Yes No