Every month, your PI firm pays invoices to 5, 8, maybe 12 different lead vendors. Each invoice represents a promise: we delivered leads that became cases. But how many of those leads actually became signed cases? How many of those signed cases will produce revenue? And does the vendor's invoice match what your case management system shows?
At most PI firms, nobody is asking those questions systematically. Marketing pays the invoices based on vendor-reported lead counts. Finance processes the AP. And the case management data that could verify the vendor's claims sits in a separate system, reviewed by a separate team, on a separate timeline. The result is a reconciliation gap — and that gap costs firms $50,000 to $200,000 per year in overpayments, misattributed cases, and undetected vendor underperformance.
The Three-Way Match
In procurement, the three-way match is standard: purchase order to receiving report to vendor invoice. If the three documents do not agree, payment is held until the discrepancy is resolved. PI marketing needs the same discipline, adapted to its unique data sources.
The three data sets you need to reconcile are:
- Vendor invoices (Accounts Payable): What the vendor says they delivered and what they charged. This includes lead counts, case counts, per-lead or per-case fees, ad spend, and management fees.
- Case management data (Operations): What your intake team actually received and signed. Lead source attribution, intake date, sign date, and case status for every case in the system.
- Settlement data (Finance): What each case actually produced in revenue. Settlement amount, fee earned, costs recovered, and the original lead source attribution carried through from intake.
Collect vendor invoices and normalize the data
Gather every vendor invoice for the month. Normalize the data into a standard format: vendor name, invoice period, total charge, number of leads claimed, number of cases claimed (if applicable), and pricing model (per-lead, per-case, retainer, or ad spend + fee). Different vendors report differently — standardization is essential.
Pull case management data for the same period
Export all leads received and cases signed during the invoice period from your CMS. Group by attributed lead source. This is your internal record of what each vendor actually delivered — independent of what the vendor claims on their invoice.
Match vendor-claimed leads to CMS-recorded leads
Compare the vendor's reported lead count to your CMS lead count for that vendor during the same period. Discrepancies are common — vendors may count leads your team marked as duplicates, wrong practice area, or outside your geographic territory. Flag any variance greater than 10%.
Verify case attribution for per-case billing vendors
For vendors that bill per signed case, confirm that each billed case exists in your CMS, is attributed to that vendor, and was signed during the invoice period. Cases that were signed but later withdrawn within the first 14 days should be flagged for credit — most vendor contracts allow a dispute window.
Append settlement data to mature cohorts
For invoices from 12+ months ago, pull settlement data for the cases those vendors generated. Calculate the actual ROI for that cohort. This does not affect current-month payment, but it creates the historical performance data that informs budget allocation and vendor renegotiation.
Common Discrepancies and How to Handle Them
When you start reconciling vendor invoices against internal data, you will find discrepancies. Some are innocent accounting differences. Others are material. Here are the most common patterns.
| Typical Impact | Root Cause | Resolution | |
|---|---|---|---|
| Vendor claims more leads than CMS shows | 5–15% overcount | Duplicate leads, wrong practice area, out-of-territory | Request lead-level detail from vendor. Cross-reference against CMS. Dispute unverified leads. |
| Vendor bills for cases your team rejected | $2,000–$5,000/mo | Vendor counts the lead as 'converted' when the client expressed interest, not when you signed | Align on case definition: signed engagement letter = case. Nothing less. |
| Invoice period doesn't match CMS dates | Timing mismatch | Vendor counts by lead delivery date; CMS records by intake or sign date | Agree on a shared date: lead delivery date for per-lead billing, sign date for per-case billing. |
| Ad spend invoiced exceeds platform data | 3–8% overage | Agency markup, platform reporting lag, or currency/tax discrepancies | Require monthly platform screenshots or API reports alongside invoices. |
| Cases attributed to multiple vendors | 2–5% of cases | Client contacted multiple sources; first-touch and last-touch attribution disagree | Establish a firm-wide attribution model (typically first-touch for PI). Apply consistently. |
Timing Adjustments for the Settlement Lag
The biggest challenge in reconciling marketing spend against outcomes is time. A vendor invoice arrives 30 days after service. The cases from that invoice settle 6 to 18 months later. You cannot reconcile spend to revenue in the same accounting period — the data does not exist yet.
Here is how to handle the timing gap:
- Monthly reconciliation: Match invoices to lead and case counts. This verifies you are paying for what you received. This can and should be done within 15 days of invoice receipt.
- Quarterly performance review: For cohorts that are 6+ months old, calculate interim metrics — cases still active, cases settled to date, cases withdrawn. This gives you an early read on vendor quality before final disposition.
- Annual ROI reconciliation:For cohorts that are 12+ months old, calculate the full revenue picture. This is where you determine whether a vendor's cases were profitable. Feed this data back into budget allocation decisions and contract renegotiations.
The key insight for finance teams: marketing spend at a PI firm should be evaluated on three timelines simultaneously. The monthly check confirms accuracy. The quarterly review monitors trajectory. The annual reconciliation measures actual return. Skipping any one of these creates a gap that vendors — intentionally or not — will exploit.
Flagging Vendors Where Numbers Do Not Reconcile
Persistent reconciliation discrepancies are a signal. A vendor whose lead counts consistently exceed your CMS records by 15% or more is either counting differently than you are (a process problem) or overcounting (an integrity problem). Either way, you are overpaying.
Build a vendor reliability score based on reconciliation accuracy. Track three metrics per vendor per month:
- Lead count accuracy: Vendor-reported leads vs. CMS-recorded leads, expressed as a percentage. Target: 95% or higher.
- Case attribution accuracy: Vendor-claimed cases vs. CMS-confirmed cases attributed to that vendor. Target: 98% or higher.
- Invoice accuracy: Total invoiced amount vs. verified amount after reconciliation. Target: 97% or higher.
| Lead Accuracy | Case Attribution | Invoice Accuracy | Status | |
|---|---|---|---|---|
| Vendor A | 97% | 100% | 99% | Green — reliable |
| Vendor B | 92% | 96% | 95% | Yellow — monitor |
| Vendor C | 84% | 91% | 88% | Red — escalate |
| Vendor D | 96% | 99% | 98% | Green — reliable |
Vendors consistently scoring below 90% on any metric should receive a formal reconciliation review. Provide them with your data, explain the discrepancy, and ask them to reconcile from their side. Good vendors will work with you to resolve the differences. Vendors who cannot explain the gap — or who explain it the same way every month without fixing it — are vendors you should be evaluating for replacement.
Building This Into Your Monthly Close
Vendor invoice reconciliation should not be a special project. It should be part of your monthly close process, the same way you reconcile bank statements and vendor payables. The workflow takes 2 to 4 hours per month for a firm with 8 to 10 vendors — and it consistently identifies $3,000 to $15,000 per month in overpayments, misattributions, or billing errors.
The return on that 2 to 4 hours of work is among the highest of any financial control your firm can implement.
RevenueScale's Case Analytics automates the three-way match — connecting vendor invoices to CMS case data to settlement outcomes — and flags reconciliation discrepancies automatically, so your finance team can focus on resolving exceptions instead of building the reconciliation from scratch every month.