Articles in this section

Setup

Required user role Manage Integrations

Preparation

In BC, create a vendor for Tipalti transaction fees so that these fees will show as paid bills under this vendor.

  1. Click the "Purchasing" button and select "Vendors".

  2. Select "New".

  3. Enter the vendor’s name, in the invoicing section select the vendor posting group and Gen. Bus. Posting Group according to your liking.

  4. Select a payment method other than “CASH”. You may enter additional info according to your needs.

 

If you want to map your BC location or dimension fields to custom fields in Tipalti, you will need to Add custom field from type “List”, and create a value with ID = -1 and value = -1 to indicate that all values shall be added. Delete this value after the actual values are synced for the first time.

Business Central uses a Description 2 field in your purchase invoice lines and purchase credit memos. Description 2 for purchase invoice lines are mapped in Tipalti’s bill lines; for purchase credit memo lines, they’re mapped in Tipalti’s vendor credit lines as custom fields.

These may be applied to the bill/VC header.

In addition, you should create a “Vendor posting group” custom field of type “List” for the “Payees” record type.

Integration configuration

Complete the following steps to configure the integration with BC in Tipalti's Tipalti Hub. Click each tab to view the how-to steps.

The following instructions are for first-time authentication.

  1. In Tipalti Hub, go to Administration > API integration > Apps.
  2. At the top right of the screen, click "Add app" and select "Business Central".
  3. The "Configure Business Central app" is presented. Click "Start setup".
  4. You will be presented with a pop-up with BC's environment fields.

  1. Fill in your BC details. The tenant ID is the GUID appearing in the “Help and support” page, under the “Report a problem” section.

  1. Click next and you will be prompted to sign-in to your BC setup. If you already signed in from your browser, the log-in will occur in the background.

  2. Once you successfully logged in, your browser will navigate back to Tipalti and continue with the first time configuration process.

Select the relevant Tipalti payer entityAn entity can be a subsidiary, division, business unit, brand, etc. of your organization. Entities can have similar or different AP processes and workflows. and the relevant BC company to map to it. If any of these contain only one option, the field will appear disabled.

You can sync one Tipalt payer entity to one BC company per each Tipalti Payer.
Once you complete the first time sync for a payer, you won’t be able to modify this mapping.


  1. Choose the objects you’d like to sync with BC.

  2. Note that syncing bills w.o. syncing vendors may cause sync failures if new vendors are created in Tipalti and not synced to BC, and syncing payments without bills may cause syncing issues as well.

Posting date field of the bill/VC header can be mapped as a custom field in Tipalti.

  1. Click the “+Add field” button according to the record type you want to map the custom field to (Bill or Vendor credit), in a later phase it will be possible to map dimensions to the bill / VC lines, and vendors.

  • You will only be able to add a new field if there are unmapped custom fields in Tipalti and unmapped dimensions/location or native fields in BC.

  • Fields that are mapped automatically in the standard integration are not available here for mapping.

  1. Select the dimension or field name in BC from the drop down under Business Central field.

  2. Select the corresponding custom field name in Tipalti, from the drop down under the Tipalti field.

    3. Business Central uses a Description 2 field in your purchase invoice lines and purchase credit memos. Description 2 for purchase invoice lines are mapped in Tipalti’s bill lines; for purchase credit memo lines, they’re mapped in Tipalti’s vendor credit lines as custom fields.

  3. Repeat the previous 3 steps for each custom field you want to map.

  4. To delete a row, hover over the mapping line and click the “delete” icon on the right side of the row and confirm the deletion.

  5. When you are finished mapping fields, click "Next" to be directed to the Accounts screen.

  6. To delete a row, hover over the mapping line, click Delete iconon the right side of the row, and confirm the deletion.

Map existing GLA general ledger (GL) is used for recording transactions related to business assets, liabilities, equity, revenue and expenses. and bank accounts between Tipalti and Business Central.

Tipalti/ BC accounts mapping

  1. A list of Tipalti accounts displays. Adjacent to each Tipalti account name, begin typing the BC account to which Tipalti payments from that account will be synchronized, then select it from the populated list.

  2. Click "Next".

Default expense account

  1. In the "Default expense accountThe general ledger (GL) account that is debited for the payment amount" field, begin typing the default expense account for bills, then select it from the populated list.

  1. Drag and drop the payment methods used in BC into the corresponding payment method in Tipalti.

  2. Note that you may not necessarily be utilizing all available Tipalti payment methods, so in such a case you shouldn’t map all, but if a vendor is created with a payment method that isn’t mapped, it won’t sync to BC.

If the Cash payment method is selected, BC will automatically mark the synced bills as paid.
If no payment method is selected, BC sets the payment method to Cash by default (unless configured differently in BC).

  1. Select the payment journal you would like the payments synced from Tipalti to be posted into.

It is advised to create a new payment journal for Tipalti, since the integration posts the whole journal for each payment.

The summary screen shows the objects that will be synchronized with BC. You will be required to confirm the start of the first sync with BC.

  1. Click "Confirm" to start off the first sync with BC. You will be directed to the main apps screen.
  2. Upon first sync completion, the status of the integration changes according to the result.

  1. A payment term for a payee should be one of the terms synced from BC (or the payee will fail to sync).

  2. Select a default from the newly synced values once the first sync was completed successfully.

Only payment terms that were synced from BC will sync, thus consider removing other payment terms.