Partner Implementation Guide

Estimated reading time: 4 min

The following documentation is intended to assist a Partner install and integrate ChargeLogic Payments (CL) 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 (email invoices), to the customer portal and full AR automation solutions (ARC). These steps will enable the flow of data (in both directions) between Versapay Cloud Platform (ARC) and BC when CL is installed.

Step 1: Configuring ChargeLogic Payments

In order to connect the Versapay Cloud Platform (ARC) and BC, we must first begin with the CL Payments configuration. To do so, please follow the steps listed on the “ChargeLogic Payments Setup Wizard” found here and here. If the client already has ChargeLogic Payments configured please ensure they are on the most recent version of ChargeLogic Payments as listed on the Release Notes found here.


New and existing ChargeLogic Payments customers will need to create an ARC Gateway Account and Store. This gateway is used to facilitate the creation of cash receipt journal lines from payments posted directly on the Versapay Cloud Platform (ARC). To complete the setup, you can utilize the ChargeLogic Payments Setup Wizard to help create the required Gateway Account, Store, and Terminal(s). If desired, open the Versapay Cloud Platform (ARC) gateway record and create one Gateway Account similar to the following (fig.1):


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 (ARC) Integration Activities” (fig.2) to display within the BC dashboard.



Step 2: Setup Versapay Cloud Platform (ARC) Integration within BC

Once the Payments set-up has been configured, select “Set Up Integration” from the “Versapay Cloud Platform Activities” panel. This will load the ” Versapay Cloud Platform (ARC) Integration Setup” page (fig.3)

When we first begin the setup, please ensure the “API Operating Mode” field within the “General” setup section is set to Test Mode. At this stage, the ARC Implementation Manager will provide an API Key and API Token. Apart from these three options, all other fields within the “General” section should remain unchanged.

Within the “Customers” section, please ensure the fields are configured as such:

  • Customer Integration: Bidirectional
  • Customer Watermark: The system will auto-manage this field. Please do not input anything in this section.
  • Customer Update Method: For the initial upload of customers, we will utilize the “Batch” setting in order to manually test the upload, this will be switched to “Real-Time” once testing is complete and we’ve coordinated a regular sync (more on this further below).


Within the “Payments” (fig.4) section, please ensure the toggles are configured as such:

  • Payments Integration: Bidirectional
  • Payments Watermark: As stated above, do not input anything here as the system will auto-manage this field.
  • Payments Update Method: Same as above, this toggle should be flipped to “Batch” throughout testing and “Real-Time” once testing is complete and we’ve coordinated a regular sync (more on this further below).
  • *Store No.: ARC
  • *Terminal No.: ARC

* Note: A Store represents a physical location, a department, a sales channel, or a logical division. A Store can use one or more Gateway Accounts, and multiple Stores can use one Gateway Account. Each Store has Terminals associated. Those terminals represent a unique user and are mapped to a Windows ID. If there are any questions around mapping the Store and Terminal Number please see Step 1.

Within the “Invoices and Credit Memos” section, ensure both toggles are set to “Real-Time” once the client is ready to move to Production.



Step 3: Process Log Entries and Importing Historical Data

(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) 

Return to the Business Central Dashboard (fig.5) and select “View Log Entries” from the list of Versapay Activities.


A pop-up window will appear. On this new page, select “Actions” from the menu tab, then “Mass Create Customers” (fig.6). This will ensure that we first import customers from Nav to ARC. We’ll want to begin with this upload before proceeding with the Invoices, to ensure there are contacts linked with each invoice.


Please Note: When we’re importing the customer list we’ll want to check the HTTP Status column for either a 200 or 201 code. These codes will indicate a successful upload. It is very likely, however, that a 412 error code titled “Precondition Failed” will occur. This simply indicates that there was an error on the file — most commonly, an “Invalid Email”.


If a 412 error code is encountered, please follow these steps:

  1. Highlight the selected row with the error code
  2. Click on “Actions” from the menu bar
  3. Click “Export Reply”
  4. This will open the error report in JSON or Notepad. On this page, we’ll be able to search for the line item with an error. This page will provide more insight into the potential error.
  5. If it is an “Invalid Email” error, open the Customer Card (fig.7a and 7b) to view their account and modify their information. Speaking with the client directly may assist in updating these accounts.
  6. If we’re unable to update the account:
  7. Open the Customer Card
  8. Scroll down to the “Payments” section
  9. Select “Do Not Sync with the Versapay Cloud Platform”

This will ensure the system will not try to continue to load the customer’s invoices in error.





If there is a different error and the action required is not clearly outlined, please put in a help desk ticket,



“Export Request”: Data requested from Nav to ARC

“Export Reply”: Data sent from ARC to Nav (Successful or Not Successful and Why?)


Once the customers have been successfully imported, at this point we’ll begin to import the invoices by clicking “Mass Create Open Invoices” from the same menu tab as above (fig.8).

These invoices are associated with the customers we’ve just imported.



Step 4: Update Configuration to Real-Time Updates

Once we’ve determined the customers and invoices are importing correctly, it’s time to configure Real-Time Updates.

Return to the original “Versapay Cloud Platform Setup” and change the “Update Method” fields from “Batch” to “Real-Time” (fig.9) in all applicable sections.

Note that the field “API Operating Mode” will remain as “Test Mode” until a Production ARC is ready to configure.


Please see the General Operations article for additional information and detailed descriptions of each setup configuration.

Was this article helpful?
Dislike 0
Views: 54
Go to Top