Replace the macro and the thirty scenarios.
Your team proves every rate change with spreadsheet macros and a few dozen hand-picked cases. VeriQuant generates the cases, computes the expected premium, and tells you exactly where a mismatch starts.
Coverage is whatever someone thought of
Twenty to forty hand-picked scenarios per change. The row nobody picked is the row that breaks.
Expected values come from the system
When the answer key is copied from the system under test, the test can only agree with it.
A mismatch says wrong, not where
Your testers spend the day tracing which factor, which table, which edition.
01
Plus the policies either side of the effective date, each with its expected premium, drafted from your rate manuals and filings, never from the system. See an example report ↗
02
Every case is a match, or a mismatch that shows where the two calculations part ways. Anything unexplained stays open, never counted as passed.
03
Your team runs the comparison in your own QA environment, exactly as today. The rulebook is plain text in git and runs in your pipeline with no model in the path.
The question you can now answer
Answered by the report itself: the case, the step, the table and the edition.
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.