VaultAP Documentation
VaultAP scores every invoice against twelve fraud rules before it is paid. Invoices scoring 25 or below clear on their own. Anything higher waits for a person, with the reason attached.
Two rules override the score entirely: a change to a vendor's bank details, and a match against a blocked vendor. Either one requires a human decision at any score.
Set it up
Account, organization, and your first scored invoice.
Quick start →Understand the scoring
How the twelve rules combine into a score, and what happens at each threshold.
How scoring works →Tune it to your invoices
Adjust weights and thresholds, and cut false positives without going blind.
Reducing false positives →All sections
Getting Started
Set up your account and process your first invoice.
Invoices
Upload, review, act on, and archive invoices.
Vendors
Records, fuzzy matching, merging, and blocking.
Risk Scoring
Rules, weights, thresholds, and AI explanations.
Dashboard
Metrics, activity, and reporting.
Settings
Organization, team, notifications, and risk configuration.
Security
Encryption, tenant isolation, audit trail, and compliance.
API
Programmatic access.
Frequently opened
- Risk rules reference
- Working the review queue
- How vendors are matched
- Importing vendors from CSV
- Audit trail
- Notification settings
Want to see it work first?
The walkthrough follows one real invoice pair end to end — the same vendor, seventeen days apart, with the bank account changed on the second one. It is the shortest path to understanding what VaultAP catches and why it matters.
Read the walkthrough →