PTCB Billing & Reimbursement common mistakes
PTCB Billing & Reimbursement · Understand the traps and how to avoid them.
When a claim comes back with a transaction-level error (bad BIN, missing cardholder ID, NDC not on formulary), the candidate answers 'file an appeal' or 'call the patient's plan to fight it.'
The words rejection and denial are used interchangeably in everyday pharmacy talk, so candidates collapse two processes that sit at completely different stages of adjudication.
What to do instead
Anchor the distinction: a rejection means the claim never adjudicated - nothing was paid or denied - and it is fixed by correcting the data and resubmitting. A denial means the payer adjudicated and refused payment, and only that outcome goes to the appeals process. Train yourself to ask first: did this claim reach adjudication at all?
With a patient who has both Medicare and Medicaid, or Medicare plus an employer group health plan, the candidate bills Medicaid or the group plan first because it 'seems like the better coverage.'
Payer order feels intuitive ('best coverage pays first') rather than rule-based, and the secondary-payer rules are learned as isolated facts instead of a decision sequence.
What to do instead
Memorize the ordering logic, not just payer names: Medicare Secondary Payer rules generally make a group health plan primary for a working-aged beneficiary whose employer has 20 or more employees, while Medicaid is a payer of last resort. Before billing, confirm working status, employer size, and any other active coverage, and document the primary-payer determination.
The candidate enters the metric quantity in the days-supply field (or the day count in the quantity field), for example placing 30 in days supply for a 30-tablet prescription written for twice daily use.
Both fields are small integers on screen, both often show '30,' and most practice prescriptions are once daily, so the error stays invisible during study and only surfaces with a titration or a PRN.
What to do instead
Compute days supply independently every time: quantity dispensed divided by the maximum daily dose, then round up for PRN and taper directions. Verify the pair makes sense before transmission - 60 tablets with 30 days supply implies BID use - and recheck both fields whenever quantity, strength, or directions change.
The claim is submitted using an NDC for a different package size than the one actually dispensed, or a brand NDC is billed when a generic exists with no product-selection code, and the candidate treats the resulting rejection as a payer glitch.
Pharmacies stock multiple package sizes of the same drug, the software may default to a preferred NDC, and product-selection (DAW) logic is treated as a front-end switch rather than a billable data element.
What to do instead
Bill the exact NDC of the package opened, and check that the billed quantity is expressed in that NDC's unit of measure so it cannot exceed the package size. When brand is dispensed despite an available generic, confirm who requested it and submit the matching product-selection code; without a valid code the payer will reject or reduce payment.
The candidate automatically runs a manufacturer copay card on a Medicare Part D or Medicaid claim to zero out the patient's cost, then treats the resulting rejection as a card-processing problem.
Copay cards work smoothly in commercial claims, so the candidate generalizes the workflow to every patient without connecting it to federal program rules.
What to do instead
Federal health care program beneficiaries cannot use manufacturer copay assistance - it raises anti-kickback exposure for the pharmacy. Screen the payer before any coupon is applied, and route those patients to manufacturer patient assistance programs, charitable foundations, or plan-negotiated pricing instead. Also keep copay, coinsurance, and deductible distinct when explaining patient cost.
A secondary claim is transmitted before the primary claim is fully resolved, or it goes out without the primary payer's paid amount and the correct other-coverage indicator.
Staff want to finish the sale quickly, and the secondary claim looks identical to a normal claim on screen, so the coordination fields get skipped as optional.
What to do instead
Complete the primary first and record its paid amount, patient responsibility, and outcome, then reverse any earlier secondary claim before rebilling. Build a habit of reading the other-coverage code back to yourself: it must describe what the primary actually did, or the secondary payer will pay as if no other coverage existed and create an overpayment the pharmacy must return.
The candidate estimates reimbursement by taking a percentage of AWP and stops there, or uses AWP and WAC as if they were the same number, and forgets the professional dispensing fee.
Reimbursement questions mix four benchmarks - AWP, WAC, MAC, and usual and customary - and candidates memorize one formula rather than understanding which benchmark the contract names and what each represents.
What to do instead
Work the contract language step by step: identify the basis (AWP minus a percentage, WAC plus a percentage, or MAC), apply the discount, then add the dispensing fee, and check the result against the pharmacy's usual and customary charge because payers generally reimburse the lesser of the calculated amount and U&C. AWP is a list benchmark, WAC is the manufacturer's price to wholesalers, and MAC is the payer's maximum allowed cost.
A duplicate-therapy or drug-interaction edit appears at adjudication, and the candidate responds by resubmitting the same claim repeatedly or filing an appeal instead of resolving the clinical conflict.
Point-of-sale conflict edits arrive looking like payment errors, and candidates have not seen that these require a documentation trail rather than a payment argument.
What to do instead
Treat the conflict as a clinical workflow: contact the prescriber, document the decision, and if therapy proceeds, resubmit with the appropriate reason-for-service and professional-service codes reflecting the actual intervention performed. Never override a conflict without a documented rationale - an undocumented override is both a claims error and a compliance risk.
After a paid claim needs correction, the candidate simply transmits a new claim for the same prescription and fill number, and keeps doing so when it rejects as a duplicate.
The instinct is that a newer claim replaces the older one, and the reversal step feels like extra work when the corrected claim is ready to send.
What to do instead
Correct through reversal-and-rebill: reverse the paid claim so the payer's record is clean, wait for the reversal to confirm, then submit the corrected claim, all within the payer's timely filing window measured from the original date of service. Keep the reversal and resubmission documentation - an unreversed paid claim plus a second claim is a duplicate-billing finding in an audit.
To get a claim paid, the candidate overrides eligibility or utilization edits - keying a lost or stolen refill, forcing a refill-too-soon, or billing a 90-day quantity when only 30 days were dispensed.
Overrides exist in the software as convenient bypasses, and the immediate goal of a clean paid claim crowds out the downstream consequences.
What to do instead
Use an override only when the facts genuinely support it - the medication really was lost, the prescriber really did authorize an early fill - and document the supporting detail in the patient record. Quantity and days supply must always match what left the shelf; billing for product not dispensed is fraud, not a billing trick, and the claim record is retained for audit.