Concord Remit
The bottleneck in B2B is not the payment. It is matching the remittance to the invoice across 800-line check stubs, mixed-format ACH addenda, and PDF EOBs. Concord runs the reconciliation autonomously and turns a back-office cost center into a structured-data product.
Currently in discovery. Taking calls with operators, payers, and issuers who see the same gap.
01 · The problem
The remittance is harder than the payment
A wire arrives. The associated 835 file arrives an hour later. The check stub from the same payer arrives by mail two weeks after that. AR teams spend more time matching these to invoices than the actual money movement took. The reconciliation tax has compounded for forty years.
02 · The thesis
Reconciliation is structured extraction, not data entry
Every remittance line carries enough signal to match an invoice deterministically. The reason this fails today is that the inputs arrive in twenty incompatible formats and the outputs need to land in a single ERP-canonical schema.
Concord normalizes any remittance source (wire memo, 835, EOB PDF, paper check) into a structured representation, then matches against AR with auditable provenance. Canonicalization is the work. OCR is a commodity input.
03 · The product
What it does
Multi-format ingestion
835, 820, 999, EOB PDFs, paper checks, ACH addenda, wire memos. All into one canonical line-item schema.
Confidence-scored matching
Match lines to AR using payment amount, date proximity, vendor identity, and invoice metadata, with an explicit score on every match.
Exception routing
Ambiguous lines escalate with the match candidates and their scores attached. Approval becomes a single click, not a forensic exercise.
Cash application API
An endpoint that lets any ERP or AP system call out for canonicalized remittance, scored matches, and posted entries.
04 · Why now
The timing case
- 1
ERP migrations to NetSuite, Intacct, and Workday Financials are forcing every mid-market business to re-platform its cash-application logic on a deadline.
- 2
Foundation models hit production-grade accuracy on multi-format extraction in 2024. The cost of building and maintaining this infrastructure has fallen by an order of magnitude.
- 3
Healthcare denial-rework cost has crossed the threshold where remittance reconciliation is now a board-level metric for hospital CFOs.
05 · Why I see it
The view from inside the work
Remittance reconciliation was the binding constraint on every product decision in my decade at the largest US healthcare clearinghouse, and again at Finexio. The canonicalization pattern carried over both times. That is the entire job.
06 · Comparable references
What's already in the market, and where the gap is
An honest read on the adjacent landscape. Not every comparable is a competitor. Some are partners. Some are the market the venture displaces.
07 · Key risks
What could break the thesis
Operator-grade pre-mortem. Surfaced because the buyers and partners worth talking to will surface them anyway.
Cash application is an entrenched buying category with established vendors.
Lead with API-first integration into modern ERPs (NetSuite, Intacct). Land on greenfield, expand into incumbent territory on lower TCO.
Healthcare 835 reconciliation has unique compliance overhead.
Operator's clearinghouse track record gives day-one credibility on healthcare lanes. B2B is a horizontal extension, not the lead.
Match accuracy below 99% creates trust issues with finance teams.
Confidence-scored output with explicit human review on low-confidence matches. The product gets adopted as a co-pilot, then earns autonomy on track record.
08 · Proof of motion
What I've already shipped on this thesis
The artifacts that turn this from an essay into something with traction. Published work, working-group seats, operator scars.
- Canonicalization Beats WorkflowPillar essay arguing why this category compounds. Concord is one of three instances.essay
- $160B/yr Change Healthcare clearinghouse experienceI built the canonicalization pattern at clearinghouse scale before founding Finexio.filing
- Finexio settlement-loop architectureSame canonicalization pattern, AP-side, $12B+ run rate. The design transfers.filing
09 · Questions partners ask
The next three follow-ups
Pre-empted because the buyers and partners worth talking to will surface them anyway.
How is this different from HighRadius?
HighRadius is a $400M+ ARR enterprise vendor that sells cash-application workflow to AR teams. Concord sells the canonicalization layer underneath, with an API-first deployment story aimed at modern ERP greenfield (NetSuite, Intacct, Workday Financials). Concord wins on TCO at the API tier and gets pulled up the stack on track record. The fight isn't on HighRadius's existing accounts. It's on the next thousand mid-market re-platforms.
Match accuracy below 99% breaks finance teams. How do you not lose trust on the first miss?
Confidence-scored output, every line. Anything under threshold escalates with the candidate matches and their scores attached. The product is adopted as a co-pilot first. It earns autonomy on track record, customer by customer. Most existing vendors run the same pattern but fail to commit to the schema underneath. We commit to the schema first.
Does this compete with Finexio?
Finexio is AP-side. Concord is AR-side. The same canonicalization pattern shows up in both directions, but the buyer is different (AP at Finexio, AR/finance at Concord). They are adjacent, not overlapping. If anything, customers running both should get cleaner two-sided settlement.
What's the first deployment look like?
A mid-market AR team on NetSuite or Intacct that's currently spending $11 a line on manual matching. Concord lands as an API behind their existing UI, drops the per-line cost by 60%+, and earns the right to expand into adjacent revenue-cycle lanes on the data trail it builds.
Status
Concord Remit is in discovery. I am taking calls with operators, payers, and issuers who see the same gap, and would talk to capital that wants to be early on the right founder for it.
Other concepts
Healthcare Adjudication
Apex Adjudication
AI claims-resolution engine for healthcare payers. Resolves manual denials at API speed.
Clearinghouse Automation
Clearing AI
Automated translation between legacy clearinghouse formats and modern APIs.
Healthcare Settlement
Ledger Health
Cryptographic settlement and audit trails for multi-party healthcare reimbursement.