WorkflowCompliance & Ethics

Open Payments Recipient Matcher

Open Payments recipient matching, with the evidence behind every match

Every payment to a clinician or teaching hospital matched to the right registry record, with the evidence behind each match.

See one case, screen by screen ↓
demo97.0%of this program year’s records matched on their own — 1,179,512 of 1,215,699
demo2.6minmedian for a reviewer to decide an uncertain match, evidence in view
demo37recordsacross three systems fixed by one decision on one recipient
demo6minfor last night’s run — 4,812 payments from five systems, 4,671 matched on their own
The problem

Why recipient matching eats the reporting year

Every payment or transfer of value has to reach the federal report against the right covered recipient: the right NPI, the right licence state and the right type — physician, physician assistant, nurse practitioner, CRNA, clinical nurse specialist, nurse-midwife or teaching hospital. The data rarely arrives that way. A rep writes “Dr Jon Ramirez” on a speaker-dinner sign-in; the registry knows him as Jonathan A. Ramirez-Ortega, PA-C, at the practice he moved to in August.

So the matching falls to people. Someone searches the NPI registry, checks the state board, compares the payment record with the HCP master and writes down why, one recipient at a time — for name variants, people who moved practice or state, initials that fit two people, grants paid to a hospital’s foundation and credentials typed wrong. When a recipient disputes a payment in April, that reason has to still be on file.

estimated3–5%of payment records matched by hand today
estimated53k–88kreviewsa year by hand, at about 1.8 million records
typical$1,000–$10,000civil penalty per payment reported wrong, rising to $100,000 when the failure is knowing
Where an analyst’s week of matching goes, in hoursestimated
By hand36 days
With the solution10 days
  • Pulling and cleaning the source feeds5 → 1 d
  • Searching the NPI registry and licence boards12 → 2 d
  • Comparing payment records with candidates9 → 4 d
  • Writing down why each match was made5 → 1 d
  • Sending HCP master fixes to the steward3 → 1 d
  • Checking profiles before the submission file2 → 1 d

Estimated split for one transparency analyst working the exception queue, by hand and with the solution.

How it works

How a payment moves

Six specialist agents clean, match, classify and cite every payment recipient; a transparency analyst decides each uncertain match.

What comes in
Payments in5 payment systems · expenses, events, consulting, research, grants
Agents at work
Feed intake agentevery night
Then
Name & address normalisernames + addresses
Then
Registry matcherregistry + licences
Then
Covered-recipient classifierrecipient type
Evidence writernumbered citations
Then
Submission file builderpre-validated
A person decides
Transparency analystdecides each uncertain match
What comes out
Matched recipients
Federal report file
Audit trail per record
One case, step by step

One recipient, from “Dr Jon Ramirez” to the submission file

A speaker-dinner sign-in reads “Dr Jon Ramirez”. Thirty-seven payments in three systems point at him, and none matched a registry record on its own. Here is what happens next, screen by screen, in the working solution.

  1. 01Morning

    The program year, and what needs her

    Lena Ortiz · Transparency reporting analyst

    Lena opens the solution for program year 2026: 97.0 % of records matched on their own, 14 exceptions waiting for her — 129 records, $292,474 — and 117 days until the submission window opens on Feb 1, 2027. Her weekly sweep closes Friday, Oct 9.

    Agents today: “Nightly batch matched 4,671 of 4,812 records on their own.”

  2. 02The queue

    Only the payments that need a person

    Lena Ortiz · Transparency reporting analyst

    Each exception shows the recipient as captured, the best match, why it needs her, the systems it came from, the records and value at stake and the agents’ confidence. Name variant, two people fit, moved practice, credential unclear, NPI deactivated, paid to a foundation — every one with a due date.

  3. 03Opened

    “Who is ‘Dr Jon Ramirez’?”

    Lena Ortiz · Transparency reporting analyst

    M-2041: 37 records, $18,420, from speaker programs, expenses & meals and consulting contracts. The agents recommend Jonathan A. Ramirez-Ortega, PA-C, NPI 1902448317, at a 93 % match score — below the 0.95 line, so a person decides. Beside it, the source: the Veltrimab speaker-dinner sign-in of Sep 17, 2026 at Sunrise Grill, Round Rock, credential written as “Dr”, signed “J. Ramirez-O.”.

    “Read from the source system as captured. Nothing changes there until you confirm.”

  4. 04Field by field

    Two candidates, every field compared

    Registry matcher

    Candidate A agrees on specialty and is a variant on name and address; candidate B, John Ramirez, MD, a cardiologist in Houston, scores 0.41. Click any cell and the registry record opens at that field: other name “Jon Ramirez”, credential PA-C, provider type code 363A00000X, practice location 2150 Sunrise Rd, Round Rock, last updated Aug 21, 2026.

    “The agents read the registry; they never edit it.”

  5. 05The reason

    Why this is the recipient, with citations

    Evidence writer

    The reason ties it together with numbered citations: the signature on the sign-in, the registry’s other name and PA-C credential, the move to Round Rock where the dinner was held, the HCP master’s licence PA-08812, and the Texas board showing that licence active. A master-data fix is proposed — credential MD → PA-C and the new address — for the steward.

    “Report him as a physician assistant — a non-physician practitioner — not as a physician.”

  6. 06How it got here

    The nightly run that raised it

    The agents

    Last night five source systems sent 4,812 payments. The agents cleaned, matched, classified and cited them in about six minutes: 4,671 matched on their own, 141 went to reviewers. M-2041 keeps its own trace of that run: the normaliser set “Dr” aside, the registry matcher found 6 candidates and hit the other name, the licence check confirmed PA-08812 active to Feb 2028, the classifier read the provider type code as physician assistant.

  7. 07One click

    Confirmed — 37 records fixed at once

    Lena Ortiz · Transparency reporting analyst

    Lena confirms the match. The recipient is written onto all 37 records, the master-data fix goes to Dana Okafor, the profile is pre-validated against the federal rules with 0 errors, and the records join the program year 2026 submission file, batch 41.

    “37 records across 3 systems now carry NPI 1902448317 · physician assistant. Decided by Lena Ortiz.”

  8. 08On file

    One verified identity, every payment behind it

    Lena Ortiz · Transparency reporting analyst

    The recipient profile shows $18,420 paid this year by nature of payment — compensation for speaking, consulting fee, travel and lodging, food and beverage — by month, every record resolved to the one NPI and the match history. The evidence pack holds the registry, licence and source records with the decision trail.

  9. 09Before publication

    What the public record will show

    Lena Ortiz · Transparency reporting analyst

    A preview of how his payments appear when the federal data is published on Jun 30, 2027: Covered Recipient Non-Physician Practitioner, physician assistant, licence state TX, $18,420 across 37 payments. The recipient sees it first, in the review period.

  10. 10The riskiest calls

    A second person on teaching hospitals

    Omar Haddad · Aggregate spend operations lead

    Not every case ends with one click. M-2047 is a $85,000 fellowship grant paid to Lakeview University Medical Center Foundation, a separate charity. The agents recommend reporting it to the hospital, which is on the program-year 2026 teaching-hospital list — and the decision goes to Omar for sign-off.

    Teaching hospitals are never auto-matched — a person always decides.

Who it’s for

Built for everyone who answers for a reported payment.

The same recipients, seen by the four people who carry them — what their year looked like, and what it looks like now.

LO
Lena OrtizTransparency reporting analyst
Reviewer
Before
Works each uncertain recipient by searching the registry and the state board, then writes down why.
Now
Opens each exception with the candidates compared, the sources open and the reason written; decides in minutes.
OH
Omar HaddadAggregate spend operations lead
Approver
Before
Signs off hospital and foundation calls without the grant agreement and the teaching-hospital list side by side.
Now
Signs off teaching-hospital, foundation and not-covered decisions with the grant agreement and the CMS list in view.
DO
Dana OkaforHCP master-data steward
Steward
Before
Hears about a wrong credential or an old address in the HCP master after it has reached a report.
Now
Receives each credential, address and duplicate fix the moment a match is confirmed, with the evidence behind it.
SP
Sam PatelDirector, healthcare compliance
Viewer
Before
Assembles proof for the compliance committee or a dispute from several systems.
Now
Opens any recipient and exports the evidence pack: the records, the lookups at the time of the match, who decided and why.
Built on the engine

6 agents. Each with one job, and hard limits.

Six specialist agents clean, match, classify and cite every payment recipient; a transparency analyst decides each uncertain match.

Feed intake agent

Pulls the nightly payment batch from the expense, events, accounts-payable, grants and clinical-payment systems, and labels each line’s source system, nature of payment, product and amount.

  • Never edits a source system
  • Rejects a batch with a broken record count
  • Keeps the recipient exactly as captured
Name & address normaliser

Splits names, sets credentials aside, records nicknames and former names as variants, and standardises addresses (suites, ZIP+4).

  • Keeps the as-captured value next to every cleaned value
  • Never guesses a credential
Registry matcher

Scores every candidate from the NPI registry, state licence lookups, the HCP master and the teaching-hospital list, field by field — name, credential, provider type code, address, licence and NPI.

  • Auto-matches only on exact NPI, licence and name
  • Never auto-matches a teaching hospital
  • Prefers the licence number over the name when both exist
Covered-recipient classifier

Decides physician, physician assistant, nurse practitioner, CNS, CRNA, CNM, teaching hospital or not covered, from the registry’s provider type code and the licence type — not the credential the business typed.

  • “Not covered” always needs a sign-off
Evidence writer

Writes the short reason for each match, with numbered citations to the exact registry, licence and source passages, and says what the person must decide.

  • Every claim cites a passage
  • Plain words — no codes without a meaning
Submission file builder

Writes confirmed recipients into the federal file layout and pre-validates NPI, licence and name, reporting any profile error back to the exception list.

  • Only confirmed records enter the file
Transparency analyst

Decides each uncertain match. The agents propose; a named person decides.

Ask in plain words

Ask it anything, in plain words

Anyone on the team can ask about a recipient, an exception or a source system — or tell it a matching rule to add. Answers cite the registry, licence and source records.

Which exceptions are worth the most?

Your five largest open exceptions by value: A. Thompson (PI, site 114), $96,400; Lakeview University Medical Center Foundation, $85,000; Northbridge Oncology Associates, $27,000; Dr. Lucas Ferreira, $22,400; Dr Jon Ramirez, $18,420. I have sorted your list by value.

Why is Jon Ramirez a physician assistant?

Because the NPI registry says so: Jonathan A. Ramirez-Ortega is listed with the credential PA-C and the physician-assistant provider type code, and his other name is “Jon Ramirez”. The rep wrote “Dr” on the sign-in, which is why the payment looked like it went to a physician. He moved to Round Rock on Aug 21 and the Texas board shows licence PA-08812 active. Confirming fixes 37 records worth $18,420.

Confirm credential fixes automatically when the state board confirms them

Done. I added the rule “Confirm a credential fix on its own when one registry record matches name and address and the state board confirms the licence” to Settings → Matching rules. It applies to two of your open exceptions — M-2052 (Angela Brooks, RN) and M-2078 (Marcus Bell, Midwife). Teaching hospitals and “not covered” calls still come to a person.

How ready are we for the February submission?

On track. 117 days until the window opens on Feb 1, 2027; files must be attested by Mar 31. 97.0 % matched on their own, 31,956 records confirmed by reviewers, 3,068 waiting for the team, 14 exceptions waiting for you, and 0 profile errors in the last pre-validation. Next: your weekly sweep closes Fri Oct 9, then year-end pre-validation on Jan 8.

Every screen

The working solution, as it ships.

12 screens from the working solution, on its sample data. Pick one to see it large.

HomeWhere every payment goes this program year, what waits for the analyst, and the submission clock.
ExceptionsPayments whose recipient needs a person, with the reason, systems, records, value, confidence and due date.
Match reviewThe recommended match and its score, the candidates compared field by field, and the source record as captured.
The registry recordClick a field to open the NPI registry record at that passage — other name, credential, provider type and practice location.
Why the agents recommend itThe reason with numbered citations, and the master-data fix proposed for the steward.
ResolvedOne decision writes the recipient onto every record, sends the master fix, pre-validates the profile and adds it to the file.
Recipient profileOne verified identity: payments by nature and by month, every record behind it, and the evidence pack.
The public record, previewedHow the recipient’s payments will appear when the federal data is published.
Teaching-hospital sign-offA grant paid to a hospital’s foundation, recommended to the teaching hospital and sent for sign-off.
FeedsThe nightly run from five source systems, step by step, with recent nights and the health of each feed.
DashboardMatch rate by source system, who was paid, why payments need a person and how fast reviewers decide.
SettingsThe auto-match line, sign-offs, matching rules and the reference data the agents match against.
Governance

Built for transparency reporting: cited, signed off, kept on file.

Every match cites its evidenceThe reason for each match carries numbered citations. Click any field to open the registry record, licence lookup, source record or HCP master at that passage.
Sources are read, never changedThe agents never edit a source system, the registry or the HCP master. Master-data fixes are proposed and go to the steward.
A high bar to match on its ownA record is confirmed without a person only at a score of 0.95 or more with no rule hit, on exact NPI, licence and name. Below that line, a reviewer decides.
A second person on the riskiest callsTeaching hospitals and foundations, “not a covered recipient” and duplicate master records each need a named person’s sign-off. Teaching hospitals are never auto-matched.
Only confirmed records reach the fileThe submission file takes confirmed recipients only, and each is pre-validated against the federal profile rules before it goes in.
Kept for five years after publicationEach decision keeps its registry, licence and source evidence with who decided and when — ready as an evidence pack when a recipient disputes a payment.
Configuration

Your matching rules, not ours

How the agents match, who signs off and where the reference data comes from are settings — and new rules are added in plain words.

SettingDefaultChoose from
Auto-match line0.950.90 · 0.95 · 0.98
Send master-data fixes to the stewardOn — Dana OkaforOn · Off
Licence before nameOnOn · Off
Teaching hospitals always need a personOnOn · Off
Confirm credential fixes on their ownOffOn · Off
Sign-off: teaching hospitals and foundationsOmar HaddadOmar Haddad · Dana Okafor · Sam Patel
Sign-off: not a covered recipientOmar HaddadOmar Haddad · Dana Okafor · Sam Patel
Sign-off: duplicate master recordsDana OkaforOmar Haddad · Dana Okafor · Sam Patel
Connections

Works with the systems you already run

Your spend systemsexpense, events, accounts payable, clinical payments and grants
NPI registrythe public weekly file, 8.9M providers
CMS teaching-hospital listthe program-year list, 1,327 hospitals
State licence lookups50 states + DC, looked up on demand
HCP masteryour customer master, with fixes sent to the steward
Federal profile filecovered-recipient profiles for pre-validation
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
97.6%
of payment records matched on their own, with the evidence on file
matched without a person
target
2.6min
median for a person to decide an uncertain match, evidence in view
estimated
2–4people
freed from manual matching at about 1.8 million records a year
Today53k–88k reviews a year
With agents16k–26k

“demo” = seen in the working solution, on its sample program-year data · “estimated” = our estimate (3–5% of records matched by hand today, at about 1.8 million records a year) · “typical” = published figures (42 CFR Part 403 Subpart I, Open Payments — civil money penalties). People, companies and products named on this page are fictional — characters and sample data in the working solution.

Questions

What transparency teams ask us.

What is Open Payments recipient matching?

Resolving each payment or transfer of value to the covered recipient it must be reported against — the right NPI, licence state and covered-recipient type. The Recipient Matcher does this for every record from your spend systems, against the NPI registry, state licence lookups, your HCP master and the CMS teaching-hospital list, and keeps the evidence for each match.

How does it match a recipient to an NPI?

The normaliser splits names, sets credentials aside and standardises addresses. The registry matcher then scores every candidate field by field — name, credential, provider type code, address, licence and NPI — and prefers the licence number over the name when both are present. At 0.95 or above with no rule hit, the match is confirmed on its own; below it, a reviewer decides.

Does it handle physician assistants and nurse practitioners?

Yes. The covered-recipient classifier decides physician, physician assistant, nurse practitioner, clinical nurse specialist, CRNA, certified nurse-midwife, teaching hospital or not covered from the registry’s provider type code and licence type, not the credential typed by the business. Registered nurses and pharmacists are not covered, and a “not covered” call needs a sign-off.

Does it change our HCP master or source systems?

No. The agents never edit a source system or the HCP master. Credential, address and duplicate fixes found while matching are proposed and sent to your master-data steward.

What do we show when a physician disputes a payment?

The recipient’s evidence pack: every record behind the payment, the registry and licence lookups at the time of the match, who decided and why. Each decision keeps its evidence for at least five years after publication.

Which systems does it work with?

Your expense, events, accounts-payable, clinical-payments and grants systems; the NPI registry weekly file; the CMS teaching-hospital list; state licence lookups; your HCP master; and the federal profile file used for pre-validation.

Do our people stay in control?

Yes. A reviewer decides every match below the auto-match line, and teaching hospitals, foundations, “not covered” calls and duplicate master records need a named person’s sign-off. The auto-match line, the sign-off owners and the matching rules are settings your team controls.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your source systems, matching rules and a sample of past spend records — and it goes live once every quality gate has passed. We will walk you through it on your own payments first.

See it on
your payments.

We’ll run the Recipient Matcher on a sample of your own spend records.