Accounts Payable Workflow Automation for Small Teams

TL;DR: An accounts payable workflow is the path an invoice takes from arrival to payment: receipt, capture, coding, matching, approval, payment, filing, and retention. In a small finance team the breakage is rarely the payment. It is the document side, where invoices sit in a shared mailbox, approvals happen in forwarded email, and nobody can find the PDF in March. The Drive AI automates that document side: the invoice arriving, being read, being routed for approval over a threshold, then named and filed.

A controller at a thirty person company does not have an AP department. They have a shared mailbox, a spreadsheet, an accounting system, and one person who also does payroll.

Invoices arrive as attachments from forty vendors who each name their files differently. Someone downloads them. Someone forwards the large ones and waits. Someone types vendor, amount, and due date into the accounting system. Someone drops the PDF into a folder, or does not. Six months later an auditor asks for the approval on a $12,000 invoice, and the answer is a search through sent mail.

An accounts payable workflow is the defined sequence an invoice follows from arrival to payment, filing, and retrieval, with a recorded decision at each point where a human has to say yes.

What are the accounts payable process steps, and where do they break?

Eight, and in a small team the first two and the last two absorb most of the time.

1. Receipt. The invoice arrives, usually by email. Breaks when there is no single AP mailbox, so invoices land in three inboxes and one gets paid twice.
2. Capture. Vendor, invoice number, date, total, tax, and due date come off the document. Breaks when it is manual typing, because the error rate is whatever a distracted person's is at 4pm.
3. Coding. The invoice gets a GL account and a cost centre. Breaks when whoever enters it does not know which department ordered it.
4. Matching. The invoice is checked against what was ordered and what arrived. Breaks when there are no purchase orders, so it is one person remembering a conversation.
5. Approval. Someone with authority says pay it. Breaks when approval is a reply saying "fine", attached to nothing.
6. Payment. The accounting system or the bank issues it. Breaks least often, because a missed payment produces a phone call.
7. Filing. The document goes somewhere permanent, named usefully. Breaks constantly, because it is nobody's job and has no deadline.
8. Retention. The invoice stays available for seven or so years. Breaks quietly, and you find out during an audit.

Steps 1, 2, 5, 7, and 8 are document problems. Steps 3, 4, and 6 belong to the accounting system. Fixing AP starts by admitting those are two jobs.

What should an approval threshold policy look like?

A threshold policy names, in writing, who can approve what amount. Three tiers, one page.

• Under $500: no approval if the vendor is approved and the invoice is a recurring service.
• $500 to $5,000: the department manager who requested the spend approves.
• Over $5,000: the controller or CFO approves, with a second signature above $25,000.
• Any amount from a new vendor: approval plus a completed W-9 before the first payment. New vendors are the fraud surface, not large invoices from a supplier of six years.

Two details people skip. Set a response window, because an approval with no deadline is a bottleneck dressed as diligence: three business days, and a lapsed approval returns to a queue rather than approving itself. Then name a delegate for every approver, because holiday is the commonest cause of a late payment fee.

What is a three way match, and does a small team need one?

A three way match compares three documents before payment: the purchase order, the receiving report or packing slip, and the supplier invoice. If quantity and price agree across all three, payment is authorised. Otherwise the exception goes to a person.

You need it when you buy physical goods in quantity, when partial deliveries are normal, or when a supplier bills by the unit. You do not need it when most spend is services, software, rent, and professional fees, because there is no packing slip for a legal retainer. For that profile a two way match, invoice against the purchase order or the engagement letter, plus the approval of whoever requested the work, gives the same control for less effort. A control everyone bypasses exists only on paper.

Who approves, and who files? Keep them different people

The person who approves an invoice should not be the person who files it and marks it paid. That is the smallest useful version of segregation of duties, and it survives in a team of three.

The reason is not distrust. Someone who can both authorise a payment and control the record of it can make an error invisible, including to themselves. Split it: one person prepares, a second approves under the threshold policy, a third releases payment in the bank. With two people, the owner holds the bank release. And an approval that never leaves a personal mailbox is a control you performed but did not record. It has to end up attached to the invoice, with a name and a timestamp.

How an accounts payable workflow runs in The Drive AI

You describe it once in plain English and the steps appear on a canvas. The canonical AP workflow, in the app's own step names:

• Email Attachment (source, free) watches the connected Gmail or Outlook account for your AP mailbox, scoped by sender, for example @acme.com, or by "Subject contains". It runs once per attachment, the email itself is not saved, and Skip duplicate files should be on.
• Save a Copy gives the attachment a storage home, Finance/Inbox in The Drive AI or a connected drive. Set "Then keep working on" to the copy, so later steps act on the filed version.
• Read Details from File (ai). Name the fields: vendor, invoice number, total, due date. Those values are then available to later steps, so they can appear in a filename, a folder path, an approval question, or a webhook body. See extracting data without templates.
• Ask AI About the File (ai) branches on the amount. Branches are authored per node and are the answers the model may give, so one node can have branches named over 5000 and 5000 or under. Use this rather than Check File Details for money: Check File Details is free and exact, but it decides on type, age, location, name, and size, not on a total inside the document.
• Ask a Person to Approve (human) on the over branch. Write "What should the approver decide?" with the values the earlier step read, for example Approve payment of {{nodes.extract_1.entities.total}} to {{nodes.extract_1.entities.vendor}}?. You do not type those tokens: the panel lists the values available at that point and clicking one inserts it. Set "Who decides?" to Specific people, "When to ask?" to Always ask, and Wait up to 3 days. The node has three exits, approved, rejected, and expired.
• Rename (ai) and Move (ai) on the approved path: rename with vendor, invoice number, and date, then move to Vendors/Pinecone Systems/2026. Under "If the same file is already there", Set it aside for review puts the copy in a "Possible Duplicates" folder rather than creating a second record of one invoice.
• Send a Message (external) to a Slack channel such as #finance, or to an email address.

Every run is recorded, can be replayed on the canvas exactly as it happened, and retried from the step that failed.

Four accounts payable workflows, written as When / If / Then

Type these as sentences, then adjust the steps on the canvas.

When an invoice attachment arrives in the AP mailbox, save a copy to Finance/Inbox, read the vendor, invoice number, total and due date, and if the total is over $5,000 ask Priya to approve before filing it under Vendors by vendor and year. If it is under, file it and post to #finance.

When an invoice arrives, file it under Vendors by vendor and year, and if a file of that name is already there, set it aside for review instead of filing it and email ap@northwind.com.

When a scanned PDF with several invoices arrives from the mailroom scanner, split it into separate invoices, send the original to Archive/Originals, then read the vendor and total from each new file and file it under Vendors by vendor and year.

When an attachment arrives from a vendor domain, decide whether it is an invoice, a statement, a credit note, or something else. File invoices under Vendors by vendor and year, statements under Finance/Statements/2026, send credit notes to Priya for approval, and leave anything else in Finance/Inbox.

The last one matters. Much of what lands in an AP mailbox is not an invoice, and filing statements as invoices creates a worse problem than the one you solved. See AI document classification and routing.

Manual AP, connectors, AP software, and Workflows compared

Dedicated AP automation software does matching, ledger posting, and payment, and we do not. What it usually does less well is being the permanent, searchable home for the document in the folder structure your firm already uses. Run both: the accounting system owns the data, the workflow owns the document.

What this will not do

• It is not an ERP and it pays nothing. No journal entries, no vendor master, no tax calculation, no bank connection.
• It does not perform a three way match on its own. It has no purchase orders and no receiving reports. It can send the fields it read to a system that does, using Send to Another App, a webhook taking a URL, a method of POST, PUT, or PATCH, and either no key, a Bearer token, or an API key header. See the webhook step explained.
• ai steps read documents and can be wrong. A smudged scan, a credit note laid out like an invoice. Put an approval in front of anything irreversible.
• Approvals expire. After 24 hours, 3 days, or 1 week the file takes the Expired exit. Connect that exit to something, or nothing happens to the file and the outcome is simply recorded.
• In place versus copy. A workflow watching a folder in Google Drive, OneDrive, SharePoint, or Dropbox renames and moves files inside that storage. Nothing is imported unless the workflow includes Save a Copy, and then only to the place you named.
• Plan requirement. Workflows on files uploaded to The Drive AI work on every plan. Connecting Gmail, Outlook, Slack, Teams, Google Drive, OneDrive, SharePoint, or Dropbox needs the Max plan on a personal workspace, or any Team plan.

Setting up your first invoice workflow

1. Connect the AP mailbox and scope the Email Attachment source by sender domain or "Subject contains".
2. Decide the threshold on paper first. Three tiers, one approver and one delegate each. A workflow encodes a policy, it does not invent one.
3. Describe it in one sentence, using the first example with your folder path and approver.
4. Name only four fields in Read Details from File. Every extra field is another thing to check.
5. Run it on one vendor for two weeks, watching the activity feed and replaying any run that looks wrong.
6. Widen the scope, then connect the expired exit so a lapsed approval reaches a human.

If you do this for clients rather than in house, how accounting firms automate client document collection covers intake, and the accounting solutions page has the rest.

Frequently Asked Questions

What is an invoice approval workflow?

An invoice approval workflow is the defined path an invoice takes between arriving and being paid: who must say yes at each spending level, how long they have to answer, and what happens when they do not. A good one records the decision against the document rather than in an email thread, so the approval can be produced later.

Can this replace our AP automation software?

Not if you use that software for matching, ledger posting, or payment, because The Drive AI does none of those. It replaces the document half: pulling the invoice out of the mailbox, reading vendor, invoice number, total, and due date, routing it for approval above your threshold, and filing it under the vendor.

How does it handle a vendor it has never seen?

It reads the document rather than matching a saved layout, so a new vendor needs no setup. That is the difference from template based capture, which wants a template per layout. It is also why an approval step matters early: reading is good but not certain, and a check before a payment is cheap. See invoice processing without templates.

What happens when the same invoice arrives twice?

Two guards. The source has a Skip duplicate files setting for an identical attachment sent again. The Move step has an "If the same file is already there" setting, and "Set it aside for review" puts the second copy in a Possible Duplicates folder instead of overwriting anything. A person then decides.

Can the approver change depending on the amount?

Yes. Branch on the total, then put a separate Ask a Person to Approve on each branch with a different approver named under "Who decides?". You can also choose Admins, so any owner or admin can decide, or Everyone. Each node carries its own wait of 24 hours, 3 days, or 1 week.

Start with one vendor

Pick the vendor who sends the most invoices, scope a workflow to their email domain, and let it run for two weeks. When filing stops being something anyone thinks about, widen it and add the threshold. See the step list on Workflows, read the email side in organising email invoices automatically, or create an account and describe your first one in a sentence.