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

COMPARE · MONITORING

Monitoring tells you something broke. Reconciliation tells you what disagrees.

Generic monitoring tools observe one system at a time. Subscription reconciliation compares two systems and finds the gap between them.

What generic monitoring does

It watches metrics, logs, and events within a single system. It is excellent at detecting outages, errors, and performance regressions. It is not designed to compare billing state against access state.

  • Single-system observability
  • Metric and log based
  • Threshold and anomaly detection
  • No cross-system comparison

What reconciliation adds

It compares two independent systems using their own data shapes, applies a policy, and produces findings with evidence. It does not replace monitoring. It fills the gap that monitoring cannot see.

  • Cross-system comparison with policy
  • Evidence-grade findings with identifiers and timestamps
  • Stable fingerprints for idempotent runs
  • Review workflow with status and notes
  • Exportable reports for finance and audit

When to use both

Use monitoring for system health and reconciliation for billing-access agreement. They answer different questions and should be used together.

Frequently asked

Does SubSync Guard replace my monitoring tool?

No. It complements it. Monitoring watches one system. Reconciliation compares two.

Can I send findings to my monitoring tool?

Alerts can be sent to Slack, email, or an allowlisted webhook. You can route them into your existing monitoring pipeline.

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.