Match invoices
Records one bank deposit as the payment for 2–100 distinct open invoices, all in this company and the deposit’s currency. Their totals must add up exactly to the deposit. The deposit must be a bank deposit, not a transfer, not split, and not already matched to a different invoice set. All invoices become paid together, with the deposit’s date as paid_date. Each invoice keeps its own revenue categories and recognition dates, including spreads and adjustments. The deposit’s accounting date becomes the earliest invoice date and its category becomes that invoice’s category (date ties use a stable invoice order). One cash entry settles the deposit total on its bank date. Matching the same set again, in any order, returns it unchanged; a different set conflicts. Any refusal leaves every invoice and the deposit unchanged. Every invoice date must satisfy the existing accounting-date bounds: on or after the company’s incorporation date (or two years ago if unset), and before three years from today. An out-of-bounds date returns 409 invoice_operation_failed with the accounting-date reason. Unmatching any invoice reopens every invoice on the payment and returns the deposit to Uncategorized Income on its own date, rather than restoring its previous category. Find candidates with GET /invoices using customer and status=open, then check their totals. Confirm with the user before combining different customers or replacing a categorized deposit. In the app, a grouped deposit’s spread can’t be changed; resolving one grouped invoice’s Stripe date review rebuilds the payment’s entries for every invoice on it. Requires the invoices feature, Invoices: Manage and Transactions: Manage.
Authorizations
API key prefixed with finta_
Path Parameters
Transaction ID with txn_ prefix.
^txn_Body
2 - 100 elements^inv_Response
Every invoice on the payment, in stable order, with the same fields as GET /invoices, including stripe_url when available. This list is not paginated.