Purpose
This guide explains how Populate processes multiple EOBs or ERAs posted against the same claim. It is intended for Customer Support and Billing teams investigating allowed amounts, patient responsibility, Insurance Balance, superseded EOB lines, Reversals, and Corrections.
1. The key concept
Populate keeps two different views of EOB activity:
Current financial state
This represents the EOB information that is currently valid. It is used for values such as Allowed Amount, patient responsibility, deductible, coinsurance, non-covered amounts, and Insurance Balance.
Transaction history
This preserves everything that happened, including earlier EOBs, payments, Reversals, Corrections, refunds, recoupments, and ledger entries.
An older EOB can therefore remain visible in history while its service lines no longer participate in current financial calculations.
A simple way to explain this is:
The history shows what happened. The Financial View shows what is currently effective.
2. Why EOB processing was changed
Previously, when multiple EOBs were posted against the same claim, Populate could add amounts from several historical postings together. This could overstate Allowed Amount, patient responsibility, and related financial values.
Populate now determines which EOB service lines are currently effective instead of adding together every historical EOB row.
The improvements also allow automatic ERAs to recognize formal payer Reversals and Corrections and maintain the relationship between the Original, Reversal, and Correction.
3. Basic terminology
ERA: An electronic remittance received from a payer.
EOB: The payer posting stored in Populate. It may be created automatically from an ERA or entered manually.
Service line: An individual billed service on a claim.
Payer level: Whether the adjudication belongs to the primary or secondary payer.
Current service line: The eligible EOB service line currently used in financial calculations.
Superseded service line: An older EOB service line replaced by a newer eligible adjudication.
Reversal: A formal payer transaction that withdraws an earlier adjudication.
Correction: A replacement adjudication associated with a valid Reversal.
Manual exclusion: A service line intentionally excluded by a biller using IsExcluded.
4. How Populate handles ordinary multiple EOBs
For ordinary EOB postings, Populate selects the current adjudication separately by:
- Claim
- Primary or secondary payer level
- Service line
When a newer EOB contains the same service line as an older EOB, the newer eligible line becomes current and the older line becomes superseded.
Example
The first primary EOB contains:
- Allowed Amount: $100
- Patient responsibility: $30
A later primary EOB for the same service line contains:
- Allowed Amount: $90
- Patient responsibility: $20
The current values are:
- Allowed Amount: $90
- Patient responsibility: $20
Populate does not calculate $190 Allowed Amount or $50 patient responsibility.
The older EOB remains visible in history, but its service line does not participate in current calculations.
5. How partial EOBs work
An ordinary newer EOB updates only the service lines it contains.
For example, the first EOB contains:
- Line A: $20 patient responsibility
- Line B: $30 patient responsibility
A later ordinary EOB contains only:
- Line A: $10 patient responsibility
The current result is:
- Line A comes from the later EOB: $10
- Line B remains from the earlier EOB: $30
- Total patient responsibility: $40
The later EOB does not remove Line B because it did not include a new adjudication for that line.
This service-line behavior applies independently to ordinary primary and secondary EOBs.
6. Primary and secondary EOBs
Primary and secondary EOBs are evaluated separately. A secondary EOB does not automatically supersede a primary EOB, and a primary EOB does not supersede a secondary EOB.
As currently implemented:
- Allowed Amount comes from the latest eligible primary adjudication.
- Patient responsibility comes from the latest eligible secondary adjudication when one exists; otherwise, it comes from the primary adjudication.
- Original billed amount continues to come from the original service and custom charges.
- Payment records remain transactional.
Example
The primary EOB contains:
- Allowed Amount: $100
- Patient responsibility: $30
The secondary EOB contains:
- Patient responsibility: $10
The current result is:
- Allowed Amount: $100 from primary
- Patient responsibility: $10 from secondary
Seeing values from different primary and secondary EOBs is not necessarily an error.
7. How EOB ordering is determined
For EOBs posted at different times, the system uses the EOB’s system-created date.
If two EOBs have the same created date, the higher EOB ID is used as the tie-breaker.
For multiple claim-payment occurrences inside the same automatic EOB, the original occurrence sequence determines their order.
8. Retirement and exclusion statuses
Older or inactive EOB service lines remain visible but receive a reason explaining why they are no longer current.
SupersededByLaterPosting
A newer ordinary EOB replaced the service line. The frontend displays this as Superseded.
SupersededByCorrection
A formal Correction replaced the earlier adjudication. The frontend displays this as Superseded.
Reversed
This service line belongs to the Original EOB that was withdrawn by a formal Reversal. The frontend displays Reversed.
Reversal
This service line belongs to the EOB transaction that performed the Reversal. The frontend displays Reversal.
IsExcluded
A biller manually excluded the service line. The frontend displays Excluded.
Automatically retired service lines do not participate in current financial calculations. They remain visible only to preserve EOB and transaction history.
9. Automatic retirement versus manual exclusion
Automatic retirement and manual exclusion have the same calculation result: the affected service line is not eligible for current calculations.
However, they are controlled differently:
- Automatic retirement is determined by the EOB adjudication rules.
- Manual exclusion is an action performed by a biller.
- A system-retired line cannot be manually restored.
- A manually excluded line can offer an Undo Exclude action.
- Removing a manual exclusion does not reactivate a line that remains automatically superseded or reversed.
If the latest ordinary EOB service line is manually excluded, the previous eligible service line may become current again.
10. How formal Reversals work
A formal automatic Reversal is identified using the structured payer claim status. Status code 22 identifies a Reversal.
A negative payment amount alone does not identify a formal Reversal. Populate does not guess based on the amount or its sign.
How the Original is identified
Populate attempts to match the Reversal to exactly one earlier eligible automatic adjudication using:
- Organization
- Internal claim
- Primary or secondary payer level
- Payer claim-control number
- Reliable payer identifier
Populate does not choose the target based only on:
- EOB number
- Payer name
- Payment amount
- Similar-looking service lines
When the match succeeds
The Reversal is linked to the Original EOB adjudication.
The result is:
- Service lines on the Original EOB display as Reversed.
- Service lines on the reversing EOB display as Reversal.
- Neither set of service lines is used as the current adjudication.
- An earlier eligible EOB may become current again.
- Both EOBs remain visible in history.
- The payment and negative Reversal payment remain visible as transactions.
Example
The claim has:
- First EOB
- Second EOB
- Reversal of the second EOB
The expected result is:
- First EOB: Becomes the active adjudication again
- Second EOB: Displays Reversed
- Reversing EOB: Displays Reversal
The second and reversing EOB service lines remain read-only and do not participate in current adjudication calculations.
When the match fails
If Populate finds no valid target or more than one possible target, it does not guess.
The automatic EOB posting is rolled back:
- The incomplete EOB is not posted.
- No insurance payment is created.
- Financial balances are not updated.
- Financial View synchronization does not run.
- The Raw ERA records a safe processing error for investigation.
11. How formal Corrections work
A formal Correction must follow a valid Reversal.
The expected lifecycle is:
- Original EOB
- Reversal of the Original
- Corrected adjudication
A later automatic adjudication is classified as a Correction only when it can be matched unambiguously to an open Reversal chain.
A newer EOB is not automatically considered a Correction simply because it was posted later.
12. Correction behavior: complete replacement
A formal Correction is a complete replacement of the reversed claim adjudication for that payer level.
This is different from an ordinary partial EOB.
Example
The Original EOB contains:
- Line A
- Line B
The Original is reversed.
The Correction contains only:
- Line A
The current result is:
- Corrected Line A becomes current.
- Original Line B does not carry forward.
- All pre-Correction service lines in that claim and payer stream are retired.
Omitting Line B from a formal Correction means Line B is not part of the payer’s corrected adjudication.
Ordinary EOB compared with Correction
An ordinary later EOB updates only the service lines it contains. Omitted lines remain active from an earlier eligible EOB.
A formal Correction creates a complete replacement. Lines omitted from the Correction do not survive from the reversed Original.
This difference is one of the most important concepts for Support and Billing teams.
13. Later EOBs after a Correction
After a Correction creates the new baseline, a later ordinary EOB can update that baseline service line by service line.
For example:
- Correction contains Lines A and B.
- A later ordinary EOB contains only Line A.
The result is:
- Line A comes from the later ordinary EOB.
- Line B remains from the Correction.
The later ordinary EOB does not become another Correction unless it follows and completes another valid Reversal chain.
14. Reversing a Correction
A Correction can later be formally reversed.
When this occurs:
- The Correction becomes inactive.
- Its service lines stop contributing to the current financial state.
- The new Reversal remains visible in history.
- An earlier eligible adjudication may become current, depending on the remaining lifecycle.
- Payment and recoupment transactions remain visible in the ledger.
15. Editing automatic Corrections
A successfully posted automatic Correction ERA is a payer-provided financial record and is read-only.
Users cannot:
- Add another patient to it
- Change its claim association
- Change service-line adjudication information
- Change payer-provided amounts
If an edit is attempted, Populate should return a clear validation message rather than a database error.
This restriction applies only to successfully posted automatic Corrections. A manually entered paper EOB remains editable according to the normal manual EOB workflow.
16. Reversal and Correction versus partial recoupment
A formal Reversal and a partial recoupment are different workflows.
Formal Reversal and Correction
A formal Reversal cancels the entire prior claim adjudication occurrence. A Correction then supplies the complete replacement adjudication.
For example:
- Original payment: +$100
- Reversal payment: -$100
- Corrected payment: +$70
- Net recovery: $30
The payer recovered only $30 overall, but it did so through a full Reversal followed by a complete Correction.
Partial recoupment
A standalone partial recoupment recovers only part of the money previously paid.
For example:
- Original payment: +$100
- Partial recoupment: -$30
- Net payment: $70
Unless the payer also sends a formal status-22 Reversal, the original adjudication remains current.
The important rule is:
A negative amount alone does not make an EOB a formal Reversal.
17. Financial values affected by the current adjudication
Only eligible, current EOB service lines contribute to adjudication-based calculations, including:
- Allowed Amount
- Patient responsibility
- Copay
- Coinsurance
- Deductible
- Non-covered amount
- Shift-to-patient amounts
- N408 deductible handling
- Encounter Financial View
- Charges
- Claims
- Patient statements
- Patient invoices
- Insurance Balance
- Insurance Balance explanations
Superseded, Reversed, Reversal, manually excluded, and otherwise lifecycle-ineligible service rows do not participate in these calculations.
18. What remains transactional or unchanged
The following values do not use latest-EOB-only selection:
- Insurance payment transactions
- Negative Reversal payments
- Patient payments
- Refunds
- Recoupments
- Payment allocations
- Ledger history
- Raw EOB history
These records remain visible because they show what financially occurred over time.
The following also remain unchanged:
- Original billed amount
- Original service charges
- Custom-service charges
- Existing CARC classifications
A retired EOB service line does not contribute to current adjudication calculations, even though its related payment transaction may remain visible in payment and ledger history.
19. Insurance Balance
Insurance Balance represents the amount that may still require insurance-side follow-up. It is not the same as total insurance payments or the patient’s balance.
Important rules include:
- Current EOB-derived amounts use only eligible adjudication service lines.
- Recoverable Insurance Adjustments contribute to Insurance Balance.
- Auto Write-Off amounts do not contribute.
- Copay, coinsurance, and deductible are direct patient responsibility.
- Non-covered patient-responsibility amounts do not count as Insurance Adjustments.
- An unresolved valid Reversal can reopen the exact recouped amount.
- A valid Correction closes the related Reversal recoupment.
- Primary recoverable adjustments can remain open after secondary adjudication.
- Denied, rejected, pending, or incomplete primary workflows may keep the billed amount open.
- Out-of-pocket and shift-to-patient encounters have zero Insurance Balance.
20. Scope and important limitations
Formal lifecycle handling currently applies prospectively to newly processed automatic ERAs.
This means:
- Previously posted EOBs are not retroactively classified or linked.
- Manual EOBs do not automatically create formal Reversal or Correction relationships.
- A possible Correction received before its Reversal is not automatically reclassified later.
- Automatic Corrections are read-only after successful posting.
- Manual paper EOBs remain part of the manual workflow.
- Ordinary automatic EOBs continue using the normal latest-service-line rules.
- Supplemental remittances are not separately classified.
- Equivalent duplicate EOBs received under different EOB numbers are not detected through a new content-matching process.
- Claim archive or void status does not replace the EOB lifecycle rules.
A later manual EOB can still supersede an earlier automatic EOB through the ordinary service-line selection rules. It simply does not create a formal Correction relationship.
21. Common scenarios
Scenario 1: Two primary EOBs contain the same service line
Expected result:
- The newer eligible primary line becomes current.
- The older line displays as Superseded.
- The amounts are not added together.
- Both EOBs remain visible in history.
Scenario 2: A later EOB contains only one of two service lines
Expected result:
- The included service line comes from the newer EOB.
- The omitted service line remains current from the earlier EOB.
- Only the replaced line displays as Superseded.
Scenario 3: A secondary EOB is posted after a primary EOB
Expected result:
- Primary and secondary remain separate payer streams.
- The secondary does not mark the primary as Superseded.
- Primary continues to supply Allowed Amount.
- Secondary can become authoritative for patient responsibility.
Scenario 4: A Reversal is posted without a Correction
Expected result:
- The target Original displays as Reversed.
- The reversing EOB displays as Reversal.
- Neither is used as the current adjudication.
- An earlier eligible EOB may become current.
- The Reversal payment remains in transaction history.
Scenario 5: A Reversal is followed by a Correction
Expected result:
- The Original is withdrawn.
- The Correction establishes a complete replacement.
- Original service lines omitted from the Correction do not survive.
- The Reversal and Correction remain visible in history.
Scenario 6: A later ordinary EOB follows a Correction
Expected result:
- The later ordinary EOB updates only the lines it includes.
- Omitted lines remain current from the Correction.
- The later EOB is not automatically classified as another Correction.
Scenario 7: A biller manually excludes the latest ordinary line
Expected result:
- The excluded line stops participating in calculations.
- An earlier eligible service line may become current.
- Undo Exclude is available only for the manual exclusion.
22. Quick reference
- Newer ordinary EOB: Replaces matching included service lines only.
- Partial ordinary EOB: Omitted lines remain active.
- Formal Reversal: Withdraws the full prior claim adjudication occurrence.
- Formal Correction: Completely replaces the reversed adjudication.
- Later ordinary EOB after Correction: Updates the Correction line by line.
- Superseded, Reversed, and Reversal lines: Visible in history but excluded from current adjudication calculations.
- Manual exclusion: Controlled by the biller and can be undone.
- Automatic retirement: Controlled by the system and cannot be manually undone.
- Negative payment: Not automatically a formal Reversal.
- Payments and ledger entries: Remain transactional.
- Automatic Correction: Read-only after successful posting.
- Manual paper EOB: Remains part of the manual editing workflow.