How it works
A small first check.
An answer you can inspect.
Start with a historical snapshot. Connect recurring sources when you need repeated checks.
- 01
Prepare the sources.
Export purchase records and all relevant grant transactions for the same bounded cohort. Keep stable application account and purchase identifiers.
Source preparation → - 02
Declare the expected credits.
Map each Price to units, currency, effective dates and grace. Missing or ambiguous rules remain unchecked.
Fields and rules → - 03
Confirm the boundaries.
Declare coverage for both exports and choose a shared check time. Preview rejected and unsupported records before saving.
Choose your path → - 04
Inspect the result.
See matched purchases, discrepancies, pending grants and unknown evidence separately. Retain the exact source snapshots and rule version.
Try the sample → - 05
Correct, then verify.
Fix your own source system and supply fresh evidence. Recheck the original cohort to see what changed; Ropely never writes financial repairs.
Evidence and correction →
When you need ongoing checks
Keep both sources current.
Connect Stripe with restricted read access. Run the PostgreSQL exporter in your environment with a dedicated reader of the export view, then deliver each ledger snapshot against its purchase import.
Explicitly configure a schedule and recipients. Monitor freshness and failed deliveries separately from discrepancies. A CSV upload does not turn on monitoring.
Prepare monitoring →