# Payer, credentialing and cash continuity workbook

Updated 2026-09-19.

## Purpose

A 26-week cash gap, reserve margin, evidenced readiness and separate payment-event exposure — what do the entered records support?

## Who uses this

Owner, credentialing lead, billing lead, and authorized contract reviewer

## Records to gather

Coded payer relationships, allowed amounts, collection assumptions, participation and bank timing, recovery assumptions, reserves and event evidence. For authorized offline fee review, gather coded annual units and both baseline and buyer allowed amounts.

## Steps

1. Read Decision Summary and Use and Limits. The Fictional Example tab contains separate cash and fee examples; neither is included in your live input totals.
2. Enter up to 20 coded relationships in Cash Inputs rows 6–25. Enter 0 only for a known zero, use weeks relative to the transition start, and record your cash-assumption support. Review all 26 weeks and keep payment-event totals separate from the cash bridge.
3. In Payer Map, enter the payer code shown on the evidence in column K. It must match the linked cash-row code in column A, with Reviewed with limits in column I and a supporting record locator in column J, to clear the evidence exception.
4. In Credentialing Path, enter each supporting record’s payer code in column H. Clearance requires a match to column A, Written confirmation or Not applicable—reason documented in column D, and a record or documented reason in column E. Recheck evidence when replacing or reordering a cash-row relationship; mismatched codes reopen its checks.
5. Use the ten blank live Fee Portability rows 6–15 only for authorized offline fee review. Enter a group code, annual units and both allowed amounts in columns A–D, with evidence and limitations in F–G. A partially completed row makes the total unavailable; known zero inputs remain valid. The fee example is on Fictional Example and never enters this total.
6. Review all seven Safety Checks. Documented or Not applicable in column C requires a supporting record or reason in column D. Open, Partly documented and blank statuses remain unresolved, as do unsupported closure statuses.
7. Use the prepared Payment Events and Contract Calendar rows for up to 100 records each. Verify notice-counting and delivery requirements against the controlling contract; assign remaining work in Review Actions.

## Key terms

- **Effective week**: Entered week when payable participation begins; it requires supporting evidence.
- **Service-to-bank days**: Modeled lag between service and bank receipt.
- **Timing gap**: Cumulative difference between steady and transition bank cash in the workbook.
- **Evidence payer code**: Code identifying the relationship covered by a supporting record; it must match the linked cash-row payer code before a map or milestone check clears.
- **Unresolved safety check**: A required check without Documented or Not applicable status and a supporting record or reason; partial and blank entries remain unresolved.

## Fictional example

The separate fictional three-payer cash example produces $30,460 steady weekly cash, a $192,830 peak timing gap and a −$32,830 margin against a $160,000 reserve. The separate fictional fee example totals −$6,740; your ten live fee rows start blank and exclude that example.

## Next action

Review each unavailable or adverse result, then assign the missing record, reviewer, due date and next action in Review Actions.

## Limits

Formulas are editable and sheet protection is not enabled. Use only the prepared rows and keep a clean copy. Recalculation and XLSX reimport were checked with Artifact Tool; Excel desktop/web, Google Sheets and native printing have not been interactively tested. These are aggregate planning tools, not professional verification. Fee Portability is restricted to authorized offline review. Keep confidential fee details, patient information, credentials and unredacted contracts out of public tools; share only permitted coded or aggregate information.

## AI coaching

Help me complete this DenQAI file using the context below. Explain the supplied fictional example first, then ask one question at a time about my permitted fictional or aggregate, non-identifying inputs. Treat missing values as unknown, not zero. Keep example values separate from my case. Do not invent records, source verification, contract terms or professional conclusions. Identify the missing evidence and responsible reviewer before the next action.

File: Payer, credentialing and cash continuity workbook (XLSX).

Question: A 26-week cash gap, reserve margin, evidenced readiness and separate payment-event exposure — what do the entered records support?

Records to gather: Coded payer relationships, allowed amounts, collection assumptions, participation and bank timing, recovery assumptions, reserves and event evidence. For authorized offline fee review, gather coded annual units and both baseline and buyer allowed amounts.

Fields or sheets: Start Here; Decision Summary; Payer Map; Credentialing Path; Cash Inputs; 26-Week Cash; Fee Portability; Participation Scenarios; Payment Events; Safety Checks; Questions & Definitions; Sources; Fictional Example; Contract Calendar; Review Actions; Use and Limits.

Key terms:
Effective week: Entered week when payable participation begins; it requires supporting evidence.
Service-to-bank days: Modeled lag between service and bank receipt.
Timing gap: Cumulative difference between steady and transition bank cash in the workbook.
Evidence payer code: Code identifying the relationship covered by a supporting record; it must match the linked cash-row payer code before a map or milestone check clears.
Unresolved safety check: A required check without Documented or Not applicable status and a supporting record or reason; partial and blank entries remain unresolved.

Steps:
1. Read Decision Summary and Use and Limits. The Fictional Example tab contains separate cash and fee examples; neither is included in your live input totals.
2. Enter up to 20 coded relationships in Cash Inputs rows 6–25. Enter 0 only for a known zero, use weeks relative to the transition start, and record your cash-assumption support. Review all 26 weeks and keep payment-event totals separate from the cash bridge.
3. In Payer Map, enter the payer code shown on the evidence in column K. It must match the linked cash-row code in column A, with Reviewed with limits in column I and a supporting record locator in column J, to clear the evidence exception.
4. In Credentialing Path, enter each supporting record’s payer code in column H. Clearance requires a match to column A, Written confirmation or Not applicable—reason documented in column D, and a record or documented reason in column E. Recheck evidence when replacing or reordering a cash-row relationship; mismatched codes reopen its checks.
5. Use the ten blank live Fee Portability rows 6–15 only for authorized offline fee review. Enter a group code, annual units and both allowed amounts in columns A–D, with evidence and limitations in F–G. A partially completed row makes the total unavailable; known zero inputs remain valid. The fee example is on Fictional Example and never enters this total.
6. Review all seven Safety Checks. Documented or Not applicable in column C requires a supporting record or reason in column D. Open, Partly documented and blank statuses remain unresolved, as do unsupported closure statuses.
7. Use the prepared Payment Events and Contract Calendar rows for up to 100 records each. Verify notice-counting and delivery requirements against the controlling contract; assign remaining work in Review Actions.

Fictional example:
The separate fictional three-payer cash example produces $30,460 steady weekly cash, a $192,830 peak timing gap and a −$32,830 margin against a $160,000 reserve. The separate fictional fee example totals −$6,740; your ten live fee rows start blank and exclude that example.

Limits:
Formulas are editable and sheet protection is not enabled. Use only the prepared rows and keep a clean copy. Recalculation and XLSX reimport were checked with Artifact Tool; Excel desktop/web, Google Sheets and native printing have not been interactively tested. These are aggregate planning tools, not professional verification. Fee Portability is restricted to authorized offline review. Keep confidential fee details, patient information, credentials and unredacted contracts out of public tools; share only permitted coded or aggregate information.

Next action: Review each unavailable or adverse result, then assign the missing record, reviewer, due date and next action in Review Actions.

## AI review

Review my permitted fictional or aggregate, non-identifying draft against the DenQAI file context below. Check the actual fields, units, periods, evidence and unresolved contradictions. Use arithmetic only where the stated model supports it; a CSV has no embedded formulas. Keep missing values unknown and separate facts, assumptions and the fictional example. Return specific corrections, questions for the responsible reviewer and the next action; do not invent professional approval.

File: Payer, credentialing and cash continuity workbook (XLSX).

Question: A 26-week cash gap, reserve margin, evidenced readiness and separate payment-event exposure — what do the entered records support?

Records to gather: Coded payer relationships, allowed amounts, collection assumptions, participation and bank timing, recovery assumptions, reserves and event evidence. For authorized offline fee review, gather coded annual units and both baseline and buyer allowed amounts.

Fields or sheets: Start Here; Decision Summary; Payer Map; Credentialing Path; Cash Inputs; 26-Week Cash; Fee Portability; Participation Scenarios; Payment Events; Safety Checks; Questions & Definitions; Sources; Fictional Example; Contract Calendar; Review Actions; Use and Limits.

Key terms:
Effective week: Entered week when payable participation begins; it requires supporting evidence.
Service-to-bank days: Modeled lag between service and bank receipt.
Timing gap: Cumulative difference between steady and transition bank cash in the workbook.
Evidence payer code: Code identifying the relationship covered by a supporting record; it must match the linked cash-row payer code before a map or milestone check clears.
Unresolved safety check: A required check without Documented or Not applicable status and a supporting record or reason; partial and blank entries remain unresolved.

Steps:
1. Read Decision Summary and Use and Limits. The Fictional Example tab contains separate cash and fee examples; neither is included in your live input totals.
2. Enter up to 20 coded relationships in Cash Inputs rows 6–25. Enter 0 only for a known zero, use weeks relative to the transition start, and record your cash-assumption support. Review all 26 weeks and keep payment-event totals separate from the cash bridge.
3. In Payer Map, enter the payer code shown on the evidence in column K. It must match the linked cash-row code in column A, with Reviewed with limits in column I and a supporting record locator in column J, to clear the evidence exception.
4. In Credentialing Path, enter each supporting record’s payer code in column H. Clearance requires a match to column A, Written confirmation or Not applicable—reason documented in column D, and a record or documented reason in column E. Recheck evidence when replacing or reordering a cash-row relationship; mismatched codes reopen its checks.
5. Use the ten blank live Fee Portability rows 6–15 only for authorized offline fee review. Enter a group code, annual units and both allowed amounts in columns A–D, with evidence and limitations in F–G. A partially completed row makes the total unavailable; known zero inputs remain valid. The fee example is on Fictional Example and never enters this total.
6. Review all seven Safety Checks. Documented or Not applicable in column C requires a supporting record or reason in column D. Open, Partly documented and blank statuses remain unresolved, as do unsupported closure statuses.
7. Use the prepared Payment Events and Contract Calendar rows for up to 100 records each. Verify notice-counting and delivery requirements against the controlling contract; assign remaining work in Review Actions.

Fictional example:
The separate fictional three-payer cash example produces $30,460 steady weekly cash, a $192,830 peak timing gap and a −$32,830 margin against a $160,000 reserve. The separate fictional fee example totals −$6,740; your ten live fee rows start blank and exclude that example.

Limits:
Formulas are editable and sheet protection is not enabled. Use only the prepared rows and keep a clean copy. Recalculation and XLSX reimport were checked with Artifact Tool; Excel desktop/web, Google Sheets and native printing have not been interactively tested. These are aggregate planning tools, not professional verification. Fee Portability is restricted to authorized offline review. Keep confidential fee details, patient information, credentials and unredacted contracts out of public tools; share only permitted coded or aggregate information.

Next action: Review each unavailable or adverse result, then assign the missing record, reviewer, due date and next action in Review Actions.

## Related guide

[Open the related guide](https://denqai.com/insurance/workbench)