Trade customers email purchase orders as PDFs, and someone retypes each one into Sales Order Processing.
PDF, JPG, PNG, BMP, HEIC, TIFF
Submit your purchase orders
Drop documents here, or choose a file
Up to 50 files per batch
Uploading...
Trade customers email purchase orders as PDFs, and someone retypes each one into Sales Order Processing. Upload one here and get the customer PO number, dates and every line with item, quantity and price as rows you can load through eConnect, SmartConnect or Integration Manager.
Dynamics GP takes sales documents through Sales Order Processing entry or an integration. Customers send PDFs, so the rows have to exist before any load can run.
Integration tools read a CSV, Excel file or database source. A customer PO is a document, so every line is copied across by hand first.
In the eConnect sales document nodes, the customer number and the item number are required elements. A buyer prints their own part number, so it has to be mapped to your item number first.
SOPTYPE separates quotes, orders, invoices and returns. A load that uses the wrong value creates the wrong document.
Microsoft has announced that Dynamics GP support ends on December 31, 2029. Order desks still on GP want less manual keying now, not a new process built around a system they will leave.
Upload the purchase order your customer sent. The AI reads the header and every line on every page and returns one clean row per line item for your GP mapping.
A one page reorder and a six page order come back in the same column layout, so one mapping serves every buyer.
The item number the customer printed and the description land in separate columns, so one lookup maps them to your GP item numbers.
The customer PO number sits beside every line, which is what ties detail rows to one document in a load.
CSV and Excel suit Integration Manager and SmartConnect. JSON suits a script that builds eConnect documents.
Dynamics GP is the Microsoft accounting and distribution system many US wholesalers and manufacturers still run. Orders from a trade customer usually arrive as a PDF purchase order by email. Someone opens the attachment, picks the customer in Sales Transaction Entry, adds each item, types quantities and prices, and checks them against the document. For a 40 line order that is slow and easy to get wrong.
The archived eConnect reference describes two nodes for a sales document. The header node, taSopHdrIvcInsert, marks six elements as required: SOPTYPE, DOCID, SOPNUMBE, DOCDATE, CUSTNMBR and BACHNUMB. SOPTYPE uses 1 for quote, 2 for order, 3 for invoice, 4 for return, 5 for back order and 6 for fulfillment order. CUSTNMBR holds up to 15 characters and the customer PO number has its own optional field, CSTPONBR, up to 20 characters. The line node, taSopLineIvcInsert, requires SOPTYPE, SOPNUMBE, CUSTNMBR, DOCDATE, ITEMNMBR (up to 30 characters) and QUANTITY.
The archived pages list those elements but do not describe how a customer or item that does not exist is handled, and Microsoft publishes no field list for Integration Manager sales order maps. Test with one document per customer before a batch. The customer PO number goes in CSTPONBR, your own sales order number goes in SOPNUMBE, and the rows we return carry the first on every line so you can map it.
To be plain about the boundary: PurchaseOrders reads the customer purchase order and returns Excel, CSV or JSON. It is not a Dynamics GP connector, it does not call eConnect, and it does not create or post documents in GP. We remove the typing that happens before the load, and nothing else. The purchasing side of GP is covered in purchase order to Dynamics GP.
What comes off the customer document and how it meets the eConnect sales document nodes, based on the archived Microsoft eConnect reference.
| From the customer PO | In Dynamics GP | Note |
|---|---|---|
| Customer company | CUSTNMBR (required) | Up to 15 characters, mapped from your customer list |
| Customer PO number | CSTPONBR (optional) | Up to 20 characters, repeat on every line of the order |
| Buyer item number mapped to your item | ITEMNMBR (required) | Up to 30 characters |
| Quantity | QUANTITY (required) | Meaning depends on SOPTYPE |
| Order date | DOCDATE (required) | One date per document |
| Unit price | UNITPRCE (optional) | Left at default pricing if not passed |
Four steps from the customer attachment to a new order document in Dynamics GP.
Drop in the PDF, the scan or the email attachment. Up to 50 files per bulk upload, with no per-customer setup.
Tip: Multi-page orders work the same way.
Check the header and every line on screen, including the buyer item number, quantity and price.
Tip: Sort by item number to spot codes missing from your cross-reference.
Add your customer number and item numbers, save as CSV and keep the column names the same every time.
Tip: Fix the SOPTYPE value for the document you want to create.
Load the file with the tool you already use for GP. Open the new document and compare the total with the customer PO.
Tip: Start with one order per customer the first week.
Not directly. GP loads sales documents through eConnect or tools built on it, which read structured data. PurchaseOrders reads the PDF and returns the rows as CSV, Excel or JSON, so your integration loads them instead of someone typing each line.
The header node requires SOPTYPE, DOCID, SOPNUMBE, DOCDATE, CUSTNMBR and BACHNUMB. The line node requires SOPTYPE, SOPNUMBE, CUSTNMBR, DOCDATE, ITEMNMBR and QUANTITY. This comes from the archived Microsoft eConnect reference.
SOPTYPE is the document type. Microsoft lists 1 for quote, 2 for order, 3 for invoice, 4 for return, 5 for back order and 6 for fulfillment order. Customer purchase orders normally become orders, so SOPTYPE 2.
The eConnect header has an optional CSTPONBR element, up to 20 characters, for the customer PO number. Your own sales order number goes in SOPNUMBE, which allows 21 characters.
Microsoft states it will end Dynamics GP support on December 31, 2029 for enhancements, regulatory updates and technical support, with security updates available until April 30, 2031. Many order desks run GP for years yet, so cutting manual entry still pays back.
Yes. It reads whatever the buyer printed and puts their item number and description in separate columns on every line. You map those to your item numbers once with a cross-reference sheet, then the same customer orders map in seconds.
No. PurchaseOrders reads the customer purchase order and returns Excel, CSV or JSON. It does not connect to GP or create documents. You load the rows with eConnect, SmartConnect, Integration Manager or your own script.
The purchasing side of Dynamics GP.
The same workflow on Dynamics 365.
The same workflow on Business Central.
The full order entry workflow.
OCR for customer orders.
Any PO to a clean CSV.
Choose your plan