Oracle Fusion Cloud ERP imports payables invoices in bulk through File-Based Data Import (FBDI), which loads a structured spreadsheet into the Payables open interface tables, not a PDF. Upload your PDF or image invoices here and get clean rows with supplier, supplier site, invoice number, dates, line items, amounts, and tax, ready to drop into the FBDI Payables invoice template.
Upload your invoices
Drop files here or click to upload
Up to 50 files
Uploading...
Oracle Fusion has a proven path for loading invoices in volume, the Import Payables Invoices process fed by an FBDI spreadsheet, but it only reads structured data mapped to the open interface tables. Invoices arrive as PDFs and scans, so the work that eats the day is converting each document into header and line rows with the right supplier and business unit. That preparation is the bottleneck, not the import itself.
FBDI reads a spreadsheet you save as CSV and zip, then loads through the Load Interface File for Import process. It does not turn a PDF supplier invoice into records, so every document has to be converted into structured rows first.
The Payables invoice template carries an Invoice Header sheet that maps to AP_INVOICES_INTERFACE and an Invoice Lines sheet that maps to AP_INVOICE_LINES_INTERFACE, linked by an invoice ID. Building both by hand and keeping them in sync is slow and error-prone.
Each invoice has to reference a supplier and supplier site that already exist in Oracle, plus the correct business unit. The name printed on the invoice will not resolve, so the data has to map to the supplier and site.
The FBDI template ships with a fixed column layout. You can hide or skip unused columns, but changing their order or deleting them makes the load process fail, so the data has to land in the exact template shape.
Each line needs a distribution combination or a distribution set and a valid tax setup. A missing account or wrong combination is one of the most common reasons a row rejects in the Import Payables Invoices report.
Keying a stack of supplier invoices into the Create Invoice page at month-end is slow, and every retyped figure risks a transposed amount that surfaces later as a duplicate or short payment.
InvoiceXLSX reads your PDF and image invoices with AI and exports the fields Oracle Fusion Payables needs as clean rows for the Invoice Header and Invoice Lines sheets of the FBDI template. You add the business unit, supplier, supplier site, and distribution, load the file through the standard process, and let Oracle create and validate the invoices. No retyping, no rebuilding the layout per 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 Payables FBDI Invoice Header and Invoice Lines sheets, so values drop into supplier, invoice date, amount, and line fields.
Each line becomes its own row with description, amount, and tax, the structure the Invoice Lines worksheet needs under one invoice header.
Process many invoices at once and export a single file so a shared-service AP team can load a weekly or monthly batch in one FBDI run.
Download a clean spreadsheet you can paste into the FBDI template, with one invoice 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 validated payables invoices in Oracle Fusion Cloud ERP.
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 one invoice number tying the lines to the header.
Tip: Batch the whole stack in one pass, then review the values against the originals.
Open the File-Based Data Import for the Import Payables Invoices process and download the Payables invoice template. Paste your extracted data into the Invoice Header and Invoice Lines sheets, then add the business unit, supplier, supplier site, and the distribution combination or distribution set for each invoice.
Tip: Keep a supplier name to supplier and site lookup so mapping each invoice takes seconds. Do not change the column order.
Generate the CSV from the template, zip it, and run the Load Interface File for Import process to load the open interface tables. Then run the Import Payables Invoices process to create the invoices, review the rejection report, fix any rows, and re-run so the batch lands in Payables ready to validate.
Tip: Save the loaded file so you can reconcile any rejected rows against your originals.
US enterprises and shared-service centers on Oracle Fusion Cloud ERP that receive invoices as PDFs rather than ready-made FBDI files.
Load a weekly or monthly batch of supplier invoices through FBDI instead of keying each one into the Create Invoice page.
Process high invoice volumes across multiple business units without adding headcount.
Backfill historical payables invoices during an Oracle Fusion implementation or go-live.
Feed clean, structured invoice data into FBDI or the AP invoice REST API instead of brittle OCR glue.
Oracle Fusion Cloud ERP loads payables invoices in bulk through File-Based Data Import rather than a single import button. You download the Payables invoice template, fill the Invoice Header sheet that maps to AP_INVOICES_INTERFACE and the Invoice Lines sheet that maps to AP_INVOICE_LINES_INTERFACE, save the data as CSV, and zip it. The Load Interface File for Import scheduled process moves it into the open interface tables, and the Import Payables Invoices process then creates the invoices. Every header needs a business unit, a supplier and supplier site, an invoice number, a date, and an amount, and every line needs a valid distribution. Most rejected rows come down to a supplier or site that does not match, a missing distribution, or a wrong amount.
The step Oracle cannot do for you is read the invoice. InvoiceXLSX converts each PDF or photo into the structured header and line rows the FBDI template expects, with one invoice number carried across the lines. Once your data is in that shape you add the business unit, supplier, site, and distribution, load it, and import. For smaller volumes Oracle also offers the ADFDI Create Invoices in Spreadsheet add-in, and integration teams can use the AP invoice REST API, but FBDI is the standard high-volume path. For US enterprises and shared-service centers on Oracle Fusion that means faster invoice processing, fewer keying errors, and an AP team that can clear a batch without retyping every line.
Yes. Oracle Fusion Cloud ERP imports payables invoices in bulk through File-Based Data Import (FBDI), which loads a structured spreadsheet into the Payables open interface tables. Oracle does not read PDFs directly, so you first convert your PDF or image invoices into the FBDI template rows, then load and run the Import Payables Invoices process.
Download the Payables invoice FBDI template, fill the Invoice Header and Invoice Lines sheets, and add the business unit, supplier, supplier site, and distribution. Save the data as CSV, zip it, run the Load Interface File for Import process to populate the interface tables, then run the Import Payables Invoices process to create the invoices.
FBDI, or File-Based Data Import, is the standard way Oracle Fusion loads data in bulk. For payables you download a predefined spreadsheet template, populate it, generate a CSV, and load it through the Load Interface File for Import scheduled process into the open interface tables. A second process then creates the records, so it is the high-volume path for invoices.
No. FBDI reads a structured spreadsheet, and the Create Invoice page expects manual entry, so neither reads a PDF or image file. To import PDF invoices, convert them to the template format first. InvoiceXLSX extracts the supplier, dates, line items, and totals from each PDF so you can map them to the FBDI Payables template.
FBDI loads a CSV through a scheduled process and is built for high volume, staging data in the open interface tables before import. ADFDI, the Create Invoices in Spreadsheet add-in, connects an Excel sheet straight to Oracle for smaller, interactive entry. Both expect structured data, so a PDF still has to be converted to rows first.
Oracle resolves the vendor by supplier and supplier site against the supplier master, not by the name printed on the invoice, and it also needs the correct business unit. Add the supplier, site, and business unit to each header row before loading. A simple name-to-supplier lookup makes mapping your extracted invoice data fast and reliable.
At minimum each header needs a business unit, a supplier and supplier site, an invoice number, an invoice date, an invoice amount, and a currency, and each line needs an amount and a valid distribution combination or distribution set. Missing any required field, or an invalid distribution, will reject the row in the Import Payables Invoices report.
Common causes are a supplier or supplier site that does not match, a missing business unit, an invalid distribution combination, a header and line that do not share the same invoice, a wrong currency or date format, or a changed column order in the template. Confirm each row references a valid supplier, site, and business unit, and that the template layout is unchanged.
The Import Payables Invoices process produces a report listing each rejected row with a reason, such as an invalid supplier site or a distribution that does not exist. Correct those fields in your spreadsheet, reload the file through the Load Interface File for Import process, and run the import again so the corrected invoices are created and ready to validate.
