We understand it might be confusing
at the beginning

To install Bankfeed and start using the free monthly trial, click the “Free trial” button on the Microsoft AppSource.

The solution is packed with useful tools so that you would be able to install and start using it in a matter of minutes:

• Assisted setup for Bankfeed preparation and bank account connection – HERE is a video on that
• HERE is a detailed user manual 
• Usually for the payment recognition setup, customers ask for assistance from our side. In such a case, please reach out to us at [email protected]

Once the free trial is activated, you can use the full Bankfeed functionality for 30 days.

Because Bankfeed is used on a subscription basis, you may cancel it anytime by emailing us at [email protected].

If you have any questions, we are here to help. Please send us a message at [email protected].

The matching rate highly depends on proper system settings, the definition of statement formation, and the quality of data. Typically, Bankfeed achieves a matching rate of at least 95%. Each payment recognition enables continuous improvement and maintenance of recognition and reconciliation rules.

Financial statement files automatically travel through the API from the bank to Microsoft Dynamics 365 Business Central and end up on a separate table. A register of statements is kept. Payment Journal entries are then automatically created from the statements. During the creation of Payment Journal entries, payment entries are automatically reconciled with the issued invoices (customer identification and reconciliation with the issued invoices is performed). Depending on the settings, the entries will be posted automatically or manually. Unrecognized entries are left in the Journal and can be reconciled manually.

Bankfeed searches for open items independently and reliably using pre-defined recognition rules, and all rules are processed serially. After a match is recognized (e.g., customer number, invoice number, transfer subject, amount), Bankfeed creates an entry and jumps to the next bank statement line for further processing.

There can be several reasons why bank accounts cannot be connected. Here are a few of them:

• The user connecting bank accounts does not have enough permissions to give access to a third party to connect to the company’s bank accounts

In such cases, there can be few solutions. Ask another employee with these permissions in the bank to connect the bank accounts (e.g., CEO or CFO). Or ask the bank to provide you with the permissions needed.

• Bank connection window is blocked by a security system (e.g. Firewall)

The additional window pops up for authentication in the bank, and sometimes, the computer’s security system blocks these windows. It is easy to identify this problem because the user cannot open the bank window for authentication after he selects the bank and clicks “Next”.

• Other problems

If you do not relate to the problems described above, please get in touch with us at [email protected].

Bankfeed uses PSD2/Open Banking APIs and does not require users to share online-banking credentials.

The connection is protected by several technical controls:
1. Strong Customer Authentication (SCA) – the user authenticates directly with the bank using PSD2-compliant multi-factor authentication. Bankfeed does not receive passwords, PINs or authentication codes.
PSD2 RTS – SCA and secure communication
2. Explicit AIS consent – access is granted only for Account Information Services (AIS) and only for the accounts and data covered by the user’s consent. This is read-oriented account-data access, not unrestricted online-banking access or payment authority.
PSD2 – Article 67, Account Information Services
3. Token-based authorization – Open Banking APIs commonly use OAuth 2.0 Authorization Code Grant or equivalent delegated-authorisation mechanisms. After successful authentication and consent, API access is performed using short-lived access tokens and, where supported, refresh tokens, instead of reusable banking credentials.
Berlin Group NextGenPSD2 specifications
4. Scoped and revocable access – token permissions are constrained by the bank-side consent, requested scopes and validity period. Consent can expire or be revoked without changing the customer’s banking credentials.
Encrypted and authenticated API communication – PSD2 requires encrypted communication and identification of regulated parties using eIDAS certificates. Implementations commonly use TLS/mTLS, including QWAC/QSealC-based identification.
PSD2 RTS – secure communication
5. Business Central security boundary – Bankfeed runs inside the customer’s own Microsoft Dynamics 365 Business Central environment. Business Central provides tenant isolation, encryption at rest using TDE, encrypted network traffic, Microsoft Entra ID authentication and granular permission controls.
Microsoft – Business Central Online security

Bankfeed therefore does not receive the customer’s bank login. The security model is:
SCA → explicit consent → scoped token → encrypted Open Banking API → customer’s Business Central environment.
This limits both the scope and lifetime of access and allows the customer to revoke the connection at any time.

For more technical information and detailed usage instructions, please refer to the User Portal.