Once a partner runs the activity, they have to prove what they spent. Proof of expense is how they do it: claims with receipts and invoices attached, filed against the approved project, drawing down the budget, and reviewed the same way every other submission is - so reimbursement rests on evidence, not trust.
The problem it solves
Reimbursing on receipts scattered across inboxes is slow and risky:Impact
Nothing sours a co-marketing relationship faster than a partner carrying your spend for a quarter. A stated deadline and a fast clear is why they front the money for you next time.See it work
How it works
A partner submits a claim against an approved project through the fund’s claim form, attaching proof of spend - receipts, invoices, creative - as document uploads. Each claim is a CRM-linked record with an amount and date, and the sum of approved claims draws down the project’s approved budget so you always know what is left. Claims run through the standard review flow: agentic approval can clear straightforward claims automatically above a certainty threshold, and anything that needs a human routes through your approval steps. There is no separate “statements” screen - the approved claims against a project are the auditable statement of reimbursable spend your finance team reimburses against. Partners can submit claims from the portal or off it, and the whole thing is worked in the project’s collaborative workspace with a claim-window deadline.Run it from your AI assistant
Going deeper
How to
Configure the claim form, proof uploads, approval, and claim window.
API reference
Integration surface and code.
Projects
Claims file against an approved proposal.
Invoices
Approved claims roll into a reimbursement statement.
Submissions & Approvals
Claims are reviewed like any submission.