Duplicate invoices
Exact and probable duplicates across vendor, invoice number, amount and currency.
Two invoice documents with matching invoice number and amount fields highlighted.Payment integrity for finance teams
SentriCap analyzes invoice, vendor and payment data and produces explainable, evidence-backed findings your team can verify.
Payment Risk Scan · Command center
Illustrative synthetic dataRisk score · 93/100
Vendor bank account changed 4 days before payment.
Approved vs. observed account
Potential exposure
Investigating$312,000
Not confirmed loss — pending human review of PAY-89440.
Explainable controls
Every alert states the rule, threshold and compared values.
Source-linked evidence
Invoices, payments and approval logs attach to each alert.
Human decision authority
SentriCap prioritizes and evidences — your team decides.
One historical scan
A single defined period, delivered as a service, no subscription.
Risk coverage
Each control is a deterministic rule with a stated condition. A triggered control is an exception that deserves review — it is not a finding of fraud, and SentriCap never presents it as one.
Exact and probable duplicates across vendor, invoice number, amount and currency.
Two invoice documents with matching invoice number and amount fields highlighted.Bank account changes shortly before a payment to the same vendor.
Timeline showing an established account, a changed account, then a payment.The payment beneficiary disagrees with the approved vendor master account.
Side-by-side comparison of the approved account and the observed payment account.Invoices above the threshold with no linked purchase order or goods receipt.
Chain from purchase order to goods receipt to invoice to payment with the goods receipt missing.The same identity created and approved the same invoice.
Approval graph showing one user identifier appearing at both the creation and approval step.Invoices clustered just below a single-approver threshold.
Bar chart of several invoices, each just below a dashed approval threshold line.Process
A single historical scan over a defined period, delivered as a service with your team.
Stage 1
Invoice, vendor and payment exports are mapped to a common schema before analysis.
vendor,invoice_no,amount
Meridian,INV-4182,184500.00
Stage 2
Deterministic rules with stated conditions run across the mapped data.
Stage 3
Your team works a prioritized queue with every source record attached.
Stage 4
Potential exposure, confirmed issues and control recommendations, reported to leadership.
Executive report
No ERP integration required for the first scan — SentriCap works from structured CSV exports.
Inside the product
Alerts are ranked by potential exposure, linked back to source records, and summarized into findings your leadership can act on. Figures below are synthetic.
Alert queue
Synthetic dataMeridian Steelworks Inc.
DUP-001
Calder Logistics Corp.
VBC-002
Aldervale Facility Services
BEN-003
Thornbury Consulting Partners
EVD-004
Evidence panel
Calder Logistics Corp. — VBC-002
Vendor record
Bank account changed 4 days before payment
Payment
$312,000 released to new account
Potential exposure — pending team review
Alerts ranked by potential exposure and severity, ready for your team to work.
Every alert opens onto the invoice, payment and vendor records behind it.
A leadership-ready summary of confirmed issues and the control gaps behind them.
Control architecture
Finance teams cannot act on a score they cannot explain. Four principles shape every control in the product.
Every alert states the rule, threshold and compared values — no opaque model score.
Invoices, payments and approval logs are attached to the alert that used them.
Potential exposure is only called a confirmed issue once your team establishes it.
SentriCap prioritizes and evidences. No control approves or blocks a payment.
Map and Prove describe the Payment Risk Scan SentriCap delivers today, in a single historical period. Attack and Heal are the direction the product is building towards and are not available yet.
Map
Available nowMap the paths by which money can leave the organization, across vendors and approval routes.
Prove
Available nowProve the evidence behind a payment: what was ordered, received, approved and paid.
Attack
PlannedTest controls with safe synthetic scenarios to see which weaknesses would let a payment through.
Heal
PlannedImprove weak controls through measured recommendations and track the exception rate.
Pricing
A single, one-off engagement over a historical period. No subscription, no integration project and no commitment beyond the scan. Priced in USD.
Up to 5,000 invoices
Starting at $1,000
One-off Payment Risk Scan
Up to 25,000 invoices
Starting at $2,500
One-off Payment Risk Scan
25,001–100,000 records or multiple entities
Custom, starting at $5,000
Scoped per engagement
Final pricing depends on data quality, number of entities, included datasets and required custom controls.
FAQ
Ready when you are
One historical period, structured file exports, no ERP integration required.