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

PROBLEM · PLAN MISMATCH

Paying for one tier, receiving another.

Plan and seat mismatches are quieter than access leaks but just as costly. A customer on a higher tier than they pay for is a margin leak. A customer on a lower tier is a churn risk.

What this problem looks like

The Stripe subscription reflects one plan or quantity. The application entitlement reflects another. The customer may be over-served or under-served relative to what they pay for.

  • Plan upgrade in Stripe did not propagate to the entitlement
  • Seat count changed but access was not updated
  • Feature flags tied to a stale tier
  • Downgrade that was not applied to the product
  • Add-on or metered usage not reflected in access

Detection method

The reconciliation engine compares the billed plan and quantity against the granted plan and quantity. A finding is raised when they disagree, with the specific field and both values recorded.

Why policy matters

Some mismatches are intentional: grandfathered plans, manual upgrades, promotional access. The policy defines which mismatches are findings and which are expected. The policy version is recorded on every finding.

Frequently asked

Are seat counts supported?

Quantity comparison is part of the reconciliation engine. The exact fields depend on the snapshot shape you provide.

What about grandfathered plans?

Grandfathered plans can be handled through the policy configuration. The finding is still surfaced; the resolution is a team decision.

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.