Bank Entry Background Processing
Overview
The Bank Entry HTML Widget in finPOWER Connect Cloud now commits transaction batches as a Background Process running through Web Services rather than blocking the user's session. Users can start a Bank Entry, walk away from the screen, close the widget, or continue working elsewhere in Cloud — the commit will keep running and the result will be available when they return.
Bank Entry sessions can involve hundreds or thousands of transactions across many accounts. Previously, committing a large batch in Cloud meant sitting and watching a spinner until every transaction was processed. If the browser tab was closed or the session timed out mid-commit, the entry could end up in an unclear state. The new background commit removes that pain point — the workflow is now consistent with the other Background Process-enabled widgets such as Account Processes and AML/CFT Reports.
This is a Cloud-only enhancement. The Desktop Bank Entry form is a native form that already commits in-process and does not require Background Processing.
Prerequisites
Setup & Configuration
No additional admin setup is required to take advantage of this enhancement. If your Cloud environment already runs Account Processes or AML/CFT Reports, the Background Processing infrastructure is already in place and the upgraded Bank Entry widget will use it automatically.
The widget version that introduces Background Processing is HtmlWidget_BankEntry v1.12 (20/03/2026). It is shipped as a built-in widget and ships with the v6.00.03 release.
If your site has a custom override of the Bank Entry widget configured under Cloud Configuration, Forms & Actions, Processes, you will need to merge in the v1.12 changes (or revert to the built-in widget) to pick up the new Background Processing behaviour.
How to Use
Navigate to Processes & Procedures, Bank, Bank Entry. The Bank Entry widget opens on its selection page.
Select the Transaction Type at the top of the page. Move on to the data entry grid and enter your transactions row-by-row (Account, Amount, Reference, etc). The grid behaves as before — only the commit step has changed.
Once you are ready, click Commit. The widget submits the batch to Web Services as a Background Process and switches to the Progress page. You will see a progress bar and an event log streaming the work as it happens.
Because the commit is now a Background Process, you do not need to keep the widget open. You can close the tab or navigate elsewhere in Cloud — the commit continues to run on Web Services. This is the same pattern used by Account Processes.
Reopen Bank Entry. The widget's Recent page lists Background Processes you have queued, along with their current status. Click an entry to return to its Progress page and see the final result, including any per-row warnings or errors.
Platform Differences
| Aspect | Desktop | Cloud |
|---|---|---|
| How Bank Entry runs | Native Bank Entry form. Commits in-process, on the user's machine. | HTML Widget. Commits via Web Services as a Background Process. |
| Can the user close the screen mid-commit? | No. The form must remain open for the duration of the commit. | Yes. The commit keeps running on Web Services and can be revisited via the Recent page. |
| Web Services dependency | Not required. | Required — Background Processing runs through Web Services. |
Tips & Best Practices
For large bank statement imports, queue the commit, then move on to the next task. The Recent page will show progress whenever you return.
While a commit is in progress, the Progress page exposes a Cancel button. Cancelling stops further rows from being committed, but rows already processed up to that point remain committed — Background Process cancellation is cooperative and not transactional.
The Desktop Bank Entry form is a native form and is not affected by this change. It continues to commit in-process. Only the Cloud widget gains Background Processing.
Knowledge Base References
Browse the live KB listings for v6.00.03 on the Intersoft support site:
The Knowledge Base articles consolidated into this release notes page: