Today's Agent Skill: Vendor Invoice Reconciler
What It Does
Accounts payable inboxes fill with PDF invoices that never quite match the purchase orders behind them — wrong line totals, duplicate submissions, quantities off by one. Most teams catch these by hand, after payment, when clawing the money back is awkward. This skill puts a reconciliation pass in front of every invoice before it reaches approval.
How It Works
The agent parses an incoming invoice into structured line items — vendor, PO reference, SKU, quantity, unit price, tax, total — then pulls the matching purchase order and compares field by field. It flags three failure classes separately: arithmetic errors inside the invoice itself, mismatches against the PO, and duplicate invoice numbers already seen for that vendor. Everything that clears all three checks gets marked auto-approvable with the reasoning attached.
How to Deploy It
Save the content below as SKILL.md in your agent's skills directory, then point the Input section at wherever your POs live — a spreadsheet, an ERP export, or a shared folder. Any SKILL.md-compatible agent will pick up the trigger phrases on the next session start; no code changes needed.
SKILL.md — Ready to Deploy
## Description
Reconciles vendor invoices against purchase orders before they enter the approval queue. Catches arithmetic errors, PO mismatches, and duplicate submissions, then produces a structured verdict with an auto-approve recommendation and an itemized exception list.
## Trigger
Fires on: reconcile this invoice, check this invoice against the PO, invoice reconciliation, does this invoice match, AP review, vendor billing check, verify this bill. Also fires when the user shares an invoice file or pastes invoice text alongside a PO number, even without explicit reconciliation language.
## Input
- **Invoice**: PDF, image, or pasted text. Required.
- **PO source**: path to the purchase order record — spreadsheet, ERP export, or folder. Required on first run, then remembered.
- **Invoice history**: prior invoice numbers per vendor, for duplicate detection. Optional but strongly recommended.
- **Tolerance**: acceptable variance in currency or percent. Defaults to $0.00 / 0%.
## Steps
1. Extract invoice fields into a structured record: vendor name, invoice number, invoice date, PO reference, line items (SKU, description, quantity, unit price, extended price), subtotal, tax, tCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.