Business Checking

Growth Scale

For companies where money now moves through a process: user permissions, approval chains, bulk payables and API access to your own data.

update Last updated 1 August 2026 list_alt 6 sections

Growth Scale carries a monthly account fee. Facilities and limits referenced here are subject to assessment and are confirmed in writing before they take effect.

Section 01

Who Growth Scale is for

At a certain size, a payment stops being a decision one person makes and becomes a process several people follow. Growth Scale is the account that models that process instead of fighting it.

  • More than one person needs to raise, approve and release payments, with separation between those roles.
  • You pay suppliers or staff in batches rather than one at a time.
  • Your accounting or ERP system should be reconciling itself rather than waiting for a statement.
  • Support delays now cost real money, so you want a priority lane.
Section 02

Permissions and approval chains

Every user gets their own credentials and their own rights. Nothing is shared, so nothing has to be untangled when someone leaves.

Roles
Initiator, approver, releaser and viewer, assigned per user. One person can hold more than one role, but the account can require that they do not.
Thresholds
Set the value above which a second, or a specific, approver is required. Different thresholds for domestic and international.
Beneficiary control
Adding a new payee can itself require approval, which is where most invoice-redirection fraud is stopped.
Audit trail
Who raised it, who approved it, when it was released, and from which device. Exportable.
Dual control on changes
Changing a limit or a user right can require a second administrator.
warning

The control that matters most

Require approval when a beneficiary’s bank details change, not only when a payment is large. Redirection fraud usually arrives as a small, plausible invoice from a supplier you already use.

Section 03

Bulk payables and automation

  • Upload a payment file and release the whole batch under one approval, with per-line validation before anything leaves.
  • Schedule recurring runs — payroll, rent, standing supplier terms — with a cut-off reminder before each one.
  • Failed lines are isolated and reported rather than silently dropping the batch.
  • Every run reconciles back into your accounting system with the original reference intact.
Section 04

API terminal access

Read your balances and transactions programmatically, and initiate payments under the same approval rules that apply in the app. The API does not bypass your controls; it inherits them.

CapabilityWhat it gives you
Balance and transaction feedNear real-time position across every account, for reconciliation and cash forecasting.
Payment initiationRaise payments from your own systems; approval still happens under your configured chain.
Beneficiary managementCreate and verify payees programmatically, with the same change controls.
WebhooksNotification on credit, debit, failure and approval events, so nothing needs polling.
SandboxA test environment with representative data before you touch the live account.
verified

Credentials are scoped

API keys carry their own permissions and can be read-only. A reconciliation integration never needs the right to move money.

Section 05

Growth Scale against Essential Base

FeatureEssential BaseGrowth Scale
Monthly feeNoneMonthly fee applies
UsersUp to threeUnlimited, individually permissioned
Approval chainsSingle approverMulti-step, threshold based
Bulk payables—File upload and scheduled runs
API access—Read, initiate, webhooks, sandbox
CardholdersUp to threeUnlimited, with per-card spend rules
SupportStandard queuePriority lane
ReportingStatements and exportsScheduled reports and audit exports
Section 06

Moving to Growth Scale

  1. 1Existing customers upgrade from inside the treasury app; the account number does not change.
  2. 2Map your roles before you switch — who raises, who approves, who releases.
  3. 3Set thresholds deliberately. A threshold nobody ever hits is not a control.
  4. 4Run the API against the sandbox before pointing anything at the live account.
Related

Documents you may also need

This document was last updated on 1 August 2026. We publish the current version here at all times; superseded versions are available on request.

If anything on this page is unclear, write to us and we will explain it.