0:06 — Introduction and agenda — The presenter introduces the webinar as a demo of APRO software covering processing an XML e-invoice into Oracle and creating payments by picking up payment files out of Oracle and sending them to the bank. The agenda covers a personal introduction, e-invoicing, the banking gateway, a demonstration, and questions. 1:14 — Presenter background — Peter introduces himself as working at APRO for almost a decade, with more than a decade of experience in Oracle Financials Cloud and Oracle E-Business Suite, on both payments and e-invoicing and on both the AP and AR sides. 1:33 — Core features of e-invoicing — Four core features are outlined: automation through direct mapping of header and line detail fields into the ERP, standardization via the Peppol network alongside country-specific government platform formats, real-time reporting where tax authorities receive invoices before customers do, and digital signatures described as a secured envelope around the XML. 3:02 — Global adoption of e-invoicing — Adoption is described across Europe, India for B2B and B2G at some companies, and Latin America — Brazil, Mexico and Chile — as pioneers of XML invoice mandates. The United States is described as upcoming and likely to adopt Peppol as a global standard network, replacing email delivery with server-to-server connections. 3:47 — Business impact and Oracle interfacing — Compliance is required per country where a legal entity exists, including the correct format and country-specific certificates, and dashboarding provides validation notifications and acknowledgements that PDF email delivery does not. Interfacing XML into Oracle is said to otherwise require significant per-country development, while XML removes the OCR step needed for PDF invoices. 5:22 — 2025 and upcoming mandates — A slide lists the countries with e-invoicing mandates in 2025 and additional countries starting the following year, covering both the AP and AR sides of a company. 5:46 — Payment file problems — Problems addressed by the payment solution are described: producing the bank-accepted format, whole batches being rejected because of a single transaction, lost discounts from late payment when a file is stuck, and heavy IT involvement without a solution for formatting and bank connectivity. 6:32 — APRO banking gateway capabilities — Stated capabilities include automated pickup and formatting from more than 1,900 banking formats, built-in approvals covering multiple banks in one place, Oracle integration via APIs, and voiding a single transaction out of a payment batch so the remainder still processes. 7:29 — Payment outbound flow — The outbound flow is walked through: due invoices form a payment batch, the batch goes to APRO, APRO creates the correct format and sends it to the bank over a host-to-host or bank-specific connection, acknowledgement files return from the bank and appear in APRO dashboarding, and payment specifications can be sent out automatically. 8:18 — Demo setup and AP invoice automation — Two supplier invoices are dropped over an SFTP connection, described as similar to a government platform delivery. The APRO cloud interface is shown with a menu leading to AP invoice automation and payments, and the import overview shows runs picking up new invoices from sources such as email and e-invoicing. 10:15 — Validating invoices and sending to Oracle — The workbench holds invoices for validation before Oracle. A validation hold shows the invoice number already exists in Oracle; the number is changed, save and validate is clicked, and both invoices move to Oracle. The invoice history and import overview confirm the invoices were recognized and sent. 12:14 — Banking workbench and payment file creation — The banking area shows payment batches awaiting approval or file creation. A payment file for a specific bank is created manually for the demo, placed on an SFTP drive to the bank, and accompanied by a report of what was sent; suppliers can receive a payment specification message when the invoice is paid. 13:41 — Invoices in Oracle — The processed invoices are opened in Oracle, showing a validated invoice with the XML automatically attached, and confirmed as approved and ready for payment. 14:59 — Payment process request in Oracle — In Oracle Payables, a payment process request named "webinar 99" is submitted from a template, picks up the two processed invoices, and is submitted. Approval thresholds in APRO are explained by amount, with a below-$1,000 example, and the resume payment process step is shown. 16:55 — APRO picks up and sends the payment file — Because the file was below 500 euros it bypassed the approval flow. In the APRO banking gateway the batches appear in create-file and in-progress states, and one unrelated batch is rejected with a reason indicating the supplier master data needs revalidation. 18:03 — Completed batch and end-to-end recap — The completed payment batch is shown as automated, downloadable and already sent to the bank, with a supplier notification of a 6 euro payment. The presenter notes the acknowledgement file was not demonstrated but can be used for approval, and recaps the full path from invoice validation in APRO and Oracle through payment batch creation, formatting, and transmission to the bank.

Home / Resources / Webinars

Demo: Full Invoice to Pay in Oracle Financials

Key takeaways

The webinar demonstrates APRO software processing an XML e-invoice into Oracle and then generating and sending the resulting payment file to the bank.
E-invoicing core themes covered are automation, standardization (including the Peppol network and country-specific government platforms), real-time tax reporting, and digital signatures.
Mandates already exist in a set of countries in 2025 with more starting the following year, covering both incoming (AP) and outgoing (AR) invoices, so companies need to be compliant in every country where they have a legal entity.
The presenter states APRO supports more than 1,900 banking formats, has built-in approvals, and integrates with Oracle via APIs, including voiding a single transaction out of a payment batch.
In the live demo, two supplier XML invoices arrive over SFTP, are validated in the APRO workbench (including a duplicate-invoice-number hold that is corrected), and are then sent to Oracle.
A payment process request is submitted in Oracle Cloud, APRO picks up the payment batch, creates the bank-specific format, and places the file on an SFTP drive to the bank; the sample batch skipped approval because it was under 500 euros.
The banking workbench shows batch status including a rejected payment that required supplier master data revalidation, and APRO can send payment specifications to suppliers automatically.

Overview

This webinar is a product demonstration of APRO software covering the full invoice-to-pay cycle in Oracle Financials. The presenter, Peter, introduces himself as having worked at APRO for almost a decade with more than a decade of experience in Oracle Financials Cloud and Oracle E-Business Suite, on both payments and e-invoicing and on both the AP and AR sides. The stated agenda is an introduction, an overview of e-invoicing and how it works with APRO, an explanation of the banking gateway used to send payment files to banks, a live demonstration running from invoice receipt through to payment, and a closing question-and-answer segment.

The e-invoicing portion describes four core features: automation, where incoming invoices are mapped directly to header and line detail fields and passed into the ERP; standardization, where a large group of countries use the Peppol network with common formats while other countries require country-specific formats tied to a government platform; real-time reporting, where invoices are sent to the tax authority before reaching the customer so tax details are collected per invoice rather than at period end; and digital signatures, described as a secured envelope around the XML invoice. Adoption is described as global, with Latin American countries such as Brazil, Mexico and Chile as early mandate adopters, India covering B2B and B2G for some companies, and the United States described as upcoming and likely to move toward Peppol. The business impact discussed includes needing compliance per legal entity and country, producing the correct format so the government accepts the invoice, and dashboarding that gives notifications and acknowledgements about whether an invoice was validated — feedback that a PDF sent by email does not provide. The presenter also notes that interfacing XML invoices into Oracle otherwise requires significant per-country development, and that XML removes the OCR recognition step needed for PDFs. A slide shows the countries with mandates in 2025 and additional countries starting the following year, for both AP and AR.

The payments portion explains the problems APRO's banking gateway is meant to address: building the correct bank-specific payment format, the situation where a single bad transaction causes a whole batch to be rejected and rebuilt, late payments and lost discounts when a payment file is stuck, and heavy IT involvement when no formatting and connectivity solution exists. APRO's stated capabilities include picking up the payment file and producing the correct format from more than 1,900 banking formats, built-in approvals so payments to multiple banks can be approved in one place instead of logging into each bank, Oracle integration through APIs, and the ability to void a single transaction so the rest of the batch still processes. The outbound flow described is: invoices become due, a payment batch is created, the batch goes to APRO, APRO creates the correct format and sends it to the bank over a host-to-host or other bank-specific connection, acknowledgement files come back from the bank and are visible in APRO dashboarding, and payment specifications can be sent out automatically.

The demonstration begins with two supplier invoices arriving over an SFTP connection, described as similar to how a government platform would deliver them. In the APRO cloud interface, which the presenter says has a look and feel similar to Oracle, the left-hand menu leads to AP invoice automation and payments. The import overview shows new runs picking up files from sources including email and e-invoicing, and the workbench holds invoices for validation before they go to Oracle. One invoice is held because the invoice number already exists in Oracle; the presenter edits the number, clicks save and validate, and both invoices move to Oracle. The invoice history view confirms the invoices were sent. Because the payment method was set to immediate, the invoices become due as soon as they reach Oracle. In Oracle, the presenter confirms an invoice is validated and that the XML is automatically attached to it.

On the payments side, the presenter shows the banking workbench with payment batches awaiting approval or file creation, manually creates a payment file for demonstration purposes (noting it is normally automatic), and shows the file placed on an SFTP drive to the bank along with a report of what was sent. In Oracle Payables, a payment process request named "webinar 99" is submitted from a template, picks up the two invoices, and is submitted. Approval flows in APRO can be triggered by payment file amount; the presenter gives a below-$1,000 threshold as an example and notes the demo file went straight through because it was below 500 euros. Back in the APRO banking gateway, batches are shown in create-file and in-progress states, and one unrelated batch is rejected with a reason indicating the supplier needs revalidation due to a master data problem. The completed batch is shown as fully automated, downloadable and already sent to the bank, with the supplier receiving a notification of a payment of 6 euros for that invoice. The presenter notes the acknowledgement file was not shown in the demo but can also be used for approval, and closes by recapping the end-to-end path: two invoices validated in APRO and Oracle, a payment batch created in Oracle, and APRO formatting and transmitting the payment file to the bank.

Chapters

0:06 — Introduction and agenda — The presenter introduces the webinar as a demo of APRO software covering processing an XML e-invoice into Oracle and creating payments by picking up payment files out of Oracle and sending them to the bank. The agenda covers a personal introduction, e-invoicing, the banking gateway, a demonstration, and questions.
1:14 — Presenter background — Peter introduces himself as working at APRO for almost a decade, with more than a decade of experience in Oracle Financials Cloud and Oracle E-Business Suite, on both payments and e-invoicing and on both the AP and AR sides.
1:33 — Core features of e-invoicing — Four core features are outlined: automation through direct mapping of header and line detail fields into the ERP, standardization via the Peppol network alongside country-specific government platform formats, real-time reporting where tax authorities receive invoices before customers do, and digital signatures described as a secured envelope around the XML.
3:02 — Global adoption of e-invoicing — Adoption is described across Europe, India for B2B and B2G at some companies, and Latin America — Brazil, Mexico and Chile — as pioneers of XML invoice mandates. The United States is described as upcoming and likely to adopt Peppol as a global standard network, replacing email delivery with server-to-server connections.
3:47 — Business impact and Oracle interfacing — Compliance is required per country where a legal entity exists, including the correct format and country-specific certificates, and dashboarding provides validation notifications and acknowledgements that PDF email delivery does not. Interfacing XML into Oracle is said to otherwise require significant per-country development, while XML removes the OCR step needed for PDF invoices.
5:22 — 2025 and upcoming mandates — A slide lists the countries with e-invoicing mandates in 2025 and additional countries starting the following year, covering both the AP and AR sides of a company.
5:46 — Payment file problems — Problems addressed by the payment solution are described: producing the bank-accepted format, whole batches being rejected because of a single transaction, lost discounts from late payment when a file is stuck, and heavy IT involvement without a solution for formatting and bank connectivity.
6:32 — APRO banking gateway capabilities — Stated capabilities include automated pickup and formatting from more than 1,900 banking formats, built-in approvals covering multiple banks in one place, Oracle integration via APIs, and voiding a single transaction out of a payment batch so the remainder still processes.
7:29 — Payment outbound flow — The outbound flow is walked through: due invoices form a payment batch, the batch goes to APRO, APRO creates the correct format and sends it to the bank over a host-to-host or bank-specific connection, acknowledgement files return from the bank and appear in APRO dashboarding, and payment specifications can be sent out automatically.
8:18 — Demo setup and AP invoice automation — Two supplier invoices are dropped over an SFTP connection, described as similar to a government platform delivery. The APRO cloud interface is shown with a menu leading to AP invoice automation and payments, and the import overview shows runs picking up new invoices from sources such as email and e-invoicing.
10:15 — Validating invoices and sending to Oracle — The workbench holds invoices for validation before Oracle. A validation hold shows the invoice number already exists in Oracle; the number is changed, save and validate is clicked, and both invoices move to Oracle. The invoice history and import overview confirm the invoices were recognized and sent.
12:14 — Banking workbench and payment file creation — The banking area shows payment batches awaiting approval or file creation. A payment file for a specific bank is created manually for the demo, placed on an SFTP drive to the bank, and accompanied by a report of what was sent; suppliers can receive a payment specification message when the invoice is paid.
13:41 — Invoices in Oracle — The processed invoices are opened in Oracle, showing a validated invoice with the XML automatically attached, and confirmed as approved and ready for payment.
14:59 — Payment process request in Oracle — In Oracle Payables, a payment process request named "webinar 99" is submitted from a template, picks up the two processed invoices, and is submitted. Approval thresholds in APRO are explained by amount, with a below-$1,000 example, and the resume payment process step is shown.
16:55 — APRO picks up and sends the payment file — Because the file was below 500 euros it bypassed the approval flow. In the APRO banking gateway the batches appear in create-file and in-progress states, and one unrelated batch is rejected with a reason indicating the supplier master data needs revalidation.
18:03 — Completed batch and end-to-end recap — The completed payment batch is shown as automated, downloadable and already sent to the bank, with a supplier notification of a 6 euro payment. The presenter notes the acknowledgement file was not demonstrated but can be used for approval, and recaps the full path from invoice validation in APRO and Oracle through payment batch creation, formatting, and transmission to the bank.

Questions this webinar answers

What does the APRO invoice-to-pay process cover end to end?

It covers receiving an XML e-invoice through a connection such as SFTP, validating it in the APRO workbench, sending it into Oracle, waiting for Oracle to create a payment batch for due invoices, then having APRO pick up that batch, generate the bank-specific payment format, and transmit the file to the bank. Acknowledgement files return from the bank and appear in APRO dashboarding, and payment specifications can be sent to suppliers automatically.

What are the core features of e-invoicing described in this session?

Four are named: automation, where incoming invoices are mapped directly to header and line detail fields and passed to the ERP; standardization, where many countries use the Peppol network with common formats while others require country-specific formats on a government platform; real-time reporting, where invoices go to the tax authority before the customer so tax data is collected per invoice instead of at period end; and digital signatures, described as a secured envelope around the XML invoice.

Why is XML e-invoicing easier to automate than PDF invoicing?

With PDF invoices, OCR recognition is needed to identify header and line details. In an XML invoice that information is already mapped and structured, so automation on the accounts payable process is more straightforward. XML delivery also provides notifications and acknowledgements confirming whether an invoice was received and validated, which emailed PDF invoices do not.

Which regions and countries were mentioned as adopting e-invoicing mandates?

Europe was cited along with India for B2B and B2G at some companies. Brazil, Mexico and Chile in Latin America were described as pioneers in mandating XML invoices sent to the government. The United States was described as upcoming, with Peppol as the likely global standard network. A set of countries already had mandates in 2025, with more starting the following year, on both the accounts payable and accounts receivable sides.

What problems does the banking gateway address?

It addresses having to build the correct bank-specific payment format, a whole payment batch being rejected because of one bad transaction and having to be rebuilt, late payments and lost discounts when a payment file is stuck, and heavy IT involvement when there is no solution for formatting and bank connectivity.

How many banking formats are supported, and how are payments approved?

More than 1,900 banking formats are supported. Approvals are built in, so payment batches or files destined for different banks can be approved within APRO rather than by logging in to each bank separately. Approval flows can be triggered by payment file amount — a file below a set threshold goes straight to the bank without approval. In the demonstration the file was under 500 euros and bypassed approval.

What happens if one transaction in a payment batch is bad?

A single transaction can be voided out of a full payment batch so the rest of the batch still processes, and the void is directly visible in the APRO system. In the demonstration, one batch showed as rejected with a reason indicating the supplier needed revalidation because of a problem with supplier master data, which stopped those specific transactions from being processed to the bank.

What was actually shown in the live demonstration?

Two supplier invoices arrived over an SFTP connection and were picked up automatically. In the APRO workbench one invoice was held because its invoice number already existed in Oracle; the number was changed and both invoices were saved, validated and sent to Oracle. In Oracle the invoice was shown as validated with the XML automatically attached. A payment process request named "webinar 99" was submitted in Oracle Payables, picked up the two invoices, and produced a payment batch that APRO formatted and placed on an SFTP drive to the bank, with the supplier receiving notification of a 6 euro payment.

Table of Contents

Get A Demo:

Simple solutions. Powerful results. Seamlessly integrated.

Get a PairSoft Demo