Prerequisites
- A DualEntry role with permission to match bank transactions. Matching has its own permission, separate from editing the underlying record, so a role that can edit a journal entry or bill doesn’t automatically have matching rights, and vice versa. Admin, Controller, and Accountant have this permission by default, but it’s configurable, so check with your Admin if you’re not sure.
- Every bank feed transaction and GL entry you want to match is already visible on the To Match tab of the Bank Match page.
Match a single pair
- On the To Match tab, select a bank feed transaction and the GL entry it settles.
- Choose Match.
Match multiple legs
A match doesn’t have to be one bank transaction to one GL entry. DualEntry supports one-to-many, many-to-one, and many-to-many matches, so you can match one deposit against several GL entries, or several bank feed lines against a single entry, in one action. Use this when a single real-world transaction, like a payroll run or a batched deposit, shows up as multiple lines on one side but not the other.- On the To Match tab, select every bank feed transaction and GL entry involved in the match, on both sides.
- Choose Match.
- All items must belong to the same bank or credit card account, and their currency must match the currency of the GL account that bank account is connected to.
- The bank transaction amounts and the matched GL entry amounts must net to the same total, rounded to the cent. DualEntry doesn’t convert between currencies or apply any other tolerance.
- When you group multiple bank transactions into one match, they must all carry the same sign: all debits or all credits. This check doesn’t apply to the GL entries on the other side; their balance is enforced by the amount rule instead.
Matching records a reconciliation link between the items you selected. It doesn’t create, post, or otherwise change anything in the general ledger, and it doesn’t require the GL entry to be posted first: an unposted draft entry matches the same way a posted one does, unless it’s actively routed through an approval workflow (see below).
If the match needs approval
If the GL entry you’re matching is a draft still awaiting approval, such as an unposted journal entry or bill sitting in a pending approval workflow, the match doesn’t land on the Matched tab right away. It’s created on the For Approval tab instead, with its own Approve, Reject, and Unmatch actions:- Approve the underlying record and the match moves to Matched, the same as any other match.
- Reject the underlying record and the match stays on the For Approval tab; rejecting doesn’t unmatch it automatically. Choose Unmatch there to send the items back to unmatched.
Undo a match
- On the Matched tab, choose Unmatch next to the match you want to undo.
- The bank transactions revert to unmatched and re-enter the suggestion pipeline, so a rule or Bank Match AI can pick them up again on a later pass.
- Unmatching one side of a bank transfer unmatches the other side too.
- For a multi-leg match, unmatching any one leg dissolves the entire match group. You can’t unmatch a single leg while leaving the rest of the group matched.
What’s next
- New to Bank Match? Start with Your First Bank Match for the core matching loop.
- Match not behaving the way you expect? See Common Errors with Bank Match.
- Read Bank Match AI for how suggested matches are generated in the first place.
- Follow Reconciliation for the full monthly workflow this fits into.