DocPipe Verify
Check an invoice before your agent or automation posts it or pays it. Send the fields you already have; get back a clear verdict and the reason for every hold.
Why it exists
Reading an invoice is no longer the hard part. Knowing whether the data is safe to act on is. Totals that don't add up, an invoice you have already paid under a slightly different vendor name, a missing purchase order, a date in the future: these are the mistakes that cost money once an automation posts or pays without a person looking.
DocPipe Verify runs the same checks DocPipe uses before it lets an invoice through to export, and answers one question: can this go ahead, or should a person look first?
The answer an agent can act on
- PASS: every check that matters ran and passed.
- REVIEW: a warning, or not enough evidence to be sure. A warning is never treated as approval.
- REJECT: a check failed. Don't post this data as given.
Every answer also says whether the invoice can be posted automatically and whether it can be paid automatically, and lists the reasons when it can't. Paying needs the duplicate check to have actually run against your recent invoices; a check that couldn't run is never reported as a pass.
Checks
| Check | What it does |
|---|---|
| Required fields | Vendor, invoice number, invoice date and total are present. |
| Arithmetic | Subtotal plus tax equals the total, with the expected and found amounts when it doesn't. |
| Line items | Line items add up to the subtotal, or to the total when there is no subtotal. |
| Dates | Not in the future; warns when over two years old or due before issued. |
| Purchase order | A PO number is present, when you require one. |
| Duplicates | Compared with your recent invoices after normalizing vendor names and invoice numbers. The same vendor and number is rejected; the same vendor and amount within a week under a different number is held for review, with the matching invoice shown. |
| Approved vendor | The vendor is on your approved list, when you send one. |
| Currency | A real currency code, the one you expect if you say so; warns on negative totals, which are usually credit notes. |
| Extraction confidence | Any field your reader was unsure of, reported field by field and never blended into a single "safe" score. |
How it behaves
- Deterministic. Plain arithmetic and rules, with no AI deciding. The same request always gets the same answer, and each answer carries a fingerprint of the request it belongs to.
- Strict about input. Amounts sent as text, unknown field names and badly formed dates are refused with the field named, never quietly guessed.
- Nothing stored. Invoice data is checked and discarded. Invoice contents are never written to our logs. No bank details are needed.
Use it
For agents and automations: DocPipe Verify is listed on an agent marketplace, where agents and automation tools can run it without a DocPipe account. Each invoice that gets a verdict costs $0.01; malformed invoices are reported and not charged. Open the listing.
For DocPipe customers: the same checks are part of the DocPipe REST API, at POST /api/v1/verify and POST /api/v1/verify/batch (up to 500 invoices per request), using the API key you create in the application. Send your invoice fields as {"invoice": {...}} and, optionally, recent invoices for the duplicate check.
Questions
Need a check that isn't listed, or want to run Verify on your own documents first? Email info@pycasdesign.com or call (847) 656-5756. For the full service, with document reading, human review and export, see AI Document Processing.