Get insights into how much money your customer spends on bank-related products and services, such as interest, bank fees, etc. This report ist appropriate for B2B and B2C use cases.
What it solves
In order to better assess, review, and advise the customer, it is important for banks and financial service providers to know what financial expenses the customer already has.
What loans does he have? What fees does he have to pay? What other obligations does he have towards financial service providers?
The bank and credit report therefore offers the possibility to present these expenses in a structured way, on a monthly basis. This allows a quick overview of the client's situation to be gained and appropriate actions to be taken.
Bank and Credit Report
The Bank and Credit Report is based on the
BANKANDCREDIT label and its further sub-labels with a higher level of detail.
The report provides an overview of data such as the number of relevant transactions, how many are incoming and how many are outgoing, what amounts are on each side, etc.
Other data includes the account information and the transactions used in the report. This is very helpful if you want to check the values, for example, as part of a detailed credit check.
In addition, further reports can be generated based on an initial report. These “Continuous Reports” can then be provided with
Triggers, which always compare the values of the previous report with the current one and search for defined changes.
This is useful if you have access to the customer's account data over a longer period of time.
It is important that not only days, but ideally months are considered.
continuous reports, the customer may have to give new consent after a certain period of time in accordance with PSD2.
A Bank and Credit Report can be generated as an Aggregation with the following query:
"alias": "Bank and Credit",
Label priorities have no effect on the Bank and Credit Report.
Used data fields
Incoming transactions of the customer are used for this purpose. This includes data like
account holder name,
amount, and so on.
The report itself is divided into the following sections.
The main part of the report can be found at
$.reports.bankAndCredit and the
type will be
This gives you a quick overview of the transactions used in the report through aggregated values that can serve as a summary.
A full API schema can be seen here: https://docs.finapi.io/?product=di#get-/cases/-caseId-/reports
Timestamp of when the report was created, in the format '
ID of the case in which the report was created.
Defines the type of the report.
Timestamp of the start date of the reporting period under review in the format '
Timestamp of the end date of the reporting period under review in the format '
The number of full days, that the reporting period under review contains.
Timestamp of the date, when user's first transaction took place in the report period under review in the format '
The number of the user transactions, that took place in the report period under review. This field takes into consideration all the transactions of the user, irrespectively of the assigned to them label.
The total count of positive transactions in the report.
The total count of negative transactions in the report.
The total income.
The total spending.
The total balance.
List of accounts-related data with the relevant transactions information.
List of reports, created automatically with the specified frequency (defined by
Account Data Section
The account data section can be found under the
It contains data about the account at the first level.
If more than one account is included in the report, they will be displayed individually in the list.
Name of the bank.
Unique identifier of the Bank, generated by finAPI.
IBAN of the bank account.
Unique identifier of the bank account belonging to the imported bank connection.
List of transactions related to the chosen report type.
This section displays the transactions used in the report and can be found under the
accountData element in the field
Please note that this list may be very long, especially for business accounts.
Depending on what the report is used for, the transactions can be retrieved for later review or documentation, or they can be turned off. The latter would be the case, for example, if you only want to do a quick check of the overall data and do not need any details.
If transactions are not of interest, you can also disable this section by giving the query parameter
withTransactions=false to the report.
The transactions include the following values.
Value date in the format '
Bank booking date in the format '
Counterpart account number.
Counterpart bank name.
A list of labels assigned by the system. This does not contain the complete label structure in the sense of level of detail.
Extracted details for transactions with related to overdraft interests.