All the frequently asked questions about Transaction Categorisation and Insights products are answered below.
The quality of categorisation can be evaluated by two parameters: transaction coverage(i.e. how many transactions get assigned to a specific category) and the error rate (i.e. how correctly the categories were assigned).
Both parameters should be evaluated together; meaning, even if the coverage is high, the quality of categorisation is high if and only if the error rate is low. This is because the lack of quality greatly diminishes predictive power when these data points are used in analytics.
Both parameters are calculated and monitored on a regular basis by sampling and manually reviewing transactions by Nordigen’s Data team, paying particular attention to all categories that are associated with high risk, for example, gambling and loans.
If the data you are willing to process is anonymised, Nordigen categorisation engine won't be able to assign distinguish the context of transactions that usually contain personal information like name and surname. Instead of being assigned to categories like To Own Account or To the Account of Relatives, all personal transfers will be categorised asOther Personal Transfers.
Unless transaction description is heavily corrupted by anonymisation algorithm, there shouldn't be any other foreseeable categorisation quality issues.
Nordigen categorisation engine is not working with 100% accuracy, and some miscategorisations are naturally possible, as it is with all existing categorisation engines. We are constantly updating our system, and we are also paying extra attention to all categories, however if you have identified an error, please open a support request with our team and share the the request_id/report_id. This feedback will be collected and used to improve the engine to prevent such cases from happening in the future.
NB: request_id can be found by opening a processed statement (this applies to both Nordigen Report and API) and looking for a field called “request ID”. It matches this pattern - xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx - with x being a combination of digits and lowercase letters.
No. For Simple score or any other product from Insights suite, information available only in a bank statement is used – might that be information from transactions or statement's meta-data.
Field calendar_months will indicate that the period is shorter than was requested. However, all calculations will be done on 3 calendar month data and will not penalize customers for not having more transactions. Meaning, for average monthly income, the divider is 3 and not 9.
All values are always in the currency that is listed in insights-details response. For example, if a statement contains two bank accounts where one has euro as the main currency, and the second has Australian dollars as the main currency, and the display currency (set through customization) is euro, then the field display_currency will have value of EUR, and applied_currency_conversions will have currency rate for conversion from AUD to EUR. Please see example response below.
{
"data":{
"attributes":{
"insights":{
"insights-income":{
"currency":{
"display_currency":"EUR",
"applied_currency_conversions":[
{
"currency":"AUD",
"rate":0.62
}
]
},
"status":"completed"
},
"type":"report processing status"
}
}
}
}
Yes, you can send several statements in a single request. When the Nordigen system receives multiple accounts in the same request, these accounts are never physically merged; however, analytics are performed on all accounts in aggregate. So you will receive the requested output (categorisation, insights, scores/features) based on all uploaded accounts in that request, with the system treating it as a single unique customer you want to analyse. This means that each account is analysed separately but insights apply to the whole data set; for example, average monthly income is computed using all accounts together.
If null is returned for fields that are aggregate values of certain categories, the statement does not have transactions that are recognised as the respective categories.
If null is returned for fields that are forecasted values of certain categories, the statement either does not have transactions that are categorised as the respective categories or there is not enough data to make a forecast.
Credit Scores and Features are available only to Enterprise tier customers, as they are not out-of-the-box products. We recommend checking out Simple Score product, if you need to make creditworthiness checks or affordability assessments.
If you would like to know more about the Enterprise tier, please contact our Sales team.
Sometimes can result in errors due to various reasons. Normally, the response would include an error code, providing information about the particular problem. You can review a list of all error codes in Overview under section “Error Handling”. The most popular reasons are usually trying to upload an unsupported input format (NO_SUITABLE_PARSERS) and not requesting any operations after file upload (TIMEOUT_PROCESSING).
Nordigen is agnostic to how you acquire the data, as long as you are able to pass it to API in a machine readable JSON format. If you're using Nordigen's free Open Banking platform, please refer to Overview section “Nordigen Open Banking JSON Input File Structure” section. If you're using a different Third Party Provider for Account Aggregation, please make sure the files you have are mapped to “Nordigen Default JSON Input File Structure” also found in Overview section.
If any explanation on key descriptions is needed to complete mapping, please open a support ticket.
The rate limit is set to 100 requests per minute, and it only applies to the report endpoint.
The maximum file size is set to 10mb. If you are uploading multiple files in a single request, the limit applies to total file size.