PurchaseOrders turns a supplier PO into Business Central-ready data. Upload a PDF, scan, or photo and the AI pulls the PO number, vendor, line items, and totals into a clean CSV or Excel file. Dynamics 365 Business Central imports that data through a configuration package, so once the columns are mapped you load it straight in. Try it on a real PO below.
Submit your purchase orders
Drop documents here, or click to file
Up to 50 files per batch
Uploading...
Dynamics 365 Business Central can import purchase orders through a configuration package or its API, but neither reads a PDF. Suppliers send PDFs and scans, so someone has to turn each order into a mapped Excel or CSV file before Business Central will take it.
Configuration packages import from Excel or CSV, and the API takes JSON, but none of them ingest a supplier PDF. The order has to be transcribed into structured columns first, which today usually means typing it by hand.
Business Central will not post a purchase order line to a vendor or item number it does not recognize. Every imported PO has to reference records that already exist in your company, so the extracted vendor and item data has to be clean.
A RapidStart configuration package expects the fields in the right places with the right formats. A stray header, a date in the wrong format, or a blank required field stops the import, so the file has to be built carefully.
Every PO carries a table of item numbers, quantities, and unit costs. Typing that into a Business Central import sheet line by line, for every supplier order, is slow and where most entry mistakes start.
PurchaseOrders reads the supplier PO and gives you clean, column-mapped data that drops into a Business Central configuration package or feeds the API through Power Automate. You stay in control of the final load inside Dynamics 365.
Export a clean CSV of vendor, dates, and line items, then map it into a RapidStart configuration package for the Purchase Header and Purchase Line tables. No more typing POs into the sheet by hand.
The AI pulls every item number, description, quantity, unit cost, and total, so the Purchase Line rows your import needs are already filled in instead of being keyed one line at a time.
No templates and no setup. The AI handles PDFs, scans, and photos from any vendor and captures the PO number, buy-from and ship-to, order and expected receipt dates, and totals.
Developers can take JSON or use the API to create purchase orders through the Business Central REST API, wired up with a Power Automate flow so extracted POs post automatically to an existing vendor.
Run more than one system? The same extraction feeds a purchase order to QuickBooks converter, a purchase order to NetSuite import, a Sage import, and a Xero import, so mixed-system teams use one tool for every target. If you just need the raw file, the PO PDF to Excel converter and CSV export produce the spreadsheet directly, and high-volume teams clear a backlog with bulk purchase order processing. For the general approach, see how to import purchase orders to your ERP, and for line-level accuracy, purchase order line item extraction.
An honest look at the two realistic ways to load a supplier purchase order into Dynamics 365 Business Central today.
| PurchaseOrders + Business Central | Manual entry into Business Central | |
|---|---|---|
| Reading the supplier PO | AI extracts every field | Read and type by hand |
| Line-item table | Captured automatically | Keyed row by row |
| Building the import file | Clean CSV or JSON, ready to map | Typed into the package |
| Bulk or list of POs | Up to 100 per batch | One at a time |
| Multi-page POs | Handled in one pass | More pages, more typing |
| Accuracy | About 98 to 99 percent | 1 to 4 percent entry error rate |
| Setup | None, no templates | None, but fully manual |
| Output formats | Excel, CSV, JSON, API | Not applicable |
Dynamics 365 Business Central imports purchase orders through a RapidStart configuration package (Excel or CSV) or the REST API, and it will not read a PDF or post to a vendor or item that does not already exist. PurchaseOrders extracts the supplier PO so your import file is ready. Always confirm current import steps and field names in your Business Central environment.
No templates and no manual line-item entry. Upload a real PO and get Business Central-ready data in seconds.
Drag in a PDF, scan, or photo of the purchase order from any vendor. There is no template or setup to configure first.
Tip: Multi-page POs and several suppliers in one batch are fine.
The AI reads the PO number, vendor, buy-from and ship-to, order and expected receipt dates, line items, item numbers, quantities, unit costs, and totals.
Download the CSV or Excel file and map it into a configuration package, or use JSON and the API through Power Automate, then review and post inside Dynamics 365.
Yes. Business Central imports purchase orders through a RapidStart configuration package from Excel or CSV, or through its REST API. Neither reads a PDF, so the slow part is turning a supplier PDF into a mapped file, which is where AI extraction with a tool like PurchaseOrders removes the manual typing.
Export your purchase order data to an Excel or CSV file that matches a configuration package for the Purchase Header and Purchase Line tables, then run the package import in Business Central. If your POs are still supplier PDFs, extract them to a clean file first so the columns line up.
Yes. The Business Central REST API v2.0 has a purchaseOrders endpoint you can read, create, and update. Creating a purchase order requires a vendor that already exists, so extracted vendor and item data has to be clean. Many teams drive the API from a Power Automate flow.
Yes. A configuration package imports many rows in one file, so you can load a batch of orders at once rather than entering each by hand. To prepare that file quickly, extract a batch of supplier POs to a single clean CSV, then run one package import into Business Central.
Yes. Business Central will not post a purchase order to a vendor or item number it does not recognize, so the vendor and items referenced on the PO must already exist in your company. Extraction gives you the vendor name and item numbers cleanly so you can map them to the right records.
PurchaseOrders is a purchase order extraction tool, not a Business Central add-on. It reads supplier POs and outputs Business Central-ready CSV, Excel, JSON, or API data. You then load that file through a configuration package or the API, so it works alongside Dynamics 365 rather than inside it.
Export PO data to a Business Central-ready CSV.
Map PO data into any ERP.
Process many POs in one batch.
Match-ready PO data for accounts payable.
