School District Occupational Therapy Contract Billing Guide

School district occupational therapy contract billing pairs a monthly invoice with a supervisor-signed timesheet and a service log. The service log ties every minute of direct and indirect time to a goal area on the student's IEP. Districts pay the packet without rebilling when OTR/L or COTA credentials appear on each line item, when evaluation, treatment, and IEP-team meeting time are separated, and when the invoice math matches the contract's billing model — flat-rate, per-session, per-IEP-minute, or retainer-plus-overage.

Three documents make up the packet. The invoice carries the dollar total, line items by student or by service block, the contractor's credentials, and the contract math the district will verify. The supervisor-signed timesheet carries daily entries showing start and end times, student-level granularity, the credential of the delivering practitioner, and the supervisor signature that validates any COTA-delivered time. The service log carries minute-by-minute logging tied to specific IEP goals, expressed in OT-native service vocabulary — sensory integration, fine motor and handwriting, ADL and IADL training, assistive technology consultation, executive-function intervention — so the entry connects to the goal it serves.

The same documentation feeds the district's downstream Medicaid claim under state programs like CA Medi-Cal LEA, NJ SEMI, and TX SHARS. The OT contractor does not file the Medicaid claim, but the contractor's service-log quality controls whether the district can recover federal match for the services delivered. That upstream relationship is why district business offices sometimes ask for service-log detail the invoice itself doesn't strictly need.

This guide is for the contractor on the provider side of that workflow — the solo OTR/L on a district contract, the OT-led non-public agency owner, or the billing and administrative staff inside an NPA. The reader already has the contract and is producing the month-end packet that AP will pay. Contract-finding, NPA incorporation, and rate negotiation sit upstream of this lane and are out of scope here.

A separate OT-specific guide exists alongside the equivalent monthly billing guide for school-based SLPs and the general provider-side guide to invoicing a school district for related services because the OT side carries specifics those articles don't and shouldn't: the OTR/L–COTA credential split and its supervision documentation discipline, the 8-minute rule for time-unit contracts (OT and PT carry it; SLP doesn't), the GO and CO modifiers that govern any private-practice work the OT runs alongside the school contract, and the IEP goal vocabulary the service log uses to describe OT intervention. Those specifics control whether the packet pays.

Invoice Structure: Header, Line Items, and Retainer-Plus-Overage Math

The invoice is the document the district AP clerk works through first. It needs to pass a quick clerical scan — header complete, line items legible, math defensible — before it reaches anyone who would read the timesheet or the service log. Treat the invoice as the cover sheet that earns the rest of the packet a look.

Header fields the district expects. Contractor or NPA legal name, OTR/L licence number, NPI, district name, contract or PO reference number, billing period (month and year), invoice number, invoice date, and remit-to address. The licence number and NPI both belong on the invoice but identify different things: the licence number is state-issued and identifies the practitioner under the state's OT practice act, while the NPI is the national identifier used for CMS-aligned billing and the one the district's Medicaid biller will quote on the downstream claim. Missing either is a frequent rebill trigger.

Line-item structure. Three structures are common, and the contract usually points to one:

• By-student. One line per student, with the month's total minutes or sessions and the resulting dollar total. Suits per-IEP-minute contracts and any contract where the district's Medicaid biller works student-by-student.
• By-service-block. Evaluation, treatment, IEP-team meetings, and parent consultation grouped into their own line totals, with student detail backing each block on the timesheet or service log. Suits flat-rate retainer contracts where the dollar total doesn't move student by student but the district still wants the work-type breakdown.
• By-date. Each session as its own line, with date, student, minutes, credential, and rate. Suits per-session contracts and any contract where the district reconciles invoice lines against district-side attendance records session by session.

Credentials on every line. Whichever structure the line items use, the credential of the delivering practitioner — OTR/L for the licensed therapist, COTA for the certified assistant — appears on each line. When both delivered portions of a single line's service under supervision, the split is visible: minutes by OTR/L, minutes by COTA, with the supervising OTR/L identified. Credentials absent from a line item is one of the four standard reasons a district rebills an OT invoice.

The four common billing models, on the invoice. School contracts price OT work in one of four ways, and each lands on the invoice differently.

A flat-rate retainer is a single monthly fee for an agreed scope (caseload size, weekly hours, defined deliverables). The invoice is short — usually one or two lines — and the timesheet and service log carry the volume evidence that justifies the fee. The contractor still produces both backing documents even when the invoice doesn't itemise against them.

A per-session contract prices each session at a contract rate. Invoice line count grows with session count, and the rate may differ for evaluation sessions, treatment sessions, and IEP-team meetings. Each line carries the date, student, session type, credential, and rate.

A per-IEP-minute contract pays a rate per minute of direct service delivered against IEP goals. The invoice totals minutes from the service log: one line per student showing total direct minutes for the month at the contract rate, with indirect time billed (if at all) under separate lines at its own rate.

A retainer-plus-overage contract sets a monthly retainer covering the first N hours of work and an overage rate for hours beyond N. Make the math explicit so the AP clerk can verify it without picking up the contract:

• Total hours delivered: 52
• Retainer hours included: 40
• Overage hours: 12
• Overage rate: $95/hr
• Overage total: $1,140
• Retainer fee: $4,000
• Invoice total: $5,140

When AP queries the calculation, the contractor needs to point at the line that shows where each number came from. Burying the math forces a phone call and a rebill.

The four common rebill triggers. Districts send OT invoices back for rebilling most often because the contract or PO reference is missing or wrong, because the licence number isn't on the header, because the billing period on the invoice doesn't match the dates on the timesheet, or because credentials are absent from line items. None of these are content questions — they're clerical misses that a final check before submission catches every time.

Invoice numbering. Sequential, unique, and traceable across the contract year. The district needs to match each invoice against its PO and against received payments; the contractor needs the same trail to reconcile accounts receivable. Numbering schemes that combine contract code, year, and sequence (for example, DISTRICT-25-007) survive multi-district and multi-year auditing better than plain incrementing numbers shared across all contracts.

Supervisor-Signed Timesheets and the OTR/L–COTA Credential Split

If the invoice fails the credential test on its line items, the timesheet is where the contractor proves the credentials are correct. The timesheet is also the document a state Medicaid auditor or district counsel reads first if a service ever gets challenged, so it has to hold up on its own — independent of the contractor's memory of what happened in the room.

Daily entry fields. Each entry carries the date, the student identifier, start time and end time, total minutes, service type code or description, the IEP goal area touched, and the credential of the delivering practitioner. Student identifier choice matters: many districts require de-identification on contractor-produced documents (initials or a district-assigned student ID) so the timesheet doesn't expose PHI when it moves between the contractor's records and the district's billing office. The contract or the district's billing instructions should specify the identifier convention; defaulting to full student names because they're easier risks a HIPAA or district-PHI rebill.

Credential as a per-entry field. The credential field is per-entry, not per-day or per-week, because a single session can split between OTR/L and COTA delivery and the split has to be visible. A 45-minute session in which the COTA delivered 30 minutes of treatment under OTR/L supervision and the OTR/L delivered 15 minutes of evaluation appears as two timesheet entries — one COTA entry of 30 minutes against the treatment IEP goal, one OTR/L entry of 15 minutes against the evaluation activity — with both credentials shown. Collapsing the split into a single 45-minute entry under one credential misrepresents the work and creates a scope-of-practice issue if the entry shows the COTA evaluating or the OTR/L exclusively running a session that was actually delivered by the assistant.

The supervisor signature. When the contractor is a solo OTR/L delivering all the services personally, the contractor signs the timesheet as both deliverer and supervisor — the signature confirms the entries are accurate and contemporaneous. When the NPA has multiple therapists, the OTR/L who supervised any COTA-delivered services countersigns those entries, and the supervising OTR/L of record is the one whose name and licence appear on the signature line. The signature itself doesn't replace state supervision compliance; it documents it. Each state's OT practice act sets the supervision frequency and documentation requirement — direct on-site, indirect, periodic, with specific encounter-frequency rules — and the contractor should be following their state's rule and using the timesheet to evidence it, not relying on the timesheet to define what supervision is.

Scope-of-practice on the document. COTAs deliver treatment under supervision. They do not independently evaluate, screen, write the plan of care, or sign IEP service entries that establish the plan. The timesheet should reflect this division so the district can verify scope compliance from the document alone: evaluation entries appear under OTR/L credentials, screening entries appear under OTR/L credentials, treatment entries can appear under either with the supervising OTR/L identified for COTA-delivered work, and any plan-of-care or IEP-goal-setting time appears under OTR/L credentials.

Defensibility under audit. A timesheet holds up when its entries are contemporaneous (created during or immediately after the work, not reconstructed at month-end), the time stamps are specific (start and end, not "morning" or "PM"), the granularity is at the student and session level rather than aggregated by day, and the supervisor signature ties every COTA-delivered entry back to the OTR/L of record. AP staff look at these features even without an audit prompt because how AP departments verify timesheet-backed contractor invoices tracks the same signals district by district: contemporaneousness, granularity, signature integrity, and consistency with the service log and invoice.

Template choice. Paper timesheets, district-provided timesheet templates, OT-specific service-log apps (My School Therapy and similar), and contractor-built spreadsheets are all in active use across districts. The contract or the district's billing instructions usually dictates which is acceptable, and some districts will accept any format provided the required fields are present. The format isn't the question that matters — the entry fields, the credential discipline, and the signature are.

The Service Log: OT Vocabulary Anchored to IEP Goal Areas

The service log is the document that has to satisfy two readers with different concerns: the district AP clerk checking that the invoice and timesheet reconcile against the work performed, and the district's downstream Medicaid biller assembling claim lines against specific IEP goals. A log that satisfies both is built around one rule: each entry connects a discrete block of time to a specific IEP goal area, expressed in OT-native service vocabulary that both readers recognise. A generic entry like "OT services delivered, 30 min" can be factually accurate and still fail this test, because neither reader can attach it to a goal or a claim line.

Entry fields. Date, student identifier, start and end times (or duration), IEP goal area, the specific IEP goal being addressed (numbered or short-quoted from the IEP document), an intervention summary in OT clinical language, and the credential of the delivering practitioner. The IEP goal field is what makes the log defensible upstream — without it, the log is a time ledger; with it, the log is documentation of IEP-driven service.

OT-native goal area categories. Most school-based OT work falls into a handful of categories, and the log should name them explicitly rather than collapsing them into "treatment" or "intervention." Using the IEP's own vocabulary also lets each entry's intervention summary map directly to the goal it serves.

• Sensory integration and sensory processing. Intervention targeting sensory modulation, sensory discrimination, or motor-based sensory integration. The intervention summary names the modality (vestibular input, proprioceptive input, tactile discrimination, sensory-motor coupling) and the IEP goal being addressed (typically a self-regulation, attention-to-task, or sensory-modulation goal).
• Fine motor and handwriting intervention. In-hand manipulation, bilateral coordination, visual-motor integration, handwriting fluency, keyboarding readiness. Tie each minute to the IEP goal it targets — legibility, speed, written-output endurance, copying accuracy, keyboarding rate — rather than describing the activity in isolation.
• ADL and IADL training. Dressing, toileting, feeding, and school-routine ADLs are the common school-contract categories. Community-based IADL training (transportation, money management, meal preparation) appears where the IEP scope extends to it, typically in transition-age services.
• Assistive technology evaluation and consultation. AT assessment, AT trial, AT implementation, and low-tech or high-tech AT consultation with the educational team. Each carries its own IEP-goal connection — independent access to curriculum, written-output support, communication access — and the log should name which.
• Executive-function and cognitive intervention. Organisation, task initiation, working memory, self-regulation, and metacognitive strategy work appear in the log when the IEP addresses them as OT-targeted goals. This category overlaps with school-counsellor and SLP work in some districts; the log should keep the OT-specific framing (sensory-based regulation strategies, motor-based task initiation work) rather than generic strategy-coaching language.

The data layer that feeds the Medicaid claim. The same entry that satisfies district AP is the entry the LEA Medicaid biller attaches to a claim line for the student. The biller pulls the date, the student, the minutes, the credential, the service category, and the IEP goal it served — and pulls them in a form that matches the state Medicaid program's documentation rule. A log that names the IEP goal in the entry text removes a reconstruction step from the biller's workflow and reduces the chance the district reaches back to the contractor asking for retroactive detail.

Service log versus clinical progress note. The service log is the time-and-goal-area ledger; the clinical progress note (full SOAP or narrative) is the intervention rationale and the documented outcome. They live in different documents and serve different readers. Some districts ask for both at month-end as part of the packet; many only need the log to process the invoice. The contract or the district's billing instructions specifies which.

Audit defensibility. A service log that names IEP goals it serves holds up against the three audit pressures the contractor is most likely to encounter: a scope-of-practice challenge (the entries show OT-appropriate intervention tied to OT-addressed IEP goals), a free-care-rule question (the entries document services delivered under an IEP, which is the exemption category), and a Medicaid recovery audit (the entries match the claim lines the district submitted). A log that lists only minutes and a generic service category fails all three even when the underlying work was correct.

Direct Time, Indirect Time, and What to Do With Cancellations

The contract decides what's billable. The contractor's job is to categorise time accurately so the contract's rules can be applied. Categorisation drift — billing indirect time as direct, or treating a no-show as a delivered session — is the slow leak that builds into a Medicaid recovery audit two years later, so getting the categories right at entry time matters more than choosing the right line on the invoice at month-end.

Direct time. Minutes spent face-to-face with a student delivering services on the IEP — evaluation sessions, treatment sessions, AT trial sessions with the student present, in-class push-in service, and any other in-person or contract-permitted telehealth service against an IEP goal. Direct time is what most contracts bill at full rate and what state Medicaid programs reimburse upstream. Push-in service in the classroom counts when the OT is working with the IEPed student on the goal, even when other students are in the room; consult-and-observe time with the classroom teacher about that same student usually does not, because the student isn't actively receiving service from the OT in that moment.

Indirect time. The OT-specific indirect categories that show up on most school-contract caseloads:

• Evaluation report writing and assessment scoring outside the session itself
• IEP-team meetings — eligibility, annual review, addendum, transition planning
• Parent and family consultation, in person, by phone, or by written communication
• Equipment recommendations and procurement coordination (writing the specification, evaluating sample equipment, coordinating with AT vendors)
• Environmental modifications — classroom set-up, sensory environment write-ups, recommendations to the classroom teacher
• AT consultation with the educational team that isn't tied to a specific AT trial with the student present
• Supervision of COTAs, including documented supervision encounters and chart review
• Documentation time itself — service log entries, progress reports, the monthly billing packet

Each of these lands differently on the timesheet depending on the contract. Some contracts bill all indirect time at the full direct-time rate. Some cap indirect time at a percentage of direct time. Some bill indirect time at a reduced rate. Some bundle indirect time into a flat-rate retainer without separately billing it. Some treat specific categories (IEP meetings, parent consultation) as billable while excluding others (documentation, supervision).

Read the contract on this. The contract document is the source of truth. This article cannot tell the contractor what their contract says about indirect time, only that they have to settle the question before the first invoice and apply the same categorisation rule consistently across the month. Inconsistent categorisation — IEP meetings billed sometimes and not others, supervision time included one month and excluded the next — is what triggers AP scrutiny.

Cancellations and no-shows. Four common scenarios, each with its own documentation discipline:

• Therapist-initiated cancellation. The contractor cancelled — illness, conflicting obligation, personal reason. Generally unbillable unless the contract explicitly carves out a therapist-initiated cancellation right.
• District-initiated cancellation. School closure, IEP-team unavailable, fire drill, district-scheduled assembly displaced the session. Often billable at full or reduced rate, contract-dependent. The log entry should name the cancellation source explicitly — "school closed for snow day," "IEP meeting cancelled by district," "student pulled for state testing" — so the entry stands up if AP asks why a session is billed without a service log entry against an IEP goal.
• Student no-show. Student absent without notice, or refused the session and could not be redirected. Most contracts treat as unbillable unless the contractor was on-site and available for the scheduled time block; some treat as billable at a reduced rate when the contractor was on-site. Document the on-site availability — "scheduled 10:00–10:30, on-site, student absent" — when the contract allows the reduced-rate billing.
• Make-up sessions. Sessions rescheduled to recover missed IEP minutes from earlier cancellations. Billable as the direct session they replace, not double-counted against the original cancelled session and not billed at a premium. The log should note the make-up nature explicitly so the entry doesn't read as the student receiving extra services beyond the IEP scope.

Borderline cases. Real OT contractors hit these regularly. A 45-minute scheduled session that ran 30 minutes because the student became dysregulated and could not continue: bill the 30 minutes that were delivered, document the early termination and the reason. A session conducted with the student plus a parent in attendance for caregiver training within the IEP scope: still direct time, with the parent presence noted on the log. A session conducted via telehealth where the contract permits it: direct time, with the modality named on the log entry so the documentation is unambiguous about delivery mode.

The variance documentation rule. Across every borderline category, the rule is the same: cancellation source, deviation from planned session length, telehealth modality, premature termination reason, and any other variance from the standard session shape appears on the service log with one sentence of context. Districts pay variant entries that explain themselves. They send back silent variances because the AP clerk can't tell the difference between a legitimate exception and a documentation gap, and the safer choice from the district side is the rebill.

The 8-Minute Rule When Your Contract Bills in 15-Minute Units

Most clinical OTs already know the 8-minute rule from Medicare Part B billing. The rule shows up on school-contract work in two places: directly, when the contract bills in 15-minute time units, and indirectly, when the district's downstream Medicaid claim bills in units even though the invoice itself bills flat-rate or per-session. Both cases push the unit math back onto the service log, so the contractor benefits from doing the conversion at entry time rather than leaving the LEA Medicaid biller to reconstruct it.

The rule. When service is billed in 15-minute time units, a single CPT-coded service must total at least 8 minutes to bill 1 unit. Beyond the first unit, the 15-minute increments compound:

• 8 to 22 minutes = 1 unit
• 23 to 37 minutes = 2 units
• 38 to 52 minutes = 3 units
• 53 to 67 minutes = 4 units
• 68 to 82 minutes = 5 units

The rule is CMS-derived — Medicare Part B billing for OT and PT timed-codes — and propagates into Medicaid school-services rules in most states. A 24-minute session of therapeutic activities bills 2 units; a 36-minute session bills 2 units; a 38-minute session bills 3 units. The breakpoints are not intuitive on first reading, which is why contractors who bill flat-rate sometimes get tripped up when a district contract later moves to time-units.

Why it matters even on flat-rate and per-session contracts. The district's downstream Medicaid claim may bill in 15-minute units against state program rules (CA Medi-Cal LEA, NJ SEMI, TX SHARS, and similar) even when the contract pays the OT in a different unit. The LEA Medicaid biller pulls unit counts from the contractor's service log. If the log only records minute totals, the biller has to convert each entry — across a caseload of 30 or 40 students, across a month of sessions — and any reconstruction error becomes a Medicaid claim rejection the district then traces back to the contractor's documentation. A log that records minutes and shows the corresponding unit count inline removes the reconstruction step entirely.

Multi-service sessions. When a single 60-minute session covers two CPT-coded services (for example, 30 minutes of therapeutic exercise and 30 minutes of self-care training), each timed code's minutes apply independently against the 8-minute rule. A session with 22 minutes of therapeutic exercise and 22 minutes of self-care training bills as 1 unit each — 2 units total — not 3 units bundled. The log entry should show the minute split per service, with each service's CPT code and minute total on its own line, so the unit math is reproducible by anyone reading the log without consulting the contractor.

OT-specific timed codes. The CPT codes most often seen on time-unit school contracts are 97530 (therapeutic activities), 97110 (therapeutic exercise), 97112 (neuromuscular re-education), and 97535 (self-care and home management training). These are timed codes — billed in 15-minute units, subject to the 8-minute rule. Evaluation codes 97165, 97166, 97167, and 97168 are tiered untimed codes — billed per evaluation regardless of minutes, with the tier determined by clinical complexity. The contract typically pays evaluations as their own line item separate from any unit-based treatment billing, and the log entry for an evaluation records the minutes for documentation but not for unit-counting.

A note for OTs with mixed school and SLP contracts. Speech-language services at the CPT level are session-based and don't carry an 8-minute rule equivalent — codes like 92507 (treatment of speech, language, voice) bill once per session regardless of length. SLP contractors working alongside OTs sometimes assume the unit rules align; they don't. An OT who also coordinates the billing for an NPA's SLP services should keep the rule sets separate at the entry level so the unit math on the OT log doesn't bleed into session-based assumptions on the SLP log.

GO and CO Modifiers: The Boundary Between School Contract and CMS-1500

Many solo OTs run a school contract alongside a private-practice caseload. The two billing universes look superficially similar — same therapist, same credentials, same clinical skills — but the documentation and billing forms are entirely different, and mixing them is the most common source of payer disputes for OTs who work both sides.

The structural boundary. School districts do not process CMS-1500 claims. The district invoice is a contract invoice paid against a purchase order. The CMS-1500 is the standard payer claim form filed with Medicare, Medicaid (under non-school models), or a commercial insurer for a private-practice encounter. They live in separate billing universes, paid by different parties, governed by different documentation rules, and they should not share session records, claim numbers, or service logs.

GO and CO defined. For OTs running private-practice work alongside the school contract, two CPT modifiers come up often enough to know cold:

• GO modifier. Indicates services delivered under an occupational therapy plan of care. Required on Medicare Part B claims (and many Medicaid and commercial claims) so the payer can attribute the service to the OT discipline rather than to physical therapy or speech-language pathology, which carry their own discipline-specific modifiers (GP and GN).
• CO modifier. Indicates services delivered in whole or in part by an occupational therapy assistant (COTA) under OTR/L supervision. CMS pays services with the CO modifier at a reduced rate compared to services delivered entirely by the OTR/L; commercial payers vary on whether they apply the differential.

Both modifiers belong on CMS-1500 claims for private-practice work. Neither belongs on a school-district contract invoice — the district pays a contract rate, not a CPT-derived payer rate, and the modifier framework doesn't apply to the contract layer.

The dual-role risk. The same minutes cannot be billed to two payers. A school-contract minute against an IEP goal is paid by the district under the contract; the same minute cannot also be billed to Medicare under a private-practice plan of care or to a commercial payer. The constraint is straightforward in principle and easy to violate in practice, particularly when the same OT works with the same student in both capacities — for example, a student who receives in-school OT under the IEP and also attends private clinic sessions outside the school day.

The AOTA Code of Ethics treats accurate documentation of services and clear separation of payer responsibilities as core ethical obligations of the OT practitioner, not just payment-policy questions. Billing the same time to two payers — whether through carelessness, documentation overlap, or session misclassification — sits in the same ethical category as misrepresenting credentials or fabricating service notes, regardless of intent.

Operational practices that prevent crossover. OTs who work both sides cleanly keep them physically and procedurally separate:

• Separate session calendars, so a school-day session and a private-clinic session never appear on the same calendar entry.
• Separate service logs, so a single minute of work never appears on both the school service log and the private clinic chart.
• Separate documentation systems, or clearly partitioned modules within a single practice-management system, with role-based access that prevents cross-population.
• Separate billing software, or partitioned modules — school-contract invoicing on one path, CMS-1500 claim submission on another.
• A documented decision rule for where each student-encounter category belongs. When the OT works with the same student in both school-contract and private-practice capacities, the IEP-aligned services belong on the school contract; medically-driven services outside the IEP scope belong on the private claim. The IEP itself and the contract document are the source of truth on which side of the line a given session falls.

References to AOTA documentation standards and the AOTA Code of Ethics are the OT-specific authority anchors the contractor should keep on their shelf alongside the contract itself. They're the documents an auditor, a payer reviewer, or a state board investigator will reach for first.

How Your Documentation Feeds the District's Medicaid Claim

The OT contractor doesn't bill Medicaid directly under most school-contract models, but the contractor's documentation quality determines whether the district can recover federal Medicaid match on the services delivered. Understanding the upstream relationship explains why districts sometimes ask for service-log detail the invoice itself doesn't strictly need — and why treating those requests as legitimate accelerates payment rather than delaying it.

The upstream model in one paragraph. The contractor invoices the district. The district pays the contractor under the contract. Separately, the district claims federal Medicaid match against the same services through its state's Medicaid-in-schools program. The contractor is not the Medicaid biller, does not file the claim, does not see the federal recovery, and is paid by the district regardless of whether the district's downstream claim is successful. But the district's ability to file a successful claim depends entirely on the contractor's service-log quality. A district that can't recover Medicaid match on a contractor's caseload is a district that renews the contract reluctantly.

State programs. Each state's Medicaid-in-schools program has its own documentation rules. CA Medi-Cal LEA, NJ SEMI, TX SHARS, and MN MA-FFS are among the larger and better-documented programs, but every state with school-based Medicaid recovery operates under one. The contractor who works across multiple districts — particularly across state lines — benefits from building the service log to meet the strictest documentation requirement among the contracts held, so the same log feeds every district's Medicaid biller without rework. Trying to maintain district-specific log formats per contract is a multiplication of effort the contractor's billing system rarely handles cleanly.

IDEA Part B as the policy floor. Occupational therapy is a related service under 34 CFR §300.34 of the IDEA regulations. Services are IEP-driven — they exist because the IEP team determined the student needs them to access the educational program. The free-care rule, which would normally prevent public agencies from billing Medicaid for services provided free to others, carries an explicit exemption for services on a child's IEP, which is what makes Medicaid-in-schools billing possible at all.

A specific parental-consent rule controls when the district can first access the child's Medicaid (or other public benefits or insurance) for IEP-required services. Public agencies must obtain written parental consent before accessing a child's or parent's public benefits or insurance for the first time to pay for services required under the child's IEP. This is set out in IDEA's parental-consent rule at 34 CFR §300.154, and the consent requirement is the reason districts sometimes ask the contractor whether a given student has the consent form on file before adding the student to the billing log.

The practical consequence for the contractor. When the district asks for service-log detail the invoice itself doesn't strictly need — IEP goal numbers, intervention summary text, minute-level breakdowns, confirmation of which students have signed parental consent, attestation that services were delivered under the IEP — the request usually traces back to the upstream Medicaid claim, not to district AP. Treating those requests as legitimate documentation needs rather than as bureaucratic friction speeds invoice processing and reduces the back-and-forth that delays payment. AP can hold an invoice while waiting for the Medicaid biller to confirm that the documentation will support the downstream claim; an invoice held that way looks identical from the contractor's side to an invoice in dispute.

The "Medicaid-billable students" roster. Some districts expect a year-start roster from the contractor identifying which IEPed students on the caseload have parental consent in place for Medicaid billing, with the roster updated when consent status changes mid-year. This is district-specific, not federally required, and the request usually comes from the LEA Medicaid biller's office rather than from AP. Asking about it at contract signing — and putting the roster maintenance discipline in place before the first month's invoice — prevents a mid-year scramble where the district can't claim federal match on caseload that turns out to lack documented consent.

Consolidating Session Logs, Timesheets, and Invoices Into One District-Submittable Packet

At month-end the contractor has a stack of source artefacts — daily session notes, the running timesheet, calendar entries for IEP meetings and consultations, signed timesheet pages, a draft invoice, and the contract document open for reference. The packet that goes to the district has to land all of that as three coherent documents that reconcile against each other. The discipline of how those documents are produced and checked is what separates a packet AP pays in one pass from one that comes back with questions.

The packet-assembly sequence. Build the service log first. It's the most data-intensive document, it carries the entry-level detail every other document derives from, and producing it first means the totals downstream cascade rather than getting reconstructed. Build the timesheet next, drawing daily entries from the service log with the credential split intact and the supervisor signature line added. Build the invoice last, with line item totals pulled from the timesheet and the contract math applied. This order means each document inherits from the prior one, and the numbers reconcile by construction rather than by month-end audit.

Three-way reconciliation. Before the packet leaves the contractor's desk, three checks need to pass:

• Service-log minutes total to timesheet minutes for each student.
• Timesheet minutes feed invoice line items at the credentials and rates the contract specifies.
• Invoice line items reconcile to the contract's billing model — flat-rate fee, per-session count at contract rate, per-IEP-minute total, or retainer plus calculated overage.

Mismatches at any junction signal an error AP will catch on receipt. Catching them first is faster than receiving the rebill notice and rebuilding the document set against the district's count. The reconciliation also catches the rebill triggers covered earlier — missing credentials, mismatched billing periods, missing contract reference — before the packet leaves.

Submission format. Districts typically require either a single PDF with the invoice on the first page, the timesheet on the next pages, and the service log on the remaining pages, or three separate files emailed together with consistent naming (contractor name, district, billing period). The contract or the district's billing instructions specifies which. PDF combination preserves order and prevents the AP clerk from receiving the timesheet without the matching invoice. Naming convention matters more than file count — a packet with three files labelled "Invoice June 2026," "Timesheet June 2026," and "Service Log June 2026" pairs cleanly with the district's filing system; a packet of three files labelled "invoice_final_v3.pdf," "timesheet.pdf," and "log.pdf" doesn't, and the district's AP system usually reflects that in how quickly it processes them. Once a packet reaches AP, how school district AP teams match invoices against POs and receiving describes the matching workflow that runs against the packet on receipt — same three-way logic the contractor just applied to themselves, from the district's side.

The tooling layer at consolidation. Solo contractors with one district often handle consolidation manually without much friction. The friction compounds when the contractor handles multiple districts simultaneously, or when an NPA runs several OTRs and COTAs across overlapping contracts with different billing models and different documentation rules per district. PDF invoices from accounting software, scanned signed timesheets, exported service-log spreadsheets, and app-generated session logs all carry the underlying data in different shapes — and the consolidation work is the work of pulling that data into a single reconciliation surface where the three-way checks can actually run.

This is where structured extraction for therapy timesheets, session logs, and PDF invoices earns its place in the workflow. Uploading the month's PDF invoice, the scanned timesheet, and any session-log exports and using a natural-language prompt to extract the relevant fields — invoice line items with credentials and rates, timesheet minutes by student and credential, service-log entries by IEP goal area — produces a structured spreadsheet that the contractor can run the three-way reconciliation against in a single pass. Each row in the output references the source file and page, so any entry the contractor wants to verify is one click away from the original document. The tool doesn't produce the packet, sign the timesheet, or submit the invoice — those steps remain the contractor's work — but it removes the manual transcription that makes reconciliation slow when document volume grows. NPAs running multi-therapist consolidation against multiple districts hit this exact pattern; extracting an NPA monthly invoice to a student-level service-minute spreadsheet walks the NPA-specific case where the consolidation produces a student-by-student service-minute roll-up against the contract.

Why this compounds with the district. The same documentation layer feeds the district's downstream Medicaid claim. A packet whose three documents reconcile cleanly against each other and whose entries the district's Medicaid biller can attach to specific IEP goals is a packet the district can build a successful claim against. Districts that recover federal match on a contractor's caseload renew the contract; districts that can't, hesitate. The reconciliation work the contractor does at month-end isn't only about getting paid this month — it's about how the contract performs over time.