All Collections
Integrations with Fyle
NetSuite
How to configure the Name field for Corporate Card expenses exported as Journal Entries in Netsuite?
How to configure the Name field for Corporate Card expenses exported as Journal Entries in Netsuite?

This article explains how you can select the name to be posted in the name field of journal entries exported to Netsuite for CCC expenses

Kamalini Yuvaraj avatar
Written by Kamalini Yuvaraj
Updated over a week ago

The name field of Journal Entries exported from Fyle to Netsuite can be customized for Corporate Credit Card expenses from the integration page. The name field in Netsuite is a searchable field and can be used to generate vendor reports or to identify the employee a corporate card expense is associated to. Based on your requirement, you can choose to export the vendor name or the employee name to Netsuite.

Following are the steps to configure the above setting:

1. Log in to your Fyle-Netsuite Integration with your admin credentials.

2. Go to Configurations -> General. If your Corporate Card export setting is Journal Entry, you'll be able to see the setting Name in Journal Entry (CCC)
โ€‹

Based on your requirement, you can select the Merchant name or the Employee name.

Note: Merchants in Fyle are Vendors in Netsuite; Employees in Netsuite can be Employees or Vendors in Netsuite. For posting Employee name, based on how your employees are set up in Netsuite (e.i. as Employee or Vendor), Fyle will post the name of the respective employee's record in Netsuite.

3. Click on Save.

Going forward, the Corporate Card expenses exported as Journal entries will carry the name of the vendor or the employee based on your configuration.

An example of a CCC expense exported as Journal Entry with Employee Name

(Even when exporting the employee name, you can capture the vendor/merchant information in the Memo field for reference)

An example of a CCC expense exported as Journal Entry with Vendor Name

If you need any assistance in setting this up, feel free to reach out to us on [email protected]

Did this answer your question?