The last step is getting the partner paid. Invoices turn approved spend into a reimbursement statement your finance team can act on - generated from the numbers already in Introw, run through approval, and closed out by marking the project paid - so nobody rebuilds the total in a spreadsheet.
The problem it solves
Reimbursement is where MDF programs get stuck:Impact
Getting paid on time, with a document their own finance team accepts, is the part partners tell other partners about. It is the cheapest reputation you can buy.See it work
How it works
A partner submits an invoice through the fund’s invoice form for reimbursement. From the approved amounts, Introw generates a reimbursement statement. It is a document whose line items are sourced from either the approved budget or the sum of approved claims, with a PO number and a downloadable PDF. It moves through its own stages: draft, pending approval, approved, paid. Once reimbursed, you mark the project paid, which updates its CRM status and logs the event, closing the loop. Like every other step, the invoice form is no-code with its own approval flow, has its own reimbursement deadline on the timeline, and can be turned off if your program reimburses another way. Partners can submit and track invoices off-portal, and the statement, PO, and payment status live on the same CRM-linked project everyone already collaborates on.Run it from your AI assistant
Going deeper
How to
Configure the invoice form, reimbursement statements, and marking paid.
API reference
Integration surface and code.
Proof of Expense
Invoices reimburse approved claims.
Projects
Invoices close out a funded project.
Form Builder
The invoice form is built and customized no-code.