Right-Sized Public Tech field kit

Transportation invoice review

A compact review for comparing what was contracted, assigned, delivered, billed, adjusted, and approved.

For K-12 transportation, finance, procurement, and IT staff

Factual resources last verified August 26, 2026

Use this kit when

The workload is real, but the review path is not.

  • Bus-contractor invoices contain many routes, days, tiers, extras, credits, or exceptions.
  • Transportation and finance use different records to approve the same payment.
  • Staff can identify disputed lines, but cannot reproduce the review later.

Minimum review packet

Bring evidence, owners, and open questions.

Packet item 1

Current contract, amendments, rate tables, and approved exception rules

Packet item 2

Route or service assignments for the invoice period

Packet item 3

Invoice lines in a reviewable export, not only a summary total

Packet item 4

Available service evidence, such as approved operational logs, GPS summaries, or exception records

Packet item 5

Credits, prior-period adjustments, and documented approvals

Packet item 6

A role map showing who verifies service, resolves exceptions, and authorizes payment

Working sequence

A 45-minute review.

  1. Normalize the keys

    Align vendor, contract, route or service, date, rate, and invoice-line identifiers. Record every unmatched identifier instead of guessing.

  2. Check authority and rate

    Tie each charge to the current contract, amendment, or documented exception. Recalculate extensions, totals, and credits.

  3. Compare assigned and delivered service

    Use the least sensitive reliable evidence available. Treat missing evidence as unresolved, not as proof that service did or did not occur.

  4. Separate exceptions from approvals

    Route disputed lines to the operational owner. Keep payment authorization with the role designated by local policy.

  5. Close the loop

    Record approved, held, credited, and corrected lines with the evidence and reviewer decision attached.

Leave with

A decision record, not another discussion.

  • Lines ready for payment
  • Lines held for specific missing evidence
  • Lines requiring a documented operational exception
  • Credits or corrected invoices to request
  • A repeatable rule or data fix for the next cycle

Local verification required

  • Do not move student names, disability information, precise student locations, or other protected records into a review file unless they are necessary and approved.
  • Contract terms and payment authority vary. Local procurement, finance, counsel, and policy owners must verify the final route.
  • Do not let the same person create the charge, resolve the exception, and approve payment without an approved compensating control.

Primary sources

What this kit relies on.

Improving the Effectiveness of Your Claims Auditing Process

New York State Office of the State Comptroller. Official local-government management guide. Last verified August 26, 2026.

Reviewing claims for authority, mathematical accuracy, supporting documentation, and evidence that goods or services were received.

Data Security: K-12 and Higher Education

U.S. Department of Education Student Privacy Policy Office. Current resource hub. Last verified August 26, 2026.

Safeguarding student records, data security, data flows, retention, destruction, and online-service considerations.

Commercial disclosure

Related JSTK option: RouteLedger

Working product demo available

JS Technology Solutions publishes this field guide and offers RouteLedger. Review the neutral workflow above before considering the product.

When it may fit

  • Recurring contractor invoices can be exported at line level.
  • Assignments, rate rules, and service evidence have stable identifiers.
  • District staff will review every flagged exception and retain payment authority.

When it does not fit

  • The primary problem is live routing, dispatch, parent communications, or driver scheduling.
  • The district lacks a reliable service record and cannot define an approved evidence source.
  • The workflow would require unnecessary student-level data.
Visit RouteLedger Open the working demo

Cut the next scope.

Turn this review into a bounded working brief.

Open the Scope Cutter