The filed rate is the charged rate.
You sign off what gets filed, and you answer for what gets charged. VeriQuant checks that the two match on every case, before the change goes live.
A rate change ships on trust
Your team files the change. Nobody can show, case by case, that the system now charges it.
Errors surface as refunds
A wrong edition or a lapsed deviation is found by a customer or a regulator, months later, with interest.
Leakage nobody measured
Undercharges never show up in a report. You only see the overcharges, and only when someone complains.
01
A case for every changed row, each with the premium your approved rates say it should charge. Every case a match, or a mismatch that names the step.
02
Re-rate the policies already written against the edition that should have applied. Each finding comes with the row and the step. Revisions themselves are read as data and checked cell by cell: rate revision testing →
03
A step-by-step calculation for every case, archived with the change record. When the question comes, you send the report.
The question you can now answer
Answered for every case you run, to the cent, before the change goes live.
The next step
A rate revision. A January table load. A bracket that moved. An edge case nobody trusts. In 45 minutes, a senior member of our team walks whoever owns your rules, your Head of QA and your CIO through how the check is built for that case, and how your team runs the comparison in your own non-production environment, exactly as you test today.
45
minutes
or email info@karatelabs.io
Need a calculation check we don’t list? We build it during your evaluation.