The platform · Powered by FohBoh | MGE™

Certification happens before anything reaches your system of record.

Eight deterministic steps, a Trust Score that gates the output, and an evidence standard built to hold up outside your building. No AI inference anywhere in the calculation.


The certification instrument

A number only becomes a claim when the evidence supports it.

Every certification cycle produces a Trust Score. It measures evidence coverage — how much of your data was actually there to check. A Certified Analytics & Audit Report is issued only at 85 or above.

M02 · Delivery Services Provider recovery — current cycle

91
Trust Score · Certified

Below 85, Sentry still issues a hash-sealed report — stamped NOT CERTIFIED, with every gap itemized and the specific steps that would close it. You never get a certified answer built on incomplete evidence, and you never get silence about why.

Specimen record · CAAR-M02-2026-07-000418 · narrative seal
sha256: fbfffe7c48071d42982a5adbac959f1fe181a87756e2238d9d31e9be29246c77


The shift

An audit tells you what happened last year. Sentry tells you what's true, every cycle.

Periodic audit

  • Evidence assembled under time pressure, once a year
  • Findings are already historical by the time you see them
  • Each engagement re-litigates whether the process was followed correctly
  • A gap in one location's records stalls everything
  • Recovery windows with processors and platforms close while you wait

Rolling certification

  • Evidence collected and reconciled weekly or monthly, not once a year
  • Every location's Trust Score reflects the latest cycle
  • The same 198-rule deterministic pipeline runs every time — reproducible by design
  • A CAAR is ready the moment a period qualifies
  • Claims get filed inside the dispute window, with the evidence already sealed

What happens after you connect

You send data. Sentry does the rest.

Your part is one thing: connect the sources, once, with our team. Everything below runs automatically, every cycle, without anyone on your side touching it — and it runs the same way every time, which is what makes the output reproducible.

Sealed on arrival

Your data is hashed the moment it arrives, so what gets certified is provably what you sent.

Checked against a second source

POS against platform settlements, POS against bank deposits. A discrepancy has to appear in two systems to count.

Scored, then certified

198 deterministic rules run and a Trust Score is calculated. Below 85, nothing certifies — you get an itemized list of what's missing.

Delivered as evidence

A sealed CAAR, every dollar traced to the rule that found it. Ready to file, not to interpret.

Talk to an account manager Thirty minutes. We'll tell you which of your sources are ready to certify and which aren't.

Evidence standard

Built to hold up outside your building.

Recovery claims get challenged. The output is structured so the argument is about the money, not about how the number was produced.

FRE 803(6)

Business records exception

Certified values are written to an append-only Vault at the time they're generated — the standard for records made in the regular course of business.

FRE 902(11)

Self-authentication

Every CAAR is sealed with a SHA-256 hash computed against the final rendered document, so authenticity doesn't require a live witness.

FRE 1002

Best evidence rule

The same inputs reproduce the same hash, every time. No model, no inference, nothing to re-litigate about how a number was reached.


Technical deep dive

The whole architecture, on one page.

Every claim above, in full: the chain of custody, how a Trust Score is built, the certification states, and how a CAAR self-authenticates. Written for the person who has to sign off on it.

01Three layers, one provable chain of custody
02Four steps, one locked record
03Three certified revenue streamsM01–M03
04One score that gates every CAAR
05How certification status is reached
06Self-authenticating evidence, no witness requiredFRE 902

See a live cycle run on your own numbers.

Thirty minutes with an account manager, using a real M01 or M02 cycle. If we don't think you'll recover enough to justify the program, we'll say so on the call.