Views:

GOsupport Logo

 

 

Revised 07/29/2026

 

 

 

Prerequisites

 
This guide addresses error messages that may occur when working in Business Central, along with solutions to common mistakes. 

  Business Central Error Messages

 

 “You can only reverse entries that were posted from a journal.”

 

This error occurs when attempting to reverse a posted Purchase Invoice from the General Ledger. Invoices cannot be reversed in the G/L and must be “Canceled & Credited” in the Posted Purchase Invoice or the Posted Income journals.  For more information, see Reverse Posted Purchase Invoices

 

 

“You cannot reverse Bank Account Ledger Entry No. xxxxx because the entry has a related check ledger entry.”

 

This error occurs when trying to reverse a payment directly from the General Ledger. 

 

Graphical user interface, text, application

Description automatically generated

 

 

 

 

 

 

 

 

 

 

 

For more information, see Voiding Checks & Payments

  

“Statement Status must be equal to ‘Open’ in Check Ledger Entry: Entry No.xxxx. Current value is ‘Check Entry Applied.’”

 

This error occurs when trying to void a payment that has been added to a Bank Account Reconciliation.

 

 

Solution: Navigate to the open Bank Reconciliation and remove the applicable line(s) associated with the check.  You can then void the check. For more information, see Voiding Checks & Payments

 

"Cannot reverse Vendor Ledger Entry No.xxxxx because the entry is applied to an entry or has been changed by a batch job.”

 

This error occurs when trying to reverse a Vendor transaction after the Purchase Invoice has already been paid.

 

Graphical user interface, text, application, email

Description automatically generated

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The solution will depend on the stage the Purchase Invoice is in.  For full instructions, please see Reverse Posted Purchase Invoices.

 

 

“Check printed must be equal to “No” in Gen. Journal Line: Journal Template Name=PAYMENTS, Journal Batch Name=xxxxx, Line No.=xxxxx. Current value is ‘Yes’”

 

This error occurs when the user attempts to delete one or more lines in a Payment Journal after a check has already been printed (but the payment was not posted).

 

The resolution is to either:

  • Post the line item for which the check was already printed.  These lines can be identified by filtering for "Check Printed" = "Yes."
  • Void the check for the lines in question if they should not be posted (because they need to be reprinted or voided completely.) For more detailed instructions, please see our guide Voiding Checks & Payments

 

 

 "Business Central Exception: The activity was deadlocked with another user who was modifying the Gen. Journal Line table. Please retry the activity. CorrelationId:  30dd4540-75fc-4f52-802d-f7856872ece8."

 
This error occurs when two users modify the General Journal simultaneously. Please try again. 
 

  Common Mistakes

 

 

Posted Check before Printing

  

If a user accidentally posts a payment without printing checks, the posted payment must be reversed before issuing a check. For more information, please see Voiding Checks & Payments

  

 

Payment Status (Folio) shows “Received,” but there no data in G/L Entries

 

When the Payment Status shows "Received" but: 

  • No data appears in the G/L Entries, and/or
  • The payment is not available in undeposited funds, and/or
  • The payment doesn’t appear in Suggest Vendor Payments

 

Communication between akoyaGO and Business Central could have been interrupted or not established properly, causing the entries to be “stuck” in the AKOYA Journal. To resolve, filter the lines in the AKOYA Journal and Post.  

 

 

 

(NOTE: The AKOYA journal should always be empty.  Every line in this journal should be addressed before a reconciliation.) For more information on Journal Entries, please see Journal Entries KA.