Localized reading guide
ap-processorPurpose, usage and source
Works the bill pile end to end: reads bills and vendor statements out of the AP inbox or from uploaded PDFs and phone photos, pulls out vendor, amount, due date, and line detail, codes each one to the right account and job, matches it against the purchase order and the receiving ticket, then stages the entries and a proposed payment run in QuickBooks, Xero, or NetSuite for the owner to approve in one pass. Nothing is entered and nothing is paid without an explicit yes. Reach for this whenever bills, vendor invoices, or paying people comes up — including "what do I owe," "the bills are piling up," "pull the invoices out of my email and into QuickBooks," "code these for me," "who needs to get paid this week," "did we get billed twice," or when the owner forwards a supplier invoice with no message at all. Use it before cash-flow-snapshot or month-end-prep so those run on real payables instead of a guess.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/ap-processor/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Development
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Works the bill pile end to end: reads bills and vendor statements out of the AP inbox or from uploaded PDFs and phone photos, pulls out vendor, amount, due date, and line detail, codes each one to the right account and job, matches it against the purchase order and the receiving ticket, then stages the entries and a proposed payment run in QuickBooks, Xero, or NetSuite for the owner to approve in one pass. Nothing is entered and nothing is paid without an explicit yes. Reach for this whenever bills, vendor invoices, or paying people comes up — including "what do I owe," "the bills are piling up," "pull the invoices out of my email and into QuickBooks," "code these for me," "who needs to get paid this week," "did we get billed twice," or when the owner forwards a supplier invoice with no message at all. Use it before cash-flow-snapshot or month-end-prep so those run on real payables instead of a guess.
How the upstream workflow works
AP Processor
Turn the bill pile into coded entries and one payment decision. Owners describe this job as printing, stamping, and hand-keying the same twenty invoices every month. It is almost entirely mechanical — right up to the part where money leaves the account, which is entirely the owner's call.
Upstream passage · L20 ↗Step 1 — Gather the bills
Pull from whatever the owner actually has: AP inbox — a mail label or folder (Gmail or Microsoft 365), or a forwarding address like bills@. Read the message body and every attachment; some vendors put the invoice in the body and no PDF at all. If the connection cannot read an attachment (a PDF or image the mail connector's tools won't open), name the message and the vendor and ask the owner to download and upload the file or paste its contents — never skip the bill silently.
Step 2 — Extract the fields, and say what you could not read
For every bill, pull: vendor, invoice number, invoice date, due date, terms, subtotal, tax, freight, total, PO number if present, and line detail. A field you cannot read stays empty and gets named. A smudged total on a photographed invoice is reported as unreadable with the vendor and invoice number attached, never rounded to something plausible. Everything downstream — the coding, the payment run, the cash forecast — inherits whatever number lands here.
Upstream passage · L37 ↗Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
Ramp is a backup path, never the primary one
Ramp can approve or reject a bill and mark it ready to sync to the ledger, so it is a genuine write path — which is exactly why it needs a rule. The ledger stays the system of record. The connected ledger (NetSuite, QuickBooks, Xero, or Zoho Books) is where bills are staged and where the payment run is decided. Ramp's approve/reject and ready-to-sync calls are used only when the owner's bills genuinely live in Ramp and no ledger connector covers them, and they sit behind the same Step 7 payment gate as everything else.
Upstream passage · L91 ↗Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- AP Processor
- Step 1 — Gather the bills
- Step 2 — Extract the fields, and say what you could not read
- Step 3 — Code each bill
- Step 4 — Match POs and receipts
- Step 5 — Show the owner the picture before touching the books
- Step 6 — Stage the entries, with approval
- Step 7 — Propose the payment run, with a separate approval
- Ramp is a backup path, never the primary one
- Check every vendor for credits before ranking them
- Step 8 — Vendor emails, when needed
- What not to do
- Output
- After the run
- Reference files
- Using a tool that isn't listed
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
a2dbac917c45a114d886a8e2d4348c04415888a2b0d51c7f2946fcd210e7736d