You can connect Trelica to your finance system in order to import spend data and match transactions to apps in your inventory. Spend data for each app is recorded in your Apps inventory and displayed in your Spend dashboard.
Before setting up a spend integration, ensure that your Trelica base currency matches the base currency of your finance system.
Set up a spend integration
Trelica offers integrations with multiple widely used finance systems, including NetSuite, Xero and Expensify. If your system is not currently supported, please contact our support team.
Each finance system has a slightly different API, and configuration varies. To find out more about setting up a particular integration, click Integration help on the integration page or refer to the integration-specific help.
Finance systems contain a range of data, some of which may be sensitive. Trelica limits its access to the roles or permissions required to import your SaaS spend data. For more details about the access Trelica requires, click the information icon next to each permission.
Limit imports to specific spend categories
When you connect to a source of financial data, Trelica looks for spend category codes that might relate to SaaS or software spend. You can add or remove categories from this list. Trelica will only import transactions from the categories that you have selected.
If you have enabled Expensed and Invoiced spend from the Spend Settings page, you can specify whether transactions from each category should be recorded as invoiced or expensed spend. You can also choose whether to import journal entries.
To control how much historic data is imported, change the start date for importing transactions.
Processing flow
This diagram describes the requests made when connecting to finance systems:
- Trelica retrieves a list of account codes from the target app.
- The user configuring the connection selects codes related to software spend and sets the start date for pulling that data.
- Trelica explicitly queries the app for just those account codes from the specified date.
- Although Trelica only needs a small number of fields, APIs typically return additional data. Trelica only stores the fields it needs and discards any additional data.
- Data is sent to our mapping engine to try to find matches against our catalog of over 16,000 SaaS apps and vendors.
The integration is then refreshed automatically on a schedule (weekly by default), in order to pull transactions that have changed or been added since the previous run.
For each transaction, Trelica stores the following details:
| Name | Status | Detail |
|---|---|---|
| Transaction ID | Mandatory | Unique ID for the transaction so that Trelica doesn’t fetch duplicate data |
| Billing Date | Mandatory | Date the transaction took place |
| Amount | Mandatory | Value of transaction |
| Currency Code | Optional | Required if the system reports data in multiple currencies |
| Description | Mandatory | Label for the transaction |
| Account Code | Mandatory | GL code or Account code |
| Vendor Name | Optional | Some systems split out the vendor name from the description field |
| Expensed By | Optional | The email address or name of the individual claiming the expense |
| Cost Center | Optional | Associated cost center for the transaction |
| Period Start / End | Optional | Start and end (for amortization) |
| Note | Optional | Memo field |
View and map transactions
Once you have imported your transactions into Trelica, you can view them by going to the Spend page and selecting the relevant data source:
Where possible, Trelica automatically maps each spend transaction to an app. The total spend to date and details of the mapped transactions are listed on the relevant app page.
Sometimes the description for a transaction is ambiguous (e.g. "Atlassian" does not tell us which Atlassian product the transaction relates to) or unclear. In this case you will need to map the transactions manually. As part of this process, you can define rules so that Trelica can map these transactions automatically in future.
For more information, see Review spend transactions.
Refresh spend data
After the first import, Trelica queries the finance system for new or updated transactions once a week. To check for changes manually, open the integrations page for the finance system and click Refresh.
To force a full refresh of all spend data, expand the context menu, select Settings and then click Reconnect to resave the current settings. This will force a full refresh for the spend categories and period requested.
Next steps
Once you have set up an integration to your finance system, the next step is to ensure your transactions are accurately mapped to apps so that you can analyze your spend. For more information, see Review spend transactions.
Comments
0 comments
Please sign in to leave a comment.