Execute insurer payments
that have already been approved.
“We’ve decided what to pay. Make the payment correctly and confirm what happened.”
A health plan or its third-party administrator (TPA) has adjudicated one or more claims and established the payable amount. An agent works within its pre-approved mandate to verify the net payable after deductibles and provider offsets, confirm the entitled payee, plan funding and enrolled payment rail, execute the payout through a qualified payment partner, release the matching 835 ERA / EOP with its reassociation trace, confirm actual settlement, and route holds or returns without paying twice.
The entitled recipient is paid the approved net amount through its enrolled method, the payment and its 835 ERA / EOP explanation carry matching trace references, settlement is verified separately from submission, and any $0 ERA-only, held or returned item is explicitly accounted for.
Operates with a health plan, TPA or disbursement partner holding outbound payout authority (distinct from practice-side payment acceptance). Clinical coverage, allowed amounts and patient cost sharing remain upstream adjudication responsibilities.
Human Journey
Someone in a health plan’s or third-party administrator’s payment operations team turns adjudicated claims into a funded disbursement, a trace-linked 835 ERA / EOP explanation, and a verified settlement record—without confusing an adjudicated claim with settled cash.
“Adjudication is finished. What is the net amount actually payable after deductibles and provider offsets, who is entitled to receive it, is plan funding ready, which rail are they enrolled in, and did both the money and the 835/EOP settle and match?”
Receive the adjudicated payable run and check net amounts.
They confirm that claim adjudication is complete and check what is actually payable. A payment run often bundles multiple claims for the same billing provider, while patient deductibles, coinsurance or provider-level adjustments (such as authorized overpayment recoupments/offsets in the 835 PLB segment) reduce the net payout—sometimes to $0. They also check that the claim or batch has not already been released.
Verify who gets paid and check payee holds.
Before selecting a rail, they check who is entitled to receive the money: the treating/billing practice under network participation or assignment of benefits, or the subscriber/member for an unassigned claim. They verify tax ID (TIN), billing NPI and payee account records, and check for W-9, sanction, fraud or compliance holds.
Confirm plan funding and select the enrolled payment rail.
For self-funded employer plans administered by a TPA, they confirm the employer’s plan funding account is funded; for fully insured plans, they check the insurer’s disbursement account. They then check the payee’s enrolled payment method (such as HIPAA-adopted ACH EFT, opted-in virtual card or paper check) so provider EFT rights and fee rules are respected.
Release the payout through the disbursement partner or bank.
When the net payable is positive and payee, funding and rail checks pass, they transmit the payment instruction through the disbursement partner or originating bank with the payable batch reference, net amount and recipient rail details.
Generate the 835 ERA / EOP and bind the reassociation trace.
Because the money transfer and the remittance explanation travel through separate channels, they generate and release the electronic remittance advice (X12 835 ERA or EOP) carrying the exact reassociation trace number (for healthcare ACH, the CCD+ addenda TRN segment matching the 835 TRN segment). When a deductible or provider offset leaves a $0 net payout, they still send the 835 ERA / EOP so the practice can close the claim without waiting for a deposit.
Confirm actual settlement and update the payer’s payable records.
They track submission, settlement and receipt as separate financial states. As bank and disbursement-rail statuses return, they check whether the transfer actually settled, cleared or was redeemed, and update the payer’s payable ledger with the verified settlement date, payment reference and linked 835/EOP trace.
Resolve held, rejected, returned or unredeemed payouts without paying twice.
When a payout was held before release (missing EFT setup or unfunded plan run), returned by the bank (such as an ACH return on a closed account), rejected, or left unredeemed on an expired virtual card or stale check, they reopen the payable exception, correct the payee or rail issue, and confirm the prior transfer is voided or returned before reissuing so the recipient is never paid twice.
An adjudication dispute, a missing EFT enrollment, an unfunded self-funded plan run and a bank ACH return are four different problems with different owners.
“The entitled payee received the approved net payout through its enrolled method, the payment and 835/EOP carry matching trace references, settlement is confirmed in the ledger, and any $0 ERA-only, held or returned item is accounted for.”
Coverage decisions, allowed amounts, coding edits, coordination of benefits and benefit design belong to adjudication—not payment execution.
Representative payer/TPA disbursement workflow grounded in US outpatient medical and dental reimbursement mechanics. Adjudication, plan funding, 835 ERA generation and disbursement rails frequently operate on separate systems and schedules.
Agent Journey
Adjudicated claims enter the disbursement queue. Follow the payer’s agent across seven stages—from net payable calculation and payee/funding checks through partner execution, 835 ERA TRN reassociation, settlement verification, and return/hold resolution.
Proposed seven-stage agent workflow for joint review. The following technical-alignment topics define the payer/TPA operating model, disbursement partner interfaces and exception rules to agree together.
Seven-step walkthrough
The agent acts for the health plan or its third-party administrator (TPA). Together with Rectangle, this workflow aligns around the participating health plan, TPA or disbursement partner network. Depending on network participation and assignment of benefits, the payee is the healthcare provider/practice (or, for unassigned claims, the subscriber/member).
The agent verifies the net payable, payee entitlement, plan funding and enrolled payment rail, executes the payout, links the 835 ERA / EOP trace, confirms settlement, and routes holds or returns. It never re-adjudicates coverage, alters allowed amounts or invents adjustment codes.
- Adjudicated payables → payer’s agent
Receive the adjudicated payable and establish the net payout.
An adjudicated claim or multi-claim payable batch enters the disbursement queue. The agent reads the adjudicated claim lines, allowed amounts, contractual adjustments (CO), patient responsibility (PR), provider-level adjustments (such as authorized overpayment recoupments/offsets in the 835 PLB segment), hold flags and prior payout runs.
Already paid or in flight? Skip execution and go to Step 06 to verify settlement and records. Net payable is $0 because a deductible or provider offset absorbed the allowed amount? Skip the money transfer and go to Step 05 to emit the $0 835 ERA / EOP explanation. Unapproved or under adjudication hold? Stop and surface the hold.
Result: a verified positive net payable ready for payee validation, a $0 ERA-only path, or a duplicate/hold stop. - Payee & enrollment records → payer’s agent
Verify payee entitlement and compliance readiness.
Before selecting a payment method, the agent checks who is entitled to receive the payout: the treating/billing practice under network contract or assignment of benefits, or the subscriber/member on an unassigned claim. It verifies billing NPI, tax ID (TIN), payee account status and any W-9, sanction, fraud or compliance holds.
If payee assignment is ambiguous, TIN/NPI records do not match, or a compliance hold is active, place the payable on pre-execution hold and route to Step 07.
Result: confirmed payee identity and entitlement, or an explicit pre-execution payee hold. - Funding & rail records → payer’s agent
Confirm plan funding and select the enrolled payment rail.
The agent verifies that plan funding is ready—distinguishing a self-funded employer plan’s TPA funding account from a fully insured health plan’s disbursement funds—and checks the payee’s enrolled payment rail (HIPAA-adopted ACH CCD+ EFT, opted-in virtual card or check).
Honor provider requests for adopted ACH EFT/ERA standards and applicable enrollment/fee rules. If self-funded plan funds have not cleared or EFT/rail enrollment is incomplete, hold the disbursement before execution and route to Step 07.
Result: confirmed funding readiness and permitted payment rail, or a pre-execution funding/enrollment hold. - Payer’s agent → DecentraCore → payment partner / rail
Execute the payout through the qualified payment partner.
For approved positive net payables with verified payee, funding and rail, the agent submits the payout instruction through DecentraCore to the qualified payment partner with an idempotency key, net amount, payee rail details and reassociation trace reference.
If Core or the payment partner blocks or rejects the submission, keep the payable open and record the reason. If the partner response times out or is uncertain, inspect the partner’s existing payment status before any retry so the recipient is never paid twice.
Result: partner payment ID, trace reference and submission state, or a blocked/uncertain execution state requiring inspection. - Payer’s agent → DecentraCore → 835 ERA / EOP system
Bind the reassociation trace and release the 835 ERA / EOP.
Because the remittance explanation and the funds transfer move through separate channels, the agent binds the authoritative trace reference (for healthcare ACH, the CCD+ addenda TRN segment matching the X12 835 TRN segment, or the corresponding EOP reference) to the remittance record and releases the 835 ERA / EOP—including $0 ERA-only explanations where no money moved.
If the money transfer succeeded in Step 04 but 835/EOP generation or trace binding fails, open a remittance-repair task; never re-execute the money transfer.
Result: released 835 ERA / EOP carrying the matching TRN / trace reference, or an open remittance-repair task. - Payment partner + adjudicated payables → payer’s agent
Confirm settlement separately from submission and verify payer records.
An emitted 835 ERA or partner submission acknowledgment does not prove money arrived. The agent checks the payment partner/rail for actual settlement, clearing or redemption, records the verified status and linked payment + 835/EOP trace references in the payer’s payable ledger, and reads back the updated record to verify accuracy.
If the transfer settled on the rail but the internal payable write fails or is incomplete, open an accounting-repair task and verify the ledger—never send a second payment.
Result: verified settled payout and linked 835/EOP trace in the payer’s ledger, or an identified accounting-repair discrepancy. - Payer’s agent → payer payment ops / exception queue
Route holds, ACH returns and unredeemed payouts for controlled resolution.
When a payable was held before release (payee, EFT or plan-funding blocker), rejected at submission, returned after submission (such as an ACH return on a closed or invalid bank account), or left unredeemed (expired virtual card or stale check), the agent reopens or preserves the payable exception with its exact code, trace history and next action.
Before any returned or unredeemed payout can be reissued onto an updated account or fallback rail, the agent confirms the original payment is voided, expired or returned so the recipient cannot be paid twice.
Result: settled items closed with full trace evidence, and held or returned items routed with verified non-duplication state and next action.
What the health plan sees afterward
- “The approved net payout settled to the entitled payee through its enrolled method, and the payment and 835/EOP carry matching trace references.”
- “Adjudication resulted in $0 net payment after deductible or provider offset; the 835/EOP explanation was released and recorded with no funds transfer.”
- “The payout was held before release, or returned/unredeemed after submission—here is the payee, funding or rail reason, prior trace status, and next step.”
Representative outcome states: adjudicated decision, released 835/EOP, submitted payment, settled transfer and returned/unredeemed payout are tracked as distinct states.
Shared premise & technical alignment
In healthcare insurance, coverage, the claim decision (835 ERA/EOP), the payment instruction and settled cash are separate facts. On behalf of a health plan or TPA, the agent turns an adjudicated payable into a controlled payout, a trace-linked 835/EOP explanation and a verified settlement record—without confusing adjudication with payment or paying twice.
Insurer disbursement is not a single “send payment” call. Establishing the net payable after deductibles and provider offsets, verifying payee entitlement (provider vs. member), checking self-funded plan funding and enrolled EFT rails, executing the transfer, binding the 835 TRN reassociation trace, confirming bank settlement, and handling ACH returns or unredeemed cards each happen across different records and failure modes.
Core design premises
- Operating model: The agent acts on behalf of a health plan or third-party administrator (TPA) disbursing approved claim payments. Rectangle’s role and the qualified disbursement partner would be agreed for the selected payer/TPA relationship.
- Where the work starts: Adjudicated claims with an established net payable amount. Clinical coverage, allowed amounts, coding edits, coordination of benefits and benefit rules remain in upstream adjudication.
- Standards & disbursement rails: Execute through a qualified disbursement partner and adopted HIPAA EFT/ERA standards (ACH CCD+ and X12 835) alongside opted-in payment rails.
- Governance: DecentraCore governs disbursement operations within a pre-approved mandate—enforcing payment controls without altering adjudicated amounts, inventing adjustment codes or overriding provider EFT rights.
Regulatory & platform context
HIPAA EFT/ERA & network standards: Under CMS and CAQH CORE EFT & ERA Reassociation rules, X12 835 (ERA) and ACH CCD+ are the adopted standards for healthcare EFT and remittance advice, linked by matching TRN reassociation trace segments across the payment and the 835 ERA. Health plans honor enrolled provider requests for adopted ACH EFT/ERA standards, and claim/provider-level adjustments (including 835 PLB recoupment offsets) determine the net disbursement amount.
Payer & partner alignment: While PayerSync connects practices with major payer reimbursement networks (including ECHO Health, Optum Financial and Zelis) on the receiving side, this use case explores how Rectangle and Decentra can support outbound payer/TPA disbursement and 835 TRN reassociation alongside a qualified disbursement partner.
References: CMS Healthcare EFT & ERA · CMS 835 Remittance & Adjustments · CAQH CORE EFT & ERA Reassociation Rule.
01 · Who is the payer-side customer, and what is Rectangle’s role?
Stakeholders: Rectangle commercial & partner leads · Health plan, TPA or disbursement partner owner
- Which health plan, self-funded TPA or disbursement network is in scope?
Confirm whether Rectangle participates alongside an existing payer disbursement partner (such as ECHO Health, Optum Financial or Zelis) or a specific TPA/plan relationship.
- Where does human payment operations work happen today after claims adjudication?
Walk through one normal multi-claim payout and one held, offset or returned payout. Identify the real manual gaps between adjudication, funding, 835/EOP generation and disbursement execution.
02 · How do adjudicated claims, multi-claim batches, $0 outcomes and provider offsets enter the payable queue?
Stakeholders: Payer claims / payables owner · EDI & remittance lead
- How does the payable instruction group adjudicated claims and provider-level adjustments?
One disbursement often covers multiple claims, while deductibles or provider-level recoupments/offsets (835 PLB) reduce the net payout. Confirm how line, claim and provider-level adjustments are read and how $0 ERA-only outcomes are separated from positive payouts.
- How do we verify that a claim or batch has not already been released?
Identify the authoritative disbursement status, batch ID and in-flight lock before any execution request is allowed.
03 · How are payee entitlement (provider vs. member), TIN/NPI and compliance holds verified?
Stakeholders: Payer provider-enrollment lead · Compliance owner
- How is the rightful payee determined (treating/billing practice vs. subscriber/member)?
Confirm how network participation, assignment of benefits, billing NPI, tax ID (TIN) and payee location determine who receives the money.
- Which payee or compliance holds must block disbursement before execution?
Confirm how W-9, sanction, fraud, payee-change or dispute holds are represented and who resolves them.
04 · How are self-funded TPA plan funding and enrolled payment rails checked?
Stakeholders: Payer / TPA treasury lead · Provider-enrollment & payment-partner owner
- How is plan funding readiness verified before releasing a payment run?
Distinguish fully insured plan disbursement accounts from self-funded employer TPA/ASO funding accounts where employer funds must clear before release.
- How are ACH EFT enrollment, alternative rails and provider method preferences enforced?
Confirm how the system checks active ACH EFT enrollment versus virtual card or check, honors provider requests for adopted EFT/ERA standards, and holds payouts when enrollment or routing details are incomplete.
05 · How does controlled execution work across DecentraCore and the qualified payment partner?
Stakeholders: Rectangle & Decentra integration leads · Payment-partner technical owner
- Which qualified payment partner executes the transfer, and what is the idempotency contract?
Confirm the partner execution interface, required idempotency keys, rail parameters and how uncertain timeouts are inspected before any retry.
- What mandate rules and hold conditions govern the Core boundary?
Define amount limits, funding checks, payee-change holds and exception queues across DecentraCore (identity; intent and authority; funding and risk; controlled execution; evidence and disputes; enterprise and agent integration).
06 · Where is the TRN reassociation trace bound to the X12 835 ERA / EOP, and when is it released?
Stakeholders: Payer EDI / 835 owner · Treasury lead · Payment partner
- Which system assigns the TRN reassociation trace across the payment and the 835 ERA / EOP?
For healthcare ACH CCD+, the addenda TRN segment must match the X12 835 TRN segment. Confirm which system generates the trace number, how virtual-card or check EOP references are linked, and how $0 ERA-only remittances are released.
- What happens if the payment instruction succeeds but 835/EOP generation or delivery fails?
Confirm the remittance-repair workflow so the missing or unlinked 835/EOP is repaired without re-executing the money transfer.
07 · How are settlement verification, ACH returns, unredeemed cards and first-proof boundaries handled?
Stakeholders: Payer treasury & accounting lead · Rectangle operations · Privacy & security leads
- How are settled funds separated from partner submission, ACH returns and unredeemed cards?
Confirm how ACH returns (e.g., closed/invalid account), rejected transfers or expired virtual cards reopen the payable exception, how prior transfers are confirmed voided/returned before any reissue, and how failed internal ledger writes trigger accounting repair rather than a duplicate payout.
- What is the smallest useful proof, and what HIPAA/BAA and baseline measures apply?
Trace one multi-claim adjudicated payable through net-payable check, payee/funding/EFT validation, partner execution, 835 TRN reassociation and settled ledger read-back, plus one held or returned exception using synthetic or de-identified records. Establish baseline metrics for duplicate-payment prevention, EFT/ERA reassociation accuracy and return-handling time.
Architecture & discovery summary for joint technical alignment between Rectangle and Decentra.