Skip to main content
Matching pairs a bank feed transaction with the GL entry it settles. Rules and Bank Match AI apply most matches for you; this guide covers matching by hand, whether that’s a simple one-to-one pair or a multi-leg match spanning several items on either side.

​
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

  1. On the To Match tab, select a bank feed transaction and the GL entry it settles.
  2. Choose Match.
The pair moves to the Matched tab.

​
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.
  1. On the To Match tab, select every bank feed transaction and GL entry involved in the match, on both sides.
  2. Choose Match.
All selected items move to the Matched tab as a single match group. DualEntry validates a few things before letting a match go through:
  • 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; the amount rule enforces their balance 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. DualEntry creates it 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

  1. On the Matched tab, choose Unmatch next to the match you want to undo.
Unmatching has a few consequences worth knowing before you do it:
  • 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.

​
Exclude a transaction from Bank Match

Excluding takes a bank statement line or a DualEntry transaction out of Bank Match without matching it. Use it for an item that will never have a counterpart, such as a duplicate feed line. Excluded items can’t be matched and no longer get Bank Match AI suggestions. Excluding needs both bank_match:edit and bank_match:archive on your role.
  1. On the To Match tab, select the items to exclude. To select every item in a long list, choose Load all first, then select the header checkbox.
  2. Choose Exclude, or press Shift+Delete.
The items move to the Excluded tab right away; there’s no confirmation step. You can also exclude from the Auto tab: selecting suggestions there and choosing Exclude excludes both the bank statement line and the DualEntry transaction it was suggested against. DualEntry also excludes some transactions automatically: anything dated before your bank-match start date, and duplicates it detects from another connected account.

​
Include an excluded transaction

Including returns an excluded item to Bank Match so it can be matched. Including needs bank_match:edit on your role.
  1. On the Excluded tab, find the item under Bank Statement Lines or DualEntry Transactions.
  2. Select it and choose Include.
The item returns to the To Match tab, and any rule that applies to it flags it again. Including doesn’t rerun Bank Match AI, so match the item by hand or with a rule. A transaction dated before your bank-match start date stays included even if you later unmatch it; see Common Errors with Bank Match.

​
What’s next

Last modified on October 15, 2026