Correct billing evidence
Distinguishes finalized invoice rows from unbilled or mixed-period evidence before any seat quantities are compared.
Find out whether a Partner Center CSV is safe for fixed-fee license reconciliation before a wrong export creates dozens of false billing gaps. The checker identifies billing state, usage records, lifecycle adjustments, missing evidence, and duplicate rows.
Local CSV inspection
Select one Partner Center CSV. Leakage Finder inspects its structure in your browser and explains whether it is safe for a fixed-fee seat comparison.
Drop your Partner Center CSV here
Or choose a file. CSV only, up to 10 MB and 50,000 rows.
Why preflight comes first
A row can represent a recurring seat, metered consumption, a cancellation credit, or a mid-cycle adjustment. Treating every quantity as an active license makes the report look precise while producing the wrong answer.
Distinguishes finalized invoice rows from unbilled or mixed-period evidence before any seat quantities are compared.
Separates fixed-fee records from consumption and surfaces credits, cancellations, conversions, renewals, and quantity changes.
Stops missing billable quantities, daily usage exports, duplicate rows, mixed workloads, and other inputs that can manufacture fake gaps.
From valid export to recoverable revenue
Preflight tells you whether the Microsoft evidence is trustworthy. Leakage Finder’s full reconciliation then matches that evidence against ConnectWise, Autotask, HaloPSA, Kaseya BMS, or another PSA export to surface review-ready quantity gaps.
No. The free preflight checker reads the CSV locally in your browser. The report contains structural counts and findings, not customer names, product names, filenames, or row values.
Use a finalized new commerce invoice reconciliation export for the billing period you want to compare. Open-period or daily rated usage exports can create misleading seat variances and are flagged by the checker.
It identifies billed versus open-period evidence, fixed-fee versus usage-based records, credits and lifecycle events, missing reconciliation fields, duplicate rows, mixed currencies, and other conditions likely to create false-positive billing gaps.
No. It validates whether the Microsoft export is suitable for comparison. A full reconciliation still needs the matching PSA billing export and human review before any billing record is changed.