Sage 100 AP automation: what to automate first

Why AP is a good place to start

If you run Sage 100 at a 40 to 400 person manufacturer or distributor, your AP clerk probably spends a good part of the day doing the same thing: open the email, open the PDF, find the vendor, type the invoice into Sage, attach the PDF, and move on. The work is steady, the documents come in many layouts, and every invoice can be checked against something you already have: a vendor record, a PO, a receipt.

That makes AP one of the better first targets for automation. This guide walks through how invoices get into Sage 100 today, the ways software can do that part, what to automate first, and what should stay with a person. The Sage steps come from Sage's own 2025 help pages. Check them against your version with your Sage partner.

How AP invoices get into Sage 100 today

There are two main paths, and which one an invoice takes depends on the vendor.

• Non-PO invoices (freight, utilities, services) go through Accounts Payable > Invoice Data Entry. When the batch is ready, someone updates the Accounts Payable Invoice Register, per Sage's help page.
• PO invoices. In Vendor Maintenance, a vendor can be set to "Use P/O Receipt of Invoice Entry." Sage calls this the preferred method so a purchase order isn't left on backorder. Receipt of Invoice Entry records the invoice only. To record the goods and the invoice at the same time, Sage says to use Receipt of Goods Entry.

Either way, the slow part isn't Sage. It's a person reading each PDF and keying it in.

Three ways software can enter invoices in Sage 100

Sage 100 runs on your own server at most companies, and it doesn't offer the kind of modern web API that cloud ERPs do. We didn't find a Sage document describing a native REST API for it, and answers on Sage's community forum point developers to the Business Object Interface instead. That leaves three routes:

Visual Integrator (VI) is Sage's import tool. A Sage community post walks through building VI imports into data entry files and points to Sage's knowledgebase article on importing into AP Invoice Data Entry. Because the data lands in a data entry batch, not straight in the books, a person can still review and update it the normal way.

The Business Object Interface (BOI), Sage says, comes with every Sage 100 activation. It lets outside programs work with Sage 100 through Microsoft's COM technology. Sage is also clear that it can't troubleshoot or debug programs it didn't write, so whoever builds on BOI owns the support.

Screen bots can type into Sage the way a person does. They work until a screen or field changes. We cover the tradeoffs in AI vs. RPA.

What to automate first

Go in this order. Each step is useful by itself, and each one builds on the one before it.

1. Get invoices out of the inbox and into a draft. Software reads each PDF, finds the vendor in Sage, and pulls the invoice number, date, terms, lines and total. It drafts the entry and shows the PDF next to it. This is where most of the clerk's typing time goes.
2. Code the non-PO bills. Freight, utilities and service bills usually go to the same GL accounts every month. Software can suggest the account from the vendor's history, and the clerk confirms it.
3. Check PO invoices against the PO and the receipt. For vendors set to Receipt of Invoice Entry, software can compare the invoice's quantities and prices to the open PO and what was received, and flag anything that doesn't match. We didn't find a Sage page describing automatic matching tolerances, so treat this as a check you build, not a Sage setting.
4. Catch duplicates. The same invoice often arrives twice: once by email, once from the vendor's portal. Matching on vendor, invoice number and amount catches it before it's entered.
5. Answer the "did you get my invoice?" emails. Once invoices are logged as they arrive, status questions can get a fast, accurate answer, and the clerk approves the reply.

Measure it simply: invoices handled per person per day, and the share that needed a fix. If the drafts are right most of the time, the clerk's day shifts from typing to checking.

What to keep with a person

Automation should make AP faster, not easier to rob. Two jobs stay with people.

Approving payments. Software can line up what's due. A person you trust releases the money.

Vendor bank changes. The most common attack on AP isn't a hacker in your ERP. It's an email that looks like it's from a real vendor asking you to pay a new account. The FBI's 2025 Internet Crime Report lists more than $3 billion in reported business email compromise losses in 2025, and says businesses reported over $30 million in losses to such scams involving AI. In the AFP's 2026 Payments Fraud and Control Survey, 76% of organizations said they faced attempted or actual payments fraud in 2025, and, as reported by Nacha, 74% experienced business email compromise, up from 63% the year before.

Business email compromise losses reported to the FBI

FBI Internet Crime Complaint Center, three-year comparison. Reported losses only; many cases go unreported.

1. 2023$2.95 billion
2. 2024$2.77 billion
3. 2025$3.05 billion

Source: FBI IC3, 2025 Internet Crime Report.

The FBI's advice is to confirm through a second channel or two-factor authentication any request to change account information. In practice: call the vendor at a number you already have, not the one in the email. Good AP software makes this easier by flagging any invoice whose remit-to details differ from the vendor record, and never changing them itself.

Let software do the typing. Keep the money and the bank details with people.

Buy an add-on or build around Sage?

Sage's US marketplace lists Sage AP Automation, developed by Quadient Accounts Payable by Beanworks, with Sage 100cloud among the supported products. Other AP tools connect to Sage 100 too. If your invoices are mostly standard and your process fits the product, an off-the-shelf tool is often the faster, cheaper choice. Ask your Sage partner which tools support your exact version.

A custom build makes more sense when the work doesn't fit a standard flow: invoices tied to job costing, vendors whose PDFs vary a lot, approvals that depend on your own rules, or AP that's tangled up with purchasing and receiving. That's also when it helps to have the same system handle purchasing and AP.

What good looks like, in numbers

Benchmarks vary a lot by survey. Ardent Partners' State of ePayables 2025, sponsored by Tradeshift and based on 204 AP and finance leaders, puts the average cost to process an invoice at $12.42, against $2.65 for the best teams. An older APQC benchmark of 1,485 organizations, reported by CFO.com in 2018, put the median at $5.83. Use them as rough markers, not targets. Your own baseline, measured on your own invoices, is the number that matters.

How Peekgentic does it

We build AP automation around the Sage 100 you already run. Software reads invoices from the AP inbox, matches each one to the vendor and PO in Sage, drafts the entry with the PDF beside it, and flags anything that doesn't match. A person approves the batch, and it goes into Sage through the route that fits your setup, usually a Visual Integrator import or the Business Object Interface. Payments and bank changes stay with your people. See how a billing and AP build works, or AP automation in Dallas-Fort Worth.