Setting Up Conditional Rules to Skip Exporting Specific Expenses from Fyle to Sage 300 CRE
The Fyle - Sage 300 CRE integration typically exports all reimbursable and corporate card expenses from Fyle to your Sage 300 CRE account based on your integration configuration. However, if specific business scenarios require skipping the export of certain expenses from Fyle to Sage 300 CRE, you can achieve this by configuring rules within the integration settings.
How to Configure a Rule to Skip Exporting Expenses:
Log in to your Fyle-Sage 300 CRE Integration using your Fyle Admin credentials.
Navigate to Configurations > Advanced Settings > Skip export.
Configure a rule to skip exporting expenses by selecting a condition, operator, and value, then click Save.
If needed, you can add another condition by selecting Add more fields. Use an AND operator to skip expenses only if both conditions match, or an OR operator if either condition should trigger the skip.
Once saved, expenses that meet the specified conditions will be automatically skipped from export to Sage 300 CRE.
Points to Note:
Conditions can be based on custom fields in Fyle such as select, multi-select, date, check-box, and text fields. Additional options include report title, report number, employee email, and spend date.
You can set up a maximum of two conditions per rule.
When using text fields, report numbers, or employee emails, you can input multiple values separated by commas.
Checking Skipped Expenses:
After configuring the rule, you can view skipped expenses under Export Log > Skipped. This provides details including report number, employee details, skip date, and expense type.
Sample Business Case Scenarios Where the Skip Export Rule Would Help:
System Migration
When migrating from another accounting system to Sage 300 CRE, ensure historical data already exported to the previous system isn't duplicated in Sage 300 CRE. Set a rule based on spend date to exclude expenses recorded before the migration date from being exported again.
Example: If migrating to Sage 300 CRE on March 1st and all data until then is already in the old system, use a spend date condition to skip exporting expenses dated prior to March 1st.
Manual Data Entry
In cases where expenses have already been manually entered into Sage 300 CRE, prevent duplication by setting a rule based on the report number. This ensures that any expenses already logged manually are not re-exported from Fyle.
Example: If expense reports have been manually entered into Sage 300 CRE with specific report numbers, set a rule to skip exporting those reports from Fyle to avoid duplicate entries.
Using Other Software for Expense Reimbursement
When using multiple software systems for different types of expense reimbursements, such as payroll software for specific categories like travel expenses, you may want to exclude these expenses from being exported to Sage 300 CRE to prevent redundancy.
Example: If travel expenses are reimbursed through payroll software for government reporting purposes, configure a rule based on expense categories to skip exporting these expenses to Sage 300 CRE.
For assistance with setting up these rules or any integration-related queries, contact us at [email protected].