# DenQAI: payer payment event ledger

File-specific companion · 2026-09-10

## Purpose

What caused this payment reversal or shortfall, and what action remains open?

**Who:** Billing lead and authorized payer-dispute reviewer

**Records:** Coded remittance summary; bank period; payer notice; applicable dispute terms and supporting ledger record.

## Complete the file

1. Choose the event_type and separate service_period, notice_or_remittance_period, and cash_period.
2. Enter amount, cash_treatment, and stated_reason without treating a notice as money already withdrawn.
3. Record the deadline, next_action, final_disposition, and prevention_change with an accountable owner.

## Definitions

- **Cash treatment:** Whether and how the event has affected bank cash.
- **Final disposition:** Documented outcome after review or dispute, not the initial allegation.
- **Prevention change:** Process correction intended to reduce recurrence.

## Fictional example

Fictional example: Event 6 is a $450 duplicate-payment reversal notice; cash_treatment is No cash event yet until the bank/remittance reconciliation confirms an offset.

## Review and next action

Reconcile the event to cash and have the reviewer resolve the earliest dispute deadline.

The ledger records events; it does not determine repayment duties or patient responsibility. Keep patient and exact claim details out of public tools.

[Related DenQAI guide](https://denqai.com/insurance)

## AI coach prompt

Help me use DenQAI’s payer payment event ledger. My question is: What caused this payment reversal or shortfall, and what action remains open? Explain these terms in plain language: Cash treatment, Final disposition, Prevention change. Ask one question at a time about the required records: Coded remittance summary; bank period; payer notice; applicable dispute terms and supporting ledger record. Walk through the supplied fictional example before asking me for inputs. Treat every missing value as unknown, not zero. Do not invent source records, contract terms, legal conclusions, or clinical facts. Use only permitted fictional or aggregate, non-identifying information. Follow this boundary: The ledger records events; it does not determine repayment duties or patient responsibility. Keep patient and exact claim details out of public tools. End with the missing evidence and this next step: Reconcile the event to cash and have the reviewer resolve the earliest dispute deadline.

## AI review prompt

Review my permitted fictional or aggregate draft of DenQAI’s payer payment event ledger against the file instructions. Check each required field and period, units, evidence locator, assumptions, arithmetic where formulas are actually supplied, and unresolved contradictions. Check the sequence: Choose the event_type and separate service_period, notice_or_remittance_period, and cash_period. Enter amount, cash_treatment, and stated_reason without treating a notice as money already withdrawn. Record the deadline, next_action, final_disposition, and prevention_change with an accountable owner. Separate facts from assumptions and missing records. Do not supply unsupported numbers or make a professional decision for me. Apply this limitation: The ledger records events; it does not determine repayment duties or patient responsibility. Keep patient and exact claim details out of public tools. Return corrections, questions for the responsible reviewer, and the next action.