- Invoice number or invoice ID
- Customer ID + invoice number
- Date + amount only as a reviewed fallback
Accounts receivable workflow
Merge Invoices with Payments
Reconcile invoice and payment exports without copying formulas across columns. A strong invoice reference is usually the best key; keep unmatched rows when the goal is to spot unpaid invoices or unallocated payments.
🔒 Local processing for normal jobsLive match reach
Recommended setup
Keep Everything preserves both unpaid invoices and payments that do not map to an invoice.
Use Master + Enrich when you only need to keep the invoice list and add payment details where matches exist.
How to reconcile the files
- Add the invoice and payment exports and choose the data sheets.
- Choose Keep Everything for a full reconciliation or Master + Enrich for invoice-focused reporting.
- Map the invoice reference. Add customer ID as a second field if the same invoice number can occur in multiple accounts.
- Review duplicates, many-to-many warnings and unmatched rows before exporting.
Partial payments can create several payment rows for one invoice. That may be correct; do not automatically treat repeated invoice references as bad data.
Common reconciliation issues
One invoice can match several payments and legitimately expand into multiple rows.
Amounts repeat often and should not be used alone as an identifier.
Prefixes and leading zeros can make invoice references look different across exports.
🔒
Normal spreadsheet jobs stay local.
Your invoice and payment contents are processed in the browser for normal jobs.
Build the reconciliation workbook
See matched and unmatched records before downloading a new Excel file.
Open MergeStudio →Confirm that the invoice reference has the same meaning in both files. Date and amount combinations should be manually reviewed when used as a fallback.