Same pipeline every time — different sources, different rules, the same sealed output. Start with one module; add others as your sources connect.
Six situations operators bring to us. Each one is the same pipeline — different sources, different rules, the same sealed output.
Interchange downgrades, tier reclassifications, and PCI and gateway line items that were never in the signed schedule. Statements come location by location, so nobody compares them against the rate card.
Output A certified effective merchant rate per location, with every disputed line item traced to the contract term it violates.
Commission taken on the wrong base, promo funding charged twice, refunds and adjustments absorbed without documentation, and orders that appear in the POS but never in a payout.
Output POS-to-DSP reconciliation at order level, with a recoverable total and the platform-facing evidence packet.
Gross sales definitions in FDD Item 6 rarely match what the POS exports or what a franchisee self-reports. Deductions get taken that were never authorized, and the disagreement is about definitions, not arithmetic.
Output Royalty calculated against the loaded FDD definition, with variances itemized per franchisee, per period.
Food cost and labor cost move because someone changed a denominator, not because the business changed. Two reports disagree and the team spends the week deciding which one to trust.
Output One authoritative KPI definition per metric, versioned, with every certified value reproducible from the same inputs.
Portfolio reporting arrives in whatever shape each operator's stack produces. Normalizing it consumes the diligence window, and the adjustments are the part that gets argued over at close.
Output Certified revenue, margin, and fee load across the portfolio — same definitions, same rules, every entity.
A recovery claim is only as good as the record behind it. Spreadsheets reconstructed after the fact invite a fight about methodology instead of about the money.
Output A CAAR sealed with SHA-256 at generation, written to an append-only Vault, structured against FRE 902(11) and 803(6).
Each module is scoped to one leakage source and runs on the same deterministic engine. Start with one; add others as your sources connect.
Recovers overcharges and misapplied fees from card processors and merchant statements — interchange, assessments, and contract-rate variance.
Recovers fee and settlement discrepancies from third-party delivery platforms — commission base, promo funding, refunds, and missing payouts.
Recovers underreported royalty base and unauthorized deductions, calculated against FDD Item 6 definitions loaded into the Vault.
Nothing here is self-serve yet. A dedicated Sentry specialist handles each step alongside your team, and you're certified in weeks — not quarters.
We map every current data source — POS, delivery platforms, bank feeds, accounting — against what certification requires, before anything is scheduled.
Select which modules apply to your system. Each one is scoped to a specific leakage source.
Your rate schedules, franchise agreement, FDD Item 6 definitions, and governance rules are loaded into the Vault as the definitions Sentry certifies against.
Our team connects each system directly. You're not handed a setup wizard — you're handed a working connection.
Your first cycle runs on the cadence you choose. Trust Scores appear in your console as each cycle completes.
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.