Bank Statement Reconciler

Match bank transactions against ledger entries and flag what is missing on either side, so a reconciliation is reviewed rather than rebuilt by hand.

What it does

Takes a bank statement and an internal ledger and reports, per transaction, whether the two agree. Each row carries both amounts and the difference, so the entries that need attention sort to the top.

Output fields

Field	Description
transactionId	Identifier of the transaction.
status	The reconciliation outcome for this transaction.
currency	Three-letter ISO 4217 currency code.
ledgerAmount	The amount recorded in the ledger.
bankAmount	The amount recorded by the bank.
difference	Bank amount minus ledger amount.
ledgerLines	How many ledger lines matched.
bankLines	How many bank lines matched.

Sample output

{
  "transactionId": "txn_771",
  "status": "amount_mismatch",
  "currency": "GBP",
  "ledgerAmount": 1250.0,
  "bankAmount": 1245.5,
  "difference": -4.5,
  "ledgerLines": 1,
  "bankLines": 1
}

Use cases

• Month-end reconciliation review.
• Finding the transactions present on one side only.
• Producing an exceptions list a finance team can clear.

Pricing

Pay per event: charged per transaction row written, plus a near-zero start event.

FAQ

Does it post entries or change my ledger?

No. It reads what you supply and reports differences. It writes nothing back.

How are amounts compared?

As canonical values, not formatted strings, so 1,250.00 and 1250.00 are the same number.

What if a transaction appears twice?

Duplicated lines are reported as their own finding rather than silently merged, because a double posting is exactly what you are looking for.

A note on what reconciliation here means

This Actor does not decide that your books are correct. It reports, transaction by transaction, where the bank and the ledger disagree, and it leaves the accounting judgement to whoever owns the books. That is deliberate: an Actor that silently "fixed" a mismatch would be producing a number nobody could audit.

Related Actors

• Invoice Aging Report
• CDR Invoice Reconciler

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Bank Statement Reconciler declares all 5 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Bank Statement Reconciler include ledgerAmount, bankAmount, difference, ledgerLines and bankLines.
• Bank Statement Reconciler needs no API key, login or account of any kind before its first run.
• Every one of Bank Statement Reconciler's 3 inputs is optional, so it runs with no configuration at all.
• Every number published about Bank Statement Reconciler is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Bank Statement Reconciler is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

Limitations

• Bank Statement Reconciler reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.