AP Invoice Processing
Automates the clerical front end of accounts payable while keeping the approve-and-pay decision with a person. It scans an AP inbox for vendor invoices, reads attachments and scans, and extracts invoice date, vendor, description, invoice number, amount, and due date, citing where each value came from. It dedupes against your AP log by invoice number so nothing is logged twice, appends one new row per invoice marked 'added by skill, needs review', forwards the email to your AP system (for example bill.com or Ramp — an example, not a requirement), applies a label, archives the email, and hands back a run summary of logged / skipped / uncertain. Vendors on your exclude list are skipped so card-paid charges handled by the sibling card-receipt-forwarding flow are not double-processed. The safety guardrail is the point: the skill never approves and never pays. It drafts and files; a human audits every new row before any money moves, and anything unreadable or conflicting is flagged 'uncertain, needs review' rather than guessed. Treat it like a sharp intern — about ninety percent right, fast on the boring parts, and always audited. Detection criteria, the exclude list, and the scheduled-run lookback window are operator settings you confirm in plan mode before the first run.
How to run AP Invoice Processing without a mail connection
The full workflow watches an AP inbox for you. If you would rather not connect one, you can run the same extraction and logging by hand — it just means you do the forwarding, labeling, and archiving yourself.
- 1
Forward the invoice into the chat
When a vendor invoice lands in your inbox, forward it into your Claude chat (or attach the PDF/scan directly). No mail connection needed for this part.
- 2
Get the extracted row back
The skill reads the invoice, pulls out the date, vendor, description, invoice number, amount, and due date, and hands you back one AP-log row marked "added by skill, needs review," citing where each value came from.
- 3
Do the filing yourself
First, do two checks the automated flow normally handles for you: look up the vendor on your exclude list, and search your AP log for the invoice number. Skip these and a card-paid charge can get logged twice. Then paste the row into your AP log, forward the email to your AP system, add a label, and archive it.
- 4
Connect a mail MCP later if you want it automated
If you decide you want the inbox watched automatically instead of forwarding invoices one at a time, connect a mail MCP such as the Gmail MCP and the same extraction and logging steps run without you doing the forwarding.
Your skill is downloading.
Get an email when we ship new skills and updates.
You're on the list. We'll email you when new skills drop.
What this skill does
This is an overview of the skill from the site, not the skill's real instructions. The full SKILL.md Claude reads when this skill is active lives on GitHub at the pinned source below.
AP Invoice Processing automates the clerical front end of accounts payable and leaves the approve-and-pay decision with a person. It watches an AP inbox for vendor invoices, reads the attachments and scans, and pulls out invoice date, vendor, description, invoice number, amount, and due date — citing where each value came from.
Each invoice is deduped against your AP log, appended as one new row marked “added by skill, needs review,” forwarded to your AP system, labeled, and archived. Every run hands back a summary of what was logged, skipped, and flagged uncertain. Vendors on your exclude list are skipped so charges already handled by the sibling card-receipt-forwarding flow are not double-processed.
The guardrail is the point: it never approves and never pays. It drafts and files; a human audits every new row before any money moves, and anything unreadable or conflicting is flagged “uncertain, needs review” rather than guessed. Detection criteria, the exclude list, and the scheduled-run lookback window are operator settings you confirm before the first run.
View full SKILL.md on GitHub