OT Invoice & Superbill Extraction for Multi-Payer Close

OT invoice and superbill extraction turns mixed occupational therapy PDFs into one service-line spreadsheet. The useful workbook does not stop at invoice number and total. It captures patient, payer, date of service, CPT or HCPCS, ICD-10, units or minutes, modifiers, billed amount, allowed amount, paid amount, write-off, patient responsibility, authorization, denial codes, and deposit reference so each payer's documents reconcile to the same ledger.

That matters because an OT practice rarely hands its bookkeeper one tidy export. A month-end folder may include therapist-generated superbills, commercial insurance EOBs, Medicaid remittance advice, school-district invoices, private-pay statements, and thin reports from a practice-management system. Each source describes the same work in a different format. The close workbook has to make those formats comparable without flattening away the fields that explain payment, denial, and patient balance.

The wrong starting point is an occupational therapy invoice template. Templates help create a bill. The bookkeeping problem begins later, after the practice has billed, payers have responded, patients have balances, and deposits have landed in the bank. At that point, the question is not "what should an OT invoice look like?" It is "which service lines were billed, which ones paid, which ones adjusted, and which ones still need follow-up?"

For a multi-payer OT close, the spreadsheet should be built around service lines. A 97530 therapeutic activities session, a 97165 evaluation, and a private-pay balance can all appear in different document families, but the bookkeeper needs one place to compare the service date, payer, amount, modifier, authorization, denial reason, and cash receipt. That is the practical job behind occupational therapy invoice reconciliation in Excel: turning source-document variety into a ledger the practice can actually close against.

Choose the row grain before choosing columns

The safest row grain for OT reconciliation is one row per patient, date of service, service code, and payer outcome. If a source document has one claim with three service lines, the close workbook should have three service rows. If an EOB pays one line, denies one line, and adjusts another, those outcomes need to stay visible at line level rather than being buried inside an invoice total.

Invoice-level rows create problems in OT because a single document can carry multiple evaluation and treatment codes. A bookkeeper may see 97165, 97166, or 97167 for low-, moderate-, or high-complexity evaluations, 97168 for re-evaluation, and treatment codes such as 97110, 97112, 97530, 97535, 97755, or 97760. Those codes are not a coding lesson in this workbook; they are reconciliation fields. If the 97530 line was allowed and paid but the 97760 line denied, an invoice-level row hides the difference.

The same logic applies to ICD-10, units, minutes, modifiers, provider NPI, and place of service. These fields help explain why a payer paid, adjusted, or denied a line. They should be extracted as context for the billed service, not interpreted as clinical guidance.

Keep document identifiers separate from accounting identifiers. Claim number, invoice number, patient account, payer trace number, check number, EFT reference, and deposit batch all answer different questions. A therapy-session extraction workflow has similar line-level needs to ABA therapy invoice extraction to Excel, but an OT private practice bookkeeping spreadsheet needs OT-specific code, modifier, authorization, and payer fields instead of a generic session table.

Map each payer document into the same ledger

The same OT session can look completely different depending on the payer document. A commercial EOB might show billed, allowed, paid, contractual adjustment, patient responsibility, and remark codes. A Medicaid remittance advice file may use program-specific adjustment language and remittance groupings. A private-pay statement may show original charge, payment received, balance due, and aging status. A school-district invoice may show service date, student or client identifier, minutes, contract rate, and approval status.

The workbook needs to preserve the source wording while mapping each document into common columns. "Contractual adjustment," "provider responsibility," "write-off," "recoupment," and "overpayment recovery" should not collapse into one vague adjustment field unless the original payer label is still retained. The normalized field helps month-end totals. The original text helps the biller or practice owner trace what the payer actually said.

This is where occupational therapy Medicaid remittance advice extraction belongs in the workflow. Medicaid RAs are one payer channel inside the close workbook, alongside commercial EOBs, TRICARE where relevant, district invoices, and patient statements. If the practice receives school-related remittance documents, the logic is close to school district Medicaid R&S report extraction, but the OT close workbook still has to tie those lines back to the practice's broader payer mix.

A prompt-defined extraction workflow is useful because the bookkeeper can describe the exact OT fields and payer mappings needed for the close workbook. With invoice data extraction for mixed payer PDFs, the prompt can ask for patient, payer, CPT, units, modifiers, allowed amount, paid amount, denial codes, authorization number, and deposit reference across superbills, EOBs, Medicaid RAs, and private-pay statements, then export the structured result to Excel, CSV, or JSON.

Give denials their own analysis tab

Denials should not live only as notes on individual service rows. A close workbook needs a denial-analysis tab that references the service-line row ID and captures payer, claim number, denial date, CARC, RARC, payer-specific code, denied amount, patient responsibility impact, original payer text, and follow-up owner.

The row ID is important because denial work starts with the service line but often gets resolved elsewhere. The bookkeeper may need to give the biller a list of claims where authorization was exhausted, the practice manager a list of patient balances affected by payer decisions, and the owner a monthly view of denied dollars by payer. Those views should all trace back to the source document and the original service line.

OT denial patterns have their own vocabulary. A pediatric practice may see prior authorization exhaustion, missing referral data, duplicate billing, or place-of-service conflicts. Practices that use OT assistants may need to surface OTA modifier mismatches. Lines approaching threshold-related documentation review may need to be flagged for biller or clinician review. None of that makes the bookkeeper responsible for coding or clinical necessity, but it does mean the workbook should expose the pattern instead of leaving it buried in payer PDFs.

Normalize denial codes without erasing payer language. CARC and RARC fields help compare denials across payers, while payer-specific codes and original denial text preserve the details needed for follow-up. Over several closes, that separate tab becomes more useful than a pile of one-off denial notes because it shows which payers, codes, settings, and authorization problems are recurring.

Track KX, modifiers, and authorizations as close fields

Modifier and authorization fields belong in the close workbook because they explain why a line may need review before the next billing cycle. For CY 2026, CMS lists the KX modifier threshold as $2,480 for occupational therapy services and separately $2,480 for physical therapy and speech-language pathology services combined, according to its CMS 2026 therapy services KX modifier thresholds guidance. In a bookkeeping workbook, that threshold is a flag for review and documentation follow-up, not payer-policy advice.

At minimum, the extracted ledger should carry GO, CO, KX, and telehealth modifiers when they appear on the source documents. It should also capture authorization number, authorized visits or units, used visits or units, remaining visits or units, and expiration date. Those fields let the practice see whether a denied or underpaid line might relate to authorization exhaustion, a missing modifier, a provider-credential issue, or a payer rule that needs biller follow-up.

Pediatric OT makes authorization tracking especially practical. A commercial payer approval letter, Medicaid remittance advice, school-related service record, and practice-management export may not carry the same authorization details. If the close workbook stores authorization number and remaining balance consistently, the bookkeeper can flag mismatches before they turn into month-after-month denials.

Units and minutes fit the same pattern. The workbook is not deciding how an OT should bill timed services. It is preserving the units and minutes shown on the source documents so the practice can spot mismatches between superbills, payer responses, and payment outcomes.

Separate OT-specific settings without fragmenting the workbook

An OT practice can serve the same client population through different settings, and the source documents change with the setting. Outpatient clinic lines may emphasize CPT, modifier, payer, allowed amount, and patient responsibility. Home health records may add assistant-related details where applicable. School-based and early-intervention documents may rely more heavily on minutes, approval status, student identifiers, or contract rates. SNF and acute rehab contexts can introduce their own payer and place-of-service complications.

The close workbook should not become a separate spreadsheet for every setting. Add a setting column and a payer-channel column, then let the workbook filter outpatient clinic, home health, school-based, early-intervention, SNF, private-pay, and district-contract lines without breaking the month-end totals. That structure keeps the ledger reconcilable while still preserving the fields that make each setting different.

Provider identifiers deserve the same treatment. A sole proprietor may use an individual NPI, while an entity may also have a group NPI. The workbook should capture the provider or organization identifier shown on the source document, along with supervising therapist or credential fields when they affect payer follow-up. Those details are often the difference between a clean reconciliation note and a vague "billing issue" category.

The pattern is related to multi-payer SLP invoice and superbill extraction, but OT needs its own workbook vocabulary. The SLP and OT close problems both involve mixed payer documents, denials, and deposits. The OT workbook has to carry OT evaluation codes, KX threshold tracking, GO and CO modifier visibility, and setting markers that match occupational therapy practice rather than speech therapy by default.

Reconcile extracted OT data to deposits and patient balances

The month-end workflow is straightforward once the workbook has the right shape. Collect the superbills, EOBs, Medicaid RAs, district invoices, private-pay statements, payer portal PDFs, and PM or EHR exports for the period. Extract them into the normalized service-line ledger. Then compare payer payments to bank deposits, tie patient responsibility to statements or open balances, categorize write-offs and adjustments, and create follow-up views for denials and authorization problems.

Practice-management exports still matter, but they are reference files rather than the whole close. They can confirm what the practice expected to bill, which appointments were completed, or which claims were submitted. The extracted workbook explains what came back from payers and patients, especially when the practice's documents come from multiple portals, payer PDFs, clearinghouse files, and internal exports that do not agree cleanly.

Private-pay statements deserve the same structure as payer documents. A patient balance should connect back to the service date, charge, payment, adjustment, and current responsibility amount. When statements are one of the source inputs, patient billing statement extraction to Excel can support the patient-side part of the same close process.

The result is a workbook the bookkeeper can hand to the OT owner without translating a pile of PDFs by memory. It shows what was billed, what was paid, what was adjusted, what still needs follow-up, and which source document supports each line.