Description
When attempting to reconcile bank transactions in the Mint App / Unreconciled Transactions view, the "Match" column displays the aggregated total of a Journal Entry for a specific bank account, rather than the individual transaction rows that were actually posted to the GL Entry (General Ledger).
This causes a major issue for payroll or batch payment workflows where a single Journal Entry contains multiple separate bank transfers.
Context & Concrete Example
When paying employees, it is standard accounting practice to create 1 single Journal Entry, but add multiple rows for the same bank account because the employees receive separate wire transfers.
Imagine a single Journal Entry created for Payroll:
- Row 1: Credit "Bank Account" for $300.00 (Payment to Employee A)
- Row 2: Credit "Bank Account" for $600.00 (Payment to Employee B)
- Row 3: Debit "Salary Payable" for $900.00
In the ERPNext General Ledger, this correctly reflects as two distinct entries for the Bank Account (-$300.00 and -$600.00).
On the real-world Bank Statement, this also appears as two separate withdrawals ($300.00 and $600.00).
Actual Behavior
In the Unreconciled Transactions view, the application groups the rows by the parent document (the Journal Entry) and shows a single matchable amount of $900.00 for the bank account. Because the actual bank statement shows the individual amounts ($300 and $600), the user cannot reconcile the lines.
Expected Behavior
The Unreconciled Transactions view should fetch and display matchable amounts based on the individual General Ledger entries (GL Entry) rather than grouping them by the Journal Entry document total. In the example above, it should display one matchable option for $300.00 and another for $600.00 so they can be matched individually to the bank statement lines.
Steps to Reproduce
- Create a
Journal Entry.
- Add at least two separate rows that Credit (or Debit) the same Bank Account (e.g., Row 1: $300, Row 2: $600). Balance the entry with an expense/payable account.
- Submit the Journal Entry.
- Check the standard General Ledger report: observe that it correctly shows two separate GL entries for the bank account.
- Go to the Mint App / Unreconciled transactions view for that bank account.
- Observe that the "Match" column only offers the aggregated total ($900) instead of the individual lines.
Description
When attempting to reconcile bank transactions in the Mint App / Unreconciled Transactions view, the "Match" column displays the aggregated total of a
Journal Entryfor a specific bank account, rather than the individual transaction rows that were actually posted to theGL Entry(General Ledger).This causes a major issue for payroll or batch payment workflows where a single Journal Entry contains multiple separate bank transfers.
Context & Concrete Example
When paying employees, it is standard accounting practice to create 1 single Journal Entry, but add multiple rows for the same bank account because the employees receive separate wire transfers.
Imagine a single Journal Entry created for Payroll:
In the ERPNext General Ledger, this correctly reflects as two distinct entries for the Bank Account (
-$300.00and-$600.00).On the real-world Bank Statement, this also appears as two separate withdrawals (
$300.00and$600.00).Actual Behavior
In the Unreconciled Transactions view, the application groups the rows by the parent document (the
Journal Entry) and shows a single matchable amount of$900.00for the bank account. Because the actual bank statement shows the individual amounts ($300 and $600), the user cannot reconcile the lines.Expected Behavior
The Unreconciled Transactions view should fetch and display matchable amounts based on the individual General Ledger entries (
GL Entry) rather than grouping them by theJournal Entrydocument total. In the example above, it should display one matchable option for$300.00and another for$600.00so they can be matched individually to the bank statement lines.Steps to Reproduce
Journal Entry.