- Home
- Payment Reconciliation Software
- SettlePair
SettlePair
What it is
SettlePair matches bank deposits to invoices using CSV exports in a browser. Its matching is deterministic and rule-based, shows evidence behind each score, and leaves the final decision to the user; it does not use AI. Users can allocate partial payments, split one deposit across invoices, or apply multiple deposits to one invoice. After reviewing matches, they can export the reconciliation as settlepair-reconciliation.csv. Invoice and bank files are parsed in the browser and are not uploaded. An account for working with personal files stores an email address only; payer rules and opted-in saved sessions stay on the user’s device, and saved sessions expire after 30 days. SettlePair does not connect to banks or accounting systems, so users import CSV files and record reviewed results themselves. It supports current desktop versions of Chrome, Edge, Firefox, and Safari, plus the same engines on mobile. Very large files may be limited by device memory. The free beta has no usage limits or subscription tiers, though an account is required to use personal files.
For and against
For
- Uses visible evidence for rule-based matching.
- Handles partial and split payments.
- Exports reviewed reconciliations as CSV.
- Files are parsed in the browser and never uploaded.
- Free beta has no usage limits.
Against
- Does not connect to banks or accounting systems.
- Very large files depend on device memory.
- Saved sessions expire after 30 days.
- Support has no guaranteed response time.
The verdict
SettlePair offers browser-based CSV reconciliation with user-reviewed matches and flexible payment allocation. It is a fit for teams comfortable importing files and recording results manually.
Who it suits
SettlePair is intended for small businesses, bookkeepers, and accounts-receivable teams that reconcile deposits with invoices from CSV exports. It suits users who want to review match evidence and record results themselves rather than connect directly to banking or accounting systems.
Plans and prices
Free reconciliation
Browser-only CSV parsing and scoring · Deterministic matching · Review queue · Partial, grouped and one-to-many allocations
Read 15 Oct 2026 · settlepair.com
On the record
- API and SDKs
- The published product pages describe no public API, SDK or developer integration surface.settlepair.com · read 15 Oct 2026
- Audience
- The pricing page describes the product as intended for small businesses, bookkeepers, and accounts-receivable teams.settlepair.com · read 9 Oct 2026
- Beta status
- SettlePair is described as an independent product in beta built and maintained by James F. Kollie, Jr.settlepair.com · read 15 Oct 2026
- Browser processing
- Parsing, scoring, allocations and export run in the browser tab using JavaScript.settlepair.com · read 15 Oct 2026
- Browser requirements
- Current desktop Chrome, Edge, Firefox and Safari versions are supported, with JavaScript enabled; mobile browsers using the same engines are also listed.settlepair.com · read 15 Oct 2026
- Browser support
- The FAQ lists current desktop versions of Chrome, Edge, Firefox, and Safari, plus the same engines on mobile.settlepair.com · read 9 Oct 2026
- Bulk approval
- Visible suggestions scoring at least 80 can be approved in one confirmed action.settlepair.com · read 15 Oct 2026
- Changelog: August 11 2026
- The August 11, 2026 release added payer-rule memory and opt-in session resume with 30-day expiry.settlepair.com · read 15 Oct 2026
- Changelog: August 18 2026
- The August 18, 2026 release added clearer confidence labels, evidence highlighting, keyboard review controls and the published scoring model.settlepair.com · read 15 Oct 2026
- Column mapping
- Column names are automatically mapped and can be corrected before reconciliation.settlepair.com · read 15 Oct 2026
- Confidence bands
- Scores of 80 or more are labelled Strong evidence, 60–79 Likely, 45–59 Worth a look, and below 45 Not suggested.settlepair.com · read 15 Oct 2026
- CSV inputs
- The invoice file uses invoice number, customer, amount and issue date fields, with due date optional; the bank file uses date, description or reference and amount.settlepair.com · read 15 Oct 2026
- Customer similarity
- Customer-name overlap and edit distance contribute between 10 and 20 points when similarity exceeds the stated floor.settlepair.com · read 15 Oct 2026
- Data handling
- Invoice and bank files are parsed in the browser and are never uploaded; an account for own files stores an email address only.settlepair.com · read 9 Oct 2026
- Date signal
- A plausible payment date contributes between 1 and 10 points, while dates more than 60 days away contribute nothing.settlepair.com · read 15 Oct 2026
- Deterministic matching
- The same two files produce the same scores because matching uses fixed rules rather than statistical or AI models.settlepair.com · read 15 Oct 2026
- Documentation
- Documentation consists of the FAQ, workflow guide, scoring-model page, security page, terms, acceptable-use policy and changelog.settlepair.com · read 15 Oct 2026
- Exact amount signal
- A deposit matching the invoice total to the cent contributes 30 points.settlepair.com · read 15 Oct 2026
