Reimbursement Payment Tracker: From Approved to Paid, Without the 'Where's My Money?' Emails

The problem this kills

The expense got approved. Everyone moved on. And now the employee is emailing you — for the third time — asking when their $340 hotel reimbursement is actually going to land in their account.

The gap between "approved" and "paid" is where reimbursements go to die. Approvals live in one system. Payouts happen in another — payroll for some people, an ACH run for others, maybe a check for a contractor. In between is a spreadsheet (or worse, someone's memory) tracking who's been paid and who's still waiting. Items slip. Some get paid twice because two people built the batch. Some sit unpaid for a month because they fell off the list. And the employee has no idea where their money is, so they ping you, and you go digging.

You don't need to be a developer to close that gap. You need a simple tracker with a real approval gate and a clear paid/outstanding view.

What you'll build

A simple internal web tool that owns the reimbursement from approval to paid. You import the approved reimbursements (employee, amount, approval date, payment method). The tool batches them by pay date and routing method — payroll items in one batch, ACH items in another — and ages anything that's been approved but sitting unpaid. AP reviews and approves the payout batch — the gate — and only then does the tool export a payout file in your bank or payroll format. You mark the batch paid, the tool emails each employee that their reimbursement is on the way, and it produces a paid/outstanding report so you can answer "where's my money?" before anyone has to ask. Duplicate guards mean the same reimbursement can never be paid twice.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — who pays reimbursements today, whether they route through payroll or your bank, the exact columns in your approved-reimbursements export, how you express payment method, your real approval rules, and your messy edge cases — so the tool matches how you actually pay people, not a generic template. From there it walks the agent through the data model, the import, the batching, the AP approval gate, the payout-file export, the paid-and-notify step, and the paid/outstanding report. Every step ends with a ready-to-copy prompt. There's also a "No API yet?" path: import a CSV and export a clean payout file plus a payment-status CSV in the exact columns your systems expect, so you can build and use the whole thing today.

The governance it includes (this is the point)

This is real money going to your own colleagues, so the plan builds in the controls a finance team needs: login so only your AP/payroll team can use it; row-level security so you only ever see your own organization's reimbursements; a complete audit trail of who imported, batched, approved, exported, and marked-paid what, and when; a hard human-approval gate where AP signs off on the payout batch before any file is generated; and duplicate guards so the same approved reimbursement can never land in two open batches — or get paid twice.

Who it's for

AP and payroll staff who actually cut reimbursement payouts and are tired of chasing a spreadsheet — and tired of being chased by employees asking where their money is. If you can describe how an approved expense becomes a payment at your company, you can build this.

You've got this — start with the plan, paste the first prompt, and answer a few questions about how you pay people. Your first clean payout batch is an afternoon away.