This article explains how data from Sage 300 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 Sage 300 either:
During initial onboarding (while setting up the integration), or
Later, as and when required.
To import data, first connect your Sage 300 account with Fyle. Refer to this guide to establish the integration connection.
Supported import fields and dimensions
Fyle supports importing a wide range of dimensions from Sage 300. These fields can be mapped to standard or custom fields in Fyle and are used during expense creation and export.
Dimension | Imported as |
Accounts | Imported as Categories (no custom mapping) |
Job | Mapped to Project, Cost Center, or Custom Field |
Cost Codes / Cost Categories | Mapped to Custom Fields |
Vendors | Mapped to Merchants (no custom mapping) |
Import the Code along with the name for specific fields
In many organizations, different values may share similar names, especially across Jobs or Departments. To avoid confusion, Fyle supports importing certain fields in a Code: Name format instead of just the name.
Example:
Instead of seeing Advertisement, users will see 1234: Advertisement in Fyle.
This helps users:
Clearly identify the correct values while creating expenses
Reduce errors during export and mapping
Supported fields:
General Ledger Accounts (not supported for Expense Types)
Projects
Cost Codes
Cost Categories
⚠️ This setting is configured during onboarding and cannot be changed later without raising a support request.
Auto-sync behavior
Fyle regularly syncs data from Sage 300 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 Sage 300 (like disabling, renaming, or re-creating values).
Behavior | Account | Vendor (Merchant) | Other Dimensions (Dept, Location, Class, etc.) |
Import rule | Only active values | Only active vendors | Only active values |
Disable in Sage 300 | Disabled in Fyle | Removed from merchant options | Disabled in Fyle |
Rename in Sage 300 | Old value disabled, new value added | Old value deleted, new value added | Old value disabled, new value added |
Delete & recreate in Sage 300 | 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 Sage 300, trigger a manual sync in Fyle to ensure updates are reflected immediately.
Always make changes in Sage 300 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.