What counts as proof of performance?
Whatever the program requires: live post URLs, event photos, creative files, media schedules, and invoices. Sizle's requirement matrix makes the list explicit per campaign type, so dealers know before they run.
Proof of performance
Before co-op funds are reimbursed, a dealer has to prove the campaign ran: post URLs, photos, creative, and invoices. Sizle collects that proof on the campaign record and validates it automatically — so reviews take days, not quarters.
Proof arrives as email attachments, named inconsistently, weeks after the campaign. Controllers cross-check invoices against budgets by hand, reject claims for missing photos, and the resubmission loop starts over. Dealers learn to expect their money in ninety days — or stop claiming at all.
Post URLs, photos, creative, and invoices upload straight to the campaign they belong to, against a requirement matrix that shows what's missing.
Submitted invoices are read automatically and matched against eligible spend and the reimbursement rules for that market and brand.
Eligibility, caps, and required proof are defined per program — so every claim is evaluated the same way, and dealers can see why.
Cleared claims export for payment with the complete chain — plan, approvals, evidence, invoice — preserved for audit.
Whatever the program requires: live post URLs, event photos, creative files, media schedules, and invoices. Sizle's requirement matrix makes the list explicit per campaign type, so dealers know before they run.
Completeness checks and invoice OCR happen before a human looks at the claim, so reviewers handle exceptions instead of every submission. Networks on Sizle review claims in days rather than across the quarter.
The dealer sees exactly which requirement failed and resubmits against the same campaign record — no new email thread, no lost history.
Tell us how your network runs today, and see the parts of Sizle that map to it.