Features - Compliance-grade sanctions screening for non-banks
MatchAudit helps non-banks, PSPs, SMEs, marketplaces, NGOs, and SaaS teams screen faster, reduce noise, and produce evidence reviewers accept.
Predictable outputs and consistent evidence, regardless of how you run the check.
MatchAudit combines a screening engine, automation, and an evidence system so teams can act quickly and still prove due diligence later.
Platform guarantees
Compliance teams need predictable outcomes, not surprises. These guarantees are designed to prevent the most common trust-breakers: double-counting, unclear evidence, and accidental overuse.
Duplicate clicks, retries, and repeated calls can be detected and deduplicated to protect your quota and bill.
Requests are validated against your entitlements so you stay within plan caps without manual policing.
Screening activity is metered as decisioning usage and checked before execution, supporting predictable packaging.
Each screening can log sources selected, sources scanned, and diagnostic context so evidence is reproducible.
Where appropriate, non-critical enforcement checks can fail open to prioritize availability while preserving core controls.
When a screening needs action, higher tiers can automatically create cases so teams move from hit -> resolution quickly.
Evidence packs
Many tools stop at "match/no match." MatchAudit focuses on defensible outcomes: inputs, sources used, timestamps, and match rationale - exported in formats stakeholders understand.
If you're evaluating for a bank or enterprise review, request an example and we'll tailor it to your workflow.
Reduce back-and-forth by giving reviewers what they ask for: consistent logic, traceable sources, and a tamper-evident record.
Governance & privacy
Visibility is scoped to roles (personal / team / org) and teams can control sharing per feature. This reduces internal leakage risk while still enabling oversight.
Analytics and audit history are scoped by role so sensitive activity isn't exposed internally.
Managers can oversee their team's workload without seeing unrelated teams unless explicitly authorized.
Teams can opt in/out of sharing per capability - so collaboration is intentional, not accidental.
Geo screening
Some cases are risky because of where funds, shipments, or operations touch. MatchAudit adds geo screening so teams can evaluate jurisdiction and territorial exposure alongside name screening.
Run geo triage by country, territory, city, region, or IP-derived location depending on what the workflow gives you.
Use jurisdiction and corridor signals to identify when a case needs deeper review before onboarding, payouts, or shipments proceed.
Geo screening is useful when names alone are not enough to explain exposure in trade, payments, logistics, or donor-disbursement workflows.
Data integrity
For audits and customer assurance, dataset transparency matters. Higher tiers can expose dataset versions, source URLs, and integrity hashes to prove freshness and prevent tampering concerns.
See the most recent version of each dataset and when it was fetched.
Verifiable hashes (e.g., SHA-256) help prove the dataset hasn't been altered.
Dataset origin URLs can be surfaced so you can explain provenance with confidence.
Start in the dashboard, scale with spreadsheet imports, add SAP GTS review workflows where needed, and integrate by API when automation becomes critical.
Most teams begin with the dashboard, add spreadsheet workflows for bulk onboarding, use SAP GTS when external trade workflows need defensible review, and move to API when automation becomes critical.
You get explainable matching and confidence bands so reviewers can understand why a hit occurred and avoid noise-driven escalations.
Screenings can record selected sources, scanned sources, and unavailable sources alongside results, so the evidence is reproducible and reviewable.
Coverage spans UN, EU FSF, OFAC SDN and Non-SDN, US CSL, BIS, DDTC, State non-proliferation programs, the UK Sanctions List and UK proscribed organisations, SECO, Canada, Australia, and selected national lists such as France, the Netherlands, Belgium, Poland, Latvia, Lithuania, Estonia, and Czech Republic, plus geo-risk datasets used for corridor review.
Yes. Teams can start in the dashboard, use batch spreadsheet workflows, and use SAP GTS review workflows when external operational exports need defensible side-by-side review before or alongside API automation.
Duplicate clicks, retries, and repeated calls can be detected and deduplicated so your quota and billing remain accurate.
Visibility is role-scoped and team-level oversight is available without exposing unrelated teams' activity unless explicitly authorized.
Start pilot once free validation is complete and your workflow is recurring: multiple reviewers, repeated evidence requests, and clear rollout timelines.
You get a searchable audit log and exportable evidence packs capturing inputs, sources, timestamps, and match rationale, reducing manual documentation.
Start free to validate match quality and evidence outputs. Contact us when you need throughput, governance, exports, or procurement support.
Tip: For security reviews, select "Security review" in the contact form.