Validators · Validator
Refund Policy Validator
Check how your refund handling affects revenue reporting — deduction timing, partial refunds, and chargeback policy.
About this validator
Refunds are simple in principle and easy to get quietly wrong in practice — undefined deduction timing, untracked partial refunds, or no chargeback policy all create gaps between what your revenue dashboard shows and what actually happened.
This validator checks how your refund handling affects revenue reporting.
Frequently Asked Questions
How is this different from the Revenue Integrity Audit?
The audit scores your entire revenue reporting integrity across many dimensions. This validator checks refund handling specifically, with an automatic verdict, in under a minute.
Should refunds restate historical revenue or just deduct from the current period?
Both are valid choices, but they need to be a deliberate decision, not a default. Deducting from the current period keeps historical months immutable (simpler for reporting); historical restatement is more accurate but requires clear versioning since past reports may no longer match current numbers for the same period.
Is my input data saved anywhere?
No. Everything is evaluated in your browser from your selections. Nothing is sent to or stored on our servers, and no account is required.
Go deeper
This validator checks one artifact. For a full system-wide score, run the Revenue Integrity Audit.
Revenue Integrity Audit →Want Dnoise to check this automatically, every month?
Connect Stripe in read-only mode and Dnoise flags these issues automatically — no manual validation required.
Connect Stripe — free →