Recurring Transactions Use Cases

Introduction

The Recurring Transactions Report provides a comprehensive overview of the customer's ongoing financial relationships. It offers key insights, including:

Payment frequency (e.g., monthly).
Details about the parties involved in these recurring transactions.
Commencement and conclusion dates of these transactions.
Aggregated totals and average amounts for the transactions.

The following use cases are examples to make them more “plastic”.

Trading Companies

UC-01: Assess solvency

Actors	Company User
Systems	Company’s application finAPI Data Intelligence finAPI Process Controller finAPI WebForm
Goals	Recognition of recurring transactions Assessment of whether contracts and thus financial obligations can be fulfilled Assessment of reliability
Preconditions	User has opened the company’s application
Flow	Company’s application asks customer to import all accounts Open finAPI Process Controller and get process token and user Call finAPI WebForm v2 to let the user import the accounts wait until the user has finished Call finAPI Data Intelligence Synchronize accounts endpoint and wait for callback Callback should create an Recurring Transactions Report with the given Data Sources Get the result of the Recurring Transaction Report Look at the result to find out what if the client is relieable

Banks

UC-01: Assesment of freely available budget

Actors	Bank User
Systems	Bank’s application finAPI Data Intelligence finAPI Process Controller finAPI WebForm
Goals	Recognition of recurring transactions Valuation of the freely available budget after deduction of recurring transactions Assessment of the financial situation based on recurring financial obligations Decision of granting credit
Preconditions	User has opened the bank’s application
Flow	Bank’s application asks customer to import all accounts Open finAPI Process Controller and get process token and user Call finAPI WebForm v2 to let the user import the accounts wait until the user has finished Call finAPI Data Intelligence Synchronize accounts endpoint and wait for callback Callback should create an Recurring Transactions Report with the given Data Sources Get the result of the Recurring Transaction Report Look at the result to find out what if the client is relieable