8 condition types. Any two data sources. Matched in minutes.
Arvexi match workbooks compare transactions across GL, subledger, bank statement, or any imported data source. Define rules with 8 condition types, from exact matching to Jaro-Winkler fuzzy similarity, and let the engine handle 1:1, 1:N, and N:N matching. Asymmetric tolerance, business calendar date matching, and regex patterns handle the edge cases that break spreadsheet VLOOKUPs.
The problem
You're still matching transactions with VLOOKUP and prayer
Every close, someone exports two files, opens them side by side, and starts matching by hand. Amount looks right. But the date is off by two days. Vendor name is slightly different. One side has a fee that the other doesn't. The VLOOKUP misses it, so your team spends hours hunting for the exceptions. Then they do it again next month.
Match condition types
From exact matches to fuzzy vendor names. All in one rule
EXACT & CONTAINS
Exact matching for reference numbers, invoice IDs, and amounts that must agree precisely. Contains matching for description fields where one source embeds a reference inside a longer string.
FUZZY (Jaro-Winkler)
Match vendor names, descriptions, and text fields with configurable similarity thresholds. 'Acme Corp' matches 'Acme Corporation' at 0.85 similarity. Prefix-weighted algorithm handles legal suffix variations naturally.
TOLERANCE & DATE_RANGE
Absolute tolerance ($5), percentage tolerance (2%), or asymmetric ranges (+$10 / -$0.50) for amounts. Date range matching with business calendar awareness for settlement timing across weekends and holidays.
Match workbooks
Define your matching logic once. Run it every period.
A match workbook defines two data sources, the fields to compare, the condition type for each field, and the tolerance. Set up a workbook for bank-to-GL matching with an amount tolerance of $0.01 and a date range of 3 business days. Set up another for AP subledger matching with exact invoice numbers and fuzzy vendor names. Each workbook runs automatically when new data arrives. No manual exports, no side-by-side spreadsheets.
N:N matching
One payment clearing five invoices? Handled.
Real-world matching isn't always 1:1. A single bank deposit might correspond to five customer payments. A wire transfer might clear three vendor invoices plus a fee. Arvexi's N:N matching engine finds groups of transactions on both sides that sum to the same total within your tolerance. Matched groups are linked together with a single match ID for audit trail clarity. Part of Account Reconciliation. Import data via Data Integration.
Business calendars
Settlement timing across weekends, holidays, and time zones
A payment posted on Friday in New York might not appear on the bank statement until Monday in London. Arvexi's business calendar support handles this natively. Define entity-specific calendars with custom holidays, and the DATE_RANGE condition counts business days, not calendar days. Cross-border matching becomes deterministic instead of guesswork.
We used to spend two full days matching our bank transactions every month. The fuzzy matching on vendor names alone saved us 60% of that time. It catches all the variations we used to hunt for manually.
Senior Accountant
Senior Accountant at Mid-Market Financial Services Company
FAQ
Ready to stop matching transactions by hand?
See how 8 condition types and N:N matching handle the edge cases that break your spreadsheet process. Book a demo with your data.
Book a demo