Reconciliation & close control · spec v4.2

Your close takes eleven days.
The next one lands on
day three.

Parity pulls every bank, PSP and ERP feed into one ledger, auto-matches 99.4% of lines within 90 seconds of posting, and stores the rule, inputs and approver behind each match so your auditor never asks you for a spreadsheet again.

SOC 2 Type II·NetSuite, SAP, Sage Intacct·11,400 bank connections

Parity · close 2026-09 · entity NW-FREIGHT-USAuto-matched 99.4%
Match group #48,201 — settlement 8821
DateSourceReferenceAmount
09-28JPM 4471ACH CR / SETTLE 8821412,908.14 MATCHED
09-28Stripepo_1QK4 · batch 8821398,441.02 MATCHED
09-28Stripefee_1QK4 · interchange14,467.12 MATCHED
09-28NetSuiteJE 90-4471 / AR clear412,908.14 MATCHED
09-29Adyen NLEUR capture · FX split61,204.77 REVIEW
1,041,882 lines this cycle1,041,876 auto-matched · 6 open
Group varianceΔ $0.00
EvidenceRule PSP-SPLIT-FX v11Matched at 09-28 04:12:07ZApprover M. OKONJOHash a71f·9d0c·4e88
Exception queueOpen lines 6 of 1,041,882Oldest 14 minOwner AP · D. REISS
Reconciling 41M lines a month for
Northwind FreightHalyard HealthCORVUS ROBOTICSOndaBrightharborVolta GridKESTREL LABSMeridian Co
The Parity position

Every number in your close should be able to name its source.

FEED11,400 SOURCESRULEVERSIONEDAPPROVERNAMED HUMANHASHSEALED

No line without a provenanceNothing written off silently

Measured, not claimed

What the numbers look like after month three

01 / MATCH RATE+99.4%Lines matched on the first pass

Across 41M monthly lines from banks, PSPs and ERPs — measured before any human touches the queue.

02 / CYCLE TIME+3.1 daysMedian close, down from 11

Across 140 finance teams in their third month on Parity. Nine of them close in under 48 hours.

03 / RESIDUAL+$0.00Unexplained variance at sign-off

Every remaining difference carries a rule version, an owner and a timestamp. Nothing is written off silently.

The system

Six parts, and the close stops being manual

Parity replaces the spreadsheet layer between your bank statements and your ledger — ingestion, matching, exceptions, eliminations, evidence and the checklist that ties them together.

Feeds that arrive already normalised

Direct connections to 11,400 banks plus Stripe, Adyen, Brex, NetSuite and SAP. New lines land in Parity within 90 seconds of posting, in one schema.

Many-to-many matching

A split settlement with an FX remainder and two partial refunds resolves as one balanced group — not six unexplained exceptions for a human to reassemble.

An exception queue with owners

Every unmatched line gets an assignee, an age and an SLA. Median time to clear is 14 minutes, and nothing hides in a tab called final_v3.

Multi-entity on one ledger

24 entities and 9 currencies reconcile against a single source. Intercompany eliminations post automatically the moment both sides balance.

Evidence attached to every match

Rule version, inputs, approver and hash are stored with the match itself. Export a full PBC package for your auditor in one click.

A checklist that runs itself

Tasks unlock when their dependencies reconcile, so your controller opens a list of real blockers instead of chairing a status meeting.

[ Matching engine ]

Kill the 4% that eats your week

One-to-one matching is easy and every tool does it. The month is lost to the residue: a €61,204.77 Adyen capture that arrives as two settlements, a chargeback, and an FX rounding difference of $3.12. Parity groups all four into one balanced entry and writes down why.

  • 01Rules are versioned and diffed like code — you can see which release started matching a pattern, and roll it back.
  • 02Tolerances are per-source, not global: 0.5 bps on FX, exact on ACH, $0.02 on card interchange.
  • 03Anything the engine will not explain stays open. Parity never force-matches to make a dashboard look green.
Exception 8821-B · Adyen NL · EURResolved in 41s
Before · 4 open linesADYEN SETTLE 1/2€38,900.00ADYEN SETTLE 2/2€22,304.77CHARGEBACK 4471−€412.00FX ROUNDING$3.12
After · 1 balanced groupGROUP #48,207€60,792.77NETSUITE JE 90-4478€60,792.77RULE PSP-SPLIT-FXv11VARIANCEΔ 0.00
Engine noteSplit capture + FX remainder within 0.5 bps toleranceLines this cycle1,041,882 in · 1,041,876 auto-matched
[ Evidence & controls ]

Hand your auditor a link, not a folder

Every match carries its own provenance: the feed it came from, the checksum on that feed, the rule version that grouped it, the person who approved it and the hash that proves none of it changed afterwards. Auditors get a scoped read-only role and pull the sample themselves.

  • SOC 2Type II, audited annually. Segregation of duties enforced at the rule level, not by convention.
  • PBCPrepared-by-client packages export as signed PDFs plus the underlying CSV, in the sample structure your firm already uses.
  • 7 yrsImmutable retention with regional residency in the US, EU and AU.
Audit trail · group #48,201Sealed
Immutable event log
09-28 04:12:07ZFeed JPM-4471 ingested — 208,441 lines, checksum verified.
09-28 04:12:48ZRule PSP-SPLIT-FX v11 applied to group #48,201. Variance Δ $0.00.
09-28 09:02:14ZM. Okonjo approved group #48,201. Evidence hash a71f·9d0c·4e88 sealed.
10-02 11:40:55ZAuditor role PWC-ENGAGEMENT-7 opened the group. Read-only, logged.
Sample requested40 of 1,041,882 linesClient hours to assemble0
From the controllers

What changed in month one

We went from an eleven-day close to three. The first month I kept re-opening the queue at 9am because I did not believe it was already empty.

Mara OkonjoController · Northwind Freight

Our PSP settlement variance was averaging $38,000 a month. Parity showed it was FX rounding on split captures. It has been under $400 since March.

Daniel ReissVP Finance · Onda

The PBC package used to take two people three weeks. Our auditors now pull their own sample. We renegotiated the engagement 22% down.

Priya VenkatesanHead of Accounting · Halyard Health
Book a working session

Your next close can land on day three

45-minute working session · we reconcile one of your real months before you sign anything

Book a demo