Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

COMPARE · SPREADSHEETS

The false positive is not a data problem. It is a policy problem.

Spreadsheet audits produce false positives because the policy is implicit. Structured reconciliation makes the policy explicit, versioned, and reviewable.

Why spreadsheets produce false positives

A spreadsheet comparison has no policy. It compares two columns and flags every difference. But some differences are expected: trials, grace periods, manual grants, and in-flight changes. Without a policy, every expected difference becomes a false positive.

  • No trial or grace-period handling
  • No manual-grant awareness
  • No snapshot completeness check
  • No freshness threshold
  • No policy version to explain the result

How structured reconciliation reduces them

SubSync Guard applies an explicit policy to each comparison. Trials can count as paid. Grace periods can suppress findings. Manual grants can be excluded. The policy is versioned and recorded on every finding.

  • Configurable policy for trials, grace, cancellation
  • Snapshot completeness and freshness checks
  • Stable fingerprints to avoid duplicate findings
  • Review state to track false positives over time

Measuring improvement

Track the ratio of findings that are resolved as expected versus genuine. A good reconciliation system should reduce false positives over time as the policy improves.

Frequently asked

Can I configure the policy?

Yes. The policy configuration covers trials, grace periods, cancellation handling, and manual grants.

What if my policy is wrong?

The policy version is recorded on every finding. You can change the policy and re-run to see the difference.

Next step

Start with the evidence. Connect nothing until the workflow earns it.

START WITH THE EVIDENCE

See the gap before it becomes a refund.

Run a private CSV audit in your browser, or create a workspace and connect an isolated Stripe TEST account.