Reconciles

Bank reconciliation API that runs statement matching from your own systems

Reconciles has a bank reconciliation API for finance and engineering teams that want matching to start from their own systems instead of a browser upload. You send a bank statement (CSV, XLSX, OFX, QFX, MT940 or CAMT.053) and a second file or JSON list of ledger, invoice or payout lines, and the API returns a run with match rate, matched pairs, exceptions and the unexplained amount as JSON. The API is part of the Scale plan at $5,988 a year, and you can test the same matching engine on your own files in the browser before you buy.

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

Why teams look for a reconciliation API

Most reconciliation tools are built for a person who logs in once a month. That works until the files are produced by a system. A nightly ERP export, a treasury feed or a payments platform already writes the bank and ledger data to disk, and somebody still downloads it, uploads it and waits.

  • The data already exists in a scheduled job, but a person is the integration layer.
  • Accounting platform APIs read and write ledgers, yet most of them do not expose a matching step you can call, so the comparison still happens by hand.
  • Banking data APIs deliver transactions but stop there. They do not tell you which ledger entry or invoice each line settles.
  • Building a matcher in house looks easy for exact amounts and gets hard at partial payments, payout batches with fees, one payment against three invoices and payees spelled four ways.

A reconciliation API closes that gap: your job sends the two sides, the engine does the pairing, and a reviewer only opens the exceptions.

What the API does, endpoint by endpoint

The API is small on purpose. Three calls cover the job, with a key from Workspace settings sent as a bearer token, JSON in and JSON out, and a limit of 60 requests a minute.

CallWhat it doesWhat comes back
GET /api/v1/accounts Lists the reconciliation accounts the key may use, with their entity Account id, name, kind and entity
POST /api/v1/runs Starts a run for one account from JSON lines or from files sent as base64 Run id, label, line counts, stats (match rate, matched, exceptions, explained, unexplained amount) and a link to the run
GET /api/v1/runs/{id} Reads a finished run Everything above plus every matched pair, every exception and every explained difference

JSON lines carry date, amount, payee and reference, with optional batch (a payout id) and fee per line. Each side takes up to 20,000 lines per run. A run can set a date tolerance of 0 to 15 days and an amount tolerance of up to 5 percent. Files can be up to 5 MB each, and an account's saved column mapping is applied to them the same way it is in the browser, so a format you mapped once keeps working from the API.

The key authenticates with the standard bearer scheme described in RFC 6750. For bank formats, CAMT.053 is the ISO 20022 statement message listed in the ISO 20022 message catalogue, and Reconciles reads its opening and closing balances, as it does for OFX and MT940, unless your request sends its own.

How a nightly reconciliation job works with the API

  1. 01 Create a key

    A workspace member with setup rights on Scale creates a named key in Workspace settings, for example "Nightly upload from our ERP". The key acts with the rights of the person who created it and stops working if that person leaves the workspace.

  2. 02 Pick the account

    Call the accounts endpoint once and store the id of each bank or clearing account you reconcile. Members limited to some entities only see and run those accounts.

  3. 03 Send both sides

    Post the statement file and the ledger, invoice or payout file, or send both as JSON lines. A processor deposit report can go in as a third file, so payouts are tied to the payments inside them.

  4. 04 Read the result

    Read match rate and unexplained amount from the response to decide whether anyone needs to look today. When the number is above your threshold, the job does nothing more. When it is not, the run link goes to the reviewer.

  5. 05 Review exceptions in the browser

    Reviewers open the run, accept AI match suggestions, write reasons and approve. The report and journal entry file come from the same run.

Who uses a bank reconciliation API

  • Finance operations at payments and marketplace companies that reconcile processor payouts against bank deposits every day and want the run to start the moment the files land.
  • Controllers whose ERP already exports a nightly bank and ledger file, who want the match rate in a morning message instead of a manual upload.
  • Accounting firms that prepare files for many clients through one script and give each client its own account and entity.
  • Software teams that need matching inside an internal tool without maintaining a matching engine themselves.
  • Government services contractors paid by agency ACH, who already track bids with a tool for finding and tracking federal contract opportunities, and need each Treasury deposit tied to the invoice it pays.

If no one on the team writes scripts, the SFTP pickup on the same plan does the same job: drop the bank file and the second file with the same name into two folders and the run starts by itself.

What the matching engine catches

  • One payment that settles several invoices, found by searching combinations of open lines from the same payee.
  • Partial and short payments, shown against the invoice with the balance left open.
  • Payout batches where the deposit is net of fees, matched through the batch id and fee fields.
  • Duplicates on either side, listed apart from ordinary exceptions.
  • Amounts in another currency than the rest of the file, labelled as a conversion difference with the rate the two amounts imply.
  • Lines dated after the statement end, carried to the next period instead of shown as errors.

The rules are the same as in the browser, which is what makes the API safe to automate: the same two files give the same result every time. For the engine itself, read the transaction matching software page.

Reconciliation API compared with the other ways to automate it

NeedAccounting platform APIBanking data APIClose suite with integration projectReconciles API
Read bank transactions Some Yes Yes You send them
Match bank lines to ledger, invoices or payouts Rarely exposed No Yes Yes
Return exceptions with reasons No No In the suite Yes, in JSON
Post entries to the ledger Yes No Yes No, you import the reviewed entry file
Time to first run Weeks of build Weeks of build Months with a services team Same day
Published price Varies Per connection Quote $5,988 a year on Scale

The honest limit: Reconciles does not connect to your bank and does not write to your ledger by itself. It is the matching step between two systems you already have. If you need bank feeds and posting in one contract, a close suite such as the ones on our BlackLine alternative page fits better, at a quote based price.

One API run, line by line

A marketplace sends 4,812 bank statement lines and 5,190 payout and invoice lines for October to the runs endpoint with a two day date tolerance. The response says match rate 97, matched 4,661, exceptions 23, explained 128 and unexplained 1,284.17. The job posts the run link to the finance channel because unexplained is above its $500 threshold. The reviewer opens the run and sees that 17 of the 23 exceptions are one processor payout of $12,406.88 that arrived as two deposits on November 1, already in the next period. Three are refunds without a payout id, which an AI suggestion pairs at high confidence. Three are real: a duplicate vendor payment, a chargeback and a deposit with no invoice. Before the API, the same review started with 40 minutes of downloads and uploads.

Which plan includes the API

The API and SFTP pickup are part of Scale at $5,988 a year billed yearly or $999 a month, with 100,000 matched transactions a month across 25 entities, 10,000 AI match suggestions, approvals and an audit log. Starter at $888 a year and Growth at $2,388 a year use the same engine through the browser, so a team can prove the matching on its files first and move to Scale when it automates. Every API run counts against the plan's monthly transactions like a browser run, and the same files matched again in one billing month count once. Full details are on the pricing page.

Bank reconciliation API questions

Run the matching on your own files first

Upload a bank statement and a ledger or payout file in the browser and see the match rate the API would return, before you write a line of code.