Import Invoices into Dynamics GP from Excel

Microsoft Dynamics GP will load a whole batch of payables invoices from one spreadsheet, but only after the data carries the right vendor ID, document fields, and balanced GL distributions. The invoices themselves show up as PDFs and scans, so the real work is turning those documents into clean rows. GP itself never reads the PDF. This guide covers the load paths that do work (Integration Manager, SmartConnect, and eConnect), how vendors are matched, and the errors that stop an import, plus the faster way to prepare the file.

Can you import invoices into Dynamics GP?

Yes. Dynamics GP imports payables invoices through Integration Manager, eConnect, or a third-party tool like SmartConnect from eOne, each of which reads structured text, Excel, or ODBC data and maps it to the Payables Transaction. GP does not have a single button that reads a PDF and posts a bill, so you first convert your PDF or image invoices into mapped rows, then load them into a named Payables batch and post.

The load itself is fast once the data is in shape. What slows teams down is preparing that data, which is why the conversion step below matters more than the import click.

How do I import payables invoices into Dynamics GP from Excel?

Put your invoice data in Excel with a column for vendor ID, document type, document number, document date, amount, and the GL accounts for the purchases and accounts payable distributions. Then use Integration Manager with an Excel source, or the free SmartConnect Excel Add-In, to map those columns to the Payables Transaction destination and load the rows into a batch you can review before posting.

The SmartConnect Excel Add-In lets a finance user enter or paste rows into a predefined Excel layout and then hit "send to SmartConnect" straight from the Excel menu, with no developer involved. eOne also ships a free Payables Transaction Excel Template that pulls your live GP accounts, vendors, and currencies into the sheet and validates entries as you go, defaulting distributions at runtime so you do not have to type every account.

What is the best way to import invoices into Dynamics GP?

For most US finance teams, SmartConnect with its Excel Add-In is the most practical path because a non-developer can run a saved map straight from a spreadsheet. Integration Manager is the classic Microsoft tool and works well for scheduled or repeatable loads from a text file or Excel source. eConnect, the underlying API, suits developers building a programmatic feed. All three end at the same destination: rows mapped to the Payables Transaction, loaded into a batch, and posted.

Whichever tool you pick, the bottleneck is the same: getting your PDF invoices into clean, mapped rows in the first place. Solve that once and any of these import paths becomes a quick final step.

Can Dynamics GP import PDF invoices directly?

No. Integration Manager, SmartConnect, and eConnect all read structured text, Excel, or ODBC data, not PDF or image files. To import PDF invoices, you convert them to rows first. An AI extraction tool reads the vendor, invoice number, dates, line items, and totals from each PDF and exports them as a spreadsheet, so the values are ready to map to the Payables Transaction. You can extract invoice data to Excel in one pass instead of retyping each bill into Payables Transaction Entry.

How do I import vendor invoices into Dynamics GP using Integration Manager?

In Integration Manager, create a Payables Transaction integration, point the source at your Excel or text file, and map each source column to the matching GP destination field: vendor ID, document type, document number, document date, purchases amount, and the distribution accounts. Integration Manager has a handy "Default Non-Imported" option that fills any distribution you did not supply with the vendor or company default account, which keeps the entry balanced.

Run the integration into a named batch rather than posting directly. That way you can open the batch, review the edit list, fix any flagged rows, and only then post to the general ledger.

How does SmartConnect import invoices into Dynamics GP?

SmartConnect sits on top of eConnect and lets you build a map from an Excel, CSV, or database source to the Payables Transaction node. With the Excel Add-In, you enter rows in the template, choose the saved map, and send the data to GP without leaving Excel. SmartConnect validates the vendor ID and the GL distributions during the run and reports any row it cannot process, so bad data is caught before it posts.

Because the map is reusable, the same setup handles next month's invoices. The only part that changes each cycle is the source rows, which is exactly the part the conversion step produces for you.

How do I match invoices to the right vendor in Dynamics GP?

Dynamics GP matches each transaction to an existing vendor by Vendor ID, not by the supplier name printed on the invoice. The vendor record has to exist in GP before the load, and the Vendor ID in your file has to match it exactly. Keep a simple lookup that maps each supplier name to its GP Vendor ID, fill that column when you prepare the rows, and the import resolves every transaction to the correct vendor with no manual selection.

The document number also matters: carry one document number across all the lines of a multi-line invoice so GP groups them into a single transaction rather than several. Clean line item extraction keeps each invoice's lines tied to its document number.

Why is my Dynamics GP invoice import failing?

Most failed imports come from a handful of causes: a Vendor ID that does not exist in GP, distributions that do not balance to the document amount, a missing or duplicate document number, a document date in the wrong format, or a posting account that is inactive. Integration Manager and SmartConnect both write the rejected rows to a log, so read the error message, fix the specific field, and re-run only the failed rows into the batch.

The cleanest defense is accurate source data. When the vendor ID, amounts, and dates are extracted correctly and the distributions tie out, the load posts in one pass.

From PDF invoices to a Dynamics GP import file

The step none of these tools does for you is read the invoice. InvoiceXLSX converts PDF and image invoices into a Dynamics GP import file, pulling the vendor, document number, dates, line items, and totals into structured rows. You add the GP Vendor ID and the distribution accounts, line the columns up with your Integration Manager source or SmartConnect map, and load the batch. If your tool wants CSV specifically, the same export gives you an invoice PDF to CSV file ready to map.

Many GP shops are now planning a move to Dynamics 365 Business Central, and the same clean rows give you a head start on that migration. The approach is the same one teams use to import invoices into any ERP: extract first, map once, then load and post. When you reconcile those posted payables against what actually cleared the bank, you can convert a bank statement to Excel the same way and match on amount and date. The result is a faster month-end, fewer keying errors, and clean books without paying anyone to retype invoices all day.