Required user roles File Integration Operator + Process Bills

Below is the general import flow for POs. Use Tipalti's PO import template to prepare your PO import file for auto-sync.

1. Once a PO is updated, all the PO lines are imported, including the ones that were not updated.
2. On the "File import" screen, as shown below, you can trace all sync attempts and view the status of the entire imported file and of a specific record in the file.
3. Tipalti takes the encrypted files from your defined input sFTP/ S3 folder and imports the data to the Tipalti Hub. Import syncs every 5 minutes. Prior to import, Tipalti checks if there are any new files in your input folder.
4.  In case the auto-sync fails:
   • If the entire file failed to import, users with the File Integration Operator role are notified by email.
   • If a specific record failed to import:
     • Tipalti creates an "Errors file" with all validation issues per record.
     • On the "File import" screen, you can view the status of the imported file and download the original file or the errors & warnings file.

     

5. Once the PO matchingThe process of matching goods and services from purchase orders to invoices (2-way matching), and receipts (3-way matching) process is complete, bills with PO data are automatically exported from the Tipalti Hub to your output folder. Export is done every hour.

PO file naming conventions

The name of the imported files includes the name of the object and the date and time of the import: {object-name} {iso time}.

For example:

• PurchaseOrder_yyyyMMdd_HHmmssfff
• PurchaseOrder_20201212_160655111

Required user roles File Integration Operator + Process Bills

Below is the general import flow for receipts (GRNs). Use Tipalti's GRN import template to prepare your GRNA goods received note (GRN) is an internal document that acts as proof of goods received to match against invoices and purchase orders. GRN, receipt, and receiving report are synonymous. import file for auto-sync.

1. Once a GRN is updated, all the GRN lines are imported, including the ones that were not updated.
2. On the "File import" screen, as shown below, you can trace all sync attempts and view the status of the entire imported file and of a specific record in the file.
3. Tipalti takes the encrypted files from your defined input sFTP/ S3 folder and imports the data to the Tipalti Hub. Import syncs every 5 minutes. Prior to import, Tipalti checks if there are any new files in your input folder.
4.  In case the auto-sync fails:
   • If the entire file failed to import, users with the File Integration Operator role are notified by email.
   • If a specific record failed to import:
     • Tipalti creates an "Errors file" with all validation issues per record.
     • On the "File import" screen, you can view the status of the imported file and download the original file or the errors & warnings file.

     

GRN file naming conventions

The name of the imported files includes the name of the object and the date and time of the import: {object-name} {iso time}.

For example:

• GRN_YYYYMMDD_HHMMSSZ

• GRN_20201212_160655111

Required user roles File Integration Operator + Payer Administration

Below is the general import flow for GL accounts. Use Tipalti's GL accounts import template to prepare your GL accounts import file for auto-sync.

1. Once a GL account is updated, all the GL account lines are imported, including the ones that were not updated.
2. On the "File import" screen, as shown below, you can trace all sync attempts and view the status of the entire imported file and of a specific record in the file.
3. Tipalti takes the encrypted files from your defined input sFTP/ S3 folder and imports the data to the Tipalti Hub. Import syncs every 5 minutes. Prior to import, Tipalti checks if there are any new files in your input folder.
4.  In case the auto-sync fails:
   • If the entire file failed to import, users with the File Integration Operator role are notified by email.
   • If a specific record failed to import:
     • Tipalti creates an "Errors file" with all validation issues per record.
     • On the "File import" screen, you can view the status of the imported file and download the original file or the errors & warnings file.

     

GL accounts file naming conventions

The name of the imported files includes the name of the object and the date and time of the import: {object-name} {iso time}.

For example:

• GlAccount_YYYYMMDD_HHMMSSZ

• GlAccount_20201212_160655111

Required user roles File Integration Operator + Payer Administration

Below is the general import flow for custom field values. Use Tipalti's custom field value import template to prepare your custom field import file.

1. Custom fields are separated so that each custom field is a different object.

2. If a specific custom field (e.g., department) is in the middle of the import process, another file of the same type cannot be manually or automatically imported in parallel, but other custom fields can.

3. Once a custom field is updated, all the custom field values are imported, including the ones that were not updated.
4. On the "File import" screen, as shown below, you can trace all sync attempts and view the status of the entire imported file and of a specific record in the file.
5. Tipalti takes the encrypted files from your defined input sFTP/ S3 folder and imports the data to the Tipalti Hub. Import syncs every 5 minutes. Prior to import, Tipalti checks if there are any new files in your input folder.
6.  In case the import fails:
   • If the entire file failed to import, users with the File Integration Operator role are notified by email.
   • If a specific record failed to import:
     • Tipalti creates an "Errors file" with all validation issues per record.
     • On the "File import" screen, you can view the status of the imported file and download the original file or the errors & warnings file.

     

Custom fields file naming conventions

The name of the imported files includes the name of the object and the date and time of the import: {object-name} {iso time}.

For example:

• Department_YYYYMMDD_HHMMSSZ

• Department_20201212_160655111

Required user roles File Integration Operator + Payer Administration

Below is the general import flow for units. Use Tipalti's payment terms import template to prepare your units import file.

1. If a payment terms file is in the middle of the import process, another file of this object cannot be manually or automatically imported in parallel.

2. Once a payment terms file is updated, all the payment terms are imported, including the ones that were not updated.
3. On the "File import" screen, as shown below, you can trace all sync attempts and view the status of the entire imported file and of a specific record in the file.
4. Tipalti takes the encrypted files from your defined input sFTP/ S3 folder and imports the data to the Tipalti Hub. Import syncs every 5 minutes. Prior to import, Tipalti checks if there are any new files in your input folder.
5.  In case the import fails:
   • If the entire file failed to import, users with the File Integration Operator role are notified by email.
   • If a specific record failed to import:
     • Tipalti creates an "Errors file" with all validation issues per record.
     • On the "File import" screen, you can view the status of the imported file and download the original file or the errors & warnings file.

     

This feature is currently supported for File Integration payers only.

Payment terms file naming conventions

The name of the imported files includes the name of the object and the date and time of the import: {object-name} {iso time}.

For example:

• PaymentTerms_YYYYMMDD_HHMMSSZ

• PaymentTerms_20201212_160655111

Required user roles File Integration Operator + Payer Administration

Below is the general import flow for units. Use Tipalti's units import template to prepare your units import file.

1. If a unit record is in the middle of the import process, another file of this object cannot be manually or automatically imported in parallel.

2. Once a unit is updated, all the units are imported, including the ones that were not updated.
3. On the "File import" screen, as shown below, you can trace all sync attempts and view the status of the entire imported file and of a specific record in the file.
4. Tipalti takes the encrypted files from your defined input sFTP/ S3 folder and imports the data to the Tipalti Hub. Import syncs every 5 minutes. Prior to import, Tipalti checks if there are any new files in your input folder.
5.  In case the import fails:
   • If the entire file failed to import, users with the File Integration Operator role are notified by email.
   • If a specific record failed to import:
     • Tipalti creates an "Errors file" with all validation issues per record.
     • On the "File import" screen, you can view the status of the imported file and download the original file or the errors & warnings file.

     

This feature is currently supported for File Integration payers only.

Units file naming conventions

The name of the imported files includes the name of the object and the date and time of the import: {object-name} {iso time}.

For example:

• Units_YYYYMMDD_HHMMSSZ
• Units_20201212_160655111