Close the month with nothing unexplained.
Ventura reads every row of your spend export and shows you the few payments that need a second look, each traced to its evidence. Nothing changes until your team decides.
Duplicate payment · Corva Freight
Rule: The same invoice paid twice
Reads exports from the systems you already use, or any CSV, Excel or PDF file.
- QuickBooks
- Xero
- Stripe
- Expensify
- Google Sheets
1,431 rows in. Five worth a person’s time.
A list nobody trusts gets ignored. Ventura judges each payment in its own context, merges findings that describe the same event, and ranks what is left by severity and confidence. Open one below, check its rows, and decide.
Findings
AP register, Sep 2026.xlsx · 1,431 rowsExample dataDuplicate payment · Corva Freight
Rule: The same invoice paid twice
Invoice
INV-77812
Days apart
14
At risk
$18,420.00
Evidence
| Date | Amount | |
|---|---|---|
| 2026-09-04 | $18,420.00 | Original |
| 2026-09-18 | $18,420.00 | Flagged |
Both payments carry invoice INV-77812 for the same amount, 14 days apart. The earlier payment is treated as the original and kept as evidence; only the later one is flagged.
Judged against the vendor’s own history
A $40,000 payroll remittance is routine. A $27,300 invoice from a vendor you normally pay around $3,000 is not. Ventura scores amounts against each category’s and each vendor’s own baseline, so the routine stays quiet and the outlier surfaces.
Patterns no single payment reveals
Invoices split to stay under an approval limit. A payment dated October but booked to September. A vendor suddenly coded to a different account. A first-time payee paid a round amount on a Saturday. None of these breaks a rule on its own, so Ventura looks at the pattern.
From an export to a review queue
No integration project. Start from the file your system already produces.
- 1
Export
Pull a GL detail, AP register or bank statement from the system you already use. CSV, Excel and PDF all work.
- 2
Upload
Ventura finds the header row, searches every sheet and maps date, vendor, amount and debit or credit columns. Credits are set aside, not dropped.
- 3
Review
Findings arrive ranked by severity and confidence, each with its rows. Resolve or dismiss them; every action is logged.
| In your file | Read as |
|---|---|
| Posting Date | Date |
| Supplier Name | Vendor |
| Debit | Amount |
| Credit | Credit |
| Memo | Description |
| GL Account | Account |
Rows read
1,431
Credits set aside
12
Findings
5
Ventura recommends. Your team decides.
Nothing in Ventura resolves, dismisses or edits a record on its own. Every status change is a person’s action, recorded with who, what and when.
- No autonomous actions
- Ventura flags and explains. It never pays, voids or edits.
- Confidence you can read
- Every finding carries a score from 0 to 100 and the reasoning behind it.
- Append-only security log
- Sign-ins, MFA checks and team changes are written server-side and cannot be edited.
Finding raised by Ventura
Duplicate payment, Corva Freight, confidence 96
Sep 30, 09:12
Status changed by d.okafor@yourco.com
Open to Under review
Sep 30, 10:05
Note added by d.okafor@yourco.com
“Second payment confirmed with Corva. Credit note requested.”
Sep 30, 11:40
Status changed by m.reyes@yourco.com
Under review to Resolved
Sep 30, 16:22
Ten checks, one review queue
Every threshold comes from a stated statistical or control rationale, not from tuning to one company’s file, so the same settings hold on your register.
- Duplicate payment
- The same amount paid twice, judged on evidence: a shared invoice number, the same day, or a second payment inside a monthly cycle. Rent on the 1st is a rhythm, not a duplicate.
- Split under approval limit
- Payments to one vendor clustered just under an approval limit, including limits Ventura finds from how your payments bunch.
- Period cut-off
- A transaction dated outside the period it is labelled with, after learning the file's own fiscal calendar.
- Unusual for the vendor
- Several times the vendor's usual payment, judged against its other payments once there are enough to trust.
- Unusual for the category
- From a vendor with no history of its own, far above the top of what that category usually costs.
- Coding change
- A vendor coded one way almost every time, suddenly booked to a different category.
- Payment burst
- More payments in a week than the vendor's own rate explains, or a new vendor paid several times at once.
- New-vendor risk
- A vendor first seen mid-register whose payment is round, large or posted on a weekend, each scored by how unusual it is in your own spend.
- Round amounts
- A round figure from a vendor that otherwise bills irregular amounts, for invoice support.
- Missing payee
- Payments with a blank or unknown vendor, so nothing posts without a counterparty.
Morning, and nothing left unexplained.
Walk through a month-end review on a sample AP register: 1,431 rows, five findings, and the decisions a reviewer makes on them.