All Collections
Integrations with Fyle
Map Fyle and Xero dimensions in the Integration
Map Fyle and Xero dimensions in the Integration

All about Mapping Xero dimensions to Fyle expense fields in the Fyle-Xero Integration

Written by Kamalini Yuvaraj
Updated over a week ago

Typically, you can import dimensions such as Chart of Accounts, Tax codes, and Customers from Xero to Fyle. All the values of the selected dimensions will be imported into Fyle as a dropdown to use in the Expense form.

However, if you don't want to import all the values from your Xero account and only want to use specific values from the dimension in Fyle, we would recommend you to create these values manually in Fyle first and then map them to their equivalents in Xero. So, for example, if you have 100 different accounts in your Chart of Accounts but only 10 are relevant to use in Fyle, you can first create these 10 accounts as Categories in Fyle and then map them in the integration.

Mapping Section in Fyle-Xero Integration

The mapping section allows admins to set up Mapping for default dimensions such as Employees, Categories, and Tax codes. You can also configure a Custom Mapping by importing dimensions like Item or Region from Xero.

Employee Mapping

By default, the integration can automatically map your employees in Fyle to Employees in Xero using unique parameter matches such as name or email. However, if you wish to map the employee data between Fyle and Xero manually, you can do so from Mappings > Employee Mappings.

Once mapped, you will see the state change to Mapped to indicate successful Mapping.

Category Mapping

The video below is an example of mapping Categories in Fyle to Chart of Accounts in Xero.

Similarly, you can map Projects in Fyle to Customers in Xero and Tax codes in Fyle to Tax groups in Xero.

The integration will use the mapping information to code the correct data in Xero for a corresponding value filled in the Fyle expense form.

Do reach out to us at [email protected] if you need assistance in setting this up.

Did this answer your question?