Manual AP is slowing you down. Here is what we are doing about it

A finance director I respect told me last month that her AP team is the slowest team in her business and she does not know how to fix it. She has four people. They process about eight hundred invoices a month. The lag from supplier-invoice-received to payment-cleared is twenty seven days. Industry median for her size is closer to fourteen.

The reason she does not know how to fix it is that no single step looks slow. The invoice arrives. Someone opens the inbox. Someone routes it to a buyer for verification. The buyer is on a different floor and has other work. The buyer sends it back. AP enters it. Someone approves it. Someone schedules it. The bank window opens on Friday.

Every step is a few hours of someone's time. Every handoff is a day. Add them up and you get twenty seven days from the invoice that landed in the inbox on the first of the month.

Where we are pulling the slack out

Five places. I am going to be specific because most posts about AP automation are not.

Inbox intake. The invoice email arrives at a generic supplier-invoices address. Calabash reads the attachment, extracts the supplier BP reference, the invoice number, the line items, the totals, and the payment terms. If the supplier is known and the data is internally consistent, the invoice is created in the system at the moment of receipt. If it is not, the inbox team gets a queue with the parsed data side by side with the original document. Either way, the buyer never sees an email.

PO match. Where a PO exists, the match runs at the point the invoice is created, not three days later when an AP clerk gets to it. Mismatches surface immediately to the buyer who raised the PO, with the specific line that disagrees flagged. The buyer is not doing free-form investigation. They are confirming or rejecting a small specific thing.

Approval routing. Approvals follow the buyer-side workflow rule on the PO, not a separately maintained AP rule that drifts. The same workflow that approved the spend approves the payment, with the same approvers, same thresholds, same delegation tree. We do not maintain a second rules engine for AP. We use the one the procurement side already has.

Bank account hygiene. The supplier business partner has bank accounts that have been verified by treasury, separately from the bank accounts the supplier supplied during KYC. When a payment goes out, the treasury-vetted account is used. Always. If there is no treasury-vetted account, the payment cannot schedule, and the supplier-onboarding workflow is alerted instead.

Payment scheduling. The treasurer's cash forecast knows which invoices are due, which have early-payment-discount terms worth taking, which have contractual penalties for late, and which are flexible. The Friday batch becomes a calculated optimisation, not a scheduling habit.

The one place we are not

Decisions. We are not trying to remove the buyer from the loop on contested invoices. We are not trying to remove the treasurer from the loop on payment timing. We are not trying to remove the AP lead from the loop on supplier onboarding. The humans in this workflow are not the bottleneck. The handoffs between them are.

Automation is for the handoffs. Decisions stay with the people who own the consequences.

What this looks like in numbers

The finance director's twenty seven day lag has two big chunks. About twelve days of it is the buyer-verification loop. About eight days is the AP-entry-and-approval loop. The rest is the bank window and small overhead.

Our model targets pulls the buyer-verification loop to under two days because the buyer is reviewing parsed structured data against a PO they already approved, not reading an email and chasing a PDF. It pulls the AP-entry-and-approval loop to under one day because the entry is automatic and the approval follows the rule the spend already cleared. The bank window does not move. The total comes in around seven to nine days.

Those are model numbers. We will know what the real numbers are when we have run real customer data for a few months. The first finance director who wants to be the one we learn with is in for an interesting next twelve weeks. Sign up for Calabash Business at calabash.app/b2b.