Reimbursements
Pay people back without losing the receipt.
Staff submit a receipt, code it to the fund it supports, and finance pays the approved request from the same books.
Available on Plus, Pro, and Enterprise · Receipts stay attached to the paid record
Receipt stays attachedApproved before paymentCoded to the right fund
How it connects
A reimbursement that stays with the fund it supports.
The receipt, the approval, and the payment should not live in three different inboxes.
- 01
Capture the receipt
Submit a photo or PDF, then review the amount, vendor, and date before it goes forward.
- 02
Approve before payment
Reviewers can ask for a change or approve the request. Nothing is paid until it is approved.
- 03
Keep the fund clear
Each request is coded to a fund, so restricted spending stays with its purpose.
What updates next
The paid receipt stays attached to the books.
Once finance pays an approved batch, the original receipt remains available from the accounting record.
- Funds
Spending stays tied to purpose. - Expenses
Approved requests are paid from the books. - Reports
The source receipt is still there. - Vendors
Spend stays easier to explain.
One current recordFundraising, people, events, files, and reports stay ready for the next team.
FundsSpending stays tied to purpose.
ExpensesApproved requests are paid from the books.
ReportsThe source receipt is still there.
VendorsSpend stays easier to explain.
Before AlignMintReimbursements handled in email and spreadsheets.
Receipt emailsOne less place to check.
Shared foldersOne less place to check.
Approval threadsOne less place to check.
Reimbursement spreadsheetsOne less place to check.
AlignMintOne system your team can actually run from.
Related workflows
See how it works with the rest of AlignMint.
Follow the record from the first action through reporting without copying it into another tool.