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

Bank deposits error with release 24

(1) Share

Report

Posted on by LD-15051834-0

Since the update to 24.0, we are unable to post Bank Deposits. We are getting different errors, at different times:

-can't post because it needs approval (deposits are not set up with a workflow)

-/The lines of the deposit must belong to the same transaction when posting as a lump sum. Please verify that the Posting Date, Document Type and Document NO. are the same for every line or modify the template used to allow unbalanced documents/

-sometimes it /posts/ a blank deposit, which uses up that Dep#. The unposted deposit is still sitting there and can't be used.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (10)

Answers (0)

Suggested answer

Valentin Castravet 31,340 Super User 2025 Season 2 on at

Like (1)

Report

I have also encountered errors related to the number series setup to be used by the general journal batch that is used by bank deposits. The number series needs to allow manual numbers, otherwise it was posting an empty bank deposit. Perhaps that's why you're getting the 3rd error as well?

I haven't had the 1st and 2nd error though. Regarding the 1st error, do you have any workflows enabled for general journals?

Valentin Castravet
Work: Zander ERP Services
Blog: Dynamics 365 Business Central Insights
LinkedIn: www.linkedin.com/in/valentin-c-0500a247/

Was this reply helpful? Yes No
AB-16050158-0 8 on at

Like (2)

Report

I can second OP's raised issues.

Since the 24.0 update, we experience the following:

PROBLEM 1

By default, Users see the Credit Amount column (Amount column is typically hidden).

If a User attempts to record a fee expense as a Deposit Line (ex. bank fee, document type Payment) with a negative amount under Credit Amount, and adds a Customer entry (ex. payment) with a positive Credit Amount and attempts to post the Deposit (Total Deposit Lines = Total Deposit Amount), the system throws the below error. It then commits a Posted Bank Deposit document, but does not delete the deposit from the unposted Bank Deposits.

ERROR MESSAGE

Error message:

Correction must be the same on all lines for the same document in Gen. Journal Line Journal Template Name='XXX',Journal Batch Name='XXXX',Line No.='20000'.

AL call stack:
"Gen. Jnl.-Post Batch"(CodeUnit 13).CheckCorrection line 15 - Base Application by Microsoft
"Gen. Jnl.-Post Batch"(CodeUnit 13).ProcessBalanceOfLines line 64 - Base Application by Microsoft
"Gen. Jnl.-Post Batch"(CodeUnit 13).ProcessLines line 59 - Base Application by Microsoft
"Gen. Jnl.-Post Batch"(CodeUnit 13).Code line 30 - Base Application by Microsoft
"Gen. Jnl.-Post Batch"(CodeUnit 13).OnRun(Trigger) line 9 - Base Application by Microsoft
"Bank Deposit-Post"(CodeUnit 1690).OnRun(Trigger) line 88 - _Exclude_Bank Deposits by Microsoft
"Bank Deposit-Post (Yes/No)"(CodeUnit 1692).OnRun(Trigger) line 7 - _Exclude_Bank Deposits by Microsoft
"Bank Deposit"(Page 1690)."Post - OnAction"(Trigger) line 2 - _Exclude_Bank Deposits by Microsoft

POSSIBLE SOLUTION (from a User's POV)

It looks like there is a COMMIT somewhere after the creation of the Posted Deposit Header, but before the generated error message. The error message should launch a rollback PRECEEDING the creation of the Posted Deposit Header.

-----

PROBLEM 2

By default, Users see the Credit Amount column (Amount column is typically hidden).

If a User attempts to record a fee expense as a Deposit Line (ex. bank fee, document type Empty) with a negative amount under Credit Amount, and adds a Customer entry (ex. payment) with a positive Credit Amount and attempts to post the Deposit (Total Deposit Lines = Total Deposit Amount), and for which the Post as Lump Sum radio button is set to TRUE, the system throws the below error. It does not commit a Posted Bank Deposit document, and does not delete the deposit. Even when the Force Doc. Balance option is unchecked (on General Journal Templates), the error message still remains.

ERROR MESSAGE

Error message:

The lines of the deposit must belong to the same transaction when posting as lump sum. Please verify that Posting Date, Document Type and Document No. are the same for every line or modify the template used to allow unbalanced documents.

AL call stack:
"Bank Deposit-Post"(CodeUnit 1690).ValidateLinesInSameTransaction line 20 - _Exclude_Bank Deposits by Microsoft
"Bank Deposit-Post"(CodeUnit 1690).OnRun(Trigger) line 64 - _Exclude_Bank Deposits by Microsoft
"Bank Deposit-Post (Yes/No)"(CodeUnit 1692).OnRun(Trigger) line 7 - _Exclude_Bank Deposits by Microsoft
"Bank Deposit"(Page 1690)."Post - OnAction"(Trigger) line 2 - _Exclude_Bank Deposits by Microsoft

------

PROBLEM 3

By default, Users see the Credit Amount column (Amount column is typically hidden).

If a User attempts to record a fee expense as a Deposit Line (ex. bank fee, document type Payment) with no amounts under Credit Amount, but a positive amont under the Amount field, and adds a Customer entry (ex. payment) with a positive Credit Amount and attempts to post the Deposit (Total Deposit Lines = Total Deposit Amount), and for which the Post as Lump Sum radio button is set to TRUE, the system posts the Deposit and creates the Posted Bank Deposit document. However, the GL Account line's amount is zeroed out, but the system did post the GL entries.

Was this reply helpful? Yes No
Suggested answer

CP-16051640-0 8 on at

Like (2)

Report

I concur and confirm the same exact errors and problems that both LD and AB have described in their posts. I now have posted deposit headers sitting "in limbo" that never actually posted to the GL, but are unable to remove or reverse. Strangely, I was able to delete the same unposted bank deposits, but the deposit headers still shows as being "posted" even though no entries were created in the GL.

This all happened when I attempted to post a bank deposit that had a fee deducted to a (Account Type) G/L Account line instead of Customer Account, as I have normally been able to post without issue.

I was able to fix the "Error message: The lines of the deposit must belong to the same transaction when posting as lump sum. Please verify that Posting Date, Document Type and Document No. are the same for every line or modify the template used to allow unbalanced documents."

To fix this, you must go to the General Journal Templates, find the Bank Depo template line and uncheck the "Force Doc. Balance" checkbox. The system will still validate the total deposit amount matches the total deposit lines, but now it will allow multiple Document Numbers.

I have not figured out how to fix the other error when recording a bank fee on a Bank Deposit line. My workaround for that was to create a Credit Memo for that customer in the amount of the bank fee. On the Credit Memo, use a G/L Account instead of an Item and enter the bank fee G/L Account. Then make the Bank Deposit for the actual deposit amount (without a bank fee line), then apply the Credit Memo to make the customer account zero.

But let's hope the Business Central Dev Team can fix this in the next update because creating the Credit Memos for all these bank fees is not acceptable.

Was this reply helpful? Yes No
LD-15051834-0 31 on at

Like (0)

Report

CP: thank you for the tip. I tried changing the setting you suggested but I still have an error where it says the batch needs approval. Even though: no approval workflow is set up for this. And I don't even see anywhere to send it for approval.

From your comment it sounds like there is no chance that Microsoft will fix the Bank Deposit problem quickly? I am thinking of changing our process to use the Cash Receipts Journal instead, but it seems ridiculous that I need to do that. We will have to re-write out Jet Reports that pull from Posted Bank Deposits, for example.

Was this reply helpful? Yes No
Suggested answer

Valentin Castravet 31,340 Super User 2025 Season 2 on at

Like (0)

Report

I tried changing the setting you suggested but I still have an error where it says the batch needs approval

Have you checked if you have workflows for the general journal enabled? If you have, and they're not filtered to skip bank deposits or the cash receipt journal, then you will get the error message you're getting.

When you post the bank deposits, the system is actually using the cash receipt journal to post the entries, this is why the workflow can affect it.

You can check in the Workflows page:

For example, if you have a workflow for general journal batches, in the first line highlighted yellow below, do you have a filter to only filter the general journal? If no, the workflow is imposed on all general journals including the cash receipt journal used by the bank deposits.

Valentin Castravet
Work: Zander ERP Services
Blog: Dynamics 365 Business Central Insights
LinkedIn: www.linkedin.com/in/valentin-c-0500a247/

Was this reply helpful? Yes No
Suggested answer

Valentin Castravet 31,340 Super User 2025 Season 2 on at

Like (0)

Report

To post the bank fees, don't enter a negative amount in the credit field. Instead, add the amount field to the page, and enter a positive amount in there. For example:

Valentin Castravet
Work: Zander ERP Services
Blog: Dynamics 365 Business Central Insights
LinkedIn: www.linkedin.com/in/valentin-c-0500a247/

Was this reply helpful? Yes No
LD-15051834-0 31 on at

Like (0)

Report

thank you Valentin. My issues with the workflow are now resolved. I also did this fix explained by CP:

To fix the "Error message: The lines of the deposit must belong to the same transaction when posting as lump sum. Please verify that Posting Date, Document Type and Document No. are the same for every line or modify the template used to allow unbalanced documents." To fix this, you must go to the General Journal Templates, find the Bank Depo template line and uncheck the "Force Doc. Balance" checkbox. The system will still validate the total deposit amount matches the total deposit lines, but now it will allow multiple Document Numbers.

After making that change I am able to post. But the document #s on the Bank Deposit get changed after I post. We have always populated the "document #" on Bank Deposit with the check # or other document # of the customer deposit. Now it is changing it when I post to Business Central #s:

Was this reply helpful? Yes No
Suggested answer

AB-16050158-0 8 on at

Like (0)

Report

Hello,

As an update to this issue, please see some of the below points:

ERROR MESSAGE

"The lines of the deposit must belong to the same transaction when posting as lump sum. Please verify that Posting Date, Document Type and Document No. are the same for every line or modify the template used to allow unbalanced documents."

This comes from an updated version, where a new validation rule was implemented.

When the Post as Lump Sum radio button is activated, Business Central looks at whether the selected Journal Template has the Force Doc. Balance option checked.

If Force Doc. Balance is checked, it confirms whether all deposit lines have the same document number, same document type and same posting date as the Deposit Header. The result is either no errors, or the above error message appears.

ERROR

In certain cases where errors are thrown, the system still posts the Deposit Header, but not the journal entries. This causes the Deposit Header to be unusable and it must be deleted and recreated.

This seems to stem from a COMMIT done in the database in codeunit 1690 that happens what seems to be after creating the Posted Deposit Header, but before the journal batch post.

This would explain why certain error messages (that happen later in the posting process) rolls the system back before the journal entries post, but NOT before posting the Posted Deposit Header -- leaving the Posted Bank Deposit document in the system, but not the related entries.

ERROR

"Force Doc. Balance must be equal to 'Yes' in Gen. Journal Template: Name=***. Current value is 'No'."

If a User attempts to record a fee expense as a Deposit Line (ex. bank fee, document type Empty) with a negative amount under Credit Amount, and adds a Customer entry (ex. payment) with a positive Credit Amount and attempts to post the Deposit (Total Deposit Lines = Total Deposit Amount), the system throws an error, creates the Posted Bank Deposit Header, but does not record GL entries.

This seems to originate from the system completing the first section of this post (see second bold section) before posting the journal lines.

During the journal lines preparation, the system reads journal lines with positive credit amounts or negative debit amounts as "Corrections".

During the posting process, if the Posting Date, Document Type or Document No on a specific line being processed were different than the last "processed" line's information, the system ensures that the Journal Template's "Force Doc. Balance" is set to true.

If the Journal Templat's "Force Doc. Balance" field is false, the system throws an error and before the journal entries post, but NOT before posting the Posted Deposit Header -- leaving the Posted Bank Deposit document in the system, but not the related entries.

This is what I was able to find by analyzing some of the code.

Hopefully this will help someone.

Was this reply helpful? Yes No
JS-23051535-0 6 on at

Like (2)

Report

Hello,

I was able to resolve these issues for our Org following the solution posted by CP

"I was able to fix the "Error message: The lines of the deposit must belong to the same transaction when posting as lump sum. Please verify that Posting Date, Document Type and Document No. are the same for every line or modify the template used to allow unbalanced documents."

To fix this, you must go to the General Journal Templates, find the Bank Depo template line and uncheck the "Force Doc. Balance" checkbox. The system will still validate the total deposit amount matches the total deposit lines, but now it will allow multiple Document Numbers."

In addition, I have needed to remove the No Series from the Bank Deposit Batches for ACH, LOCKBOX, and WIRE by clicking Batches with the Bank Deposit line highlighted while in General Journal Templates. This let our team populate the check numbers and the posted document didn't overwrite these values with the number series.

I hope this helps.

Was this reply helpful? Yes No
JM-23051815-0 2 on at

Like (0)

Report

Since this issue creates invalid Posted Bank Deposit Headers

Anyone with delete permissions, can clean these up by simply printing the Posted Bank Deposit one time. (Preview will not work)
After it has been printed, you can delete.
Note: If users want sequential header nos, the No. Series may also need to be updated.

"No. Printed" is simply a field which is incremented by one every time a user prints the posted deposit header.

Was this reply helpful? Yes No