Accounts Payable Still Runs on Email and Attachments

Accounts payable still lives in attachments and clarifying threads. IBM’s agent overview notes finance and supply-chain automation must emphasize privacy when it touches payments data (IBM). NIST’s AI Risk Management Framework is the reference finance and IT use when they want structured risk conversations before expanding automation; see also NIST AI 100-1 (PDF). OECD AI Principles include accountability and security expectations that map cleanly to AP controls. The Commission’s EU AI Act portal documents transparency trends as AI touches enterprise software—relevant when your ERP vendor “helpfully” adds assistants to invoice screens.

OpenAI’s agent governance memo warns about autonomous actions in high-stakes domains without human gates (OpenAI arXiv PDF). Anthropic’s MCP announcement illustrates industry pressure to connect models to operational systems through standard interfaces (Anthropic). The tool-use survey frames extraction workloads and expanded attack surface (arXiv:2404.11584). Brookings documents AI diffusion across industries including finance operations (Brookings). OECD due diligence guidance for responsible AI is procurement language that still ends up forwarded to AP with “please confirm we are covered.”

The gap is not OCR. It is change management.

Mid-market teams delay vendor portals because training is harder than the license. If extraction returns a short table—vendor, amount, due date, line questions—a staff accountant can still post while leadership keeps a story about controlled AI tied to explicit forwards.

Human approval on numbers is not negotiable. The safe split is: machines read, humans post. If your workflow cannot state who approved vendor totals before the payment file leaves, you are not automating—you are accelerating mistakes.

OCR failures will happen. Scans will be crooked. Vendors will send screenshots of invoices like it is a personality trait. The fallback is still the same as 2010: ask for a clean PDF, escalate politely, document the delay. The agent’s job is to make the clean path faster—not to pretend illegible pixels are “structured data.”

Three-way match arguments usually arrive as mail, not as ERP poetry. Forward the purchase order excerpt, the receiving note, and the invoice header together when you want useful extraction. The model cannot infer attachments you never included.

Vendor blasts are where “surprise fees” hide in plain sight: a paragraph that reads like marketing and a table that reads like a rate hike. Digest Vendor Updates is useful because it forces the blast into obligations: what changed, when it starts, and what you must do to opt out. Humans still decide whether to fight; the agent reduces the chance you miss the paragraph entirely.

Per-forward helpers (posting stays human)

via.email is an email-based AI agents platform. Each specialist has a dedicated address. You forward invoices and notices; replies use fixed expert prompts. Attachments are supported on eligible tiers. The service does not silently read your inbox, send mail for you, or remember unrelated threads.

Extract Invoice Data — extract.invoice.data@via.email pulls structured fields from invoice PDFs you attach for import into downstream workflows.

Verify Vendor Tax Form — verify.vendor.tax.form@via.email flags common W-9 issues and missing fields before year-end panic.

Audit Expense Receipt — audit.expense.receipt@via.email checks receipts against policy cues you provide—still human approval on reimbursements.

Decode Tax Changes — decode.tax.changes@via.email translates dense notices into bullet points finance can act on or forward to counsel.

Digest Vendor Updates — digest.vendor.updates@via.email compresses long vendor blasts into rate changes, deadlines, and required responses.

Redaction before forward

If you would not email it to audit, do not forward it to an agent. Strip customer PII, bank details you do not need, and unrelated thread history.

Related via.email finance mail

Invoice-heavy workflows: finance teams extract in email. Procurement friction: procurement stalled by manual work. Contract timing surprises: deadlines hiding in attachments. When the inbox is mostly noise, triage patterns from reply-or-not decisions still apply before dollars move.

Three-email pilot

Run invoice PDF, vendor blast, and tax notice—one forward each, redacted as required. Measure whether posting prep time drops without adding another login.

Limits

Agents do not approve payments, reconcile banks, or replace tax advisors. They accelerate reading and normalization where AP already works: mail.

The GL is sacred. The inbox is where the truth arrives messy. Clean the inbox first.