Reconciles

How automated reconciliation works, from file to close

Automated reconciliation in Reconciles runs in four steps. It parses your bank statement and second file, normalizes dates, signs and currencies, matches transactions with rules and AI suggestions, and sends whatever does not match to an exceptions queue. Every match has a reason and a confidence score, and nothing reaches your ledger without review.

Your files are processed in your browser and never stored. No card needed.

What you put in

Every run starts with two files. The first is a bank statement in CSV, XLSX, OFX, QFX, MT940 or CAMT.053, or a PDF statement once you have an account. The second is whatever you reconcile it against: open invoices or bills, a ledger export from QuickBooks Online, Xero, NetSuite or Sage, or a payout report from Stripe, PayPal, Adyen, Shopify Payments or Amazon.

Under Options you set the date tolerance (same day, 3 days or 7 days) and the amount tolerance (exact or within 1%). Then you press Reconcile now.

Step 1, Parse

Reconciles reads both files and finds the columns that matter: date, amount or separate debit and credit columns, payee or counterparty, reference, currency and, in payout files, the batch or payout id. Column names differ from bank to bank and system to system, so detection works on the content, not only on the header. The progress screen shows how many lines were read from each file. If a file has no date or amount column, you see a clear message instead of a wrong result.

Step 2, Normalize

Different systems write the same transaction differently. One shows a debit of 1,240.00, the other a payment of -1240. One uses day first dates, the other month first. Payee names carry card numbers, city names and extra spaces. Reconciles brings dates, signs, currencies, payee names and references to one format, so the matching step compares like with like.

Step 3, Match

Matching runs in layers, from the most certain to the least.

  • Exact matches on amount and reference come first.
  • Your saved matching rules run next, such as payee contains, amount range or account.
  • One to many and many to one groups follow: a payout made of many charges, or one transfer that pays several invoices.
  • Amounts within your tolerance and dates within your window come after that, with processor fees and currency conversion taken into account.
  • Fuzzy payee matching and AI suggestions handle the pairs that are still unclear. A suggestion is proposed, never forced.

Every match records why it was made, for example "amount and reference", "payout batch net of fees" or "partial payment", together with a confidence score.

Step 4, Exceptions

Whatever does not match goes to the exceptions queue, sorted by type: unmatched, partial, duplicate, amount difference and date difference. Each item says why it was not matched and by how much it differs. On Growth you can assign exceptions and comment on them, and on Scale you add approvals and a full audit log. Duplicates and missing transactions are detected on both sides, so a payment entered twice in the ledger is caught as surely as a deposit missing from the bank.

Reconcile now

Matching rules and exports

Rules that carry over

When you resolve an exception, you can save the decision as a rule. Rules run before AI suggestions every month, so recurring items match on their own and do not use your suggestion limit. Starter includes 20 rules, Growth and Scale have no rule limit.

Exports for the close

You export the reconciliation report in XLSX or PDF, the matched pairs, and journal entries as CSV for QuickBooks, Xero and NetSuite. Nothing is posted to your ledger until someone on your team has reviewed it. See the integrations page for the step by step guide for each system.

What the demo result page shows

When you run the demo on the home page, your files go through the same four steps and you land on the real result screen. A summary bar shows the match rate, the matched count, exceptions by type and the unexplained difference. The first 10 matched pairs are fully visible with their match reasons. The rest of the matched rows and the exception details are locked until you create an account.

You can still click through filters, the Matched, Exceptions and Duplicates tabs and row details. Opening a locked row, exporting, resolving an exception or adding a rule opens a short signup. After you confirm your email, more rows unlock and your account gets one more sample run of up to 500 lines. Demo files are processed in your browser and never stored.

Automated reconciliation questions

Watch the four steps on your own files

Upload a bank statement and a second file. You see the progress and the first matched pairs before you create an account.