Acumatica order entry automation: from email and PDF POs

The job you want to stop doing

Here's the routine at a lot of 40 to 400 person manufacturers and distributors on Acumatica. A customer emails a PO as a PDF. Someone opens it, finds the customer, picks the order type, types each line, matches the customer's part numbers to yours, checks the price and unit, enters the ship-to, and saves. Then the next one. On a busy day it's most of a person's job.

Acumatica order entry automation means software does that typing. It reads the PO, finds the customer and items, and drafts the order. A person checks the draft and approves it. This guide covers what Acumatica gives you to build on, using Acumatica's own help pages and product pages as checked on Oct. 21, 2026. Acumatica released 2026 R2 on Oct. 1, 2026. If you're on an older version, check the details with your Acumatica partner.

The Acumatica pieces order entry runs on

You don't need anything exotic. Acumatica already has the parts. Software just has to use them the way your order desk does.

Order types. Acumatica ships predefined sales order types, such as SO for orders that ship, IN for orders that only need an invoice, and BL for blanket orders. You activate the ones you use on the Order Types (SO201000) screen. Automation should pick the same type your people pick. If a customer's POs are releases against a blanket order, that's a rule to write down before you start.

Customer part numbers. This is the most useful piece. Acumatica's help says that once item cross-references are set up, entering a customer's alternate ID on a sales order fills in your inventory ID and the item price. A cross-reference can also carry its own unit of measure, so a customer who orders by the case gets the case unit on the line. Two cautions from the same page. Acumatica does not check that alternate IDs are unique across the system. And typing a new alternate ID on a sales order line creates or replaces that customer's cross-reference for the item. So a wrong match can quietly rewrite your table. Software should flag new or changed part numbers for a person, not save them on its own.

How software creates the order

There are two routes for software to put a customer's order into Acumatica.

1. The contract-based REST API. Acumatica's developer help shows a single PUT request to the SalesOrder entity that creates an order with its lines. The example sets the customer, the order type, the location, the lines, and Hold set to true. That last part matters. Software can save the order on hold, and a person takes it off hold after review. The example uses the 26.200.001 version of the Default endpoint.
2. Import scenarios. Acumatica can import records through scenarios you build on the Import Scenarios (SM206025) screen. You pick the target screen, a data provider that describes the file, and a field mapping. This works when PO data already sits in a spreadsheet or file. It doesn't read a PDF for you.

Your license sets the API ceiling. Acumatica's help says every license limits API sessions, concurrent requests, and requests per minute. Once requests in a minute reach 50% of the limit, new ones get delayed. A request is declined if more than 20 are waiting or one waits more than 10 minutes. An order desk rarely hits that. But software that doesn't sign out can hold a session open and block other apps, so ask any vendor how they handle sign-out.

What about Acumatica's own AI?

Acumatica has added a lot of AI. It's worth knowing what it does before you buy anything else.

• AP document recognition. Acumatica can recognize vendor invoices attached to incoming emails and turn them into AP bills. You point a dedicated mailbox at it, and results show up on the Incoming Documents (AP301100) screen. It uses an outside recognition service, and the number of documents is limited by your license. Acumatica's own page says "complete accuracy cannot be guaranteed." This is for bills you owe, not orders you receive.
• AI Automation agents. On the Agents (ML202000) screen, you can build an agent that reads the current record, updates it and its lines, and looks up data from generic inquiries. Acumatica's AI page gives an example of an agent applying a discount across matching sales order lines. An import scenario can also call an agent for each record it creates. The help page describes file input only for the built-in expense receipt agent.
• AI Studio and 2026 R2. Acumatica says AI Studio was first introduced in early 2025. The 2026 R2 release adds to AI Assistant, AI Automation and anomaly detection. The 2026 R2 press release also adds a connection that lets outside AI tools such as Claude or ChatGPT reach your Acumatica data under your existing permissions.

All of this is useful. What we didn't find on any Acumatica page is a built-in feature that reads a customer's PDF PO from email and creates a sales order with your items, units and prices. The agents work on records already in Acumatica. The recognition service reads vendor invoices. Getting the customer's PO into a draft order is still the gap.

Acumatica reads your vendors' invoices. Your customers' POs still need a route in.

What the Acumatica Marketplace offers

The Acumatica Marketplace lists solutions from Acumatica's technology partners, sorted by category. The categories include OCR, Document Management, EDI and Manual Process Automation. Some listings say they create sales orders from inbound POs. One example: the UnForm listing says it can process PDFs from email and, using the Acumatica REST API, turn inbound purchase orders into Acumatica sales orders. The listing shows it validated on versions 2024 R2 through 2026 R1. We haven't tested it, and it isn't the only option. When you look at any add-on, ask four things. Does it use your cross-references or its own mapping? Does it save on hold for review? How does it handle a PO layout it hasn't seen? Is it validated on your version? Pricing varies, ask.

What to automate, and what to keep with a person

The cross-reference table is where most of the value sits. Your people already carry it in their heads: this customer's "AC-778" is your "BRK-SS-0400," sold by the case. If those links aren't in Acumatica yet, loading them is the first step. It helps your order desk today, with or without automation.

Where the other side has a point

If most of your orders come through EDI or a web store, your PDF problem may be small. Acumatica's 2026 R2 release also lists Amazon, Shopify and BigCommerce enhancements. If you get ten PDF orders a day from five customers in the same format, a Marketplace add-on or a clean import file may be enough, and a custom build may not pay off. Start there if it fits. A custom build makes sense when POs come in many layouts, with messy part numbers, notes buried in the PDF, and rules only your veterans know. Either way, you keep Acumatica. We wrote about that in automating without replacing your ERP.

How Peekgentic does it

We build order entry around the Acumatica you already run. Software reads customer POs from the order inbox, matches each line to your customers, cross-references, units and prices in Acumatica, and drafts the sales order with the PDF beside it. Anything that doesn't match gets flagged instead of guessed. The order is saved on hold through the REST API, and a person on your team approves it. See how an order-processing build works, or our guide to automating order entry.