Here's how a reimbursement usually starts: a text at 9 PM with a photo of a receipt, taken at an angle, in a dark kitchen. No note about what it was for. You save it to deal with later, and "later" becomes a pile.
None of that is the volunteer's fault. They spent their own money on your group's bake sale, and the only instructions they ever got were "just send me the receipt." The fix isn't chasing people harder. It's changing what arrives in the first place.
Give requests one front door
Pick a single way requests come in and hold the line. A form is best, a printed sheet in the supply closet works too, but it has to be one place. The moment receipts arrive by text, email, and a crumpled envelope, you've become the system, and the system goes home tired.
When someone sends a receipt some other way, reply kindly and point them at the front door. It takes two weeks of gentle redirecting, and then it just works.
Ask for five things, every time
A request you can process without asking a single follow-up question needs exactly five things:
- The date on the receipt. Not the day they sent it. This is the date that matters for your deadline and your records.
- What they bought, item by item. "Cups, plates, napkins" beats "Target." A receipt showing only a total is the number one reason a request bounces back with questions, because a card slip proves someone paid, not what they paid for.
- What it was for. The event or the budget it belongs to. The best trick I know: give them a list to pick from instead of a blank box. Nothing arrives mislabeled when the labels are right there.
- How they'd like to be paid. Check, Venmo, whatever your group uses. Asking up front saves a whole round of messages later.
- The receipt itself. A photo is fine. What matters is that it's attached to the request and not floating in a text thread you'll have to excavate in June.
Write the packet once
Nobody gets paid until somebody signs off, and whoever signs off needs the same things every time: who paid, what they bought, what it was for, which budget it comes out of, the receipt, and the exact amount. I call that the packet, and assembling it by hand was the part of the job that actually ate my weekends.
So build the packet once, as a template, and fill in the blanks each time. One page. If you collected the five things above, every blank is already answered, and nothing comes back with questions. The person signing gets everything they need in one look, which is also how you earn a reputation for having your act together.
Batch your payouts
Don't pay people one at a time as requests trickle in. Pick a rhythm, maybe when the board meets or whenever you sit down to do the banking, and pay everyone who's waiting in one sitting. One summary for your approver, one stack of payments, one tidy update to your records.
Volunteers wait a few days longer at most, and you get your evenings back. If someone genuinely needs the money sooner, they'll tell you, and you can make an exception on purpose instead of treating everything as urgent.
Set a deadline and say it out loud
Every group needs a line like "receipts within 30 days, please." Real groups run anywhere from two weeks to sixty days, and the exact number matters less than having one and putting it where people see it. Without a deadline, June becomes the month of mystery receipts from October, and nobody enjoys that conversation.
June-proof as you go
Whoever reviews your books at year end will ask the same question about every payment: where's the receipt, and what was it for? If every request came through the front door with its five things, the answer is already sitting in one place. The audit stops being an archaeology dig and becomes an afternoon with coffee.
The message that starts it all
Here's a version of the note I'd post in the group chat. Steal it:
That one message, plus a front door and a packet template, is honestly most of the job. The rest is ticking boxes.