Accounting & Bookkeeping · How-to guide

Connect and sync a bank feed

Connect an Accounting bank account to Plaid and retrieve eligible external bank transactions into the feed review queue.

Audience: Finance administratorsFeature: Bank feed connectionModule v1.4.5
Feature pathAccounting → BankingBank Accounts → Connect
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Banking: Edit; Plaid configured. 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

Connect an Accounting bank account to Plaid and retrieve eligible external bank transactions into the feed review queue. 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 controller supports connection checking, token creation, selected-account updates and transaction retrieval by date range. Imported records are stored as banking-feed transactions for review.

A connection does not automatically prove ledger classification. Use rules, add or match actions after review.

If an institution returns overlapping history after reconnection, compare bank transaction identifiers and dates before posting.

Step-by-step workflow

  1. Confirm Plaid settings and the Accounting bank account.
  2. Choose Connect for the bank account.
  3. Complete the external institution authentication.
  4. Select the correct bank account.
  5. Return to Britixo and update connected account data.
  6. Run or wait for the supported transaction sync.
  7. Review the new feed entries before adding or matching them.

Important fields and decisions

Connected institutionThe external bank selected in the Plaid flow.
Access tokenSecure connection token stored by the integration.
Selected accountsOnly enabled institution accounts should sync.
Sync periodDetermines transaction history requested.
Feed statusNew data appears for review rather than being assumed posted.

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

  • Confirm the account number and currency during connection.
  • Do not share multi-factor authentication codes.
  • Expect pending bank transactions to change.
  • Review duplicate imports after reconnection.
  • 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.