Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Account details and gateway settings · How-to guide

Set the Tide reconciliation lookback period

Detailed client guidance covering set the Tide reconciliation lookback period, with exact eligibility, security, verification and troubleshooting boundaries for the shipped Tide payment and Open Banking controls.

Audience: Administrators and authorised payment operations staffPermission: Settings or relevant capabilityModule v1.0.0
Jump to steps
Where to goTide Payments → Settings
Before you startConfirm the intended tenant, remote account or invoice context, and your Settings or relevant capability access. Keep credentials and tokens out of screenshots, tickets and exported evidence. If a previous write may have reached an external service, verify remote state before retrying.

What you’ll accomplish

Detailed client guidance covering set the Tide reconciliation lookback period, with exact eligibility, security, verification and troubleshooting boundaries for the shipped Tide payment and Open Banking controls. This article is intentionally scoped to the behaviour enforced or exposed by the supplied module and does not treat provider marketing features as implemented integration capabilities.

How the workflow fits together

Tide payment instructions, AIS transaction import, exact reconciliation, native invoice payment status and audit evidence are connected but separately verifiable stages. A payment instruction is not proof of receipt; a bank transaction is not a certified invoice payment until it passes the reconciliation gates.

Follow these steps

  1. Open Tide Payments → Settings.
  2. Confirm the intended tenant, invoice/connection/transaction where applicable, and your Settings or relevant capability access before continuing.
  3. Review existing customer-facing account details before editing.
  4. Enter only the account details for the intended Tide Business Account.
  5. Respect the 6-digit sort code, 8-digit account number, 6-character A-Z/0-9 prefix and 1–90 day lookback rules.
  6. Save once and test an eligible low-risk invoice instruction.

Fields and decisions to review

This guide’s focusDetailed client guidance covering set the Tide reconciliation lookback period, with exact eligibility, security, verification and troubleshooting boundaries for the shipped Tide payment and Open Banking controls.
Account fieldsAccount name is free text; sort code is normalized to digits and must be exactly 6 digits when supplied; account number must be exactly 8 digits when supplied.
PrefixThe reference prefix is uppercased, stripped to A-Z/0-9 and limited to 6 characters; an empty value falls back to BRX.
LookbackReconciliation lookback is clamped server-side to 1–90 days and defaults to 7.
Automatic reconciliationThe automatic-reconciliation toggle controls whether after-cron processing attempts a bank-feed match.
Customer exposureConfigured account details are customer-facing only through an eligible payment instruction.

How to confirm it worked

Reopen the intended invoice, Tide transaction/reconciliation register and audit evidence. Confirm the full Tide transaction identifier where available, exact amount/currency/reference, reconciliation state, native invoice payment and latest timestamps. If the bank-feed state cannot be independently verified, keep the task unresolved and use the supported troubleshooting flow.

Questions clients commonly ask

When is an invoice actually treated as paid?Only when an eligible Tide credit is exactly reconciled and the native gateway payment is recorded; showing transfer instructions is not payment confirmation.
Can staff override a close-but-not-exact bank match?The automatic flow intentionally requires exact eligibility, reference and current outstanding amount. Investigate the bank/reference/invoice state instead of weakening the control.
What should I include in a support case?Include invoice ID, Tide transaction ID if available, reference, amount/currency, booking timestamp, connection status and visible error. Never include access/refresh tokens or private keys.
Does disconnecting remove history?No. Active connection tokens/state can be removed while historical payment, reconciliation and audit evidence is retained.

Technical basis for this guidance

This guide was checked against the supplied module code paths: tide_payments.php; controllers/Tide_payments.php; controllers/Tide_payments_client.php; models/Tide_payments_model.php; helpers/tide_payments_helper.php; libraries/Tide_gateway.php; libraries/Tide_open_banking_client.php; libraries/Tide_partner_client.php; views/admin; views/client/pay.php; install.php; config/routes.php. It documents shipped behaviour, validation, routes and evidence controls; it does not claim successful live provider network calls from offline inspection.

Controls, checks and common mistakes

  • Work in the intended tenant and remote accounting/business context.
  • Do not paste credentials, access tokens, refresh tokens or private keys into tickets or notes.
  • Do not bypass a missing mapping, validation error, permission gate, duplicate check or remote-verification requirement.
  • Do not repeat a non-idempotent write until you know whether the previous request reached the remote service.
  • Keep native record, remote evidence and audit/history state aligned before closing the task.
Provider and accounting boundaryConfigured account details are customer-facing only through an eligible payment instruction.
Browse connected topics: Account details and gateway settings Tide Payments Accounting & Bookkeeping
Understand the payment-reference prefix length and character rulesEnable or disable automatic Tide reconciliationAccounting & Bookkeeping guides