Synchronization

• Payee payment terms sync bidirectionally (and payer payment terms sync from NetSuite to Tipalti).
• Inactive vendors in NetSuite are marked as suspended in Tipalti and vice versa.
• Vendors that are deleted in NetSuite are closed in Tipalti.

Tipalti to NetSuite

Bills in the following statuses are synchronized automatically from Tipalti to NetSuite:

• Scheduled for payment
• Submitted for payment
• Paid
• Partially paid

Payers can choose to sync bills from Tipalti to NetSuite before or after bill approval. Syncing before approval syncs bills in "Pending approval" status, which allows payers to see their bills earlier in the ERP.

Currently, syncing bills before approval is not available for payers using the PO Matching feature.

When a synchronized bill is "deleted" or "disputed", it is removed from NetSuite. If the bill is "un-deleted" or "undisputed", it is re-created in NetSuite.

Bills paid manually

The GLA general ledger (GL) is used for recording transactions related to business assets, liabilities, equity, revenue and expenses. account type (Bank/ Credit card) and transaction date for bills marked as paid manually are synced to the payer's ERP under the relevant bill payment.

Bills marked as prepayment

You can mark a bill for prepayment using Tipalti's prepayment feature, which represents a superior alternative to NetSuite's prepayment module (this feature replaces the need to use NetSuite's prepayment module). Refer to Prepayments for PO-backed bills for details.

Bill refcode

You can map the bill refCode to a Free Text custom field in NetSuite. this value is useful for tracking and reconciliation purposes in NetSuite.

NetSuite to Tipalti

• Sync of approved bills. After sync further updates should be done in Tipalti.
• PO lines marked as "Closed" in the ERP are synced to Tipalti and will not be available for PO matchingThe process of matching goods and services from purchase orders to invoices (2-way matching), and receipts (3-way matching).

A vendor credit is created for a payee's transaction fee and is linked to the payee's bill. When the payment is submitted to Tipalti, both vendor credit and bill are synced to NetSuite.

When the payment is paid:

1. If the payment is a NetNow payment, the payee NetNow fee is added as a line on the fee vendor credit.
2. If the payee's payment is subject to withholding, a different vendor credit is created for the withholding amount and is linked to the bill.
3. All vendor credit information is synchronized to NetSuite and a bill payment is created.
4. If there is a payee foreign exchange (FXForeign exchange) fee, it is added to the bill payment.

Bill = $1000

Vendor credit 1:

    Payee transaction fee = $3
    Payee NetNow fee = $2

Vendor credit 2: Withholding amount = $4
Payee FX fee = $1
 
Net amount (received by payee) = $990

Bill payment = Net amount + Payee NetNow fee + Payee FX fee = $993

Expense transactions are synchronized as actual Expense Reports to employees, including sync of expense categories, employees, expense attachments, and expense reports (including Tax codeA code for the type of tax applied to a bill line (e.g., VAT-UK) and Tax amount information, and VAT for mileage).

Card Transaction attachments (such as receipts) are synchronized to NetSuite. This integration is automatically enabled for payers syncing Card transactions.

All payments in Tipalti that were added, updated or deleted since the last synchronization are collected and synchronized to NetSuite.

Mapped fields

All GL accounts in NetSuite that were added, updated or deleted since the last synchronization are collected and synchronized to Tipalti.

Mapped fields

All vendors that were "added", "updated" or "deleted" since the last synchronization are collected and synchronized to NetSuite, Tipalti, or both systems.

Mapped fields

All bills that were "added", "updated" or "deleted" since the last synchronization are collected and synchronized from Tipalti to NetSuite.

Mapped fields