Troubleshooting Bank Bridge¶
Start with the relevant check below. These are investigation steps; the cause depends on the bank integration, setup and transaction data.
A payment is missing from the proposal¶
Check the journal batch's Currency Code Filter and Payment Method Filter, the proposal criteria and the source vendor entry.
If the vendor's total balance is zero or negative but an invoice should still be paid, review Create Transfer Even if Vendor Balance is Zero or Negative on Bank Bridge Journal Template. This is relevant, for example, when a deposit offsets the vendor balance. See Payment journal setup.
Review the payment archive as well. Payments recorded there are excluded from subsequent proposals, including payments whose archive records are marked Restored.
Do not create a replacement transfer solely because an expected line is missing. Check the previous export and the bank's result first.
Payments for one vendor remain in separate groups¶
Compare the vendor number, vendor bank account number, currency code and Split Payment setting. All four must match for payments to belong to the same group. A common vendor number alone is not sufficient.
See Outgoing payments.
A restored payment is not proposed again¶
This is expected. Suggest Vendor Payments... checks whether the payment exists in the archive and excludes it regardless of the Restored flag. Restoration has already returned the transfer to Bank Bridge Payment Journal; correct and export that transfer from the journal when a resend is required.
The original archive record cannot be restored again after it has been marked Restored. Before resending the corrected payment, resolve the original export at the bank so that the same operation is not authorized twice.
A bank fee is assigned to the wrong account¶
Compare the statement's bank account and operation code with the entries in Bank Bridge Operation Code Mapping. Review both Account Type and Account No. Correct the setup and review the affected statement or journal line before posting.
If you need to correct the account assignment on a statement that has already been sent to the journal, follow Restore and reprocess a statement. The procedure depends on whether the journal has already been posted.
A customer or vendor transaction is not matched¶
Check the counterparty's bank account number in the statement against the customer or vendor's bank account information. Bank Bridge uses this number to recognize the counterparty.
For entry matching, check the transaction description first. If description matching found no entry, the exact-amount fallback requires exactly one open entry with that amount for the recognized customer or vendor. Several open entries with the same amount require a manual review of the intended application.
Review or complete the application in the destination journal using the available Business Central application actions. Do not treat an imported line as fully processed until its account and application have been checked.
The statement balances do not agree¶
Confirm that the statement and journal belong to the same bank account and that the expected lines are present. Compare debit and credit totals and transaction counts with the source statement.
If the opening balance agrees but the closing balance differs, select journal lines and compare Balance with the bank PDF's running balance after each corresponding operation. Find the first line where the values diverge and check its amount. A manually edited journal amount can cause the difference.
Compare figures in the same currency. Balance is the running balance after the selected line; it is not the same value as End Balance.
See Bank statements and Balance checks and posting.
Imported descriptions contain incorrect characters¶
Review Code Page in Bank Bridge Statements Setup and compare it with the statement file's encoding. Also confirm that Import Format matches the file supplied by the bank.
If the statement has already been imported and you need to replace the file, follow Reimport a replacement statement file. Review the import setup and obtain a corrected export from the bank where needed before importing again.
Restoring a statement leaves journal lines or posted entries in place¶
This is expected. Restore Statement... only clears the Bank Bridge statement's archived status and makes it available for editing again. It does not remove Cash Receipt Journal lines or reverse posted entries.
If the journal is unposted, manually delete the statement's original journal lines before restoring, correcting and sending it again. If it has already been posted, manually reverse its original postings using the appropriate standard Business Central procedures first. See the statement correction procedures.
A statement file with the same name cannot be imported again¶
Bank Bridge prevents importing the same filename while the existing statement record remains. Clearing its archived status alone does not allow another import.
When a replacement file is needed, first resolve any journal lines or postings from the original import. Then restore the archived Bank Bridge statement, delete its statement record and import the replacement file. See Reimport a replacement statement file for the full sequence.
The statement uses unexpected document numbers or the wrong journal¶
Review Journal Template Name and Journal Batch Name in Bank Bridge Statements Setup. Check Do not Increment Document No. as well: enable it for one document number covering the whole statement, or leave it disabled for separate numbers on the lines.
A file or API request is rejected¶
Record the error message and identify the failed operation: payment export, payment submission, statement import or statement retrieval.
For file exchange, confirm that the file belongs to the configured bank and format. For an API connection, have the service configuration and the bank's response reviewed by the person responsible for the integration.
If a payment request may have reached the bank, establish its outcome before retrying it.
Contact support¶
Send the following information to office@appower.io:
- Business Central and Bank Bridge versions.
- Bank name and the communication method used.
- The page, action and steps that produced the issue.
- The error message and expected result.
- A screenshot or example with confidential information removed where it is not needed to explain the issue.
Keep bank credentials, certificate passwords and private keys out of support messages.