Introduction
This guide provides step-by-step instructions for creating an integration between Xledger and Ignite. We show how to generate the API token necessary for integrating Xledger with Ignite, and how to configure Ignite for the integration. It is designed for users with basic technical knowledge. Special attention is given to security measures to protect your data.
Prerequisites
Access to Xledger with an Administrator role.
Access to Ignite with an Administrator role.
Steps to Create an API Token
1. Log into Xledger
Access the Xledger-page at Xledger Login. Make sure you are logged in as an Administrator. Be attentive to the company owner you are logged into.
2. Open the API Tokens Page
You can access the API tokens page in two ways:
Directly via API Tokens Link.
Through the Menu: Administrasjon → Tilgangskontroll → GraphQL → API tokens. (Refer to Figure 1 in the document for visual guidance).
3. Generate a New Token
Click the “Generate New Token” button.
Enter a descriptive name for the token, like “Ignite Integration Token”.
4. Select Entities for Access
You must grant Read Access to the following entities in order for the integration to work:
Accounts Payable
APTransaction
Common
Address
Company
Contact
Country
Currency
GLDimension
Object
ObjectValue
Owner
Subledger
Supplier
SystemValue
GeneralLedger
Account
RecentTransaction
Transaction
TransactionHeader
Figure 1: How to navigate to the API tokens page
Figure 2: What it should look like after having created the token
5. Secure Your Token
Immediately copy the token. Note: You cannot view it again.
Do not share the token over unsecured channels like email.
Follow your company’s security policies for transferring API secrets.
Encrypt any message containing the token. Send the encryption key through a different channel.
6. Configure integration within the Ignite application
Navigate to the following URL and insert the token to configure things on the Ignite side. Make sure you are logged in on your production tenant.
7. All done – sit down and wait ~15 minutes for everything to finish
After you have pasted the token, the Ignite application does the rest. We fetch new data every 3 days. You'll have ready-to-go transaction and supplier tables with the most recent and valuable data you have from Xledger.
Integration Security Practices
In the integration process with Ignite, we ensure the security of your data by:
Filtering out all IDs associated with payroll transactions.
We first query for all line IDs that have the payroll document type
These line IDs are used to create a list of exceptions that we include in our query to not receive payroll data on Ignite's side
Make a query towards transactions, and apTransactions with the ID filters, so that we never receive sensitive data in the response from the Xledger API.
Conclusion
Following these steps will help you create an automatic and recurring integration between Xledger and Ignite. Remember to handle the token with care and abide by your company's security protocols at all times.
FAQ
What data sources do you use?
The easiest answer to this question is that we use the data found in the list of point 4. When looking at the data in Ignite, we are using "Transactions", which is the general ledger, as the foundation for your spend table. We use foreign keys to fetch supplier data from the "APTransactions" table, so that we can see which supplier all transactions are associated with. Other similar enrichments are also done so we can
What document types do you take in to Ignite?
We only include document types (bilagstyper in Norwegian) that are relevant for spend analysis. These are 1) AP = accounts payable; 2) BA = bank account documents; 3)ER = expense reports
Do you filter away any particular data from the general ledger?
Yes, we remove all accounts from 1900 to 3000. We also conduct some complex pre-queries to filter out all salary data from the general ledger.