Skip to main content
All CollectionsIntegrations with FyleSage Intacct
Import Allocations from Sage Intacct to Fyle
Import Allocations from Sage Intacct to Fyle

Learn how to import Allocations from Sage Intacct to Fyle for use in expense coding

Hemanth Singanamalla avatar
Written by Hemanth Singanamalla
Updated over a week ago

If you have Allocations set up in your Sage Intacct account and use them to split transactions into multiple dimensions such as departments, locations, etc., and you are exporting expenses from Fyle as Bills or Journal Entries in Sage Intacct, this article is just for you.

The Fyle <> Sage Intacct integration now lets you import your Allocations from Sage Intacct to Fyle. These Allocations will be available in a dropdown list for users to select when creating expenses. The integration will also export the selected Allocation values back to Sage Intacct, which will then handle splitting transaction amounts into multiple dimensions based on how the allocation is set up.

Let's talk about how to import Allocations from Sage Intacct to Fyle,

  • Login to Fyle as an admin

  • Go to Settings > Integrations > Native Apps > Sage Intacct Integration

  • Navigate to the Configuration tab > Import Settings tab

  • Click on Choose Sage Intacct field

  • Select Allocation from the dropdown

  • Map it with any one of the Fyle expense fields - Cost Center, Project or create a new custom expense field

  • Turn on the toggle for Import to Fyle and hit on Save!

All Allocations from Sage Intacct will be imported into Fyle, allowing users to select an Allocation when creating an expense. Based on the selected Allocation, the integration will export the expense to Sage Intacct, where the amount will be split into various dimensions according to the setup.

A sample preview of what an expense form will look like in Fyle after importing allocations,

A sample preview of what an export of a Bill with allocation will look like in Sage Intacct,

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


Did this answer your question?