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

PROBLEM · STALE ACCESS

The subscription ended. The access did not.

Stale premium access is one of the clearest revenue leaks and one of the easiest findings to get wrong. The difference is policy and evidence, not a clever query.

What this problem looks like

A cancellation, failed payment, or expiry has landed in Stripe, but the application still grants premium features. Sometimes this is an intentional grace period. Sometimes it is a leak that nobody has noticed.

  • Cancellation processed but entitlement not revoked
  • Failed payment with no dunning or grace logic
  • Manual grant that was never reconciled
  • Cached entitlement that outlived the subscription
  • Seat count that was never reduced

Grace versus leak

The same data can be a grace period or a leak depending on a written policy. SubSync Guard surfaces the disagreement and lets the team apply the policy version they have chosen. The policy is explicit, not implicit.

  • Define the grace period length in days
  • Define whether trials count as paid
  • Define whether manual grants override billing
  • Record the policy version on every finding

Detection method

A finding is raised when a cancelled, unpaid, or expired subscription has a matching active entitlement. The finding includes the subscription status, the access state, and both snapshot times.

Frequently asked

Should I revoke access immediately?

That is a product and policy decision. The tool surfaces the disagreement; it never revokes access.

What about grace periods?

Grace periods are configured in the policy. A finding within the grace window is still surfaced but can be resolved as expected.

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.