Britixo CRMBritixo CRM Enterprise Help Centre
Accounting & Bookkeeping · How-to guide

Configure Plaid bank-feed settings

Set the environment and connection values used by the optional Plaid integration before connecting bank accounts.

Audience: Finance administratorsFeature: Plaid settingsModule v1.4.5
Feature pathAccounting → Settings → Plaid Environment
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Settings: Edit. A related screen can remain hidden when an optional module is inactive, a source record is in an ineligible status, the selected account is inactive or the user is not an assigned approver.

What this feature does

Set the environment and connection values used by the optional Plaid integration before connecting bank accounts. It forms part of Britixo Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.

How the module flow works

The module includes actions to create a Plaid token, update the environment, connect bank accounts, update selected accounts and fetch new transactions. A verification controller is also included.

Plaid availability and data freshness depend on the external institution and configured environment. Britixo does not manufacture missing bank data.

If a connection fails, record the time and non-sensitive error state, then review credentials, redirect configuration and institution status.

Step-by-step workflow

  1. Obtain approved Plaid credentials.
  2. Open Plaid Environment settings.
  3. Select the correct environment.
  4. Enter credentials through the protected settings form.
  5. Save and use the Connect action from Bank Accounts.
  6. Complete the institution flow and select accounts.
  7. Verify new transactions in Banking Feeds.

Important fields and decisions

EnvironmentUse the approved sandbox, development or production context.
Client credentialsStore only values issued for the organisation.
Token stateRepresents the connection to a financial institution.
Bank account selectionChoose which connected accounts are imported.
Logs or verificationUse available status data to diagnose connection issues.

What happens after completion

After the action is saved, Britixo keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.

  • Open the saved record and confirm its final status.
  • Review the source reference and every debit and credit line where ledger data was created.
  • Use the relevant register, ageing, reconciliation or report to verify the wider effect.

Controls, checks and common mistakes

  • Never paste production secrets into support messages.
  • Test in a non-production environment where possible.
  • Do not reconnect repeatedly when a token is valid.
  • Review regional and institution availability.
  • Use the least destructive correction available and record the reason for material changes.
  • Do not bypass a permission, approval or closed-period control by changing unrelated data.
Accounting and data safetyDeletion, reset, void, refund, mapping, journal and reconciliation actions can change financial history. Use approved access, retain supporting evidence and validate the result in the General Ledger or relevant control report.
Browse connected topics:bankingreconciliationcheckreportcurrencyapprovalmappingPlaiddouble-entryavailabilitycustomers
Connect and sync a bank feed →Review and edit banking feeds →Create and manage an Accounting bank account →Banking workspace overview →Import bank transactions from a spreadsheet →Export, edit and re-import banking feeds →