Overview

The following documentation is intended to assist a Partner to install and integrate Versapay Payments and Business Central (BC) with the Versapay Cloud Platform (ARC) System. This allows organizations that use any portion of the Versapay Cloud Platform, from the PayNow (electronic invoicing), customer portal, full AR automation solutions (ARC), or e-commerce transactions. These steps will enable the flow of data (in both directions) between Versapay Cloud Platform (ARC) and BC when Versapay Payments version 4.2.2 is installed.

Configuring Versapay Payments

In order to connect the Versapay Cloud Platform (ARC) and BC, we must first begin with the ChargeLogic Payments configuration. You will create a VPYNETWORK Gateway Account and related Store. The easiest way to do this is to use the “ChargeLogic Payments Setup Wizard” and enter the API TOKEN and API KEY in the setups. For step-by-step instructions on setting up via the wizard, review the document found here. For new ChargeLogic implementations, this is the recommended approach.

If you choose to set this up manually, you’ll need to ensure you fully setup the Gateway, Gateway Account, Synchronization Setups, Store, Terminals, and Terminal Account IDs with the relevant information.

Enabling ChargeLogic Payments will introduce a new set of activities within the following role centers:

• Accounts Receivable Administrator (9003)

• President – Small Business (9020)

• Business Manager (9022)

• Credit and Collections Manager (36603)

Once configured, this will also introduce the “Versapay Cloud Platform (Collaborative AR) Integration Activities” to display within the BC dashboard.

Set Global Settings for Versapay Cloud Platform (Collaborative AR) Integration within BC

Once the Payments setup has been configured, select “Set Up Versapay Cloud Platform” from the “Versapay Cloud Platform Activities” panel. This will load the “Versapay Cloud Platform Setup” page shown below.

Fill in the Setup fields based on the descriptions below:

• Division Mapping – Specifies the method of determining the Division when sending invoices and credit memos to the Versapay ARC system. The options are “Do Not Use”, “Use Company”, “Entered Value”, “Global Dimension 1” & “Global Dimension 2”. Often the ARC system requires the use of a division, especially with invoices and credit memos. Consult with the ARC implementation staff to determine if a division is

• Preset Division Value – Specifies the static value to send as the division to the Versapay ARC system when Division Mapping is set to Entered

• New Customer Template – Specifies which template to use for creating a new Customer record within Business Central.

• Non-Designated Customer No. – Specifies the customer to use if payments are received from the Versapay Cloud Platform where the customer has not been indicated (e.g. from an initial payment or lockbox files). It is recommended that this customer have the field “Do not Sync with Versapay Cloud Platform” checked on their related customer

• Prefix / Suffix Usage – This field is being deprecated and should not be used.

• Prefix / Suffix Value –This field is being deprecated and should not be used.

Additional Features/Actions

Update Customers – Use this action to mark which customers you wish to update the Do Not Sync to Versapay Cloud Platform field on. This means Ledger Entries created after this change will not get synched.

Duplicate E-mail Check – Use this action to find any duplicate e-mail addresses for Contacts from the same Customer. The Versapay Cloud Platform uses the e-mail address as a unique record, where the ERP does not. This causes an issue when multiple contacts have the same email, as the integration can’t identify which record to associate transactions to. This duplicate check allows you to find and correct bad data.

Reference Field Setup – This setup allows you to add up to four (4) Reference fields that are available in the Versapay Cloud Platform. First, you select the table you wish the additional data item to be pulled from.  Your choices are Posted Sales Invoice, Posted Sales Credit Memo, Posted Service Invoice, Posted Service Credit Memo and Finance Charge Memo.  Next, you identify which of the Reference fields you are attempting to map to. Lastly, you choose the Field No. from the table you selected to be mapped to the respective Reference Field.

Convert to Versapay Tokens – Use this action to move from Encrypted Storage or Remote Storage to Tokenization. See the Converting to Versapay Tokens guide for more information.

Mass Create – Use this action to create and send data from the ERP to the Versapay Cloud Platform. Only use this action if you are sending less than 100 records at a time. See additional details below regarding this action.

Create Job Queue – Use this action to create a Job Queue entry that will send/retrieve updates from the Versapay Cloud Platform at your desired interval. If you choose not to set this up, you will need to manually retrieve using the action on your Role Center.

Mass Create Records

Once the integration has been configured, it’s now time to send data from the ERP up to the Versapay Cloud Platform. This data includes Customers, Invoices/Credits, Wallet entries, and Divisions. From the Actions Menu, choose Actions > Mass Create.

Select the appropriate record for the data you are trying to send up and optionally set any filters you wish to use. Clicking OK will send the data to the Versapay Cloud Platform Log Entries page, where they will be processed.

If you are sending more than 100 records, you should be using the Bulk Upload Action which send a flat file of data, rather than individual API calls. Failing to use the Bulk Upload will likely cause the upload to time out.

Helpful Tip

Make sure the Customer upload is done first, as that record needs to exist before any Invoices/Credits or wallet entries can be associated with it.

(If you are using the Versapay Cloud Platform for PayNow (email invoicing) only, you may or may not choose to send historical data to the platform. Sending open invoices will result in the creation and sending of a corresponding email(s) to the customer. Exclusive PayNow users may simply establish the data connection as outlined above and send new invoices only to the platform for delivery to the customer)

If you run into issues, or are getting errors in the Last Error Message field of the Open Log Entries, please review the Troubleshooting Guide.