Product data — DupProof

The complete product data

Everything DupProof 1.0.0 does, how it does it, and what it needs — the same facts that ship in the box. No marketing fog: if a capability is not listed here, the product does not claim it.

Version

1.0.0 (11 November 2026) — first release

Size

~4.5–4.9 MB download per platform; single self-contained application file; ~20 MB on disk

Platforms

Windows 10/11 (64-bit) · macOS Intel & Apple silicon · Linux x86-64

Requirements

No admin rights, no database server, no runtime to install. A web browser is used for the local workbench UI. Works fully offline, including on air-gapped machines.

Data storage

One local SQLite database file, in a folder you choose. Back it up like any file.

Network

None. The application makes no network requests and binds its local UI to 127.0.0.1 only. (Verified by source audit and runtime socket inspection.)

The seven duplicate classes

Class	How it happens in real AP	What the engine checks
Exact duplicate	The same bill is keyed or imported twice and paid twice.	Same vendor + invoice number + amount, any dates.
Invoice-number typo	A digit is mis-keyed or transposed (1023 vs 1028), defeating ERP exact-match checks.	Edit distance 1–2 including transpositions, with amount/date/vendor evidence.
Tax-rate variance	One entry is gross, the other net of VAT/GST/sales tax.	Amount pairs related by standard tax rates (5/10/15/20%, 1% tolerance).
Vendor-name variant	"Acme Ltd" vs "ACME LIMITED"; "Müller" vs "Muller"; "A.C.M.E." vs "ACME".	Canonical vendor matching: case, legal suffixes, punctuation, diacritics and initialisms folded.
Cross-period double	A bill paid in March is paid again in May after a query or resubmission.	Matches are not limited to a date window for strong evidence; weaker matches decay with distance.
Format variants	INV/2026/001 vs INV-2026-001; 0012345 vs 12345.	Invoice-number normalisation removes separators and leading zeros before comparison.
Split-plus-full overpayment	Instalments are paid against a bill — then the full amount is paid again.	Payment groups are totalled against the register bill; overpayment is flagged at group level.

Two guards keep legitimate patterns quiet: recurring series (rent, subscriptions) are recognised and suppressed, and instalments that together settle a bill exactly are never flagged. Every finding lists the rules that fired, in plain language. Sequential invoices with identical amounts (e.g. 5001 and 5002) can still be flagged for review — deliberately: a bill entered twice with a typo produces the same pattern, and a missed duplicate costs more than a one-click dismissal (your dismissal is remembered permanently).

Import specification

Formats: CSV (comma-delimited, UTF-8/BOM, CRLF) and XLSX.
Kinds: invoice register, payments, bank statement lines, GL control totals, receipts (AR), AR invoices.
Mapping: QuickBooks and Xero presets; automatic header detection; manual mapping remembered per company by header fingerprint.
Amounts: currency symbols, thousands separators, EU decimal format (1.234,56), negative amounts, values in cents where the export says so.
Dates: ISO and common local formats; ambiguous slash-dates are counted and disclosed, never silently guessed.
Quality: bad rows are rejected individually with reasons (bad amount, impossible date, missing vendor); re-importing the same file is idempotent — nothing double-counts.

Modules in detail

Duplicate Payment Audit

Payments audit + register (double-entered bill) audit
Orphan payments — paid with no register entry
At-risk totals: pending vs confirmed
Dispositions: confirmed / valid / vendor contact, with notes and a full audit trail that survives re-runs

Close Reconciliation

Subledger vs GL control vs bank
GL difference with an explicit scope note
Exceptions: payment without invoice · aged unpaid invoices · bank lines unmatched · payments not on statement

Cash Application

Rule order: reference-exact → reference-partial → split (receipt = two invoices) → unique amount per customer → 1% tolerance
Overpayments capped at open balance and flagged
Unapplied cash listed openly — never force-matched

Reports

Findings report (PDF + XLSX): every finding with its evidence and fired rules, a per-vendor recovery list (who owes you what), and the disposition audit trail.
Reconciliation report (PDF + XLSX): totals, GL difference, exception categories with ageing.
Cash application report (PDF + XLSX): applied/unapplied per receipt; spreadsheet money cells are true numbers, not text.

Measured performance

200,000 payments: import ≈ 3.0 s, audit ≈ 2.3 s (measured on a modest cloud VM).
Planted-corpus benchmark (207,714 payments with embedded duplicates): audit ≈ 1.5 s; recall 100%, precision 95.3%, zero false positives on the clean control corpus.
Benchmarks use synthetic corpora built from documented real-world duplicate patterns. Accuracy on live company data is established per-customer during the trial — run your own year of AP and judge the findings yourself; that is what the trial is for.

Download checksums (SHA-256)

File	SHA-256
Windows (ledgerproof-1.0.0-windows-amd64.zip)	7ab7f3a24d051fb098396da1f9c7bec8c03d3dd00c33fad6bbba03b800ba09ae
macOS Intel (ledgerproof-1.0.0-darwin-amd64.zip)	8961c1f4755c09cd3b487736e8ce1503bc3a448b5a45d565b0a578039f1eed64
macOS Apple silicon (ledgerproof-1.0.0-darwin-arm64.zip)	4ac562219755c4f716e58a8f3330c66e59d1ed2a0596d3cf6e3ff65432a4a416
Linux (ledgerproof-1.0.0-linux-amd64.zip)	4f0be65b55ccc28a31bc5c65db95b1ce37b481685f12550f3364b203f21ecb73
Release bundle (LedgerProof-1.0.0-Release.zip)	d3b974c42f90b33d3dbe275a2561f12617d734a1ab53d08cfccf1aea3ae448bf

Binaries in this release are not yet code-signed; checksums are the integrity guarantee until signing ships. The product contains exactly one third-party component (an SQLite library, BSD-3-Clause); everything else is first-party code and the standard library.