The best way to import extracted document data into your ERP is to extract it with Lido in the exact format your ERP expects. Lido matches your ERP's column names, date formats, and vendor IDs during extraction, so the file is ready to import without manual reformatting.
In this tutorial, we will walk you through how to extract invoice data with Lido and import it into NetSuite, QuickBooks, SAP, Dynamics 365, or any other ERP. Simply follow the steps below.
Before you start, export a sample import file or template from your ERP. This shows you the exact column names, date format, and vendor ID format your ERP needs.
Most ERPs let you download an import template or export existing transactions. Keep this file open, since you will match it in the next steps.
If you don't have a Lido account yet, you can create one for free here.
Once you're logged in, create a New File.

Select the Extract Data button at the top of the sheet. Then drag and drop your invoices into Lido, or click to browse. You can upload up to 100 files at a time. For bigger backlogs, folder connections make running large document batches easier.


Enter each column name exactly as it appears in your ERP's import file. For a NetSuite vendor bill, that might be External ID, Entity, Tran Date, Tran ID, Account, Amount, and Memo.
Using your ERP's exact column names means you won't need to rename anything before importing.
In the Extra Instructions box, tell Lido how your ERP needs the data formatted. Common instructions include:
Dates: "Format all dates as YYYYMMDD" for SAP, or "Format dates as M/D/YYYY without leading zeros" for NetSuite.
Line items: "Extract each line item as its own row and repeat the invoice number on every row."
Vendor IDs: Click + Context Doc and attach your ERP's vendor list (vendor name and vendor ID). Then add "Match each vendor name to the vendor list and return its vendor ID." This prevents the most common import error, where "Acme Corp" on the invoice doesn't match "Acme Corporation" in your ERP.
Once done, click Process All Files.
Review the extracted data and compare it with your ERP's sample import file. Check that the columns, date format, and vendor IDs line up.
If you want to change the output, such as adding a column, update your setup and process the files again. Lido offers free reprocessing within 24 hours.
Click Export to Excel to download your data. If your ERP needs a CSV file, open the file in Excel and save it as CSV.
Import a small batch of 5 to 10 invoices into your ERP first. Once they post correctly, import the rest of your invoices the same way.
Extracting the data is only half the job. Every ERP has its own import rules, and one small mismatch can make the whole import fail. The three most common problems are:
Date formats: The same date of January 5, 2026 must be written as 1/5/2026 for NetSuite, 20260105 for SAP, and 01/05/2026 for QuickBooks.
Vendor IDs: NetSuite and SAP identify vendors by ID numbers, not names. QuickBooks needs the vendor name to match your vendor list exactly, so "ABC Supply Co." will fail if your list says "ABC Supply Company."
Line item structure: Some ERPs expect one row per invoice, while others expect one row per line item. Getting this wrong can cause errors, duplicate transactions, or amounts posted to the wrong accounts.
Lido solves all three during extraction, using your column names, formatting instructions, and vendor list. That consistency matters when choosing a dedicated extractor or an AI chatbot for invoice data.
Use this quick reference to set up your columns and formatting rules in Step 4 and Step 5.
Where to import: Setup, then Import/Export, then Import CSV Records.
Required columns: External ID, Entity (the vendor's internal ID, not its name), Tran Date, and at least one line with an Account and Amount. Tran ID, Due Date, Department, Class, and Location are optional.
Date format: M/D/YYYY without leading zeros.
Row structure: The first row of each bill holds the header fields. Later rows for the same bill leave the header fields blank and only fill in Account, Amount, and Memo. You can find vendor internal IDs by exporting your vendor list from Lists, then Relationships, then Vendors. For more, see our guide to the best OCR tools for NetSuite.
Where to import: QuickBooks Online has no built-in bulk bill import, so most teams use an importer app like Transaction Pro Importer or SaasAnt.
Required columns: Vendor (an exact match to your vendor list), Bill Date, Due Date, Ref No, Category, and Amount.
Date format: MM/DD/YYYY.
Where to import: File, then Utilities, then Import, then IIF Files.
File format: IIF, a tab-separated text file. Each bill uses a TRNS row for the header, an SPL row for each line item, and an ENDTRNS row to close it.
Date format: MM/DD/YYYY with leading zeros.
Amounts: The TRNS row amount must be negative, and SPL row amounts must be positive, or the bill posts backwards. For more, see our guide on scanning invoices into QuickBooks.
Where to import: Transaction MIRO mass upload or LSMW for flat files. Automated IDoc imports need middleware such as SAP PI/PO or MuleSoft.
Required columns: Company Code, Vendor Account Number, Invoice Date, Posting Date, Reference Document Number, Document Type (usually "RE"), Currency, Header Amount, GL Account, line Amount, and Tax Code. Cost Center may also be required.
Date format: YYYYMMDD with no separators.
Vendor numbers: Exactly 10 digits, padded with leading zeros, so vendor 12345 becomes 0000012345.
Where to import: Workspaces, then Data Management, then Import, using the "Vendor invoices" data entity.
Required columns: Invoice Account, Invoice Number, Invoice Date, Currency Code, and at least one line with a Procurement Category or Item Number, Quantity, Unit Price, and Line Amount.
Date format: YYYY-MM-DD is the safest choice across locales.
Tip: Dynamics 365 lets you save import mapping templates, so you only need to match your column names once.
Sage Intacct: Import bills under Accounts Payable, then Bills, then Import. Required columns are Vendor ID, Bill Date (MM/DD/YYYY), Due Date, Bill Number, GL Account Number, Amount, and Department if your setup uses it.
Acumatica, Epicor, Infor, and others: Export a sample file from your ERP, match your Lido columns to it, and test a small batch before importing in bulk.
For more tools that automate this process, see our guide to data entry automation software. If you're starting with invoices, our guide on extracting invoice data into Excel covers the extraction step in more detail.
Now that you know how to import extracted data into your ERP, you can move invoices from PDF to posted transaction without retyping a single field.
NetSuite accepts CSV files through Setup, then Import/Export, then Import CSV Records. The first row of each bill holds the header fields, and later rows hold the line items with blank header fields. Dates must use M/D/YYYY, and vendors must be listed by their NetSuite internal ID.
QuickBooks Online has no built-in bulk bill import. To create bills from a CSV file, use an importer app like Transaction Pro Importer or SaasAnt. Your file needs the exact vendor name, bill date in MM/DD/YYYY format, reference number, category, and amount.
SAP requires dates in YYYYMMDD format with no separators, so January 5, 2026 becomes 20260105. Any other format, including 2026-01-05, will cause the import to fail.
Export your vendor list from your ERP with vendor names and IDs. In Lido, attach it as a context document and add an instruction to match each vendor name to the list. Lido returns the correct vendor ID for each invoice, even when the names don't match exactly.
The extraction itself stays the same, since Lido reads the same fields from every invoice. Only the column names and formatting instructions change. If you import into more than one ERP, create one Lido file for each ERP with its own columns and instructions.