0:06 — Introductions and agenda — Richard Brammer, director of strategic go-to-market, opens the webinar on APRO Banking Gateway and global payments in Oracle Financials, joined by John, VP of sales architecture. The half-hour session is set out as a high-level overview, top features, and a live demonstration, with questions taken in chat and answered at the end. 1:07 — The manual-process problem — Businesses with globally distributed teams, customers, and suppliers face growing complexity, and finance and IT departments backfill technology limitations with people. The result is manual, repetitive, low-skilled work that costs money, adds risk, hurts employee satisfaction, and keeps companies reactive instead of proactive. 2:08 — Where APRO fits and what it maintains — The APRO platform spans global invoice automation including e-invoicing regulations, AP and AR workflow automation, and bank reconciliation and cash application; this session covers the bank and cash side. Over 25 years APRO has built and maintained direct integrations with Oracle EBS and Fusion plus bank connections worldwide, all available out of the box so customers do not build or maintain them internally. 3:39 — Bank connectivity and format coverage — Off the shelf, the banking solution offers over 1,600 formats: more than 500 bank statements, over 1,000 payments, over 100 direct debits, and over 25 acknowledgements. Connection methods cited include host-to-host SFTP, APIs, EBICS, and SWIFT. 4:14 — Inbound and outbound functional scope — Inbound functionality covers bank reconciliation, cash application, and customer remittances. Outbound covers supplier payments, direct debits, refunds, and acknowledgements — the end-to-end process the presenters say non-customers most often struggle with. 5:00 — Cash application scope and remittance advices — John narrows the demonstration to cash application, focused on ACH and wire receipts, while noting the same approach applies to lockbox files, check files, and receipt files. A bank statement or lockbox line shows that a customer paid but not the detail, so a remittance advice is needed to identify which invoices are covered; any readable file from a bank or other source can be enhanced this way. 7:36 — Email monitoring and mixed-format remittances — APRO monitors an email inbox and imports remittance advices automatically in any format — Excel templates with long invoice columns, Word tables, PDFs, or remittance detail in the email body. Logic locates the transaction numbers however they appear and identifies the amount being paid, then matching rules apply the correct customer. 9:04 — Running the import and OCR — The import is kicked off manually for the demo, emptying the monitored inbox, after which documents go to an OCR engine and the returned results are run through APRO’s matching rules. The presenter notes AI was a major theme at Oracle CloudWorld and is intended for future product versions, but that matching currently runs on configurable rules and logic rather than AI. He also notes the same process serves customers loading EDI files of 35,000 to 40,000 lines weekly. 11:33 — Remittances workbench and validation — The workbench separates documents needing revalidation from validated ones, so users act only on exceptions. A validated Deep Forest Raceway remittance shows data read from the document beside values validated against Oracle — customer and open amounts both match, producing a matched status — while a longer document with 391 identified invoices illustrates the matching logic at volume. 14:14 — Loading a bank statement and matching receipts — After remittances are validated, loading a bank statement prompts APRO to check for advices that can be connected to statement lines; the load is done manually only for the demo. Of 17 statement lines, those flagged as receipts appear on a receipts tab, with rules available to exclude lines that should post directly to general ledger instead of receivables. 16:59 — Remittance-connected receipts and Oracle attachments — A receipt line whose bank description contains no payment detail is still matched to three transaction numbers, because APRO searched eRemittances for an advice matching that customer and amount and set the remittance-connected flag. The source document can be downloaded from the line and can be attached to the receipt APRO creates in Oracle, keeping the backup with the transaction. 18:33 — Receipt Management for late-arriving advices — When the payment lands before the remittance advice, Oracle Receivables sends unapplied receipts back to Receipt Management, which rechecks eRemittances for an advice that has since arrived. A Dragon Trail receipt shows as cleared but unapplied in Oracle with only a note to see the remittance advice, while APRO already proposes complete applications sourced from a matched PDF; approving the match — itself automatable — triggers a background process that calls Oracle’s APIs to update the receipt.

Home / Resources / Webinars

Demo: The APRO Banking Gateway for Oracle Financials Cloud and E-Business Suite

Key takeaways

APRO Banking Gateway targets bank reconciliation and cash application for Oracle EBS and Fusion (Oracle Financials Cloud), covering both inbound receipts and outbound payments.
APRO maintains prebuilt connections to banks and to Oracle, offering over 1,600 formats out of the box — more than 500 bank statement formats, over 1,000 payment formats, over 100 direct debit formats, and over 25 acknowledgement formats — via host-to-host SFTP, APIs, EBICS, or SWIFT.
The eRemittances module monitors an email inbox and imports remittance advices in whatever format arrives — PDF, Word, Excel, or text in the email body — running them through OCR and matching rules to identify customers, invoice numbers, and amounts.
A remittances workbench sorts imported documents into validated versus needs-revalidation buckets, so staff only handle the exceptions; matched documents are ready for use with no user action.
When a bank statement or lockbox file is loaded, APRO links receipt lines to the stored remittance advices automatically — including cases where the bank line carries no invoice detail — and can attach the source document to the receipt created in Oracle.
Receipt Management pulls unapplied receipts back from Oracle Receivables, checks eRemittances for a matching advice that arrived later, and on approval pushes the invoice applications to Oracle through Oracle’s APIs.
The presenters said AI is not currently part of the matching, which runs on configurable rules and logic, but that they intend to incorporate it in future product versions.

Overview

This 30-minute webinar, presented by Richard Brammer (director of strategic go-to-market) and John (VP of sales architecture), introduced the APRO Banking Gateway and its role in bank reconciliation and cash application for Oracle E-Business Suite and Oracle Financials Cloud. The framing argument was that finance and IT teams compensate for gaps in current technology with manual, repetitive work, which raises cost and risk, hurts employee satisfaction, and pushes organizations into reactive rather than proactive operation. APRO’s stated aim is to supply the workflows and bank connections that Oracle does not automate itself.

The opening section set out scope. APRO’s broader platform spans global invoice automation including e-invoicing regulation, AP and AR workflow automation, and bank reconciliation and cash application; this session covered only the bank and cash reconciliation side. Over 25 years the company has built and maintained direct integrations with Oracle EBS and Fusion, plus connections to banks worldwide, all available to customers out of the box rather than built in house. On the banking side the presenters cited more than 1,600 formats available off the shelf: over 500 bank statements, over 1,000 payments, over 100 direct debits, and over 25 acknowledgements, reachable through host-to-host SFTP, APIs, EBICS, or SWIFT. Functionally the product covers inbound bank reconciliation, cash application, and customer remittances, and outbound supplier payments, direct debits, refunds, and acknowledgements.

The live demonstration concentrated on cash application, and specifically on ACH and wire receipts, though the presenter noted the same approach applies to lockbox files, receipt files, and any readable file from a bank or other source. The problem addressed is that a bank statement line often shows that a customer paid but not which invoices the payment covers. APRO’s eRemittances module monitors an email inbox and imports remittance advices in mixed formats — Excel templates with long invoice lists, Word tables, PDFs, or remittance text in the email body — passing them to an OCR engine and then applying configurable matching rules to identify the customer, the transaction numbers, and the amount paid. The presenter said the same process handles both small remittances of five to twenty invoices and EDI files of 35,000 to 40,000 lines loaded weekly by other customers, and demonstrated one document containing 391 identified invoices.

In the remittances workbench, imported documents are grouped by status. Validated items required no user action: for a document from a customer named Deep Forest Raceway, the data read from the remittance appeared alongside the values validated against Oracle, with matching customer and open amounts producing a matched status. Items flagged as needing revalidation are the only ones a user touches, which the presenters described as isolating the exceptions so staff work only on what needs attention. Loading a bank statement then triggered automatic linking: of 17 statement lines, those flagged as receipts appeared on a receipts tab, with rules available to exclude lines that are receipts but should post directly to general ledger rather than to receivables. One receipt line with no payment detail in its description was still matched to three transaction numbers, because APRO searched eRemittances for an advice matching that customer and amount and set a “remittance connected” flag. The source document can be attached to the receipt APRO creates in Oracle, so the backup stays available there.

The final segment covered the reverse timing case, where the money arrives before the remittance advice. Oracle Receivables sends unapplied receipts back to APRO’s Receipt Management module, which lists receipts awaiting application and rechecks eRemittances for an advice that has since arrived. The presenter opened a receipt for a customer named Dragon Trail that showed as cleared in Oracle but unapplied, with only a “see remittance advice” note; in APRO the same receipt number was already marked complete with proposed applications sourced from a matching remittance PDF, alongside the full list of open transactions for comparison. Approving the match — a step that can itself be automated — hands the applications to a background process that calls Oracle’s APIs to update the receipt, on a schedule the presenter did not wait out during the demo. Throughout, several steps were run manually purely for demonstration purposes; the presenter noted the difficulty of demonstrating automation and confirmed that import, statement loading, and approval can all run unattended.

Chapters

0:06 — Introductions and agenda — Richard Brammer, director of strategic go-to-market, opens the webinar on APRO Banking Gateway and global payments in Oracle Financials, joined by John, VP of sales architecture. The half-hour session is set out as a high-level overview, top features, and a live demonstration, with questions taken in chat and answered at the end.
1:07 — The manual-process problem — Businesses with globally distributed teams, customers, and suppliers face growing complexity, and finance and IT departments backfill technology limitations with people. The result is manual, repetitive, low-skilled work that costs money, adds risk, hurts employee satisfaction, and keeps companies reactive instead of proactive.
2:08 — Where APRO fits and what it maintains — The APRO platform spans global invoice automation including e-invoicing regulations, AP and AR workflow automation, and bank reconciliation and cash application; this session covers the bank and cash side. Over 25 years APRO has built and maintained direct integrations with Oracle EBS and Fusion plus bank connections worldwide, all available out of the box so customers do not build or maintain them internally.
3:39 — Bank connectivity and format coverage — Off the shelf, the banking solution offers over 1,600 formats: more than 500 bank statements, over 1,000 payments, over 100 direct debits, and over 25 acknowledgements. Connection methods cited include host-to-host SFTP, APIs, EBICS, and SWIFT.
4:14 — Inbound and outbound functional scope — Inbound functionality covers bank reconciliation, cash application, and customer remittances. Outbound covers supplier payments, direct debits, refunds, and acknowledgements — the end-to-end process the presenters say non-customers most often struggle with.
5:00 — Cash application scope and remittance advices — John narrows the demonstration to cash application, focused on ACH and wire receipts, while noting the same approach applies to lockbox files, check files, and receipt files. A bank statement or lockbox line shows that a customer paid but not the detail, so a remittance advice is needed to identify which invoices are covered; any readable file from a bank or other source can be enhanced this way.
7:36 — Email monitoring and mixed-format remittances — APRO monitors an email inbox and imports remittance advices automatically in any format — Excel templates with long invoice columns, Word tables, PDFs, or remittance detail in the email body. Logic locates the transaction numbers however they appear and identifies the amount being paid, then matching rules apply the correct customer.
9:04 — Running the import and OCR — The import is kicked off manually for the demo, emptying the monitored inbox, after which documents go to an OCR engine and the returned results are run through APRO’s matching rules. The presenter notes AI was a major theme at Oracle CloudWorld and is intended for future product versions, but that matching currently runs on configurable rules and logic rather than AI. He also notes the same process serves customers loading EDI files of 35,000 to 40,000 lines weekly.
11:33 — Remittances workbench and validation — The workbench separates documents needing revalidation from validated ones, so users act only on exceptions. A validated Deep Forest Raceway remittance shows data read from the document beside values validated against Oracle — customer and open amounts both match, producing a matched status — while a longer document with 391 identified invoices illustrates the matching logic at volume.
14:14 — Loading a bank statement and matching receipts — After remittances are validated, loading a bank statement prompts APRO to check for advices that can be connected to statement lines; the load is done manually only for the demo. Of 17 statement lines, those flagged as receipts appear on a receipts tab, with rules available to exclude lines that should post directly to general ledger instead of receivables.
16:59 — Remittance-connected receipts and Oracle attachments — A receipt line whose bank description contains no payment detail is still matched to three transaction numbers, because APRO searched eRemittances for an advice matching that customer and amount and set the remittance-connected flag. The source document can be downloaded from the line and can be attached to the receipt APRO creates in Oracle, keeping the backup with the transaction.
18:33 — Receipt Management for late-arriving advices — When the payment lands before the remittance advice, Oracle Receivables sends unapplied receipts back to Receipt Management, which rechecks eRemittances for an advice that has since arrived. A Dragon Trail receipt shows as cleared but unapplied in Oracle with only a note to see the remittance advice, while APRO already proposes complete applications sourced from a matched PDF; approving the match — itself automatable — triggers a background process that calls Oracle’s APIs to update the receipt.

Questions this webinar answers

Which Oracle systems does APRO Banking Gateway connect to?

APRO maintains direct integrations with Oracle E-Business Suite and Oracle Fusion, which it has built and maintained over roughly 25 years. The integrations are provided out of the box, so customers do not have to build or maintain them in house. The cash application demonstration shown involves Oracle Receivables, including reading unapplied receipts from Oracle and writing invoice applications back through Oracle’s APIs.

How many bank formats and connection methods are supported?

The banking solution provides over 1,600 formats off the shelf: more than 500 bank statement formats, over 1,000 payment formats, over 100 direct debit formats, and over 25 acknowledgement formats. Connection methods cited include host-to-host SFTP, APIs, EBICS, and SWIFT.

What file formats can remittance advices arrive in?

The eRemittances module accepts essentially any readable format that arrives by email, including PDF files, Word documents with invoice tables, Excel templates with long columns of invoices, and remittance detail written into the body of an email itself. Documents are passed to an OCR engine, and logic then locates the transaction numbers however they are laid out and identifies the amount being paid. Beyond email attachments, lockbox files, check files, receipt files, and bank statements from any source can be used the same way.

Does the matching use AI?

No. At the time of this presentation, matching was performed by configurable matching rules and logic within the product, not by AI, with an OCR engine handling document recognition beforehand. The presenters said AI is an area of attention following its prominence at Oracle CloudWorld and that they expect the products to benefit from that technology in the future.

What happens when a bank statement line does not say which invoices were paid?

APRO uses the information it does have — such as the paying customer and the amount — to search stored remittance advices for a match. In the demonstration, a receipt line whose bank description contained no payment detail was still matched to three transaction numbers this way, and the line was marked with a remittance-connected flag showing the advice had been used for the match. The source remittance document can be downloaded from that line and can also be attached to the receipt created in Oracle so the backup stays with the transaction.

What if the payment arrives before the remittance advice does?

Receipt Management handles that case. Oracle Receivables automatically sends unapplied receipts back to APRO, where they are listed as awaiting application, and the module rechecks eRemittances for an advice that arrived later. In the example shown, a receipt appeared in Oracle as cleared but unapplied with only a note to see the remittance advice, while APRO had already matched a remittance PDF and proposed the complete set of invoice applications. Once approved, a background process calls Oracle’s APIs to apply the invoices and update the receipt.

How much manual work does a user actually have to do?

The workbench separates documents that are already validated from those needing revalidation, and users only need to act on the ones flagged for revalidation; validated documents have had their applications done by the system. In the demonstration, that meant three of the loaded remittances required attention while the rest did not. The presenters described the goal as surfacing only the items that need attention rather than requiring staff to review everything, and noted that approval steps in Receipt Management can also be automated.

Can the process handle high volumes of invoice lines?

Yes. Alongside typical remittances covering five to twenty invoices, customers load EDI files containing 35,000 to 40,000 lines on a weekly basis through the same process. One document shown during the demonstration contained 391 identified invoices handled by the matching logic.

Why were steps performed manually during the demonstration?

The email import and the bank statement load were kicked off by hand purely so the matching behavior could be shown on screen; both can run fully automated in production. The presenter noted the general difficulty of demonstrating automation, since showing it requires inserting manual steps and then explaining that they normally do not happen.

Table of Contents

Get A Demo:

Simple solutions. Powerful results. Seamlessly integrated.

Get a PairSoft Demo