|
TUE · NOV 10 · EDITION |
AP invoice coding with an AI first pass and a human sign-off
Manual GL coding of AP invoices is slow partly because you are rebuilding context every time - repasting account numbers, re-explaining cost centers, starting over for each entity. This workflow loads your chart of accounts into a prompt template once, then produces a proposed code and cost center for each invoice that a designated reviewer checks before anything touches the ledger. It is built for teams coding moderate-to-high invoice volumes who want speed without removing the human judgment that catches miscodes.
BUILD WITH AI
How to code AP invoices faster with a general-purpose AI assistant
This workflow uses a general-purpose AI assistant to produce a first-pass GL code and cost center for each AP invoice, then routes every suggestion to a human reviewer before it touches the ledger. Set it up once per client or entity; the prompt carries the chart of accounts context so you are not retyping it each time.
1 |
Export or copy the relevant section of your chart of accounts - account numbers, account names, and any cost center codes - into a plain text file you will paste into the prompt template. |
2 |
Open your general-purpose AI assistant and start a new session for the entity you are coding (do not carry context across entities). |
3 |
Paste the following prompt, filling in the bracketed fields with the actual invoice data: 'You are an accounts payable coding assistant. Here is the chart of accounts for this entity: [paste account numbers and names]. Here is the invoice detail: Vendor: [vendor name]. Invoice date: [date]. Invoice total: [amount]. Line item description: [exact description from invoice]. |
4 |
Copy the assistant's response into your AP coding log - a spreadsheet with columns for vendor, invoice number, AI-proposed code, AI-proposed cost center, reviewer name, final code, and a notes field. |
5 |
Have a designated reviewer - not the person who ran the prompt - check each proposed code against the invoice and the chart of accounts before accepting it. |
6 |
Where the reviewer overrides the AI suggestion, record the original proposal and the corrected code in the notes column. |
7 |
At the end of each week, scan the correction log for vendors or description patterns that consistently produce wrong suggestions, and add explicit examples for those cases to the prompt template. |
8 |
Enter only reviewer-approved codes into the ERP; never post directly from the AI output. |
WORKED EXAMPLE
In practice
A three-person accounting team is coding a stack of 40 AP invoices for a mid-size distribution company for the month just ended. One invoice is from a vendor called 'Apex Facility Solutions' with the line description 'Monthly service agreement - equipment and grounds.'
What came back. The assistant returned two alternatives: 6210 Equipment Repairs and Maintenance ('the description references equipment service as the first element') and 6300 Grounds and Landscaping ('grounds care is explicitly named'). It flagged the invoice for manual review and suggested asking the vendor for a service breakdown. The reviewer noted that the vendor's contract specifies a split between grounds care and equipment maintenance - a detail the assistant had no way to know - so the reviewer allocated the invoice manually across both codes.
How it was checked. The reviewer pulled the original vendor contract on file and confirmed the service breakdown, then matched the split allocation against prior months in the ledger to confirm consistency.
A constructed example. The prompt is usable as written; the figures show the shape of a result, not a measured one.
WHEN TO USE IT
| WHEN NOT TO
|
Yes, that Arnold Schwarzenegger.
He has a newsletter on beehiiv. So do Codie Sanchez, Jay Shetty, David Begnaud, Colin & Samir, and Joanna Stern.
They could publish just about anywhere. They chose beehiiv to build a direct connection with the people who want to hear from them most. And you can do the same, whether you’re world-famous or just at the start of your plan for world domination.
FROM OUR PARTNERS
1 | AI Starter Kit 1 friend · 10 copy-ready prompts for everyday work | Free gift |
3 | Close Prompt Playbook 3 friends · All 20 month-end prompts with reviewer's guides | $39 value |
5 | Playbook + Close Skills 5 friends · The Playbook plus five Claude skills: bank rec, flux review, duplicate payments, deferred revenue and journal entry review | $99 value |
10 | Month-end close kit 10 friends · The Playbook, the Close Skills and the AI-assisted month-end close workflow | $149 value |
Playbook + Close Skills, founding price The prompts, plus five skills that do the matching and the math. The 20 close prompts and five Claude skills: bank reconciliation, flux review, duplicate payments, deferred revenue and journal entry review. Tested scripts, so totals tie the same way every time. One payment. Founding price: $79 for the first 50 buyers, until November 21. Then $99.
New: the AuditFriendly Library, 49 close, audit and bookkeeping tools from $9, some free. Playbook buyers get the matching Library items free. Browse the Library |
GO DEEPER
Go deeper
Next issue: more of the tools and shifts reshaping how accounting gets done.
Forward this to the partner still doing it the old way.
An original workflow written for practitioners. Replicate it in a sandbox first; nothing here replaces your review.
How accountants are using AI, automation and smarter workflows to close faster, audit cleaner, and free up time for real work.
| Month End Closers · Everything that moved in accounting this week |
| Accounting Stack · The software, head to head |
| The Remote Accountant · Remote accounting roles with pay, every weekday |
| The Finance Nomad · Remote finance roles with pay, every weekday |
Audit Friendly · modernaccounting.ai · Audit Friendly Data

