DocPipe Verify

Check an invoice before your agent or automation posts or pays it.

Send the invoice fields you already have, from any extractor. You get back a verdict, two flags your agent can act on, and the reason for every hold.

Field	Meaning
verdict	PASS: every check that matters ran and passed. REVIEW: a warning, or not enough evidence (for example, totals that can't be reconciled). REJECT: a check failed, so don't post this data as given.
canAutoPost	true only when the verdict is PASS
canAutoPay	true only when the verdict is PASS and the duplicate check actually ran against priorInvoices and passed
holdReasons	Why either flag is false, for example TOTAL_MISMATCH, POSSIBLE_DUPLICATE, DUPLICATES_NOT_CHECKED, TOTALS_NOT_VERIFIED

A warning is never an approval, and a check that couldn't run is never reported as a pass.

The checks are deterministic: plain arithmetic and rules, with no AI deciding. The same request always gives the same answer, and inputHash identifies the request. It's computed from the parsed values, so key order, spacing, 561.6 vs 561.60 and Unicode spelling don't change it.

Checks

Check	What it does
requiredFields	Vendor, invoice number, invoice date and total are present
arithmetic	Subtotal + tax = total (to half a cent), with the expected and found amounts
lineItems	Line items add up to the subtotal (or the total when there is no subtotal)
dates	Not in the future; warns when over two years old, or due before issued
purchaseOrder	PO number present, when you set poRequired
duplicate	Compared with your priorInvoices on normalized values ("Northwind Supply Co." = "NORTHWIND SUPPLY, INC"; "INV-0041" = "inv 0041"). Same vendor and number: REJECT. Same vendor, currency and total within 7 days under a different number: REVIEW, with the matched invoice, since it may be a re-issue or a recurring charge.
approvedVendor	Vendor is on your approvedVendors list, when you send one
currency	A real ISO 4217 code, matching expectedCurrency if you set it; warns when currency is missing or the total is negative (credit note)
extractionConfidence	Fields your extractor scored below minFieldConfidence (default 0.8). Confidence is reported per field and never blended into a "safe" score.

Input rules

Amounts must be JSON numbers (not strings) with at most 4 decimal places. Dates must be YYYY-MM-DD. Unknown field names are rejected, so a typo like totl never silently becomes "missing total". Malformed invoices come back as verdict: "ERROR" with the field named, and aren't charged.

Example

Input:

{
  "invoices": [{
    "vendor": "Northwind Supply Co.", "invoiceNumber": "NW-20841", "invoiceDate": "2026-09-30",
    "currency": "USD", "subtotal": 520.00, "tax": 41.60, "total": 601.60
  }],
  "options": {
    "priorInvoices": [{ "vendor": "Northwind Supply Co.", "invoiceNumber": "NW-20799", "total": 388.10, "invoiceDate": "2026-09-02", "currency": "USD" }]
  }
}

Dataset item:

{
  "index": 0,
  "invoiceNumber": "NW-20841",
  "verdict": "REJECT",
  "canAutoPost": false,
  "canAutoPay": false,
  "holdReasons": ["TOTAL_MISMATCH"],
  "checks": { "requiredFields": "PASS", "arithmetic": "FAIL", "lineItems": "NOT_CHECKED", "dates": "PASS",
              "purchaseOrder": "NOT_CHECKED", "duplicate": "PASS", "approvedVendor": "NOT_CHECKED",
              "currency": "PASS", "extractionConfidence": "NOT_CHECKED" },
  "issues": [{ "code": "TOTAL_MISMATCH", "severity": "ERROR", "field": "total",
               "message": "Subtotal 520.00 + tax 41.60 = 561.60, but stated total is 601.60 (difference 40.00)",
               "reason": null, "expected": 561.60, "found": 601.60, "matchedInvoice": null }],
  "missingFields": [],
  "validatedFields": { "vendor": true, "invoiceNumber": true, "invoiceDate": true, "subtotal": false, "tax": false, "total": false },
  "fieldConfidence": {},
  "rulesetVersion": "2026-10.2",
  "inputHash": "sha256:..."
}

Pricing

You're charged once for each invoice that gets a verdict. Malformed invoices aren't charged. When your run's spending limit is reached, the run stops; it never goes over. If the platform restarts a run, invoices already charged are delivered from saved results and aren't charged again.

Your data

Invoice fields are sent over HTTPS to the DocPipe API (Pycas Design Innovations, hosted on AWS) to be checked, and are not stored there. Invoice contents are never logged. Results are saved only in your own Apify storage. Send only the fields the checks need: no bank details are required.