Stop matching exported data by hand.
We build a repeatable reconciliation workflow around your actual business rules: exact matches, approved fallback rules, visible variances, duplicate handling and an exception list you can audit.
A reconciliation you can explain.
The goal is not to hide mismatches with fuzzy automation. The goal is to turn your rules into a clear, repeatable process and expose anything that still needs human review.
Deterministic rules
Exact and fallback rules are written down before implementation. Tolerances, duplicates and one-to-many cases are explicit.
Traceable results
Source identifiers stay visible. Each match records why it matched, while unexplained records stay in the exception queue.
Reusable delivery
You receive the reconciled output, an exception-focused review view, summary counts and plain-language run instructions.
From messy exports to a controlled workflow.
Define the sources
Tell us which exports you use, their formats, approximate size and which fields are authoritative.
Lock the rules
We define exact matches, allowed fallback rules, tolerances, duplicates and mandatory exception cases.
Validate safely
We reproduce the logic on a small anonymized or synthetic sample before final processing.
Deliver & explain
You get the reconciled file, visible exceptions, summary counts and a readable rule/version note.
Synthetic example
This example is fictional and exists only to show the shape of the output. It is not a customer case study and does not claim recovered revenue.
| Billing record | Operational record | Rule | Variance | Result | Evidence |
|---|---|---|---|---|---|
| INV-1001 | INV-1001 | Exact invoice reference | $0 | PASS | Invoice ID + amount |
| INV-1002 | INV-1002 | Exact invoice reference | -$50 | EXCEPTION | Amount mismatch |
| INV-1003 | INV-1003 | Exact invoice reference | $0 | PASS | Invoice ID + amount |
| INV-1004 | ADJ-778 | Unique work-order fallback | $0 | PASS WITH FALLBACK | Work order WO-504 |
| INV-1005 | — | None | — | EXCEPTION | Billing-only record |
| — | INV-1006 | None | — | EXCEPTION | Operational-only record |
Validation pricing
These fixed tiers are deliberately bounded so scope is clear before work starts. Pricing is being validated and may change as real buyer evidence accumulates.
Starter
$199For a small, well-defined reconciliation.
- 2 data sources
- Up to 1,000 rows per source
- Up to 3 deterministic rules
- 3-day target delivery
- 1 revision
Standard
$449For recurring operational reconciliation with more rule depth.
- Up to 3 sources
- Up to 5,000 rows per source
- Up to 6 rules
- Duplicate handling
- Reusable run instructions
- 5-day target delivery, 2 revisions
Advanced
$799For larger exports and a repeatable handoff workflow.
- Up to 4 sources
- Up to 10,000 rows per source
- Up to 10 rules
- Repeatable workbook or script workflow
- Rule-version note + handoff docs
- 7-day target delivery, 2 revisions
A scope check happens before acceptance. Work outside a tier's limits is not silently added to the order.
Good fit
- Invoice vs payment exports
- Billing vs operational records
- Timesheet vs work-order exports
- Recurring CSV or spreadsheet matching
- Client-specific exact/fallback rules
- Exception reports that need an audit trail
Not included
- Bookkeeping, tax or legal decisions
- Payment initiation or money movement
- OCR/image extraction in the current offer
- Fuzzy guessing or silent correction
- Writing back into production systems
- Unspecified live integrations or dashboards
- Ongoing managed reconciliation unless separately scoped
Common questions
Do you need access to our production systems?
No, not when exports are sufficient. The preferred starting point is client-provided CSV, Excel or similar exported files. Do not send passwords or credentials.
Will every row be matched automatically?
No. Ambiguous, missing or rule-breaking records should remain visible as exceptions rather than being silently forced into a match.
Can the rules include tolerances?
Yes, but tolerances must be explicitly defined and approved. The default is no hidden tolerance.
What do I receive?
A reconciled spreadsheet or table with source identifiers retained, match status, rule/evidence, relevant variances, an exception-focused view, summary counts and readable run instructions.
How is payment handled?
First we confirm scope and the appropriate tier. A payment method or secure payment request is then agreed before paid work begins. No payment details should be sent by email.
Have two files that should agree — but do not?
Send the file types, row counts, matching keys and the exceptions that matter. We will tell you whether the current fixed-scope service fits.