Oracle Fusion Cloud Payables Agent Streams: Complete Guide with Sample Test Scenarios

Meta Description: Learn how to use Oracle Fusion Cloud Payables Agent Streams for invoice processing. This guide explains Invoice Image Documents, Mass Invoice Documents, Electronic Invoice, Supplier Portal, Manual, and Internal Sources with navigation paths and sample test data.

Introduction

Oracle Fusion Cloud Payables provides multiple ways to receive and process supplier invoices. With Payables Agent Streams, organizations can route invoices through different channels depending on how the invoice is received and what type of data is available.

A PDF invoice received from a supplier is handled differently from an XLSX mass invoice file, an electronic XML invoice, or an invoice entered through the Supplier Portal.

Understanding these streams is therefore important when designing an invoice automation solution and preparing CRP or UAT test scenarios.

This article explains the major Payables Agent Streams and provides practical test scenarios, sample invoice data, and navigation paths.

What Are Payables Agent Streams?

A Stream represents an invoice/document intake channel within the Payables Agent capture framework.

The streams visible in the environment can include:

Invoice Image Documents
Mass Invoice Documents
Internal Sources
Manual
Electronic Invoice
Supplier Portal

Each stream has a different purpose and processing mechanism.

A simplified architecture is:

                    PAYABLES AGENT
                         |
                       CAPTURE
                         |
                       STREAMS
                         |
       +---------+-------+-------+---------+---------+
       |         |       |       |         |         |
       ▼         ▼       ▼       ▼         ▼         ▼
    Image      Mass   Internal Manual  Electronic Supplier
   Documents  Invoice  Sources          Invoice     Portal
       |         |       |       |         |         |
       ▼         ▼       ▼       ▼         ▼         ▼
    Document   Feeder  Internal  User    XML/JSON   Supplier
      IO       Source  Process  Entry              Submission
       |         |       |       |         |         |
       +---------+-------+-------+---------+---------+
                         |
                         ▼
                  PAYABLES INVOICE
                         |
                         ▼
                 Validate / Account
                         |
                         ▼
                      Payment

1. Invoice Image Documents

What is it?

Invoice Image Documents is designed for image-based supplier invoices.

Typical supported formats in the environment include:

PDF
TIF/TIFF
PNG
JPG/JPEG
DOC/DOCX

This is the stream to use when a supplier provides an invoice as a document and Oracle needs to extract invoice information from it.

Example

Supplier sends:

Test_Supplier_Invoice_10027.pdf

Invoice:

Field	Value
Supplier	TEST SUPPLIER
Supplier Number	10025
Invoice Number	TS-INV-10027
Invoice Date	19-Sep-2026
Currency	USD
Total	950.00

The sample PDF used for testing contains four invoice lines and a total of USD 950.

Processing flow

Supplier
   ↓
PDF Invoice
   ↓
Invoice Image Documents
   ↓
Document IO
   ↓
Invoice Data Extraction
   ↓
Payables Invoice
   ↓
Validation

Navigation

Payables Agent
 → Configuration
 → Capture
 → Streams
 → Invoice Image Documents

Use View Details to review the stream configuration.

Testing scenario

Test Case: Image-based invoice processing

Input: PDF

Invoice Number: TS-IMG-10001

Expected Result:

Supplier identified
Invoice number extracted
Invoice date extracted
Currency identified
Invoice amount extracted
Invoice lines extracted
Payables invoice created

2. Invoice Image Documents – Training

One of the important capabilities associated with invoice image processing is Training.

Training is useful when invoices from the same supplier repeatedly follow a similar layout.

Example

Supplier invoice contains:

Invoice Number → TS-IMG-10001
Invoice Date   → 21-Sep-2026
Supplier       → TEST SUPPLIER
PO Number      → 4500001234
Total          → 950.00

The recognition process needs to correctly associate the document fields with the corresponding Payables attributes.

Navigation

Payables Agent
 → Configuration
 → Capture
 → Streams
 → Invoice Image Documents
 → Actions
 → Training / Onboarding New Format

Training should be viewed as a recognition/layout learning capability.

It does not mean that an unsupported file type such as XLSX can automatically become a supported Document IO image format.

That distinction is important when designing supplier invoice automation.

3. Mass Invoice Documents

The Mass Invoice Documents stream is particularly interesting for organizations processing invoices in bulk.

Your environment shows:

CSV, XLSX

This makes it different from Invoice Image Documents.

Example test data

Supplier Number	Site	Invoice Number	Invoice Date	Currency	Amount
10025	TEST2	TS-MASS-10001	21-Sep-2026	USD	950
10025	TEST2	TS-MASS-10002	21-Sep-2026	USD	500
10025	TEST2	TS-MASS-10003	21-Sep-2026	USD	750

Navigation

Payables Agent
 → Configuration
 → Capture
 → Streams
 → Mass Invoice Documents
 → View Details

The Feeder Source configuration is important here because the expected input and processing mechanism depend on how the stream is configured.

Typical processing concept

CSV / XLSX
    ↓
Mass Invoice Documents
    ↓
Feeder Source
    ↓
Invoice Interface
    ↓
Import Payables Invoices
    ↓
Payables Invoice

Scheduled Process

A typical downstream Payables import process is:

Navigator
 → Tools
 → Scheduled Processes
 → Schedule New Process
 → Import Payables Invoices

Important clarification

Mass Invoice Documents should not automatically be interpreted as "supplier can email any Excel invoice and Document IO will read it."

An Excel file designed as a human-readable invoice and an Oracle mass-import spreadsheet are two different concepts.

Before testing XLSX, review:

Mass Invoice Documents
 → View Details

and confirm the configured feeder source and expected format.

4. Internal Sources

Internal Sources represents invoices or invoice information originating from internal Oracle/application processes.

This is different from a supplier emailing an invoice document.

Example

An internal process generates:

Supplier       TEST SUPPLIER
Invoice        TS-INT-10001
Amount         USD 950
Currency       USD

Conceptual flow

Internal Oracle Process
        ↓
Internal Sources
        ↓
Payables Processing
        ↓
Payables Invoice

Testing

Use an internal Oracle process that generates invoice data and then verify the resulting invoice.

Verification

Payables Agent
 → Invoice List

Search for:

TS-INT-10001

Test objective

Verify that internally generated invoice data reaches Payables correctly without using the supplier email/image-processing channel.

5. Manual Invoice

The Manual stream represents the traditional AP invoice creation process.

This is also an excellent baseline test because it removes Document IO and external ingestion from the equation.

Sample test data

Field	Value
Supplier	TEST SUPPLIER
Supplier Number	10025
Site	TEST2
Invoice Number	TS-MAN-10001
Invoice Date	21-Sep-2026
Currency	USD
Amount	950

Navigation

Navigator
 → Payables
 → Invoices
 → Create Invoice

Enter:

Supplier       = TEST SUPPLIER
Supplier Site  = TEST2
Invoice Number = TS-MAN-10001
Invoice Date   = 21-Sep-2026
Currency       = USD

Enter the invoice lines:

Description	Qty	Unit Price	Amount
Office Supplies	10	12.50	125.00
Consulting Services	5	100.00	500.00
Software Subscription	1	250.00	250.00
Miscellaneous Charges	1	75.00	75.00

Total = USD 950

Then:

Save
 → Validate
 → Account

Test objective

Confirm:

Supplier setup
Supplier site
Business Unit
Currency
Payment terms
Tax
Accounting
Validation

before troubleshooting automated invoice ingestion.

6. Electronic Invoice

Electronic invoices are different from image-based invoices.

Instead of asking Document IO to recognize information from a visual document, the invoice information is already structured.

Examples include:

XML
JSON
B2B/e-invoicing messages

Your stream currently shows:

XML, JSON

Conceptual example

<Invoice>
    <InvoiceNumber>TS-XML-10001</InvoiceNumber>
    <InvoiceDate>2026-09-21</InvoiceDate>
    <SupplierNumber>10025</SupplierNumber>
    <Currency>USD</Currency>
    <Amount>950.00</Amount>
</Invoice>

Note: This is illustrative data, not necessarily the exact production XML schema required by your Oracle environment.

Typical architecture

Supplier / E-Invoicing Provider
             ↓
       XML / JSON
             ↓
     Electronic Invoice
             ↓
Collaboration Messaging Framework
             ↓
     Invoice Interface
             ↓
 Import Payables Invoices
             ↓
      Payables Invoice

Configuration areas

Depending on the integration design, configuration can involve:

Setup and Maintenance
 → Manage Collaboration Messaging Service Providers

and trading-partner/message configuration.

Test invoice

Invoice Number = TS-XML-10001
Supplier       = TEST SUPPLIER
Supplier #     = 10025
Amount         = USD 950

Test objective

Verify that a structured electronic invoice can be received, transformed/mapped, imported and created as a Payables invoice.

7. Supplier Portal

The Supplier Portal provides another invoice submission channel.

Instead of sending a PDF to an email endpoint, the supplier submits invoice information through the supplier-facing application.

Example

Supplier
   ↓
Supplier Portal
   ↓
Create Invoice
   ↓
Oracle Payables

Sample test

Supplier       = TEST SUPPLIER
Supplier Site  = TEST2
Invoice Number = TS-PORTAL-10001
Invoice Date   = 21-Sep-2026
Currency       = USD
Amount         = 950

Supplier-side navigation

Depending on the enabled Supplier Portal experience:

Supplier Portal
 → Invoices and Payments
 → Invoices
 → Create Invoice

For a PO-backed invoice, select the appropriate purchase order and invoice the applicable PO lines.

Test objective

Verify:

Supplier authentication
Supplier/site selection
PO matching
Invoice creation
Invoice submission
Payables validation
Approval workflow

8. Comparing the Streams

Stream	Primary purpose	Example input	Document IO?	Typical user
Invoice Image Documents	Image/document invoice recognition	PDF/JPG/PNG	Yes	Supplier/AP automation
Mass Invoice Documents	Bulk invoice ingestion	CSV/XLSX	Depends on feeder configuration	AP/Integration
Internal Sources	Internal invoice generation	Application data	No	Internal processes
Manual	Direct invoice entry	User input	No	AP User
Electronic Invoice	Structured electronic invoice	XML/JSON	No image recognition	Supplier/Integration
Supplier Portal	Supplier self-service submission	Portal entry	Not required	Supplier

9. Recommended CRP/UAT Test Pack

For a real Oracle Fusion implementation, I recommend creating these six test cases:

TC01 – Manual Invoice

TS-MAN-10001

Purpose: Validate basic AP configuration.

TC02 – PDF Invoice / Document IO

TS-IMG-10001

Purpose: Validate supplier invoice image extraction.

TC03 – Document IO Training

TEST SUPPLIER
Repeated PDF layout

Purpose: Validate recognition learning for a recurring supplier layout.

TC04 – Mass XLSX Invoice

TS-MASS-10001

Purpose: Validate the configured Mass Invoice Documents feeder.

TC05 – Electronic Invoice

TS-XML-10001

Purpose: Validate structured electronic invoice processing.

TC06 – Supplier Portal

TS-PORTAL-10001

Purpose: Validate supplier self-service invoice submission.

10. Key Takeaway

The most important design principle is:

Choose the stream based on how the invoice enters Oracle, not simply based on the file extension.

For example:

PDF from supplier
       ↓
Invoice Image Documents
       ↓
Document IO

Whereas:

Structured XLSX/CSV mass data
       ↓
Mass Invoice Documents
       ↓
Feeder / Import

And:

Structured XML/JSON
       ↓
Electronic Invoice
       ↓
Messaging / Integration

While:

Supplier enters invoice
       ↓
Supplier Portal

This distinction becomes especially important when designing a "Supplier Email → Excel → Automatic AP Invoice" solution. The fact that Mass Invoice Documents displays XLSX does not by itself mean that an arbitrary supplier-designed Excel invoice can be emailed and interpreted like a PDF Document IO invoice.

Oracle Fusion Cloud Payables Agent Streams Explained: Invoice Image, Mass Invoice, Electronic Invoice, Supplier Portal & More

Oracle Fusion Cloud Payables Agent Streams: Complete Guide with Sample Test Scenarios

Introduction

What Are Payables Agent Streams?

1. Invoice Image Documents

What is it?

Example

Processing flow

Navigation

Testing scenario

2. Invoice Image Documents – Training

Example

Navigation

3. Mass Invoice Documents

Example test data

Navigation

Typical processing concept

Scheduled Process

Important clarification

4. Internal Sources

Example

Conceptual flow

Testing

Verification

Test objective

5. Manual Invoice

Sample test data

Navigation

Test objective

6. Electronic Invoice

Conceptual example

Typical architecture

Configuration areas

Test invoice

Test objective

7. Supplier Portal

Example

Sample test

Supplier-side navigation

Test objective

8. Comparing the Streams

9. Recommended CRP/UAT Test Pack

TC01 – Manual Invoice

TC02 – PDF Invoice / Document IO

TC03 – Document IO Training

TC04 – Mass XLSX Invoice

TC05 – Electronic Invoice

TC06 – Supplier Portal

10. Key Takeaway