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

THE PRODUCT

A control plane for the
space between billing and access.

Six capabilities, one narrow job: turn two incomplete sources of truth into findings a human can review, explain, and close. No write access. No automatic revocation. No black-box score.

WHAT IT ACTUALLY DOES

Capabilities, with their
operating requirements.

Each card states what the staging build can do and what must be configured. Availability labels are part of the product, not marketing decoration.

Staging

Snapshot ingestion

Three ways in: a browser CSV audit, a read-only Stripe TEST connection, or a signed entitlement snapshot from your own Supabase project. Each source declares whether the snapshot is complete.

Stripe keys are verified against customers, subscriptions, invoices, products, and prices before they are stored.

Staging

Policy-driven comparison

The engine applies an explicit policy to trials, dunning, cancellation at period end, and access expiry. The policy version is attached to every finding so a later policy change does not silently rewrite history.

No machine-learned guesswork. The comparison is deterministic and reviewable.

Staging

Stable findings

A fingerprint built from stable identifiers prevents duplicate rows across runs. A resolved issue that reappears reopens the same record instead of creating a parallel history.

Fingerprints use source identifiers, not display names or row order.

Staging

Review workflow

Findings move through open, investigating, resolved, and ignored. Reviewers can record notes and export the current view as CSV or print a report.

No automatic remediation and no hidden assignment model. The team owns the decision.

Needs config

Alert routing

Route high-priority findings to email, a Slack incoming webhook, or a custom webhook whose host has been approved by the deployment administrator. Test sends make delivery visible.

Email delivery requires RESEND_API_KEY and EMAIL_FROM on the backend.

Staging

Workspace governance

Roles, expiring email-bound invitations, member removal, and owner-only destructive actions. Owners can export or erase audit data without a support ticket.

Invitation acceptance requires a signed-in account whose email matches the invitation.

WHO CAN DO WHAT

Permissions that are
enforced, not implied.

Every browser-facing action passes through a server function that verifies the Supabase JWT and the caller’s workspace role. The database also enforces row-level security.

RoleScope

Owner

Full workspace control, billing settings, destructive actions, data export and erasure.

Can invite admins, analysts, and viewers.

Admin

Connections, monitoring, alerts, findings, and workspace settings.

Can invite analysts and viewers. Cannot grant admin.

Analyst

Review findings, change status, add notes, run reconciliation, and export reports.

Cannot invite or change roles.

Viewer

Read-only access to overview, findings, monitoring, and reports.

Cannot invite or change anything.

Server-side enforcement

The UI hides actions a role cannot perform, but hiding a button is not security. The workspace API re-checks the role on every request, including destructive actions and billing.

Invitation binding

Invitation tokens are single-use, expire after seven days, and are only redeemable by an authenticated account whose email matches the invited address. Raw tokens are not readable through the client table grant.

INTERFACE PREVIEW

Dense where it matters.
Quiet everywhere else.

The interface is built around the finding, not around a vanity chart. These are layout previews with sample data, not customer metrics.

Overview · sample
Connected

Paid, no access

3

sample

Access after end

2

sample

Plan mismatches

1

sample

Resolved this cycle

7

sample

cus_sample_02

active → free

HighOpen

cus_sample_03

canceled → premium

ReviewInvestigating

cus_sample_07

team → team (seat mismatch)

ReviewOpen

Source status

Stripe TEST

Synced 14:02 UTC

OK

Entitlement snapshot

Complete · 842 rows

OK

Reconciliation

Policy v0.1

Ready

Deliberate limits

  • No writes to Stripe or your database
  • No automatic access revocation
  • No live-money billing in this build
  • No compliance certification claims

What we measure

Disagreements between billing state and access state, under a documented policy. Not “revenue recovered,” unless a verified price and time window support it.

What you receive

A finding with identifiers, timestamps, policy version, priority, recommended next step, status, and notes. Exportable and printable.

What happens next

Your team decides. Restore access, correct a plan, record an exception, or ignore the signal with a reason. The audit does not act on its own.

SEE IT WITH YOUR OWN DATA

Start with a local audit. Decide about connections later.

The CSV audit runs entirely in your browser. If the pattern is real, the documentation explains how to add read-only Stripe TEST and signed Supabase snapshots.