peekgenticBook a call

Analysis · AI in business

Sage 100 order entry: how to stop retyping customer POs

Customer POs arrive as PDFs and emails, and someone keys them into Sales Order Entry. What Sage 100 already checks, the ways an order can get in without typing, why you should test the checks on imported orders, and what to keep with a person.

By Miguel GutierrezCo-founder, Peekgentic · Dallas
· 8 min read
Preview card: Sage 100 order entry, stop retyping customer POs.
The order still lands in Sales Order Entry. The typing is what goes away.Peekgentic

In brief

You stop retyping by adding a step in front of Sage 100, not by replacing it. Software reads the PO, matches the customer and items against Sage, and shows a person a draft to approve. Then the order goes in through Visual Integrator or the Business Objects Interface. Before you start, turn on Sage's duplicate PO check and load your customers' part numbers as alias items. And don't assume Sage's on-screen warnings will catch problems on an imported order. Test that with your own orders.

  • We found no Sage 100 feature that reads a customer's PDF. The fix is a step in front of it, with a person approving each draft.
  • Sage's duplicate PO check only runs if you tick the files to check. Alias items are the right home for customer part numbers.
  • Sage warns against importing directly into transaction files. Use the data entry files and the normal update.
  • Sage's help describes its PO and credit warnings as on-screen. Test what happens on an import before you trust it.

The job nobody planned for

A customer emails a PDF. Someone on your order desk opens it next to Sales Order Entry and types the customer, the ship-to, the PO number, then each line. If the customer uses their own part numbers, they look those up too. Then the next email comes in.

Sage 100 (the product once called MAS 90 and MAS 200) is good at what happens after the order exists: pricing, credit, shipping, invoicing. We found no feature in its documentation that reads a customer's PDF. Sage's What's New guide for 2026 lists one new AI feature, a help assistant, and nothing that enters orders. So the gap between the email and the order screen stays a person's job unless you fill it.

This guide covers that gap. If you're still deciding between an add-on and a custom build, start with our Sage 100 add-ons vs. custom automation guide. We don't resell Sage or any add-on. We read Sage's own help pages on Nov. 6, 2026 for what follows, and we say where we only have a forum post.

What retyping actually costs

The best public benchmark we've found is old, and it comes with a caveat. In 2016, the research group APQC published Cutting the Costs of Sales Order Processing, sponsored by Esker, a company that sells order automation. It compared the total cost of managing sales orders across 608 organizations.

Total cost to manage sales orders, per order

APQC benchmarking data, 608 organizations, 2016. Covers the whole "manage sales orders" process, not typing alone.

  1. Top performers$5.11
  2. Median$24.21
  3. Bottom performers$40.87

Source: APQC, Cutting the Costs of Sales Order Processing, 2016 (sponsored by Esker).

Treat those dollars as a rough guide, since they're ten years old and the sponsor has a stake. The more useful point is where APQC says the cost comes from: labor, plus the time lost when part of an order goes missing, when an entry error is made, or when a change comes in. Your own number is easy to get. Time ten orders, count your orders per week, and multiply. Our guide to measuring office automation shows how.

What Sage 100 already does for you

Before you buy or build anything, check that these are on. Each one makes a later automation safer, and most of them help your team today.

Built-in Sage 100 settings that matter for order entry

SettingWhat it doesWhere it's set
Duplicate customer PO checkShows a message if the PO number is already on another order or invoiceSales Order Options. Only runs if you tick which files to check
Alias itemsLets you link many customer or vendor part numbers to one item codeAlias Item Maintenance
Credit limit checkingWatches the credit limit, aging, both, or neitherAccounts Receivable Options
Hold status and reason codesRecords why an order is being heldSales Order Entry
Purchase ControlLimits which items a customer or ship-to state can buySales Order Options
  • The duplicate PO check is opt-in. Sage's Sales Order Options page says you pick which entry and history files to search. If none are ticked, nothing is checked. A PO entered twice can ship twice, and this check costs nothing to turn on.
  • Alias items are your part number map. Sage's alias page says one inventory item can have many aliases, and they can be added on the fly in Sales Order Entry. Type an alias in the item field and Sage finds the real item. Any tool reading POs can use the same table, so the years of cross-references in your team's heads and spreadsheets should go here first.
  • Credit checks show up on screen. Sales Order Entry opens the Customer Credit History window when a customer is on credit hold or over their limit. The method is set in Accounts Receivable Options. Orders a person places on hold after that check get a Hold status, and you can add a reason code.

Five ways an order can get into Sage 100

The doors into Sales Order Entry

DoorGood forWatch for
EDI add-onBig customers who require EDIDoesn't help with the customers who email PDFs
Visual Integrator (VI)Clean, structured files such as CSVSomething has to make the clean file. Mapping takes care
Business Objects Interface (BOI)A program that creates orders directlyNeeds a developer. Sage won't debug outside code
eBusiness Web ServicesWeb apps and ecommerceOlder SOAP style, and needs an IIS administrator
TypingRare, odd or very small ordersYour current cost, and your current error rate

EDI. SPS Commerce and TrueCommerce both connect EDI to Sage 100, and TrueCommerce describes turning inbound 850 purchase orders into sales orders. If a customer offers EDI and has the volume, take it. It's the cleanest input you'll ever get.

Visual Integrator. VI imports files, so it fits at the end of the chain, after something else has read the PO. Two warnings. Sage's transaction data page says that importing directly into transaction files can cause out-of-balance conditions and damage your accounting data, so import to data entry files such as the sales order entry files, then run the normal update. It also warns that importing the same transactions twice can throw you out of balance. Second, the setup has traps. One user on Sage's Community Hub found each CSV row was creating its own sales order, and worked through it with other users until the job was set up differently. That's a forum post, not Sage's documentation, but it's the kind of thing to expect.

BOI. Sage's BOI FAQ says it comes with your activation and lets developers reach Sage programs through COM. It also says Sage can't troubleshoot or debug programs its own developers didn't write. So you need someone who owns that code and will test it on each new version.

Web services. Sage's eBusiness Web Services guide covers read, create, update and delete for sales orders, customers and customer contacts over SOAP. Sage says the manual is written for experienced IIS administrators. It's worth a look if you already run it.

A warning on a screen does nothing for a batch job with nobody looking at it.

The check most people forget to test

Here's the part that catches people. Sage's help describes the duplicate PO message and the credit window as things that happen in Sales Order Entry, when a person is at the screen. We did not find a Sage page that says which of these checks fire during a VI import or a BOI write, or what happens when one does.

So don't assume, in either direction. Before you trust any import, try it in a test company with orders built to fail: a PO number you've already used, a customer on credit hold, a customer over their limit, a discontinued item, and an item the customer isn't allowed to buy. Write down what Sage did with each one. Whatever it doesn't catch, your tool has to catch before the order is written, and has to show the person approving it.

What a good setup does

The tool matters less than the steps. Whether you buy or build, the whole chain should do this:

  1. Catch the order. Watch the shared inbox or inboxes where POs land, including the ones sent to a salesperson.
  2. Read every format. PDFs, scans, spreadsheets and orders typed in the body of an email. If it only handles your top three customers, your team still types the rest.
  3. Match to Sage. Customer and ship-to first. Then items: the exact item code, then the alias table, then flag anything left over. Never guess a part number.
  4. Compare. Does the price match your price level or the quote? Is the date possible? Is this PO number already in Sage? Is this customer on hold?
  5. Show a person. The PO and the draft order side by side, with the odd parts flagged. They approve or fix it in seconds.
  6. Write it properly. Through BOI or a VI import into the data entry files, never straight into the database. Users on the Community Hub say the bundled ODBC driver is read-only, which makes it useful for lookups and nothing else. That's a forum answer, not official documentation.
  7. Keep the trail. Save the original PO with the order, and record who approved it.
  8. Feed the map. When a person confirms a new customer part number, it should become an alias in Sage, so it's never a question again. A person makes that call, not the software.

That's the pattern we used for a food-equipment manufacturer that supplies national grocery chains: software reads each order and fills it in, and their team approves it, in the system they already run. See how order processing works.

What stays with a person

Even a good setup leaves real decisions on the desk. A customer asks for something you've stopped carrying and you want to offer a substitute. A big order comes in from an account that's past due. A price on the PO doesn't match and it might be an old quote or might be a negotiated deal. Someone writes "same as last time, but rush it" in the email.

Those aren't typing. They take judgment and they affect the relationship, and they're what you want your team spending time on. Revised POs are another one. They need their own handling, because the risk is a second order instead of a changed one. We cover that in automating revised POs and change orders.

When not to automate

To be fair, not every desk needs this. If you get 20 orders a week from five customers, a template and a careful person may be the cheapest answer. If one customer sends most of your volume, ask them about EDI or a portal first. If your emailed orders are clean spreadsheets, a VI job and a little training may do the whole thing. And if your item master is a mess, with duplicate items and price levels nobody trusts, fix that first. Automation checks orders against your Sage data, so it's only as good as that data.

Plan for upgrades too. Sage's 2026 upgrade checklist tells you to talk to your partner or developer first if you have custom modules or modifications, and Sage 100 2026 is 64-bit only. A tool that sits outside Sage has less to reinstall, but it still has to be tested on each new version. Ask whoever builds it who does that testing.

What to do this week

  1. Open Sales Order Options and see whether any duplicate PO files are ticked.
  2. Ask your desk where customer part numbers really live. Load the top customers into alias items.
  3. Pull 20 real POs from the last month, including the worst ones. That's your test set for any tool or vendor.
  4. Time ten orders, start to finish. Write the number down before anyone changes anything.
  5. Set up a test company and try the failing orders above with a VI job.

Common questions

Can Sage 100 read a PDF purchase order by itself?

Not that we can find. Sage's What's New guide for 2026 lists one new AI feature, a help assistant. Visual Integrator imports structured files such as CSV, so something else has to read the PDF first.

What's the best way to get orders into Sage 100 automatically?

It depends on the order. Use EDI for customers who offer it. For emailed PDFs, have software read them and a person approve a draft, then write the order through the Business Objects Interface or a Visual Integrator import to the data entry files.

Can Visual Integrator import sales orders?

Yes. Sage lists the sales order entry files among the data entry files you can import to. Sage warns against importing directly into transaction files, and warns that importing the same transactions twice can cause out-of-balance conditions.

How do I stop duplicate customer POs in Sage 100?

In Sales Order Options, select the files to check for duplicate customer PO numbers. Sage then shows a message in Sales Order Entry and Invoice Data Entry when the number is already in use. Test how it behaves on imported orders.

How do I handle customer part numbers in Sage 100?

Use alias items. Alias Item Maintenance lets you link many customer, vendor or general part numbers to one inventory item, and they can be added on the fly in Sales Order Entry.

Do credit holds still work on imported orders?

We didn't find a Sage page that says. Its help describes the credit window as part of Sales Order Entry. Test it in a test company with a customer on hold, and have your tool flag credit status before a person approves.

Do we need to replace Sage 100 to automate order entry?

No. The reading and checking happen in front of Sage, and orders still land in Sales Order Entry where your team already works. Replacing an ERP is a different and much bigger decision.

Sources

  1. Sage, Sales Order Options fields, Sage 100 2026 help, checked Nov. 6, 2026
  2. Sage, Sales Order Entry fields, Sage 100 2026 help, checked Nov. 6, 2026
  3. Sage, Alias Item Numbers, Sage 100 2026 help, checked Nov. 6, 2026
  4. Sage, Accounts Receivable Options fields, Sage 100 2026 help, checked Nov. 6, 2026
  5. Sage, Importing Transaction Data, Sage 100 2026 help, checked Nov. 6, 2026
  6. Sage, Business Objects Interface FAQs, Sage 100 2026 help, checked Nov. 6, 2026
  7. Sage, Introduction to eBusiness Web Services, published April 10, 2025
  8. Sage, What's New in Sage 100 2026
  9. Sage, Sage 100 2026 upgrade checklist
  10. Sage Community Hub, VI Import Multiple Lines for a Single Sales Order (user forum)
  11. Sage Community Hub, 64-bit ODBC read/write driver for Sage 100 2024 (user forum)
  12. SPS Commerce, Sage 100 integration
  13. TrueCommerce, Sage 100 integration overview
  14. APQC, Cutting the Costs of Sales Order Processing, 2016 (sponsored by Esker)

More from Peekgentic

Published November 6, 2026 · Written by Miguel Gutierrez, Co-Founder, Peekgentic (Dallas, TX). Every statistic links its source.