Resources / Business Office / Expense documentation

Getting receipts back after the money is spent

The short answer

Once the money is spent, the natural moment for the paperwork has passed. The conference is over, the purchase is made, and the receipt the staff member fully intended to submit is sitting in a downloads folder or a coat pocket, one small task among many with nothing attached to bring it back up. Getting it back depends entirely on follow-up, and in most districts the follow-up is a person: someone in the business office keeping a mental list of who still owes documentation and sending reminder emails weeks after the fact. Doing this well means the follow-up is built into the process itself, so the request that approved the spending stays open until the documentation comes back, and the reminders happen without anyone keeping the list.

On this page

Why this is its own problem How districts handle it now Where it goes wrong

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

Why this is its own problem

Approving spending and documenting spending are two halves of the same process, but almost every tool a district uses treats them as separate events, and the two halves have completely different timing built in. The approval happens at a moment when the task and the person's attention are naturally together: the staff member needs something, and the request is how they get it. The documentation comes due weeks later, when the trip is over and the person is back inside a full workload, and nothing in the process reconnects the task to their attention. A purchase order system closes its loop when the order is placed. An email approval thread ends when the supervisor replies. Nothing in the chain is still watching three weeks later when the receipt, the conference claim form, or the purchasing card documentation is due. The gap is not that districts lack a policy requiring receipts. Nearly all of them have one. The gap is that the policy depends on remembering, at exactly the point in the process where remembering is all that's left.

How districts handle it now

The receipt comes back when someone chases it. A staff member attends a conference, spends the money, and moves on to the next thing. The claim form they were supposed to complete sits unfinished. Weeks later, someone in the business office notices the open item, and the chase begins: an email, a reminder at a staff meeting, a note in a mailbox. Some districts keep a spreadsheet of outstanding documentation. Some rely on the month-end reconciliation to surface what is missing. Either way, the enforcement mechanism is a person's memory and persistence, and when the chase fails, the district writes it off or processes the claim without the documentation it was supposed to have.

Where it goes wrong

The process fails quietly, and not because anyone is avoiding it. The staff member who spent the money is busy, the receipt is one small task among forty, and the process gives them nothing at the moment they'd actually complete it. All they have is a policy they're supposed to remember and a form they have to go find. Remembering becomes the system, and remembering is exactly what a full workload crowds out. So the business office ends up carrying the follow-up by hand, which means the person doing the chasing absorbs both the work and the discomfort of repeatedly asking colleagues for something overdue. And the record ends up incomplete in exactly the places an audit looks: money spent, approval documented, and nothing showing the documentation ever came back or that anyone followed up when it did not.

What doing it well actually requires

Getting documentation back reliably after the money is spent comes down to building the follow-up into the process itself, and it has a few specific parts.

The request that approved the money stays open until the documentation returns

The approval and the documentation belong to one record, not two events. When a staff member's conference request is approved, that same workflow is still open after the conference, waiting on the receipt and anything else the district requires. The process does not close until the documentation is complete. There is no separate follow-up form to remember, because the follow-up is the tail end of the request itself.

The reminder arrives carrying the task, not just the request

The system tracks what is outstanding and follows up automatically, and the reminder is a door, not a memo. One click puts the staff member directly on their open item, presented so that completing it takes a minute right then, not a form to locate later and a task to defer. Staff at Teton County School District #1 in Wyoming ran the old version of this process: a PDF emailed around, approvals by reply, documentation that was supposed to follow and often didn't, because nothing brought the task back to the person at a moment they could act on it. Moving the process into a workflow that does its own following up changed that: the reminder shows up with the work attached, and the business office stopped keeping the list.

It covers whatever the district requires back, not just the receipt

The documentation owed after spending varies by process. A conference generates a receipt and often an evaluation. A purchasing card generates itemized documentation on a cycle. Philipsburg School District No. 1 in Montana runs its conference claim forms through this model alongside purchase orders, and Harlowton Public Schools runs purchasing card expenditures the same way. The workflow holds whatever the district's own process requires before it closes, not a generic single receipt field.

The record is complete without anyone assembling it

Every request, approval, and returned document is logged in one place as the process runs. When a question comes up, from a supervisor, an auditor, or a board member, the answer is a search, not a folder hunt. Philipsburg's business office exports its purchase order data to a spreadsheet each month with the information needed for processing claims, pulled from the system rather than reassembled from email threads and paper files.

Common questions

Questions we hear from every business office.

How do school districts get staff to actually turn in receipts after a conference?

Mostly by chasing, which is why it works inconsistently. The chase also misreads the problem. Staff aren't withholding receipts; they're busy, and the receipt is a small task with no natural moment attached to it. The durable fix makes the moment: the request that approved the conference stays open, the system sends the reminder itself, and the reminder links straight to the open item so finishing it takes a minute right then. Return rates change when submitting the receipt becomes the easiest available version of the task.

What should happen when a staff member never returns documentation for a purchasing card charge?

The district's own policy decides the consequence. What the process should guarantee is that the missing documentation is visible: the open item shows exactly who owes what and for how long, so the business office is applying the policy to a known list rather than discovering gaps at reconciliation. In a workflow-based process, that list is the set of requests still open past the documentation step.

Do receipt reminders have to be sent by hand, or can they be automated?

They can be automated, and in a process built this way they are the default rather than a feature someone configures. The system tracks what is outstanding against each open request and follows up on its own schedule. The business office sees the status; it does not send the emails.

Can the receipt and the evaluation come back through the same process after professional development?

Yes, and they should, because splitting them recreates the chase twice. A professional development request built as one workflow collects the approval before the event and the receipt and evaluation after it, inside the same record. Nothing closes until both are in.

Does this replace how our business office processes claims in the accounting system?

No. The accounting system stays exactly where it is. This is the layer in front of it: the approval, the documentation return, and the complete record, delivered to the business office ready to process instead of arriving as loose paper and email attachments. Philipsburg exports its monthly purchase data straight into the format its claims processing needs.

How Flow Forms handles it

Flow Forms builds the district's actual post-spending process into the workflow itself: the request stays open until every required document is back, reminders go out automatically with the task attached, and the complete record of who spent, who approved, and what came back lives in one searchable place. The districts running conference claims, purchasing card documentation, and professional development receipts this way stopped chasing because the process took the chase over.

See how it would work for your district →