private deployment

Enterprise
reconciliation,
deployed for your stack

Reconify is installed inside your infrastructure and configured by our team. Deterministic matching, structured diffs, and a repeatable reconciliation workflow without managing the rollout yourself.

Private deployment
Implementation support
Audit-ready outputs
0records matched
0.0%match rate
0exceptions surfaced
reconciliation engine

From raw exports to structured output

Sources, rules, and output — three stages that run the same way every close period, without spreadsheet drift.

reconify reconciliation runlive
# source mapping
bank.csvbank export
psp-report.csvpayment rails
ledger.jsoninternal truth
transactions.csverp export
normalize: dates, identifiers, amounts
implementation

Three steps to repeatable reconciliation

The deployment starts with your exports and ends with a workflow your finance team can run each close period.

01source mapping

Connect Your Sources

Bring bank exports, PSP reports, ledgers, and internal files into one reconciliation workflow.

02rule config

Configure Rules

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

03automated run

Reconcile Automatically

Run deterministic matching and review structured diffs instead of rebuilding spreadsheets.

demo

See Reconify in action

Watch how Reconify handles multi-source reconciliation — from raw exports to structured, audit-ready output.

capabilities

Deployment features for repeatable reconciliation

Built for finance and engineering teams that value accuracy, repeatability, and clear operational evidence.

matching

Automated Matching

Rules match transactions across exports and systems without spreadsheet drift between runs.

sources

Multi-Source Integration

Bank exports, payment processor reports, ERP ledgers, and CSV files move through the same workflow.

audit

Audit Trail

Structured outputs show each match, exception, tolerance, and reconciliation result.

exceptions

Exception Alerts

Missing, duplicate, timing, and amount issues surface as labeled records for finance review.

dashboard

Finance Dashboard

Enterprise teams can monitor runs, review results, and track reconciliation work in one place.

workflow

Team Collaboration

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

audit output

Structured, audit-ready results

Every run produces labeled output — matched records, exceptions by type, and metrics ready for finance review or downstream export.

audit_output run_20241201
total records
1,261,210
matched
1,260,142
exceptions
68
run id
run_20241201
statussourcetargetcount
matchedbank.csvledger.json1,260,142
missingpsp-report.csv3
duplicatebank.csvbank.csv42
timing gappsp-report.csvledger.json18
amount issueledger.jsonbank.csv5
open source cli

Or if you have a dev team, they can run it directly.

The open-source Reconify CLI runs the same deterministic engine without the dashboard. Your engineers can script reconciliation runs, pipe JSON output into downstream systems, and embed audit trails into your existing CI or finance automation.

  • Same matching engine 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
terminalreconify v0.1.1
# Install
$go install github.com/reconifyhq/reconify/cmd/reconify@latest
# Validate your config
$reconify config validate
# Check a source file 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 output with audit trail
$reconify reconcile --pair bank-ledger --audit --deterministic --out results.json
run_id: a154af3a, sha256 embedded, output saved to results.json
faq

Frequently asked questions

Deployment boundaries, source mapping, and implementation scope for finance and engineering teams.

How does Reconify handle complex matching scenarios?

Reconify uses configurable matching rules, identifiers, date windows, and amount tolerances to compare records across sources. The output labels matches, missing records, duplicates, timing gaps, and amount issues.

What integrations does Reconify support?

Reconify supports workflows built from bank exports, payment processor reports, accounting ledgers, manual CSV uploads, and internal APIs. The implementation maps each source into the same reconciliation engine.

Is financial data sent to a hosted Reconify service?

Reconify runs inside your infrastructure for private deployments. Files, logs, and outputs stay within the boundary your team chooses.

How long does implementation take?

Implementation depends on the number of sources, export formats, and rules. A first run usually starts with mapping source columns, configuring match logic, and reviewing the structured output.

Can I customize matching rules?

Yes. Teams can define matching logic, tolerance levels, source mappings, and exception handling to match their reconciliation workflow.

ready to ship

Make reconciliation repeatable.

Talk through your source systems, matching rules, deployment boundary, and first reconciliation workflow with the Reconify team.