SAP S/4HANA imports supplier invoices in bulk through the Import Supplier Invoices app, which reads a downloaded spreadsheet template, not raw PDFs. SAP added Joule and AP AI agents in 2026, but those are licensed S/4HANA Cloud add-ons. Upload your PDF or image invoices here and get clean rows with supplier, invoice number, dates, amounts, and tax, ready to drop into the SAP upload template instead of keying each one in FB60.
Last updated June 2026
Upload your invoices
Drop files here or click to upload
Up to 50 files
Uploading...
SAP can post a batch of supplier invoices from one upload file, but only when each row matches the template and references a real supplier and company code. The invoices arrive as PDFs and scans, so the work is converting each document into correctly formatted rows before SAP will accept them. Keyed one at a time in FB60 or MIRO, a month of invoices takes days.
The Import Supplier Invoices app reads a spreadsheet template, and FB60 and MIRO expect manual entry. Either way, PDF and image invoices have to be transcribed into structured data first.
Each invoice has to reference a supplier that already exists in SAP, along with the right company code. A name printed on the invoice will not post, so the data has to map to the supplier master.
The downloaded template ships with the correct headers for supplier, invoice date, posting date, reference, amount, tax code, and company code. A renamed header or a wrong date format stops the upload.
SAP needs the right tax code and account assignment on each line. Missing or wrong tax codes are one of the most common reasons an upload row fails validation.
Posting invoices one at a time in FB60 or MIRO is slow, and every retyped figure is a chance for a transposed amount or a wrong reference that surfaces later as a payment error.
Even when you upload through the SAP app or a third-party invoice hub, the data behind it has to be accurate and structured, or the post fails downstream.
SAP shipped Joule and AP AI agents in 2026 that can read invoices and match them to purchase orders, but they require S/4HANA Cloud and the Business AI entitlement. On-premise or ECC sites, and anyone not yet licensed for Joule, still load invoices through the upload template.
InvoiceXLSX reads your PDF and image supplier invoices with AI and exports the fields SAP needs as clean rows. You add the supplier number, company code, and tax code, line the columns up with the SAP upload template, and import through the Import Supplier Invoices app. No FB60 retyping, no rebuilding the layout for every vendor.
Upload native PDFs, scanned bills, or phone photos. The AI extracts supplier, invoice number, dates, line items, tax, and totals from any layout.
Output arrives as structured columns that line up with the SAP upload template, so values drop into supplier, invoice date, reference, amount, and tax code.
Each line becomes its own row with description, amount, and tax, the structure a multi-line supplier invoice needs in SAP.
Process many invoices at once and export a single file so a centralized AP team can upload a weekly or monthly batch in one pass instead of keying each one.
Download a clean spreadsheet that fits the SAP template, with the invoice reference 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 supplier invoices in SAP.
Upload your PDF or image invoices to InvoiceXLSX. The AI reads each one and returns supplier, invoice number, dates, line items, tax, and totals as structured rows, with the reference repeated across each invoice and its lines.
Tip: Batch the whole stack in one pass, then review the values against the originals.
In SAP S/4HANA, open the Import Supplier Invoices app and download the template so the correct headers are in place. Paste your extracted data into the matching columns, then add the supplier number, company code, tax code, and account assignment for each invoice.
Tip: Keep a supplier-name to supplier-number lookup so mapping each invoice takes seconds.
Save the file in the template format, upload it back through the Import Supplier Invoices app, and let SAP validate the rows. Review any errors it flags, fix the supplier, tax code, or date, and post the batch so the invoices land in accounts payable.
Tip: For smaller batches you can also use the extracted data to speed up manual FB60 or MIRO entry.
US enterprises and shared-service centers on SAP that receive invoices as PDFs rather than ready-made upload files.
Upload a weekly or monthly batch of supplier invoices into SAP in one pass instead of keying each FB60 entry.
Process high invoice volumes for multiple company codes without adding headcount.
Backfill historical invoices during an S/4HANA migration or go-live.
Feed clean, structured invoice data into an SAP upload or invoice hub instead of brittle OCR glue.
SAP gives you a few ways to get supplier invoices in. For volume, S/4HANA ships the Import Supplier Invoices app, where you download a spreadsheet template, fill it with invoice data, and upload it back so SAP posts the batch. For one-off entry there is FB60 for non-PO invoices and MIRO for PO-based invoices. All of them assume the data is already structured: the supplier exists in the master, the company code and tax code are correct, and the amounts and dates are clean. Most failed uploads come down to a supplier that does not match, a missing tax code, or a date in the wrong format.
The step SAP cannot do for you is read the invoice. InvoiceXLSX converts each PDF or photo into the structured rows the upload template expects, including a line per item and a single reference carried across those lines. Once your data is in that shape you add the supplier numbers and tax codes, upload through the app, review the flagged rows, and post. For US enterprises and shared-service centers on SAP that means faster invoice processing, fewer keying errors, and a centralized AP team that can clear a batch without retyping every FB60 line. Discrete and process manufacturers running SAP can route each supplier PDF through manufacturing invoice processing first, so the line data is ready for three-way matching before the upload.
SAP gives you four practical paths in 2026, and the right one depends on your edition and whether you are licensed for Business AI. This is an honest comparison so you can pick.
| Approach | Reads a PDF? | Requires | Best for |
|---|---|---|---|
| Manual FB60 / MIRO entry | No, keyed by hand | Any SAP edition | A handful of invoices |
| Import Supplier Invoices app (template upload) | No, needs structured rows | S/4HANA | Monthly batches once data is clean |
| Joule / AP AI agent (native capture + PO match) | Yes | S/4HANA Cloud + Business AI license | Licensed Cloud sites wanting hands-off matching |
| InvoiceXLSX to template | Yes | Any SAP edition, free tier | Turning PDFs into upload-ready rows on any edition |
SAP's 2026 AP agents are genuinely capable, reading invoices and resolving straightforward PO exceptions on their own, but they sit behind an S/4HANA Cloud and Business AI entitlement. If you run S/4HANA on-premise, are still on ECC, or just are not licensed for Joule yet, converting PDFs to the upload template stays the fastest route, and InvoiceXLSX gives you that on a free tier with nothing to install.
Yes. SAP S/4HANA imports supplier invoices in bulk through the Import Supplier Invoices app, which reads a downloaded spreadsheet template. SAP does not read PDFs directly, so you first convert your PDF or image invoices into the template format, then upload the file and let SAP validate and post the batch.
Open the Import Supplier Invoices app in SAP S/4HANA and download the template so the headers are correct. Add your extracted invoice data, supplier numbers, company code, and tax codes to the columns, save in the template format, upload the file, fix any flagged rows, and post the batch into accounts payable.
No. The Import Supplier Invoices app reads a spreadsheet template, and FB60 and MIRO expect manual entry, so neither reads PDF or image files. To import PDF invoices, convert them to a template-ready file first. InvoiceXLSX extracts the supplier, dates, amounts, and tax from each PDF so you can map them to the SAP template.
FB60 posts a single non-PO supplier invoice through manual entry, and MIRO posts PO-based invoices. The Import Supplier Invoices app is for volume: you upload a spreadsheet of many invoices at once and SAP posts the batch. For a month of invoices the app is far faster than keying each one in FB60.
SAP resolves the vendor by supplier number against the supplier master, not by the name printed on the invoice, and it also needs the correct company code. Add the supplier number and company code to each row before uploading. A simple name-to-number lookup makes mapping your extracted invoice data fast and reliable.
Yes. SAP requires a tax code and account assignment on each invoice line, and a missing or wrong tax code is a common reason an upload row fails validation. Add the correct tax code per line before importing so the batch posts cleanly into accounts payable without manual correction.
Yes. SAP is built to accept invoices captured by external OCR or invoice-capture solutions, as long as the data is structured to the upload template. InvoiceXLSX produces that clean, structured output from your PDF and image invoices, so it feeds the Import Supplier Invoices app or your invoice hub directly.
Common causes are a supplier number that does not exist, a missing or wrong tax code, an incorrect company code, a date in the wrong format, or renamed template headers. Confirm each row references a valid supplier and company code, the tax code is correct, and the headers match the downloaded template exactly.
Yes, in S/4HANA Cloud. SAP rolled out Joule and accounts payable AI agents in 2026 that read supplier invoices, match them to purchase orders, and resolve simple exceptions, cutting manual processing time sharply. These capabilities require S/4HANA Cloud and a Business AI entitlement, so on-premise, ECC, and unlicensed sites still load invoices through the upload template.
The Import Supplier Invoices app and manual FB60 entry are included with your S/4HANA license at no extra charge, so the only cost is the staff time to prepare each file. SAP's native AI capture through Joule is a separately licensed Business AI add-on priced by SAP. InvoiceXLSX has a free tier to convert PDFs into upload-ready rows, with paid plans for higher volume. Confirm SAP licensing with your account team.
From the same family of tools
