Bank Connections
One configured integration with one bank — endpoint, credentials, file transfer, the identifiers the bank assigned, and how often to collect. Credentials are encrypted on the way in and never come back out.
Where to find it
- Module: Accounting
- Group: Working Capital
- Section: Banking
- Screen: Bank Connections
Address in the console: /accounting/bank-connections
List · 11 columns · 33 fields on its form · 6 of them required · 4 actions
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Connection | Code | code |
| Bank | Text | bank |
| Environment | Status | environment |
| Channel | Status | integration_type |
| Auth | Status | auth_method |
| Accounts | Number | accounts |
| Statements | Code | statement_format |
| Payments | Code | payment_format |
| Status | Status | status |
| Health | Status | health |
| Last sync | Date and time | last_sync_at |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Bank required | Choice | Looked up from existing records | |
| Connection code required | Text | e.g. BANK-CHASE-01 | |
| Name required | Text | ||
| Environment | Choice | sandbox, uat, production | Production is real money. Nothing else about the configuration changes. |
| Channel required | Choice | Configuration list | The test refuses a channel the bank does not offer. |
| Authentication required | Choice | Configuration list | |
| API endpoint | Text | HTTPS only. | |
| OAuth token endpoint | Text | ||
| Client ID | Text | ||
| Scopes | Text | e.g. balances:read, transactions:read, payments:write | |
| Certificate expires | Date | The test warns thirty days out and fails once it has passed. | |
| SFTP host | Text | ||
| SFTP port | Number | ||
| SFTP username | Text | ||
| Inbound directory | Text | Where the bank leaves statements. | |
| Outbound directory | Text | Where payment files are collected from. | |
| PGP key id | Text | ||
| Bank-assigned company id required | Text | ||
| ACH company id | Text | The immediate origin on a NACHA file. Without it no ACH file can be built. | |
| ACH company name | Text | ||
| Originator id | Text | ||
| Division code | Text | ||
| Webhook URL | Text | Where the bank posts real-time notifications. Store a signing secret alongside it. | |
| Notification email | Text | ||
| Collect every (minutes) | Number | ||
| Statement format | Choice | Configuration list | |
| Payment file format | Choice | Configuration list | |
| Match the feed automatically | Yes or no | ||
| Amount tolerance | Number | How far two amounts may differ and still be the same payment. | |
| Date window (days) | Number | ||
| Platform connection | Choice | Looked up from existing records | Links this to the cross-application integration record. |
| Owner | Choice | Looked up from existing records | |
| Notes | Long text |
What you can do here
Test primary
Is this integration usable?
Store credentials
Store the bank credentials
Asks for: OAuth client secret API key Client certificate (mutual TLS) SFTP private key Webhook signing secret
Sync
Collect and match
Receive movements
Receive a batch of movements
Asks for: Account Movements*
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.