Claim to Payment Workflow
Key Takeaways
- Claim submission turns coded and charged services into a payer request for reimbursement.
- Clearinghouse edits can reject claims before payer adjudication.
- Payer adjudication determines allowed amounts, payments, denials, adjustments, and patient responsibility.
- Payment posting must match the remittance advice and identify underpayments or incorrect denials.
- Secondary billing and patient billing should occur only after primary payer processing and applicable rules are handled.
Once documentation is complete, codes are assigned, and charges are captured, the account moves into claim generation. The claim communicates who the patient is, who provided the service, what was done, why it was medically necessary, when and where it occurred, what was charged, and what payer should process it. CBCS candidates should know the broad purpose of common claim formats, such as professional claims and institutional claims, while focusing on the workflow and error logic behind them.
Before a claim reaches the payer, it may pass internal claim edits and clearinghouse edits. These edits check for missing or invalid information, formatting problems, payer-specific rules, invalid code combinations, member ID issues, or required fields. If the claim fails these edits before payer adjudication, the account may show a rejection. Rejections should be corrected quickly because the payer may not consider the original submission a valid claim for timely filing purposes.
After the payer accepts the claim for processing, adjudication begins. The payer compares the claim to eligibility, benefits, contracts, medical necessity rules, coding edits, coordination of benefits, and policy requirements. The payer may pay the claim, deny all or part of it, apply a contractual adjustment, assign deductible or coinsurance to the patient, request information, or process it as secondary.
A typical claim-to-payment flow is:
| Step | Output | CBCS focus |
|---|---|---|
| Claim generation | Claim record ready for submission. | Correct patient, provider, payer, codes, modifiers, charges, dates, units, and attachments. |
| Internal edits | Clean or failed claim. | Fix preventable issues before transmission. |
| Clearinghouse transmission | Accepted or rejected transaction. | Correct rejections and preserve timely filing awareness. |
| Payer adjudication | Payment, denial, adjustment, or request. | Interpret payer decision and reason codes. |
| Remittance | ERA or paper remittance advice. | Post payment, contractual adjustments, and patient responsibility accurately. |
| Follow-up | Appeal, corrected claim, secondary claim, patient statement, refund, or write-off. | Choose the action payer rules support. |
Payment posting is more than depositing money. The posting team compares the payment and remittance to expected reimbursement. The remittance advice may show billed charge, allowed amount, paid amount, adjustment reason, patient responsibility, denial reason, and remark codes. Contractual adjustments reduce the balance according to payer agreements. Deductible, copay, and coinsurance amounts may become patient responsibility after payer processing. Noncovered charges may or may not be billable to the patient depending on payer rules, notices, and contracts.
Secondary billing requires coordination of benefits. If a patient has more than one active plan, the primary payer usually processes first, then the secondary payer receives the claim with primary payment information. Billing the patient too early can create complaints and compliance problems. The patient statement should reflect payer adjudication, contractual adjustments, secondary payments, and any required notices.
Exam trap: a denial is not always solved by sending the same claim again. If the payer denied for missing authorization, unsupported medical necessity, untimely filing, or bundled services, a duplicate submission may simply deny again. The correct action may be an appeal with documentation, a corrected claim, a provider query, a write-off according to policy, or patient billing if allowed. The CBCS skill is to match the payer response to the next valid action, not to reflexively resubmit every unpaid account.
Reading the Claim as a Story
A claim tells a payer a structured story: who the patient is, who provided care, what happened, why it was medically necessary, when and where it happened, what payer rules apply, and how much was charged. The CMS-1500, UB-04, and electronic 837 transactions are different formats for that story. If any part is inconsistent, the payer may reject, deny, downcode, request records, or assign responsibility differently than expected.
Before submission, a billing specialist should check patient and subscriber identifiers, payer routing, provider identifiers, place of service, dates of service, diagnosis codes, diagnosis pointers, procedure or supply codes, modifiers, units, charge amounts, authorization numbers, accident or employment indicators, and required attachments. The exact fields vary by claim type and payer, but the principle is stable: the claim must be complete, consistent, and supported by documentation.
After submission, the workflow shifts from creation to monitoring. A front-end rejection means the claim did not enter adjudication and should be corrected quickly. A payer denial appears after adjudication and requires analysis of the reason code, payer policy, documentation, and timely filing limits. A payment requires posting of allowed amount, paid amount, contractual adjustment, patient responsibility, and any secondary billing. The exam often asks which step comes next, so always identify whether the claim is pre-submission, rejected, denied, paid, underpaid, overpaid, or ready for patient billing.
A claim fails a clearinghouse edit because the member ID is invalid. What should happen next?
Which document or transaction is commonly used to post payer payments and adjustments?
Why is sending the same unpaid claim again not always the best response to a denial?