From AP inbox to payment-ready: an overnight invoice workflow

Why this is the flagship workflow

Invoice processing is concrete. The inputs are already digital. Three-way match, duplicate detection, and vendor master rules are things a CFO can audit. Payment authority already exists in the ERP. That makes AP a better first overnight queue than a workflow that ends in a regulated decision.

The walkthrough is INV-77319 from Helios Packaging: $14,280, PO-44108, two thousand shippers received at Dock 3. The three-way match is clean. The duplicate check is not.

What enters the system

1. 01

   AP inbox

   PDFs and e-invoices landing in the shared Outlook mailbox, plus supplier-portal uploads.

2. 02

   Commercial record

   Coupa POs and goods receipts, NetSuite vendor master, tax codes, and remit instructions.

3. 03

   Payment policy

   Terms, early-pay discounts, duplicate windows, and the treasury limit on a single ACH run.

What happens overnight

1. 01

   Capture

   Each file is split, read, and tied to a vendor candidate. Multi-invoice PDFs do not become one payment.

2. 02

   Vendor match

   Legal name, alias table, and remit account are compared to the vendor master. “Helios Packing” can resolve to VND-1184 without paying a new vendor.

3. 03

   Three-way match

   PO quantity, received quantity, and invoice quantity are compared. Variances above the configured band become exceptions.

4. 04

   Duplicate detection

   Invoice number, amount, date, vendor, and PO are compared to recent postings. Near-matches are held — they are not auto-voided and not auto-paid.

5. 05

   Payment-ready file

   Clean invoices are added to the next ACH preview. Exceptions stay out. Treasury still releases the file.

What AP sees in the morning

Lena Cho has sixty-four invoices ready and eleven exceptions. INV-77319 is at the top because INV-77301 posted last Tuesday for the same amount. The engine also shows a different PO and a new goods receipt. That is the question: new shipment, or a vendor who reissued a number?

A second exception, Apex Facilities, has an invoice that reads Net 15 against a vendor master of Net 45. The engine will not schedule the early payment. Lena either updates the master or keeps the hold.

Clear automation boundaries

How corrections are validated

If Lena marks INV-77319 as a new shipment, the pair (77301, 77319) becomes a labeled example: same vendor and amount, different PO and GR, not a duplicate. If she marks it a duplicate, that example goes the other way.

A hypothesis that treats similar amounts as duplicates fails Northline history — split shipments are common. A PO-aware duplicate boundary beats the previous model on held-out history and ships. The looser rule does not.

What a 30-day pilot measures

Proposed metrics for a single AP entity. Do not treat the targets as promised savings.

Implementation

Systems

AP mailbox, Coupa or equivalent P2P, ERP vendor master and payment file, optional supplier portal.

Data required

A year of invoices, POs, receipts, voids, and duplicate decisions. Alias tables if you already keep them.

Deployment

Hardware on the finance VLAN. Shadow on historical inbox mail, then supervised on live mail, then payment-preview writes.

Who operates it

AP manager owns exceptions. Treasurer owns the payment run. IT owns the mailbox connector. We own the machine.

Security and deployment architecture

Invoices, bank accounts, and vendor masters never leave the building for training. The engine calls Coupa and NetSuite from your IP space. There is no Overnight Engine cloud copy of the AP inbox.

This is the workflow we recommend first because rollback is simple: stop writing the payment preview, keep the hardware, and AP works as it did on Friday.