Overview: Prendio - Sage Intacct Connector

This document summarizes the integration activity between Prendio and Sage Intacct using a connector

The Sage Intacct Connector for Prendio allows Prendio to create vendors and vendor bills in Sage Intacct, while also keeping track of the payment status of any bills pushed over. The process of pushing items over will require the act of mapping some objects in Prendio to the corresponding objects in Sage Intacct.

  1. Integration Activity
  2. Mapping Overview
  3. Multi-Entity Company Considerations
  4. Authentication Mechanism
  5. Additional Data Considerations
  6. Support for Sage Intacct and Payment Services

 


 

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 processed 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 bill 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 Sage Intacct objects, Prendio must have the System IDs of the Sage Intacct objects. Prendio uses a “Get” transaction for payment terms and any enabled accounting segment for pulling the system IDs into Prendio.

 

 

Get Suppliers (Pull Activity)

For the purpose of mapping Prendio Suppliers to the corresponding Sage Intacct Vendors, Prendio must have the System IDs of the Sage Intacct Vendors. Prendio uses “Get” transactions that pull the system IDs into Prendio.

 

 

 

Create Supplier / Update Supplier (Push Activity)

If a vendor does not exist in Sage Intacct when mapping suppliers for a bill push, the Prendio Let’s Align feature is able to create a Sage Intacct Vendor and automatically map the supplier to it. Additionally, the Prendio Let’s Push process has an option to update the Sage Intacct Supplier if a remit address change is detected.

In both situations, Prendio pushes the following vendor data:

  • Company Name

  • Billing/Remit Address

  • Tax Number
  • Payment Term (based on the default payment term in the Prendio Supplier profile)

  • Currency (based on the default currency in the Prendio Supplier profile)

  • Entity ID (if connector is configured to push Vendor to a specific entity)

 

 

Create AP Bill (Push Activity)

During the Let’s Push process, Prendio will send the following data to create an AP Bill in Sage Intacct:

  • Bill Header

    • Intacct Vendor ID
    • Invoice Number

    • Invoice Date

    • Payment Term

    • Currency (Transaction Currency and Base Currency, as required by Sage Intacct)

    • Purchase Order (PO) Number

    • Entity ID (if connector is configured to push AP Bills to a specific entity)
  • Bill Line Detail (each line for the bill)

    • Line Description

    • Line Amount

    • Intacct Department ID

    • Intacct GL Account ID

    • Intacct Project ID

    • Intacct Channel ID

    • Intacct Entity/Location ID

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

 

 

When a bill is successfully pushed to Sage Intacct, it is moved to the Unpaid Bills tab in Prendio and monitored for bill payment.

 

 

Get Bill Payments (Pull Activity)

While Prendio users can manually request from the Unpaid Bills tab, Prendio has a nightly job that queries Sage Intacct for the bill payment status for any bill in the Unpaid Bills tab. If Sage Intacct indicates there that the AP Bill has an associated Bill Payment, Prendio collects the following information and moves the bill to the Paid Bills tab:

  • Payment Date

  • Amount of associated payment

  • Check / Payment #
 

 

Note: Prendio also uses the Get Bill Payments integration point as a way to detect and prevent the creation of duplicate invoices under one Sage Intacct Vendor.

 


Mapping Overview

 

The Prendio - Sage Intacct Connector handles the data exchange activity. This table shows the default mapping of Prendio Segments to Sage Intacct Segments:

 

Intacct Segment Prendio Segment
Department Department
GL Account GL Account
Project Project
Channel Class
  • Entity (Parent)
  • Location (Child)
Location


Notes
:

  • If the Sage Intacct company is multi-entity enabled, that can impact how the Location segment is used in Prendio. See the Multi-Entity Company Considerations section for more information.
  • While a "Custom" segment is shown on the ERP Integration page in Prendio, that is not currently a mappable object between Prendio and Sage Intacct.

 

This table shows the mapping of Prendio Suppliers and Payment Terms to the corresponding objects in Sage Intacct:

 

Intacct Object Prendio Object
Vendor Supplier
Term Term

 

 


 

Multi-Entity Company Considerations

 

The Prendio - Sage Intacct Connector supports Intacct companies that are multi-entity enabled. However, there are considerations based on how you want AP Bills and Vendors created in Intacct.

There are three different "sync strategies" available when it comes to creating AP Bills and Vendors, depending on if you want them created under a specific entity or in the top level of the Intacct company.

  • Top Level AP Bills and Vendors
    • Prendio creates AP Bills and Vendors at the top level of your Intacct company.
    • The Location segment in Prendio must be enabled for this sync strategy, due to requirements from Intacct. This means a Location field will be available to select in Prendio carts and is a mappable field when pushing bills.
  • Entity Level AP Bills and Vendors
    • Prendio creates AP Bills and Vendors under a specified entity in the Intacct company.
    • With this strategy, you must provide the Prendio technical team with the Entity ID to which you want AP Bills and Vendors created.
    • The Location segment in Prendio is optional. If used, you can only map to Locations setup under the specified Entity ID in Intacct.
  • Entity Level AP Bills, Top Level Vendors
    • Prendio creates AP Bills under a specified entity in the Intacct company and Vendors at the top level.
    • With this strategy, you must provide the Prendio technical team with the Entity ID to which you want AP Bills created.
    • The Location segment in Prendio is optional. If used, you can only map to Locations setup under the specified Entity ID in Intacct.
    • This strategy might be preferred if you plan to integrate Sage Intacct with a payment service such as Bill.com.

 

 


 

Authentication Mechanism

 

The Sage Intacct Connector for Prendio uses a functional user ID to authenticate with the Sage Intacct Company ID. 

You must provide the Prendio technical team with the Company ID, username, and password that will be saved under [AP Management > General > Accounting] for the integration. These fields are only available to the Prendio technical team and not to company-level Prendio users.

A Sage Intacct admin must also configure a Web Services Authorization with a "Sender ID" that the Prendio technical team will provide at the time of implementation.

 

 


 

Additional Data Considerations

 

Currency

When Prendio sends an AP Bill to Sage Intacct, it sends the bill with the same currency as the corresponding PO in Prendio.

In order to support a currency in Sage Intacct that will potentially be referenced by Prendio, you will need the help of an Intacct admin to setup the following:

 

 


 

Support for Sage Intacct and Payment Services

 

While Prendio integrates with Sage Intacct, the Prendio team does not directly support Intacct itself. For Intacct problems and questions unrelated to the integration with Prendio, the following resources are available:

 

It is possible to integrate Sage Intacct with payment services such as BILL. As long as that service syncs the payment info back to Intacct for AP Bills, the Prendio bill payment sync process will continue working without a problem. If there is a problem with the integration between Intacct and your payment service, you need to contact the support team for the payment service.