How to increase transparency in the allocation of bank statements in the system

This article is about increasing transparency in the allocation of bank statements in the system using the following channels:

• BankConnect
• CAMT53 Upload
• Finion Direct Debit

Overview:

• Introduction
• Detailed Allocation Process
• What happens if no match is found

Introduction

Allocating bank statements in the system is a crucial process for accurately recording payments and keeping member accounts up to date. This article explains how allocation works when using various import channels.

Detailed Allocation Process

1. Search for Booking Number:

• The system first attempts to find a booking number in the payment reference (e.g., from a payment run, in the format studio-prefix--xxxx-xxxxxxx).
• If such a number is found, the system searches for a corresponding payment run position.

2. Verify Payment Run Position:

• If a matching payment run position is found and a direct debit return exists, a corresponding bank transfer entry is created in the member’s account and saved as an incoming transfer.

3. Search for Member Number:

• If no booking number is found or it does not contain a direct debit return, the system searches for a member number in the payment reference.
• If a member number is found, the system checks if the IBAN of the transfer matches the member associated with the member number. If yes, a bank transfer entry is created for the member and saved as an incoming transfer.

What Happens When No Match is Found

If none of the above methods result in a match, the bank statement remains open and must be manually allocated to the correct member. The studio can find the open transfer under Tasks / Account Movements / Transfers or Direct Debit Returns.