Overview

AP Intake Agent

Reads the bills, runs the match, queues the exceptions.

Reads vendor PDFs, emails, and EDI feeds. Extracts header and lines, runs three-way match Bill PO Receipt, queues only the exceptions for human approval.

Start free

No credit card Live in 60 seconds Off-switch per agent

Saves

92% touch-free

Touches

Accounts payableOCRThree-way match

01What it actually does

No demo magic. Real actions, real audit trail.

Each action runs through the same engine your humans use: same posting rules, same approval routing, same audit log. The agent's name is on every transaction it touches.

Pulls bills from every channel

Watches the AP inbox, EDI partner feed, vendor portals, and any storage drop folders you wire up. Ingests PDF, image, EDI 810, JSON, CSV.

Extracts header and lines

Vendor, bill date, due date, terms, currency, totals, tax breakdown. Line items mapped to PO lines via item code, description, and amount; remainders flagged.

Runs the three-way match

Bill PO GoodsReceipt within tolerance bands you set. Match passes queued for posting. Mismatch opens a Disputed bill with the specific deltas named.

Routes the exceptions

Approver chosen by the Approvals Agent's policy. Bills under tolerance and within preferred-vendor terms post unattended; the rest get a one-line summary and a 'why this needs you' note.

02How it decides

The logic behind every action.

Not a black box. The decision rules are explicit, configurable, and surfaced on every action so the auditor (and you) can trace the why.

Tolerance bands per vendor

Default $25 / 2% / 1 unit. Override per vendor, strict for new vendors, looser for known partners with consistent rounding.

Confidence score on extraction

Below 95%, the bill enters a review queue with the source document and the extracted JSON side-by-side. Above 95%, it posts.

Duplicate detection

Hash on (vendor, bill_no, total). If the agent has seen this bill before, it routes to the original AP clerk for de-dup confirmation rather than posting again.

03What you control

Off-switch per agent. Always.

Every agent runs on a leash you set. Approval thresholds, dry-run mode, per-entity disable, audit trail, your call.

Per-vendor automation level

Off / Review-only / Auto-post. Set globally and override per vendor.

Approval thresholds

Bills above $X always require human approval, regardless of match quality.

Quarantine new vendors

First N bills from a new vendor always queue for human review, even with a perfect match, guards against AP fraud via spoofed vendor onboarding.

04This morning

A real activity log.

Excerpted from a production tenant. Every line is signed, timestamped, and traceable to the action it represents.

AP Intake Agent · activity log · today

08:14

Ingested 23 bills overnight (4 EDI, 17 email PDF, 2 portal).

08:14

Three-way match: 19 passed, 3 disputed (line-amount delta), 1 quarantined (new vendor).

08:15

Posted 19 bills auto. Queued 3 disputes to AP-Manager. New-vendor bill routed to AP-Lead for first-bill review.

05Built on

The skills this agent calls.

Every agent is composed from the underlying ERP skills, the same ones your humans use. No private data path, no shadow ledger.

Accounts payable Procurement Warehouse

06FAQ

Common questions.

Asked by the people whose name goes on the audit packet.

How do you handle handwritten or poor-quality scans?

Below the 95% confidence threshold, bills route to human review with the source document attached. Manual posting takes the same path as today; the agent just removes the easy 90%.

What about fraud risk?

Three layers: (1) duplicate detection on (vendor, bill_no, total), (2) new-vendor quarantine for the first N bills, (3) Approvals Agent enforces your existing thresholds, the AP agent doesn't bypass any control your policy has today.

07The other 7 agents