
Every claim checked before a handler opens it.
Every file had to be checked for completeness before a handler could start.
The first pass runs around the clock. Every routing decision carries its reason.
- E/02 Runtime enforcement
- A/04 Approvals
Claims that need sorting. Invoices that need matching. Questions that need a cited answer. Different work, same controls.
All three run on Gatehouse, the software we built and operate.

Every file had to be checked for completeness before a handler could start.
The first pass runs around the clock. Every routing decision carries its reason.

Real mismatches got lost among the small differences.
Clean invoices go through as ERP drafts. Every exception shows its sources.

The same easy questions every day. The hard ones waited behind them.
People only get answers the library backs up. Every correction becomes a worked example.
What changes is the scope, the role, the limits and who approves. Read a row across to see one gate on all three.
| Gate | W/01 · InsuranceClaims triage | W/02 · DistributionInvoice matching | W/03 · Internal operationsPolicy answers |
|---|---|---|---|
| 01SCOPE | Read the intake channels · write to the intake queue only | Read the AP inbox, purchase orders and goods receipts · write ERP drafts and match results | Policy library, read-only · answers with a cited clause |
| 02ROLE | Classify and route · never decide or reject a claim | Match and draft · never post a final payment | Answer policy questions · never act outside the policy library |
| 03LIMITS | A spend limit on each run, set in the signed manifest | A spend limit on each run, checked before the action | A spend limit on each run, set in the signed manifest |
| 04REVIEWwhere it stops for a person | Low-confidence files held for a named claims handler | Over the limit, outside tolerance or a changed bank detail → the AP lead, by name | Below the confidence threshold → named support lead |
| 05SEAL | Each routing decision in the audit trail, with its reason | Each match, draft and hold in the audit trail, with its sources | Each answer with its clause in the audit trail |
Each case draws on more than one engagement. Names and figures are changed, anonymised by agreement. No case names a customer. Each one is labelled.
Each write-up names the Gatehouse parts it uses, and each part has its own page. The seven parts
Tell us what comes in, who handles it and where it breaks. A person replies, usually inside two business days.
support@surehand.io