Who did what
Every step records the person and the time. With segregation of duties on, the person who prepared a reimbursement cannot also approve it.
Prove It Financials › Grant reimbursement software
A reimbursement is not finished when it is submitted. The funder may approve less than you claimed, pay it in parts, or send it back. Prove It Financials carries each reimbursement from draft to paid and keeps every one of those amounts as its own fact.
Each program-month is one reimbursement. Its status moves only when someone with the right role moves it.
Every step records the person and the time. With segregation of duties on, the person who prepared a reimbursement cannot also approve it.
A critical review issue blocks Fiscal Approved, and an unexplained reconciliation difference blocks Ready to Voucher — unless an authorized person overrides it with a written reason, which stays on the record.
Each generated voucher is saved as a version, so what was submitted can be shown later even if the records change.
Most spreadsheets track a reimbursement with one amount and a “paid” checkbox. That hides the cases finance teams actually spend time on: the funder approved $5,000 less than was claimed, the payment arrived in two parts, or a payment was recorded against the wrong month. Prove It records each of these separately:
| Illustrative example | Amount |
|---|---|
| Submitted | $100,000 |
| Approved by the funder | $95,000 |
| Paid — first payment | $50,000 |
| Paid — second payment | $25,000 |
| Outstanding ($95,000 − $75,000) | $20,000 |
Illustrative figures, not a customer’s.
A returned reimbursement is recorded with the funder’s reason and reworked as a draft; the resubmission is recorded as its own submission.
A reimbursement is marked Paid when the payments cover it. If the funder pays less and nothing more is expected, it is closed short with a written reason.
A voucher marked Paid before payments were tracked, with no payment amount, is shown as a gap — never counted as paid.
For each reimbursement: who prepared, reviewed and approved it, the version that was filed, every payment with its reference, and every override with its reason. Changes and exports are written to a permanent audit history, and roles decide who can record what. Federal awards follow the same record through the SF-425 workflow.
Related: the monthly checklist · how vouchers are prepared · payroll allocation · spenddown forecasting · funders such as NYC DYCD, HHS Head Start and DOJ OJP.
Bring one contract and one submitted reimbursement. Record what was approved and paid, and see exactly what is still outstanding.
No. Your team submits through the funder’s own system. Prove It prepares the reimbursement and records the submission, approval and payments you enter.
Yes. Each payment is recorded with its date and reference; outstanding is the approved (or submitted) amount less the payments recorded, and a mistaken payment is voided with a reason rather than deleted.
Record the approved amount. Outstanding is then measured against it, and both figures stay visible. Your recorded spending does not change.
No. Spending is what was recorded as expense; cash received is tracked separately in Receivables.