This article explains how data from NetSuite is imported into Fyle. You’ll understand what types of accounting dimensions are supported, how import behavior works, and key considerations for a smooth setup.
Prerequisites
You can import fields from NetSuite either:
During initial onboarding (while setting up the integration), or
Later, as and when required.
To import data, first connect your NetSuite account with Fyle. Refer to this guide to connect Fyle with NetSuite.
Supported import fields and dimensions
Fyle supports importing a wide range of dimensions from NetSuite. These fields can be mapped to standard or custom fields in Fyle and are used during expense creation and export.
Dimension | Imported as |
Expense Accounts | Imported as Categories (no custom mapping) |
Expense Categories | Imported as Categories (no custom mapping) |
Items | Mapped to Cost Center, or Custom Field |
Vendors | Imported as Merchants (no custom mapping) |
Customers | Mapped to Project, Cost Center, or Custom Field |
Projects | Mapped to Project, Cost Center, or Custom Field |
Locations | Mapped to Project, Cost Center, or Custom Field |
Custom lists/records/segments | Mapped to Project, Cost Center, or Custom Field |
Best practice recommended is to map the Project or Customer dimension in NetSuite to the Project field in Fyle, as this allows restricting certain projects to specific employees.
Auto-sync behavior
Fyle regularly syncs data from NetSuite to keep your fields up to date. Most fields are refreshed automatically every 24 hours, but you can also perform a manual sync when needed.
Here’s how each type of field behaves when changes are made in NetSuite (like disabling, renaming, or re-creating values).
Behavior | Chart of Accounts | Vendor (Merchant) | Other Dimensions (Dept, Location, Class, etc.) |
Import rule | Only active values | Only active vendors | Only active values |
Disable in NetSuite | Disabled in Fyle | Removed from merchant options | Disabled in Fyle |
Rename in NetSuite | Old value disabled, new value added | Old value deleted, new value added | Old value disabled, new value added |
Delete & recreate in NetSuite | Record updated with correct internal ID | Record updated with internal ID | Record updated with internal ID |
Manual additions in Fyle | Not applicable | Preserved | Preserved |
Re-import after deletion in Fyle | Will be re-imported if still active | Will not be re-imported | Will not be re-imported |
Tips & best practices
If you’ve made changes in NetSuite, trigger a manual sync in Fyle to ensure updates are reflected immediately.
Always make changes in NetSuite and sync them to Fyle—avoid modifying imported fields directly in Fyle.
Turn on import toggles for all essential fields to keep your data accurate and up to date.
Troubleshooting import issues
Issue | Resolution |
Missing values | Trigger a manual sync. Automated sync runs every 24 hours. |
Field not updating | Try deleting and re-importing the mapping if needed. |
Need help setting this up? Reach out to us at [email protected], and we’ll be happy to assist you.