Resources / Business Office / Travel reimbursement

Routing staff mileage and travel reimbursement

The short answer

Mileage and travel reimbursement is two problems wearing one form: getting the request approved through the right people, and getting the math right against a rate that changes. In most districts the traveler looks up the rate, does the multiplication themselves, and the business office checks the arithmetic on the way through, which means every claim is calculated twice and trusted once. Doing it well means the form itself carries the current rate and computes the amount from the miles entered, the claim routes through the district's own approval path, and a rate change is a single deliberate update rather than something each traveler is supposed to have heard about.

On this page

Why the rate is the real problem How districts handle it now Where it goes wrong

What doing it well actually requires Common questions How Flow Forms handles it

Why the rate is the real problem

Approval paths for travel look like approval paths for anything else. What makes mileage its own headache is that the number at the center of the claim is not fixed. The IRS adjusts the standard rate, boards set their own local rates, and the current figure lives somewhere, a handbook, a memo, last year's spreadsheet, that each traveler has to find and apply correctly. A claim filed on an outdated form pays at an outdated rate. A traveler who misremembers the rate creates an error someone downstream has to catch or absorb. The business office becomes the arithmetic checker of record, re-multiplying miles against the rate on every claim, which is exactly the kind of work that fills a week without appearing on anyone's job description.

How districts handle it now

The traveler downloads or photocopies the mileage form, fills in dates, destinations, and miles, multiplies by whatever rate they believe is current, signs it, and sends it toward a supervisor. The supervisor signs and forwards it to the business office, where someone verifies the trip is legitimate, the rate is right, and the math holds, then processes it for payment. Travel involving more than mileage, lodging, meals, registration, adds receipts to the packet, and the packet travels as paper or email attachments. When the rate changes, the change goes out in a memo or a handbook update, and old forms with old rates keep circulating for months, because the form and the rate are separate objects that nothing keeps in sync.

Where it goes wrong

The errors are small, constant, and all downstream. A claim at last year's rate, caught or not. Miles estimated generously or conservatively, with no consistent standard for what counts. The business office correcting arithmetic and then explaining the correction, which turns a routine claim into a conversation. Claims batched and filed late because the form is somewhere else and the trip is over, the same timing gap that swallows receipts. None of it is anyone acting in bad faith; it's a process that asks every traveler to be current on a number that changes and asks the business office to verify that they were, one claim at a time.

What doing it well actually requires

Handling mileage and travel reimbursement well means the form carries the rate and the claim routes like everything else the district approves, and it comes down to a few specific parts.

The form carries the rate and does the math

Flow Forms builds calculation directly into forms: the traveler enters the miles, and the form computes the amount against the rate stored in the workflow. Nobody looks anything up, nobody multiplies, and the business office stops checking arithmetic, because there is no arithmetic to check. The claim arrives calculated correctly at the current rate, every time, from every traveler.

A rate change is one update, made on purpose

The stored rate never changes silently. When the IRS adjusts the standard rate or the board sets a new one, the district updates the rate in the workflow, or tells Flow Forms to make the change, and every claim from that moment forward pays at the new figure. There is no transition period where old forms circulate at old rates, because there are no copies of the form to go stale; there is one form, and it is current.

The claim routes like everything else the district approves

Traveler to supervisor to business office, or whatever the district's own path is, with any conditions the district applies, an overnight trip picking up an extra approval, a claim above a threshold adding a second signature. Andrea Keller, clerk and business manager at Harlowton Public Schools, names travel reimbursements among the paper processes her office moved into routed workflows, alongside leave requests, purchasing card expenditures, and requisitions: one routing model carrying the business office's recurring paper.

The travel that involves more than miles stays one claim

Lodging, meals, registration, and the receipts behind them belong to the same trip, and the workflow holds them as one record rather than a packet of attachments assembled by hand. What reaches the business office is the whole trip, approved and documented, ready to process.

Common questions

Questions we hear from every business office.

How do school districts keep mileage claims at the current reimbursement rate?

Mostly by publishing the rate and hoping, which is why claims at stale rates are a routine correction. The structural fix is putting the rate inside the form itself: stored in the workflow, applied automatically to every claim, updated in one place when it changes. The traveler never handles the rate at all; they enter miles and the form does the rest.

Who is supposed to calculate the reimbursement amount, the employee or the business office?

In most current processes, both, the employee calculates and the office verifies, which doubles the work and still lets errors through. In a form with built-in calculation, neither does: the amount is computed from the entered miles at the stored rate, and both sides see the same correct figure from the start.

What should the approval path for a travel reimbursement look like?

Whatever the district's policy already says, enforced rather than remembered: supervisor approval, business office processing, and any conditions the district sets applied automatically, a second approver above a dollar amount, an extra step for overnight travel. The path is defined once and every claim follows it.

Can mileage and travel expenses like lodging and meals go through the same claim?

Yes, and keeping them together is the point: one trip, one record, with the mileage calculated by the form and the receipts attached to the same workflow. Splitting a trip across a mileage form and an expense packet is how pieces of it go missing.

Does the reimbursement still get paid through our normal accounting process?

Yes. Payment runs through the accounting system exactly as it does now. What changes is upstream: the claim arrives at the business office calculated, approved through the district's path, and complete, instead of arriving as arithmetic to verify.

How Flow Forms handles it

Flow Forms builds the district's travel reimbursement as a routed workflow with the calculation inside it: the current rate stored in the form, amounts computed from entered miles, the district's own approval path enforced on every claim, and the full trip, mileage, expenses, and receipts, held as one record. Rates change only when the district changes them or asks Flow Forms to, so every claim pays at the figure the district actually set.

See how it would work for your district →