Getting started with Bank Bridge¶
Use this guide to prepare Bank Bridge for its first payment export and bank statement import. The examples in these instructions use the English Business Central interface.
Before you start¶
Have the following information ready:
- The Business Central company and bank accounts that will use Bank Bridge.
- The currency of each bank account.
- The payment and statement formats, or the API service, agreed with the bank.
- The vendor bank account details needed for outgoing payments.
- The G/L or other accounts to use for bank fees, interest and internal transfers.
- The person responsible for reviewing payments, approving them at the bank and posting statements.
Bank Bridge supports the Essentials and Premium editions of Business Central. Its published interface languages are English and Polish. It is designed for electronic banking in Poland and does not require the Polish Localization. Confirm the required Polish banking integration for your Business Central environment before installation.
Install and register the app¶
- Install Bank Bridge in the intended Business Central environment using the Microsoft Marketplace offer.
- Register the APPower subscription. Follow the shared subscription registration guide.
- Assign the appropriate Bank Bridge permission set and access to the Business Central journals used in your process.
Existing subscriptions are described in Managing existing subscriptions.
Assign permissions¶
Bank Bridge provides two permission sets:
| Permission set | Intended role |
|---|---|
| BB-ADMIN PWR | Administrators responsible for Bank Bridge configuration. |
| BB-USER PWR | Users working with Bank Bridge in the finance process. |
Assign permissions according to the person's responsibilities. Review the required access to standard Business Central bank accounts, journals and ledger entries as part of the overall permission setup.
Prepare the bank setup¶
Work through the following items with the person configuring the integration:
| Item | What to confirm |
|---|---|
| Bank connection | File exchange or API, and the operations supported by that connection. |
| Bank account | The correct Business Central bank account and its currency. |
| Payment journal template | Bank and fee defaults, and whether to suggest payments when the vendor balance is zero or negative. |
| Payment journal batch | Bank account, currency and payment method filters, export format and service code. |
| Statement setup | Import format, code page, destination journal template and batch, and document numbering. |
| Operation mappings | The bank operation codes and the accounts to assign to them. |
| Bank approval | How exported or submitted payments are reviewed and authorized at the bank. |
Set up Bank connections, Payment journals, Statement imports and Operation code mappings before the first run.
Check the first payment and statement¶
For the first run, use a small, controlled selection of payments and a statement that the finance team can reconcile independently.
- Prepare the outgoing payment proposal.
- Check recipients, bank account details, currencies, amounts and payment dates before exporting or sending the payments.
- Confirm the bank's response and any approval still required there.
- Import the statement, then review account recognition, applications and operation mappings.
- Check balances and journal lines before posting.
Export and execution are different steps
A payment export or submission should not be treated as confirmation that the bank has executed the transfer. Check the bank's result before deciding whether a payment needs to be sent again.