Invoice processing automation

Supplier invoices arrive by email in every layout. We read them, match them to purchase orders, post the clean ones, and send the mismatches to a person with the reason attached.

For: Accounts payable teams re-keying supplier invoices from email and PDF into an ERP.

A fanned stack of invoice documents
Sample data271 of 312 handled without a person

What changes

Today

  1. Invoices land in a shared inbox as PDFs, scans, and the occasional photo.
  2. Someone opens each one, finds the PO, and types vendor, amount, and lines into the ERP.
  3. Mismatches sit in the inbox until month-end, when they become a scramble.

With 189TH

  1. Each invoice is read on arrival: vendor, amount, PO number, due date, and lines.
  2. Clean matches post to the ERP with a log of what was read and where.
  3. Anything that doesn't match a rule goes to a person as an exception with the closest PO already found.

What stays with your people

  • Approving any invoice without a matching PO.
  • Setting the tolerance for amount and quantity differences.
  • Deciding what happens to a vendor that keeps sending bad invoices.

Generative AI here

Reading unstructured PDFs and emails, and matching messy vendor names and references to your master data.

Not here

Posting to the ledger or approving spend. Those follow rules you set, or a person decides.

The first steps

  1. Map the current path of an invoice from inbox to payment, with real examples.

  2. Run the reader on a month of past invoices and compare against what was actually posted.

  3. Turn on posting for the clean matches only; everything else routes to a person.

Common questions

Does this replace our ERP's AP module?
No. It feeds it. The ERP stays the system of record; we remove the typing and the chasing in front of it.
What happens when the reader gets a field wrong?
Low-confidence fields are flagged and routed to a person before anything posts. Corrections are logged and used to tighten the rules.
Which systems can you connect to?
Most systems with an API, a database, or a file export. We confirm the specifics for your ERP in the first conversation.

Other processes we automate

What process is eating your week?

Tell us what runs on email, spreadsheets, and PDFs. A short description is enough; we’ll ask the rest in a first call.

Prefer email? Write to admin@189thsolutions.com.

We use what you send only to reply. Privacy notice.