Overview: Prendio - Oracle Fusion Connector

Fusion Segment	Prendio Segment
Department	Department
Account	GL Account
Project	Project
Class	Class
Location	Location
Cost Center	Cost Center
Product	Product

 

Note: Department and GL Account are required accounting segments in Prendio.

 

This table shows the mapping of Prendio Suppliers and Terms to the corresponding objects in Oracle Fusion:

 

Fusion Object	Prendio Object
Vendor	Supplier
Payment Term	Term

 

 

---

 

Integration Activity

Prendio follows the same general workflow for ERPs when it comes to pushing bills and syncing on their payment status. When vouchers are completed and ready to push, a company can push them in Prendio under the AP Push tab.

After a successful push to an ERP, Prendio will keep the voucher in the Unpaid Bills tab while periodically checking the ERP for the bill status. Once the bill is paid, Prendio moves the bill to the Paid Bills tab, marking the end of the integration workflow for that bill.

 

 

Get Accounting Segments and Payment Terms (Pull Activity)

For the purpose of mapping Prendio accounting segments and payment terms to the corresponding Fusion objects, Prendio must have the System IDs of the Fusion objects. For payment terms and any enabled accounting segment, Prendio uses a Fusion Report Service Endpoint that pulls the system IDs into Prendio.

 

 

For the purpose of mapping Prendio Suppliers to the corresponding Fusion Vendors, Prendio must have the System IDs of the Fusion Vendors. Prendio uses a Fusion Report Service Endpoint that pulls the system IDs into Prendio.

 

 

Note: While the capability is available with other ERP Connectors, it is not possible to send new vendors to Oracle Fusion using Let's Align or update vendor address information during Let's Push.

 

 

Push Invoice with Attachment (Push Activity)

During the Let’s Push process, Prendio will use a Fusion Interface Service Endpoint to send invoices over.

 

 

The invoices contain the following information:

• Invoice Body

  • Invoice Number

  • Invoice Amount

  • Invoice Date

  • Fusion Vendor ID
  • Currency ISO Code
  • Description / Memo (References Prendio PO # and Voucher #)
  • Fusion Payment Term ID
  • Received Date
  • Requester Name
  • Purchase Order Number

• Invoice Line Detail (each line for the bill)

  • Line Description

  • Line Amount

  • Invoiced QTY
  • Unit Price
  • Account Distribution Code Combination that contains the Fusion IDs for any enabled segments between Prendio and Fusion, including but not limited to:

    • Department

    • GL Account
• AP Push PDF Attachment (based on setting in Prendio)

Note: A Fusion Interface Service Endpoint is used to validate acceptable Account Distribution Code Combinations used in invoices based on constraints configured in Oracle Fusion.

 

Successfully pushing invoices to Oracle Fusion results in:

• The invoices being available to review in Oracle Fusion for import into the ledger.
• The corresponding Prendio Vouchers being moved from the AP Push tab to the Unpaid Bills tab in Prendio and monitored for bill payment.

 

Get Payments (Pull Activity)

Prendio uses a Fusion Interface Service Endpoint to check on payment information for invoices in Fusion. While Prendio users can manually request bill payment updates from the Unpaid Bills tab, Prendio has a nightly job that queries Oracle Fusion for the payment status of any bill in the Unpaid Bills tab.

If Fusion indicates that the invoice has an associated Bill Payment, Prendio collects the following information and moves the voucher from Unpaid Bills to the Paid Bills tab:

• Payment Date

• Amount of associated payment
• Payment Currency
• Check / Payment #

 

Note: Prendio also uses a similar Fusion Interface Service Endpoint as a Duplicate Bill Check when you are pushing invoices.

If Fusion indicates that the invoice number already exists for the specified vendor, Prendio will not push the bill to Fusion. Instead, it will associate the voucher to the existing invoice in Oracle Fusion and move that voucher to the Unpaid Bills or Paid Bills tab.

 

 

---

 

Authentication Mechanism

Prendio connects to an Oracle Fusion instance URL and authenticates with a username and password. Connectivity to the Oracle Fusion endpoints occur with SSL encrypted connections.

The Prendio Technical team must save the provided login information for a Prendio company under [AP Management > General > Accounting] for the integration. These fields are not available to company-level Prendio users.

 

 

---

 

Additional Data Considerations

 

Currency

Prendio sends currency to Oracle Fusion during the Push Invoice operation. The currency is sent over as a three-character ISO code, such as USD for “US Dollars” and EUR for “Euro”.

 

Business Unit / Site

The Business Unit and Site codes to be used with Fusion must be provided to Prendio, otherwise it will not be possible for the integration points to work correctly. These values are required when pushing invoices.

The Prendio Team needs to update server infrastructure with the Business Unit and Site values to be used by the Oracle Fusion Connector. If your company anticipates needing to rename or change either value in Oracle Fusion, please reach out to Prendio Technical Support in advance of that change to avoid disrupting the integration.

 

 

---

 

Support for Oracle Fusion and Payment Services

 

While Prendio integrates with Oracle Fusion, the Prendio team does not directly support Fusion itself. For Fusion problems and questions unrelated to the integration with Prendio, please contact your Fusion consultant or Oracle Support.

It might be possible to integrate Oracle Fusion with outside payment services. As long as that service syncs the payment info back to Fusion for invoices, the Prendio bill payment sync process will continue working without a problem. If there is a problem with the integration between Oracle Fusion and your payment service, you need to contact the support team for the payment service.