Dynamics 365 Business Central imports purchase invoices from a structured file through a configuration package, not from PDFs. Upload your PDF or image invoices here and get a clean CSV with vendor number, invoice date, due date, document number, item lines, quantities, and amounts, ready to load into the Purchase Header and Purchase Line tables.
Last updated June 2026
Upload your invoices
Drop files here or click to upload
Up to 50 files
Uploading...
Business Central can load purchase invoices through configuration packages and the Edit in Excel feature, but only from rows that match its table structure. Real invoices arrive as PDFs and scans, so the work that eats your time is turning those documents into mapped header and line rows with the right vendor numbers. That preparation step is where AP teams stall.
The configuration package import accepts structured CSV or Excel records, not PDF or image files. Every supplier invoice has to be converted into rows before Business Central will accept it.
Each purchase invoice has to reference an existing vendor by Vendor No. A plain vendor name will not resolve, so the data has to be mapped to the card, not just typed.
Invoice-level data goes to the Purchase Header table (38) and line detail to the Purchase Line table (39), linked by document number. Building that two-table structure by hand is fiddly and easy to break.
Each line carries its own type, item or G/L account number, quantity, direct unit cost, and amount. Miss a column or use the wrong account and the line posts wrong or the package import fails.
Retyping amounts, dates, and account codes from a PDF invites transposed figures, which become duplicate payments and painful reconciliations later.
At month-end, hand-preparing header and line rows from a stack of PDFs becomes the bottleneck in your close, especially across multiple vendors and dimensions.
Business Central 2026 Wave 1 added a Create Purchase Invoice from PDF action and a Payables Agent that reads invoices with Azure Document Intelligence, but the agent runs on consumption-based Copilot Credits (about 5 credits, roughly $0.05, per invoice line). For a one-off bulk load or a historical backfill, paying per line is not the cheapest route.
InvoiceXLSX reads your PDF and image invoices with AI and exports the fields Business Central needs as clean rows. You drop the values into your configuration package columns, add the vendor number, and apply the package. No retyping, no rebuilding the layout per vendor.
Upload native PDFs, scanned bills, or phone photos. The AI extracts vendor, invoice number, dates, line items, tax, and totals from any layout.
Output arrives as structured columns that line up with the Purchase Header and Purchase Line fields, so values drop straight into your configuration package or Edit in Excel sheet.
Each item or G/L line becomes its own row with description, quantity, and unit cost, exactly the structure the Purchase Line table needs for multi-line invoices.
Process many invoices at once and export a single spreadsheet, then apply the package once instead of keying each invoice into a journal.
Download clean .csv or .xlsx that loads into a configuration package, with the document number carried across each invoice and its lines.
Invoices are processed over encrypted connections and deleted after extraction. Your supplier data is never sold or used to train public models.
From a folder of PDF invoices to posted purchase invoices in Dynamics 365 Business Central.
Upload your PDF or image invoices to InvoiceXLSX. The AI reads each one and returns vendor, invoice number, dates, line items, tax, and totals as rows, with the document number repeated across each invoice and its lines.
Tip: Batch the whole stack in one pass, then review the values against the originals.
Match each invoice to its Business Central vendor by Vendor No., since the system will not resolve a vendor by name alone. Paste the header values into the Purchase Header columns and the line values into the Purchase Line columns of your configuration package or Edit in Excel sheet.
Tip: Keep a simple vendor-name to Vendor No. lookup so this mapping takes seconds.
In Business Central, search for Configuration Packages, open or create a package that includes tables 38 and 39, import your file, then choose Apply Package. Review any errors flagged on the package lines, fix them, and the purchase invoices appear ready to review and post.
Tip: Start the package from the default config package so common fields are already mapped.
US businesses and finance teams on Dynamics 365 Business Central that receive invoices as PDFs rather than clean structured files.
Move a month of purchase invoices into Business Central in one package instead of keying each one.
Keep the close on schedule by removing manual data entry from the purchase invoice workflow.
Backfill historical invoices for a new client during a Dynamics 365 implementation and go-live.
Handle large supplier-invoice volumes without adding headcount to AP.
Business Central separates the import by transaction type. Bills you receive from suppliers go in as purchase invoices and post to accounts payable, while invoices you raise for customers go in as sales invoices and post to accounts receivable. Both load through configuration packages under the Purchase Header and Purchase Line tables (or the sales equivalents), so pick the right tables before you map columns. For each record, the vendor is matched by Vendor No. rather than a name, which is why mapping the vendor number is the step that makes or breaks the import.
The part the configuration package cannot do is read the invoice document itself. That is what InvoiceXLSX handles: it converts each PDF or photo into the structured rows the package expects, including a line per item or G/L account and a single document number carried across those lines. That per-line breakdown comes from invoice line item extraction, which puts every G/L line on its own row for the Purchase Line table. Once your data sits in that shape, you import the file, apply the package, and review before posting. For US businesses on Dynamics 365 that means a faster month-end, fewer keying errors, and clean books without paying someone to retype invoices all day. For the broader pattern across systems, see our guide to importing invoices into an ERP.
Dynamics 365 Business Central 2026 Wave 1 (BC28.1) added native ways to read a PDF, so you now have a few real options. Here is how they compare for a US AP team.
| Method | Reads the PDF? | Best for | Cost |
|---|---|---|---|
| Manual key into a configuration package | No, you transcribe | A handful of invoices a month | Free, but slow and error-prone |
| Create Purchase Invoice from PDF (2026 Wave 1) | Yes, one PDF at a time into a draft | Entering a single invoice as you receive it | Included, but one document at a time |
| Payables Agent (Azure Document Intelligence) | Yes, from a monitored mailbox | Hands-off day-to-day capture inside Business Central | Consumption Copilot Credits, about $0.05 per invoice line |
| InvoiceXLSX to CSV, then apply package | Yes, any layout to package rows | Bulk loads and historical backfills, no per-line metering | Free tier to test, volume-based after |
For a single invoice as it lands, the native Create Purchase Invoice from PDF action is convenient. For continuous emailed bills, the Payables Agent automates capture but meters per line. When you need to load a large batch at once or backfill historical invoices during an implementation, converting the PDFs to package-ready rows and applying the package in one pass is the faster, lower-cost path.
Yes. Dynamics 365 Business Central imports purchase and sales invoices through configuration packages, which read structured CSV or Excel rows mapped to the Purchase Header and Purchase Line tables. It does not read PDFs directly, so you first convert your PDF or image invoices into that row format, then import the file and apply the package.
Search for Configuration Packages, open or create a package that includes the Purchase Header (38) and Purchase Line (39) tables, import a CSV or Excel file with your invoice data mapped to those fields, then choose Apply Package. Fix any flagged errors, and the purchase invoices appear ready to review and post.
Not through the configuration package. The package import accepts structured CSV or Excel rows, not PDF or image files. To import PDF invoices, convert them to mapped rows first. InvoiceXLSX extracts the vendor, dates, line items, and totals from each PDF so you can load them into the package.
Use a configuration package that includes the Purchase Header and Purchase Line tables. Put invoice-level data in the header rows and one item or G/L line per row in the line rows, linked by document number, and reference each vendor by Vendor No. Import the file and apply the package to create the purchase invoices.
Yes, through configuration packages and the Edit in Excel feature, which read structured Excel or CSV rows mapped to the underlying tables. It does not read a PDF invoice as Excel, so convert PDF invoices to structured rows first, then load that file into the package.
Business Central resolves the vendor by Vendor No., not by the name printed on the invoice. Add the correct Vendor No. to each header row before importing. Keeping a simple lookup of vendor name to Vendor No. makes mapping your extracted invoice data fast and reliable.
At minimum you need the Purchase Header table (38) for invoice-level data such as vendor number, invoice date, due date, and document number, plus the Purchase Line table (39) for line detail such as item or account, quantity, unit cost, and amount. The default configuration package already covers both.
Common causes are a vendor number that does not exist, header and line rows that are not linked by the same document number, a date in the wrong format, or required line columns left blank. Confirm each invoice references a valid Vendor No. and that every line shares its header document number.
Yes, as of the 2026 release wave 1 (BC28.1). Business Central added a Create Purchase Invoice from PDF action for one document at a time, plus a Payables Agent that watches a mailbox, imports PDF attachments to the Inbound E-Documents queue, and extracts the data with Azure Document Intelligence. The agent runs on consumption-based Copilot Credits, so it is billed per use rather than included on every plan.
Importing through a configuration package or Edit in Excel is built into Business Central at no extra charge, so loading a CSV of invoice data costs nothing beyond your existing subscription. The native Payables Agent that reads PDFs automatically uses consumption-based Copilot Credits, around 5 credits or roughly $0.05 per invoice line, billed prepaid or pay-as-you-go. Confirm current Copilot Credit pricing with Microsoft, since rates change.
From the same family of tools
