SettlePair
settlepair.com
What it is
SettlePair is a free browser tool that matches bank deposits to invoices from CSV exports. Its deterministic, rule-based scoring shows the evidence behind each result and leaves the final match decision to the user; it does not use AI. Payment exceptions can be handled by allocating partial payments, splitting one deposit across invoices or applying several deposits to one invoice. After review, users export a file named settlepair-reconciliation.csv. Invoice and bank files are parsed in the browser and never uploaded. An account for personal files stores an email address only. Payer rules and opted-in saved sessions stay on the user’s device, with saved sessions expiring after 30 days. SettlePair does not connect to banks or accounting systems, so users import CSV exports and record reviewed results themselves. It supports current desktop Chrome, Edge, Firefox and Safari, plus the same browser engines on mobile. Very large files depend on available device memory. The product targets small businesses, bookkeepers and accounts-receivable teams. Its beta plan costs nothing, with no subscription tiers or usage limits.
Spec sheet
- What it does
- SettlePair matches bank-deposit CSV records to open-invoice CSV records and lets users review the proposed matches.Read 15 Oct 2026 · settlepair.com
- Purpose
- SettlePair matches bank deposits to invoices using CSV exports and leaves match decisions to the user.Read 9 Oct 2026 · settlepair.com
- Audience
- The pricing page describes the product as intended for small businesses, bookkeepers, and accounts-receivable teams.Read 9 Oct 2026 · settlepair.com
- Integrations
- SettlePair has no bank or accounting-system connection and does not post entries to Xero, QuickBooks or other ledgers.Read 15 Oct 2026 · settlepair.com
- Support
- Support is provided by email and is best-effort without a guaranteed response time or service-level commitment.Read 15 Oct 2026 · settlepair.com
- Maker
- SettlePair is an independent product built and maintained by James F. Kollie, Jr.Read 9 Oct 2026 · settlepair.com
- API and SDKs
- The published product pages describe no public API, SDK or developer integration surface.Read 15 Oct 2026 · settlepair.com
- Beta status
- SettlePair is described as an independent product in beta built and maintained by James F. Kollie, Jr.Read 15 Oct 2026 · settlepair.com
- Browser processing
- Parsing, scoring, allocations and export run in the browser tab using JavaScript.Read 15 Oct 2026 · settlepair.com
- Browser requirements
- Current desktop Chrome, Edge, Firefox and Safari versions are supported, with JavaScript enabled; mobile browsers using the same engines are also listed.Read 15 Oct 2026 · settlepair.com
- Browser support
- The FAQ lists current desktop versions of Chrome, Edge, Firefox, and Safari, plus the same engines on mobile.Read 9 Oct 2026 · settlepair.com
- Bulk approval
- Visible suggestions scoring at least 80 can be approved in one confirmed action.Read 15 Oct 2026 · settlepair.com
- Changelog: August 11 2026
- The August 11, 2026 release added payer-rule memory and opt-in session resume with 30-day expiry.Read 15 Oct 2026 · settlepair.com
- Changelog: August 18 2026
- The August 18, 2026 release added clearer confidence labels, evidence highlighting, keyboard review controls and the published scoring model.Read 15 Oct 2026 · settlepair.com
- Column mapping
- Column names are automatically mapped and can be corrected before reconciliation.Read 15 Oct 2026 · settlepair.com
- Confidence bands
- Scores of 80 or more are labelled Strong evidence, 60–79 Likely, 45–59 Worth a look, and below 45 Not suggested.Read 15 Oct 2026 · settlepair.com
- 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.Read 15 Oct 2026 · settlepair.com
- Customer similarity
- Customer-name overlap and edit distance contribute between 10 and 20 points when similarity exceeds the stated floor.Read 15 Oct 2026 · settlepair.com
- 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.Read 9 Oct 2026 · settlepair.com
- Date signal
- A plausible payment date contributes between 1 and 10 points, while dates more than 60 days away contribute nothing.Read 15 Oct 2026 · settlepair.com
- Deterministic matching
- The same two files produce the same scores because matching uses fixed rules rather than statistical or AI models.Read 15 Oct 2026 · settlepair.com
- Documentation
- Documentation consists of the FAQ, workflow guide, scoring-model page, security page, terms, acceptable-use policy and changelog.Read 15 Oct 2026 · settlepair.com
- Exact amount signal
- A deposit matching the invoice total to the cent contributes 30 points.Read 15 Oct 2026 · settlepair.com
- Export
- The reviewed output is exported as settlepair-reconciliation.csv with allocation, decision, confidence and evidence fields.Read 15 Oct 2026 · settlepair.com
- File limits
- Very large files are limited by the available memory on the user's device.Read 9 Oct 2026 · settlepair.com
- File separators
- Comma-, semicolon- and tab-separated files are supported.Read 15 Oct 2026 · settlepair.com
- Grouped allocations
- Users can split one deposit across several invoices, apply several deposits to one invoice, or leave money unapplied.Read 15 Oct 2026 · settlepair.com
- Integer-cent arithmetic
- Amounts and allocations are stored in integer cents to prevent rounding drift.Read 15 Oct 2026 · settlepair.com
- Invoice digits signal
- A numeric invoice core of at least four digits in the bank description contributes 45 points.Read 15 Oct 2026 · settlepair.com
- Invoice reference signal
- A full invoice reference in the bank description contributes 55 points to the score.Read 15 Oct 2026 · settlepair.com
- Large-file limit
- Very large files are constrained by the memory available on the user's device.Read 15 Oct 2026 · settlepair.com
- Licence
- The terms grant a personal, non-exclusive, non-transferable and revocable use licence and state that the underlying code is owned by the operator or licensors.Read 15 Oct 2026 · settlepair.com
- Limit: accounting accuracy
- The product disclaims accounting accuracy and requires users to check every result before posting it.Read 15 Oct 2026 · settlepair.com
- Limit: local-storage expiry
- Opt-in saved sessions expire after 30 days and local data depends on the device and browser storage.Read 15 Oct 2026 · settlepair.com
- Limit: manual workflow
- Users must obtain bank exports themselves and record the reviewed reconciliation in their accounting system.Read 15 Oct 2026 · settlepair.com
- Maker legal details
- The terms say the operating entity and governing jurisdiction have not yet been finalised.Read 15 Oct 2026 · settlepair.com
- Matching
- Its matching is deterministic and rule-based, with visible evidence behind each score; it does not use AI.Read 9 Oct 2026 · settlepair.com
- No uploads
- Invoice and bank files are not uploaded to SettlePair servers.Read 15 Oct 2026 · settlepair.com
- Partial payments
- A part payment leaves the invoice with a remaining balance and is not marked settled.Read 15 Oct 2026 · settlepair.com
- Payer rules
- Users can save payer-description rules locally and export, import or erase those rules.Read 15 Oct 2026 · settlepair.com
- Payment exceptions
- Users can allocate partial payments, split one deposit across invoices, or apply several deposits to one invoice.Read 9 Oct 2026 · settlepair.com
- Review queue
- Users can search by invoice, customer or bank description and filter or sort suggestions.Read 15 Oct 2026 · settlepair.com
- Saved data
- Payer rules and opted-in saved sessions stay on the user's device, and saved sessions expire after 30 days.Read 9 Oct 2026 · settlepair.com
- Security architecture
- The product has no upload endpoint or server-side database for reconciliation data; accounts hold an email address only.Read 15 Oct 2026 · settlepair.com
- Security limits
- SettlePair claims no certification, audit, formal compliance programme or uptime commitment.Read 15 Oct 2026 · settlepair.com
- Security reporting
- There is no bug bounty and no legal safe harbour for security testing.Read 15 Oct 2026 · settlepair.com
- Self-hosting
- The service is offered as a hosted browser workbench; the terms do not grant access to underlying code or describe self-hosting.Read 15 Oct 2026 · settlepair.com
- Session resume
- Opt-in saved sessions preserve rows and decisions locally and expire after 30 days.Read 15 Oct 2026 · settlepair.com
Plans and prices
Strong points and limits
Strong points
- Deterministic matching with visible evidence
- Handles partial and split payments
- Browser parsing keeps files unuploaded
- Exports reviewed reconciliation CSV
- No subscription tiers or usage limits
Limits
- No bank or accounting-system connections
- Very large files depend on device memory
- Support is best-effort by email
- Saved sessions expire after 30 days
Who it suits
It suits small businesses, bookkeepers and accounts-receivable teams reconciling CSV exports. Users who want browser-only processing and visible, user-controlled matching may prefer its approach.
Verdict
SettlePair offers a straightforward CSV reconciliation workflow with local browser processing and explicit user decisions. Its lack of direct integrations means the reviewed output must be recorded elsewhere.
Where Specifiction places it
- Payment Reconciliation Software#8 of 297.9