Synchronization

• Tipalti supports only payment terms that depict a number of days after the invoice date, thus only terms of the format shall be synced.
• Only payment terms that were synced from BC may be used on payees (otherwise their sync will fail).

• Existing vendors are synced from BC to Tipalti during the first time sync.
• Vendors in BC have a Vendor Posting Group (VPG) field which indicates their AP account. This should be configured in Tipalti as a custom field of type list, and mapped in the configuration wizard, or else the default VPG will be set in BC.

• The payee’s selected payment method is synced to BC. If the payment method wasn’t selected, the payment method configured as default in BC will be set in BC. If the payment method is CASH - BC will automatically mark the approved bill (posted purchase invoice) as ‘Paid’ in BC, and the actual payment details won’t be synced.

• In BC, ‘location’ is a native field and can be mapped as a custom field of type list on bill/VC header/ lines.
• Dimensions are read from BC to Tipalti and may be mapped with Tipalti’s custom fields.
• The chosen custom field value on a bill or VC header / line is synced to BC, as part of the invoice’s sync.

• Custom field value deletions and status change (active/inactive) in BC are not synced to Tipalti. Thus, if you delete a value in BC you need to manually delete it in Tipalti, under Administration > General > Custom fields.

• Project and task fields are mapped as custom fields in Tipalti.

• Bills in the following statuses are synced automatically from Tipalti to BC as posted purchase invoices:
  • Pending payment
  • Scheduled for payment
  • Submitted for payment
  • Paid
  • Partially paid
• Currently, syncing bills before approval is not available.
  • Edit post approval is supported (according to the bill’s settings), but this will be synced to BC same as retract approval, since BC doesn’t allow editing posted invoices.
  • Retract approval is supported. The bill will be reversed in BC (by applying a purchase credit memo to it) and a new invoice with the original invoice number with a suffix will be created, with the updated information, once it is reapproved.

Invoice files can be automatically synced to BC and downloaded from within the bill record under Incoming Document Files.

To sync bill invoice files:

• In the Sync Wizard screen, under Sync Preferences, check the Sync bill image box.

  

Vendor credits are synced as ‘Posted Purchase Credit Memos’ to BC, similar to bills, with the exception of:

• Voiding and updating vendor credits is currently not supported: the purchase credit memo should be canceled manually in BC.

• Payment are synced from Tipalti to BC.
• Currently only payments paid from accounts with the same currency as the payment will be synced to BC (No payer Fx). Multi-currency payments with Fx must be entered manually to BC.
• Void payments are not synced, thus a voided payment must be handled manually in BC (E.g., a rejected payment).

• GLA general ledger (GL) is used for recording transactions related to business assets, liabilities, equity, revenue and expenses. and bank accounts sync from BC to Tipalti.
• Currently all accounts (excluding bank accounts and AP accounts) are displayed on the bill line expense accountThe general ledger (GL) account that is debited for the payment amount drop down.
• Bank accounts with no currency are set in Tipalti with the company’s base currency from BC.
• A deletion of a GL account or bank account in BC is not synced to Tipalti, but blocked accounts aren’t synced and will be updated as inactive in Tipalti if already synced.

This section details the mapped fields between Tipalti and BC.

Mapped fields

Mapped fields

* If the currency from BC is empty - the company’s currency in the ERP will be used.

Mapped fields

*Only synced during the first time sync from BC, since the numbering convention can be set in BC and must be unique.

**When syncing a payee from Tipalti, the name is determined according to the payee entityAn entity can be a subsidiary, division, business unit, brand, etc. of your organization. Entities can have similar or different AP processes and workflows. type:

• Company: the Name will be equal to the company name

• Person: first + middle + last name (whichever exists)

When syncing a payee into Tipalti - the same logic will apply in reverse (for person - first name will contain the first word from the name field, and last name will contain the last word from the name field).

Mapped fields

Vendor credits are synced to BC as credit memos. The mapping is identical to bills.