Bank Account Configuration
Beyond the identity fields, a bank account carries the settings that tune day-to-day banking behavior. This is the reference — what each dial does and when to touch it.
Access you'll need. Configuring these settings requires the Accounting Admin v2 or Accounting Controller v2 permission set. The Accounts Payable v2, Accounts Receivable v2, and Read Only v2 sets can view the account but not change it.
The configuration fields
| Setting | Effect | Touch it when… |
|---|---|---|
| GL Account | The ledger twin — all cash postings through this bank hit it; reconciliation compares against it | Set once at creation; changing it mid-life orphans history — don't |
| Currency Code | The account's currency, enforced on statements, deposits, reconciliations, and matched documents ("…must match the Bank Account currency…") | Set once; it's the master value |
| Current Balance / Last Reconciled Date | Maintained by completed reconciliations — your at-a-glance account health | Read, don't write |
| Adjustment GL Account | Pre-fills the offset line of reconciliation adjustment journals (bank fees, interest) | Set to your bank-charges account before the first reconciliation |
| AI Match Window Days (default 10) | Date tolerance for matching: how many days apart a statement line and a document may sit and still pair — used by auto-match and candidate sorting | Widen for accounts where checks clear slowly; narrow for high-volume accounts where tight dates prevent wrong pairs |
| Auto-Create Reconciliations | Approving one period's reconciliation auto-creates the next period's draft | Turn on after your first clean cycle — the monthly rhythm then sustains itself |
| Check stock fields | Starting/Ending/Next Check Number + stock description | See Check Stock & Check Printing |
| Is Active | Inactive accounts refuse new statements | Closing the real account? Finish its last reconciliation first, then deactivate |
The two match windows, side by side
Banking has two date tolerances with similar names and different jobs — worth one careful minute:
| AI Match Window Days (bank account) | Match Window Days (reconciliation) | |
|---|---|---|
| Default | 10 days | 30 days |
| Question it answers | How far apart in date may a statement line and a document sit and still pair? | How far beyond the accounting period's edges do statement lines still belong to this month's reconciliation? |
| Who uses it | Auto-match's date-range pass, AI matching, and the candidate sorting in the workspace | The reconciliation itself, when gathering its scope of lines |
| Tune it when… | Checks clear slowly (widen) or volume makes tight dates safer (narrow) | Prior-period payments routinely clear deep into the next month |
The help text on the account's window is the summary worth remembering: "How many days before/after a bank statement line date to look for matching transactions when using AI matching. Default is 10 days. Increase for accounts with longer clearing times."
The record page as banking HQ
The bank account's page gathers the whole operation: the Import Statement tool embedded right on the page, and related lists for Bank Statements, Reconciliations, Matching Rules and Bank Feed Setups (the integration point where connected bank feeds deliver statements automatically — provided by integration packages where in use).
A Bank Feed Setup record describes one connection: the provider, whether it points at a sandbox or production environment, its sync status (Active, Paused, Error or Disconnected) and when it last synced. The connections are managed by the integration package that provides them — in REDA Financials they're read-only for everyone, Admins included, which is why a feed problem is fixed at the provider, not by editing the setup record.
The guardrails on the record
| The message | What it means / what to do |
|---|---|
| "Account Last 4 must be exactly 4 digits." | The display identifier is strictly four digits — or enter the full account number and it derives itself. |
| "Either the Entity or GL Account on this Bank Account is inactive. Replace with active records." | Someone retired a foundation record under a live bank account — repoint to active ones. |
| "Currency Code must match the organisation default currency in single-currency mode." | Foreign-currency accounts need multi-currency mode; otherwise everything runs in the org default. |
| "Bank Account is inactive." | The message a statement import meets on a deactivated account — reactivation is deliberate. |
Common mistakes to avoid
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Hand-editing Current Balance or Last Reconciled Date | They're the system's record of the last proven position — overwriting them makes the account's health display lie | Read them; let completed reconciliations write them |
| Widening AI Match Window Days to force one match | Every future month inherits the loose window, and closest-date can start picking wrong neighbors | Fix the one line by hand; set the window from your bank's real clearing behavior |
| Repointing GL Account on an account with history | Everything already posted stays on the old ledger account; reconciliation now compares against an account that holds only the future | Set-once. A true re-banking means a new bank account record |
| Turning on Auto-Create Reconciliations before the first clean cycle | Drafts spawn into a process nobody has proven yet | Reconcile month one by hand; automate the rhythm once it works |
Where to go next
- Bank Account Rules — teaching the account your recurring transactions.
- Importing Bank Statements — the monthly feed.
- Starting a Reconciliation — where the settings pay off.
Frequently asked questions
The date tolerance in matching's second pass: a statement line can pair with a document up to that many days away (closest date wins). It also widens which lines a reconciliation period pulls in — prior-month checks clearing this month are the classic case.
Current Balance updates when reconciliations complete — it's the last reconciled position. The GL account is live to the second. Between reconciliations they legitimately drift by the unreconciled activity.
Deactivation stops new statement imports ("Bank Account is inactive."). Tidy first: finish outstanding reconciliations so history ends clean, then deactivate.
No — the auto-creation is deliberately best-effort: the approval itself always goes through, and if the next period's draft can't be created for some reason, you simply create it by hand as usual. Automation assists the rhythm; it never holds the sign-off hostage.
Accounting Admins and Accounting Controllers, who have full rights over all banking records. AP, AR and Read Only roles see everything here but edit nothing — configuration is books-owner territory, and Bank Feed Setups are read-only for everyone.
Was this article helpful?