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

HOW IT WORKS

Four steps.
Zero automatic writes.

Reconciliation is less about a clever query and more about agreeing on identity, completeness, and policy. The product is built around those three decisions.

01

Start with a read-only export

Export subscriptions from Stripe and the matching entitlement rows from your application. The browser audit normalizes column names, detects common delimiters, and reconciles locally. No row is uploaded.

If you only have one side of the comparison, stop here and fix the export first. A partial snapshot produces confident nonsense.

Run the browser audit
02

Write the access policy down

Decide how trials, past-due accounts, cancellations, annual contracts, and manual grants should be treated. These are product decisions, not database defaults. Record the version you are using.

A finding without a policy is an argument waiting to happen. The policy is the shared reference that makes review possible.

Read the policy guide
03

Add read-only connections

For continuous checks, connect a restricted Stripe TEST key and deploy the signed Supabase snapshot function in your own project. Secrets are encrypted server-side; the browser never receives them back.

The current build only supports Stripe TEST mode. Live mode is disabled until payment and legal gates are satisfied.

Read the connector docs
04

Review, decide, close

Each finding carries both identities, both snapshot timestamps, the policy applied, a priority, and a recommended next step. Reviewers change status and add notes. Exports preserve the evidence.

SubSync Guard never cancels a subscription or revokes access. The team makes the change in the system that owns it.

See the finding shape

THE POLICY TABLE

Billing status is not access policy.
Make the mapping explicit.

These are the defaults the reconciliation engine can express. Your product may choose differently, but the choice should be written, versioned, and reviewable.

Stripe stateDefault treatmentWhat to verify

active

Entitled

A paid subscription is the strongest signal. If access is missing, review the mapping first.

trialing

Entitled if the product grants trial access

Make trial access explicit. Do not infer it from a marketing promise.

past_due

Entitled during a written dunning window

Record the grace end date. Do not rely on the status string alone.

canceled at period end

Entitled through current_period_end

Compare the effective access window, not just the current status.

canceled immediately

Not entitled

Check whether a manual grant or support exception exists.

unpaid / incomplete

Not entitled by default

Any exception needs an owner and an expiry date.

Boundary conditions are the real test

A period that ends at midnight UTC is not the same as midnight local time. Test the minute before and after expiry, including a daylight-saving transition if your users span timezones.

Manual grants need an expiry

Support extensions, partner accounts, and founder deals are legitimate. Record them as exceptions with an owner and an expiry date so the engine can cite them instead of rediscovering them every run.

THE SNAPSHOT CONTRACT

A snapshot must declare
what it is missing.

The receiving service cannot distinguish a canceled subscription from a truncated page. Completeness has to be part of the payload.

Complete flag

True only when the sender has finished all pages and knows the row count.

Snapshot time

The moment the source was read, in ISO 8601 UTC, not the moment the request arrived.

Row count

Compared with the accepted rows before reconciliation; a mismatch is a review state.

Source version

A connector version and secret version so a behavior change can be traced.

Idempotency key

A nonce stored under a unique constraint and inserted atomically with the snapshot.

Signed request shape
illustrative
POST /functions/v1/supabase-ingest
x-integration-id: 9f2c...
x-timestamp: 1763152924000
x-nonce: 4b1d9e0a0c7f4a1e
x-signature: 7f9c2a...

{
  "complete": true,
  "snapshot_at": "2026-11-14T20:02:00.000Z",
  "row_count": 842,
  "rows": [
    {
      "user_id": "usr_sample_88",
      "stripe_customer_id": "cus_sample_02",
      "is_premium": false,
      "plan": "free",
      "access_expires_at": null
    }
  ]
}

Signature material

hex(HMAC-SHA256(secret, timestamp + "." + nonce + "." + rawBody))

FINDING LIFECYCLE

A closed loop, not a notification stream.

Findings are durable records. The lifecycle is intentionally small so teams can adopt it without a new process.

Open01

Detected in a complete run. Priority and recommended next step are attached.

Investigating02

A reviewer has accepted the signal and is checking identity, policy, or the source record.

Resolved03

The underlying billing or access record was corrected in the system that owns it.

Ignored04

A documented exception. The reason stays with the record for the next reviewer.

A finding that disappears from a later run is not silently deleted. It is marked resolved and keeps its history.

THE FIRST TEN MINUTES

Run the audit before you connect anything.

Download a subscription export, export your entitlement table, and compare them locally. If the output is useful, the docs explain how to make it continuous.