When a user connects more than 1 account to the same overview, transfers between the connected accounts are recognised to be 'internal bookings'. This prevents those transfers to be falsely registered as an income or an expense on either account. Our platform manages this interaction (referred to as “own account detection”) and ensures that the resulting income and expense overview remains valid.

---

Definition of own accountsCopied!

When we refer to 'own accounts', we refer to bank accounts that are connected by the user. If a user connects 4 bank accounts via our PSD2 service, these 4 bank accounts are known to be owned by this user. As a result, any transfer or other transactions between these 4 accounts are considered as internal bookings. This means they will be treated differently in the categorisation process and detection of recurring payments.

Additionally, each transaction has an ownAccount boolean attribute, which is set to true if the transaction is to/from another PSD2-connected bank account. Bank accounts that are not connected to the PSD2 overview, are never marked as own account, even if they might be registered to the same accountholder.

Adding new accountsCopied!

In personal finance use cases, it may occur that a user connects more bank accounts to the overview at a later stage, or removes existing connections. In those cases, the transactions' prior categorisation will be re-processed in case we now see any transactions moving to or from the newly connected account.