Import Invoices into SAP from Excel or CSV

SAP will take a batch of supplier invoices in a single upload, but only as a spreadsheet that matches its own template, with the supplier, tax, and amount fields filled in exactly the way SAP expects. It will not read a PDF, a scanned image, or a free-form Excel file. So the job has two halves: turn each invoice into clean spreadsheet rows, then run those rows through SAP's import template and post them. This guide walks both halves for SAP S/4HANA, with the app you use, the fields the template needs, how suppliers and tax codes are matched, and the errors that stop an upload cold. If your invoices are still PDFs or photos, drop them into the converter at the top of this page first and you will have an import-ready file in a few minutes.

Can you import invoices into SAP?

Yes. SAP S/4HANA imports supplier invoices in bulk through the Import Supplier Invoices app, so an accounts payable team can post a whole batch at once instead of keying each one in FB60. You download a spreadsheet template from the app, fill in the invoice details, upload the completed file, and post the invoices from inside the app. It reads the template format (Excel), not PDFs or scanned images, so those invoices have to become structured rows first.

That split shapes the whole task. The SAP side is a short download, fill, upload, post sequence once your file matches the template. The real work is preparing accurate rows in the field layout SAP expects, including the supplier number, company code, tax code, and amounts, which is where most failed uploads actually start.

How do I import supplier invoices into SAP from Excel?

Log on to the SAP Fiori launchpad as an Accounts Payable Accountant, open the Import Supplier Invoices app (transaction F3041 in S/4HANA), and choose Download to get the spreadsheet template in your chosen language and format. Enter one invoice per block of rows, fill in the supplier, company code, invoice date, amounts, and tax data, then upload the file and post. The app validates each invoice and flags any that fail before posting.

Keep each file within SAP's per-upload limit (commonly a few hundred to a couple of thousand line entries depending on your release) and split larger batches across files. Because the template ships from your own system, the fields already match your configuration, so the work is filling it accurately rather than guessing at a layout.

Can SAP read PDF invoices?

Not through the standard import. The Import Supplier Invoices app reads its spreadsheet template, not a PDF or a scanned image, so a supplier's PDF bill has to be converted into structured rows before SAP will accept it. SAP does offer separate document and AI services for capture, but the everyday template upload expects data already in columns, not a raw document.

This is the step that eats the most time when teams do it by hand, because every PDF gets retyped field by field into the template. Running the invoices through an extraction tool first gives you the supplier, date, invoice number, line items, tax, and totals as columns, ready to drop into the SAP template. The converter at the top of this page does exactly that, and you can pull invoice line item extraction into the same file so each line carries its own amount and tax.

What is the Import Supplier Invoices app in SAP?

The Import Supplier Invoices app (F3041) is the standard S/4HANA tool for loading many supplier invoices at once from a spreadsheet. You download its template, enter invoice details, upload, review the validation results, and post the valid invoices. It is built for two jobs in particular: migrating historic invoices at go-live, and processing the regular weekly or monthly batches a central AP team would otherwise key one at a time.

One detail trips up new users: in S/4HANA Cloud the app does not calculate tax for you from the tax code, so the tax amount has to be entered in the file itself. Get the tax figures into your spreadsheet during extraction and the upload posts cleanly instead of bouncing on a tax mismatch.

How do I mass upload invoices in SAP?

For a true mass upload, use the Import Supplier Invoices app rather than FB60 or MIRO, which post one invoice at a time. Download the template, build one row block per invoice with the supplier number, company code, dates, line amounts, and tax codes, then upload and post the batch. For very high volumes or scheduled loads, teams move to SAP's OData or SOAP APIs to create supplier invoices programmatically.

The choice comes down to volume and frequency. A monthly stack of a few hundred invoices fits the template upload comfortably. A continuous feed of thousands, or invoices that must reference open purchase orders, is usually better handled through the API so the data flows in without anyone touching a spreadsheet.

What is the difference between FB60 and MIRO in SAP?

FB60 posts a supplier invoice without a purchase order, straight to a vendor and a GL account, while MIRO posts an invoice with reference to a purchase order so SAP can match it to the PO and goods receipt. Both are single-invoice transactions: you key one invoice and post it, then move to the next. Neither does a bulk upload on its own.

That is why the template app exists. If your AP team is keying dozens of non-PO invoices through FB60 every week, those are exactly the invoices that belong in an Import Supplier Invoices batch instead. PO-based invoices that need three-way matching usually stay in MIRO or move to an API that can carry the PO reference.

How does SAP match a supplier when importing invoices?

SAP matches each imported invoice to a supplier by the supplier (vendor) number you put in the file, combined with the company code, and that business partner has to exist in SAP first. It matches on the number, not the supplier's printed name, so a missing master record or the wrong company code will fail that invoice during validation rather than create a new vendor.

Set up or confirm the business partner records before the import, and keep a short reference list of supplier numbers next to your extraction file so the right number drops into every row. Pairing the correct supplier number with the correct company code on each line is the single biggest factor in a clean batch.

Why won't my invoices import into SAP?

Most failed SAP uploads trace to a handful of causes: a supplier number that has no matching business partner, a missing or wrong company code, a tax amount that was left blank when the app expected it filled in, a date in a format the template rejects, amounts that do not balance against the tax, or a file that exceeds the per-upload item limit. The app lists the invoices it could not post and the reason for each.

Fix the data in your spreadsheet, not inside SAP, so the source file stays correct for the next run. The quickest checks: confirm every supplier number and company code exists, enter the tax amount explicitly, use a consistent date format, make sure line amounts and tax add up to the invoice total, and split oversized files. Correct the rows the validation flagged, re-upload, and post.

From PDF invoices to an import-ready SAP file

The reliable workflow is short. Convert your PDF and image invoices into spreadsheet rows, check the supplier, company code, date, invoice number, line items, tax, and totals, drop them into the downloaded SAP template, then upload and post. The converter at the top of this page handles the first step, and you can read the full method in how to extract invoice data to Excel and the format details in the invoice PDF to Excel converter guide.

Once your file is clean, the SAP side rarely fights you. The import invoices to SAP page covers the supplier and template specifics in more depth, and if your AP team also reconciles those invoices against payments, converting the bank side with a bank statement to Excel converter keeps both halves in the same spreadsheet. Teams running more than one platform can compare the steps for each in the how to import invoices into an ERP overview. Extract once, fill the template once, and a monthly batch of invoices posts in minutes instead of a week of keying.