Payment reconciliation software

Automated payment reconciliation for finance ops

Reconify matches bank deposits, PSP reports, fees, refunds, payouts, and ledger records. Finance teams get reconciliation exceptions and audit-ready records without rebuilding close work in spreadsheets.

Get started See how it works

Private financial data

Implementation support

Audit-ready records

Documentation →·GitHub →

reconifyhq.com/results/a154af3a

Reconify

Reconciliation results

← New Reconciliation

Reconciliation Results

bank.csv vs ledger.json

Export Unmatched

Cleared rate

97.2%

1,224,858 of 1,260,142 transactions cleared

Source volume

1,260,210

685,320 left source, 574,890 right source

Open items

2 left, 1 right

Review items

5 amount, 18 timing, 42 duplicate

Cleared1,224,858

Open items3

Amount variances5

Timing variances18

Duplicates42

Export

Left sourceRight sourceStatus

REF-29183

$4,244.49

May 10, 2024

Stripe payout

REF-29183

$4,244.49

May 10, 2024

Stripe payout

Cleared

REF-41023

$1,665.72

Apr 9, 2024

Invoice #8821

REF-41023

$1,665.72

Apr 9, 2024

Invoice #8821

Cleared

Reconciliation workflow

close run

Sources

Bank, PSP, ERP, ledger

Rules

IDs, dates, tolerances

Exceptions

Unmatched and variances

Audit

Review-ready records

0transactions matched

0.0%match rate

0exceptions flagged

payment reconciliation workflow

From bank and PSP reports to reconciled records

Source data, matching rules, and exception reports run the same way every close period, without spreadsheet drift.

reconify reconciliation runlive

payment data mapping

bank.csvbank export

psp-report.csvpayment rails

ledger.jsoninternal truth

transactions.csverp export

→ normalize: dates, identifiers, amounts

close workflow

Three steps to repeatable payment reconciliation

The implementation starts with your bank, PSP, ERP, and ledger data. It ends with a workflow finance can run each close period.

Connect Payment Data

Bring bank statements, PSP reports, ERP exports, ledger records, and internal files into one workflow.

BankPSPERPLedgerCSV

Set Matching Rules

Set identifiers, date windows, amount tolerances, and exception categories for repeatable reconciliation.

Date window3 days

Amount tolerance±0.01%

Review Exceptions

Run transaction matching and review unmatched items, timing differences, and amount variances.

Unmatched item

Timing difference

Amount variance

finance operations capabilities

Payment reconciliation controls for finance operations

Built for teams that need transaction matching, exception management, close evidence, and private handling of financial data.

Rules-Based Transaction Matching

Configurable rules match bank, PSP, ERP, and ledger transactions without spreadsheet drift between runs.

Bank, PSP, ERP, and Ledger Data

Bank statements, payout reports, ERP exports, ledger records, and CSV files move through one workflow.

Audit-Ready Reconciliation Records

Each run records matches, unresolved exceptions, tolerance rules, and reconciliation results.

Exception Management

Unmatched items, duplicates, timing differences, and amount variances surface for finance review.

Finance Review Workspace

Finance teams monitor runs, review exceptions, and track reconciliation work in one place.

Private Financial Data Controls

Finance and engineering share a repeatable workflow with clear ownership and access controls.

Reconciliation Run · Q1 2026

total records

1,261,210

matched

1,260,142

exceptions

period

Q1 2026

statusdata sourcescount

matchedBank → Ledger1,260,142

missingPSP Report3

duplicateBank Statement42

timing gapPSP Report → Ledger18

amount issueLedger → Bank5

audit trail

Audit-ready reconciliation records

Every run records matched transactions, unresolved exceptions, variance categories, and review metrics for finance handoff or downstream export.

product tour

See payment reconciliation in Reconify

Watch how Reconify reconciles payment data across sources, flags exceptions, and produces audit-ready records for finance review.

Developer teams can run the payment reconciliation CLI directly.

The open-source Reconify CLI runs the same rules-based matching workflow without the dashboard. Engineers can script payment reconciliation runs, pipe exception reports into downstream systems, and embed audit trails into existing finance automation.

Same transaction matching rules as the managed platform
JSON, NDJSON, CSV, and table output formats
Audit-ready output with SHA-256 file hashes and run provenance
Streaming mode for large files without memory pressure

View on GitHub →Read the docs →

terminalreconify v0.1.1

# Install

$go install github.com/reconifyhq/reconify/cmd/reconify@latest

# Validate your config

$reconify config validate

# Check a bank statement matches your schema

$reconify config check-source --source bank --file export.csv

# Run a reconciliation

$reconify reconcile --pair bank-ledger

✓ matched 1,260,142 records in 4.32s

# JSON exception report with audit trail

$reconify reconcile --pair bank-ledger --audit --out results.json

✓ run_id: a154af3a, sha256 embedded, output saved to results.json

faq

Frequently asked questions

Data sources, transaction matching, exception review, and private deployment for finance operations teams.

How does Reconify handle complex payment matching scenarios?

Reconify uses configurable matching rules, identifiers, date windows, and amount tolerances to compare bank, PSP, ERP, and ledger records. The output labels matched transactions, unmatched items, duplicates, timing differences, and amount variances.

What integrations does Reconify support?

Reconify supports workflows built from bank statements, payment processor reports, ERP exports, manual CSV uploads, and internal ledgers. The implementation maps each data source into the same reconciliation process.

Is financial data sent to a hosted Reconify service?

Reconify runs inside your infrastructure for private deployments. Files, logs, and reconciliation records stay within the environment your team approves.

How long does implementation take?

Implementation depends on the number of data sources, export formats, and reconciliation rules. A first run usually starts with mapping bank, PSP, ERP, and ledger fields, configuring transaction matching, and reviewing the exception report.

Can I customize matching rules?

Yes. Teams can define matching rules, tolerance levels, data mappings, and exception handling to match their payment reconciliation workflow.

Automate payment reconciliation for close.

Talk through your bank, PSP, ERP, and ledger data, matching rules, exception review, and private deployment needs with the Reconify team.

Get started View GitHub