Exact matching
Same reference, amount, and date can clear as a clean match.
Reconciliation
Upload two or more datasets, map the columns that identify a match, run deterministic rules, and review only what did not clear.
Try the free missing-transaction checker
Sample preview
Fictional demonstration data. Not a live workspace.
| Reference | Counterparty | Amount | Status | Note |
|---|---|---|---|---|
| ACH-1842 | Harbor Supplies | $1,248.50 | Unmatched | No invoice on the AP file |
| CHK-9921 | Northline Rent | $3,100.00 | Tolerance | Date differs by 2 days |
| WIRE-440 | Westfield LLC | $8,750.00 | Duplicate | Same amount posted twice |
| DEP-2201 | Oak Street Cafe | $86.40 | Matched | Exact amount and date |
Month-end matching is often a new VLOOKUP, a new pivot, and a new risk of a broken formula. AuditExport keeps the original files unchanged and produces a structured result: matched rows, unmatched left and right, duplicates, and items that need a person.
How it works
Step 1
Bring two or more Excel or CSV files. Source files stay stored as uploaded.
Step 2
Identify amount, date, reference, and party columns once.
Step 3
Choose exact keys, optional tolerances, and how duplicates should be treated.
Step 4
The engine matches rows deterministically and records why a row matched or did not.
Step 5
Work unmatched, duplicate, and tolerance items instead of every row.
Step 6
Export results, then save the mapping and rules for the next period.
What this workflow is designed to do with uploaded files.
Same reference, amount, and date can clear as a clean match.
Match on the fields that actually identify the transaction, not on row order.
Combine vendor, invoice number, and amount when one column is not unique.
See repeated amounts or references instead of treating them as a silent double-count.
Each side keeps its own unmatched list so you can see which file is missing the row.
Keep the mapping and rules so next month starts from the last good setup.
Each match or exception can be inspected. The engine does not hide the rule that fired.
A common pair is a bank statement against the cash account in the general ledger, or a vendor statement against an AP export. The same path applies to both: map, run, review exceptions, export.
Example 1
Statement deposit $12,480.00 matches GL receipt $12,480.00 on the same date.
Example 2
Supplier shows INV-4412; AP does not. The row lands as unmatched on the statement side.
The time you save is the time you no longer spend rebuilding the same lookup file. Control comes from a repeatable rule set and a result you can hand to a reviewer without sending the original working spreadsheet.
Continue with the workflows that usually sit next to this one.
Exact, tolerance, fuzzy, partial, 1:N, N:1, and N:N matching with visible rules.
Work the rows that did not match — status, comments, assignment, and history.
Save mappings, matching rules, and workflow setup. Configure once. Reuse next month.
Turn run results into Excel, PDF, and management packs a reviewer can open.
No. You can start with the Excel or CSV exports you already produce.
No. Original uploads stay immutable. Results are stored as a separate run.
Yes. Save the mapping and matching rules as a recipe and apply them to the next period's files.
Start on the free plan. Keep the original spreadsheets unchanged.