What this article is about
Real payments are messy: a vendor collects three invoices in one transfer, a client pays an invoice in two instalments, a payment covers most of an invoice but not the last few cents. TaxItEasy handles all of these without forcing you to pretend one payment equals one invoice. This article covers the three mechanisms — manual splits, bundle suggestions, and the one narrow case where a bundle links itself — plus partial payments.
Splitting one transaction across several invoices (web)
On web, you can split a single bank transaction across as many invoices as it actually paid. Open the transaction and allocate an amount per invoice. The editor protects you from the classic mistakes:
- you can't allocate more than the transaction amount,
- you can't mix payment directions (an outgoing payment only allocates to bills you received),
- you can't allocate to the same invoice twice,
- currencies have to line up.
Each invoice can also be unlinked individually later, without disturbing the rest of the split.
On mobile, splits are view-only. The banking screen's Matched filter includes split matches, and invoices show their allocation state — but creating or editing a split happens on web.
Partial payments
When a payment covers between 10% and 95% of an invoice and the payment text carries the invoice number, it becomes a partial-payment suggestion instead of being forced into an all-or-nothing match. The invoice then shows as partially paid with a progress bar (for example "40.00 of 100.00 EUR · 40%") and a "Link another payment" action for the rest. An invoice counts as fully paid with a 1% tolerance, so foreign-exchange drift and rounding cents don't leave invoices stuck at 99%.
Bundle suggestions — "Bundle · N"
When the payment text mentions two or more invoice numbers and those invoices add up to the payment amount (within 5%), the matching inbox shows them as one grouped entry labelled "Bundle · N" instead of N separate guesses. You review the group as a unit: one approve links all member invoices to the payment in a single action; one reject dismisses the whole group.
Bundle suggestions are never auto-matched — a human always confirms them. If the member invoices' dates sit far from the payment date, the suggestion carries an amber caveat ("These invoices sum to the payment, but their dates are far from it — double-check this bundle").
On mobile, a bundle entry opens a review sheet with the member invoices and a sum check, so you can verify the math before approving.
The one bundle that links itself
There is exactly one situation where a multi-invoice link happens without your action, and it's deliberately strict. All of the following must be true:
- all invoices are from the same vendor and share the same invoice date,
- same direction and same currency as the payment,
- each invoice is individually smaller than the payment,
- they sum exactly to the payment amount — no tolerance,
- everything sits within 90 days of the payment,
- and there is exactly one such group — no competing combination.
Anything weaker falls through to normal scoring or a user-confirmed suggestion. And like every automatic match, a silent bundle is visible in the Matched list and fully reversible: unmatching reverts the entire bundle and returns every invoice to its previous state. See why this matched — and how to undo it.
Related
- Why this matched — and how to undo it — explanations, caveats, and the undo paths
- How the matching pipeline works — the scoring behind suggestions
- How matching learns from you — what your confirmations teach the system
- Duplicate uploads and statement repair — when transactions look doubled