The SentriCap platform
One platform to detect, prove, investigate, stress-test and improve payment controls.
SentriCap turns invoice, vendor and payment exports into explainable, evidence-backed findings — organized into five capabilities that work together across a payment's life, from first exception to control improvement. Your team always makes the final call.
Pillar A
Find the exceptions that matter before money moves.
SentriCap runs a library of deterministic and pattern-based controls across every invoice, vendor record and payment in scope, so the exceptions finance teams care about most surface first.
- Flags exact and probable duplicate invoices across formatting and date-window variations.
- Scores new or recently changed vendors for onboarding and identity risk.
- Watches for vendor bank-account changes shortly before a payment release.
- Compares beneficiary details on the payment file against the approved vendor account.
- Detects invoices submitted without linked purchase order or delivery evidence.
- Spots invoices clustered just under an approval threshold.
- Surfaces approval conflicts where a creator and approver are linked.
- Identifies payments that exceed the accepted invoice amount.
Control firing rate
8 controls activeEach bar is one detection control watching a stream of invoices, vendor records and payments; color reflects the highest severity it has produced.
Example / synthetic data
Pillar B
Back every finding with a source-linked chain of evidence.
Each flagged payment gets a Payment Passport: a single record that links the invoice, purchase order, receipt, approval, vendor identity, beneficiary and payment, and separates confirmed issues from amounts still in question.
- Builds one Payment Passport per exception with every linked source record.
- Marks each link as verified, missing, mismatched or needing review.
- Compares a baseline expectation against what was actually observed.
- Separates potential exposure from confirmed issues so nothing is overstated.
- Gives reviewers a document trail they can hand to a vendor or an auditor.
Payment Passport · PAY-88231
Meridian Steelworks Inc. · $184,500
- InvoiceVerified
Original invoice, booked in ledger 4102
- InvoiceMismatch
Second booking with an identical number and amount
- Purchase orderVerified
Structural steel, single release
- Goods receiptVerified
One delivery recorded against PO-77120
- ApprovalVerified
Approved by Controller ID 1187
- Vendor identityVerified
Vendor master unchanged for 14 months
- BeneficiaryVerified
Beneficiary matches the approved vendor account
- PaymentReview required
Second wire released against the duplicate booking
Every link traces back to a source record — invoice, PO, receipt, approval, vendor, beneficiary and payment — so a reviewer can compare baseline against observed and see exactly where the exception sits.
Example / synthetic data
Pillar C
Move a reviewer from queue to decision in minutes, not days.
Alerts are prioritized by explainable score and severity, carry the control that produced them, and come with recommended verification steps and a disposition workflow so a case can be closed and reported on.
- Ranks alerts by explainable score, severity and potential exposure.
- Shows which control fired and why, in plain language.
- Tracks status through investigating, needs information and disposition.
- Recommends concrete verification steps for each alert type.
- Rolls closed cases into executive-ready summaries.
Prioritized alert queue
16 open itemsExact duplicate invoice · Score 96
Vendor bank account changed shortly before payment · Score 93
Beneficiary does not match approved vendor account · Score 91
Missing purchase or delivery evidence · Score 84
Invoices clustered below an approval threshold · Score 81
Every alert carries an explainable score, the control that fired, and recommended verification steps — so reviewers can move straight from queue to case summary.
Example / synthetic data
Pillar D
Prove your controls hold up before an attacker finds the gap.
The Financial Red Team runs safe, synthetic attack scenarios — bank-change diversion, duplicate replay, invoice splitting — through your control paths, then maps a Blast Radius of what a compromised vendor, account or disabled control would actually touch.
- Runs synthetic scenarios that never touch real vendors, accounts or payments.
- Traces each scenario step through the controls that should catch it.
- Flags gaps where a control path let a step through unchecked.
- Fans out Blast Radius across affected vendors, entities, payments and approvers.
- Quantifies potential exposure for each blast-radius target.
Financial Red Team · Bank-change diversion
A synthetic actor requests a vendor bank-account change by email, then submits a routine invoice for release in the next ACH run.
Blast Radius analysis
6 invoices · 3 payments · 2 approvers
9 invoices · 5 payments · 3 approvers
34 invoices · 21 payments · 9 approvers
Example / synthetic data
Pillar E
Turn every exception into a stronger control over time.
Continuous Monitoring tracks control health, learns from recurring legitimate exceptions, and proposes Self-Healing Control recommendations — changes a human owner reviews and authorizes, never an automatic change SentriCap applies itself.
- Tracks coverage, alert volume and confirmed-issue rate per control.
- Learns exception patterns to reduce recurring false positives.
- Recommends specific control tuning for a human owner to authorize.
- Produces executive reporting on exposure, trend and remediation status.
- Tracks remediation items through to close.
Control coverage
Self-Healing Control recommendations — such as tightening a match window or requiring a callback — are surfaced here for a human owner to authorize; SentriCap never applies a control change on its own.
Example / synthetic data
See it work end to end
From first exception to a stronger control environment.
Bring one historical period and see the full platform run against it, or explore the dashboard with synthetic data first.