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

Match a bank transaction

Connect a feed row to an existing Accounting transaction such as a customer payment, supplier payment, transfer or manual entry.

Audience: Accounting staffFeature: Transaction matchingModule v1.4.5
Feature pathAccounting → Banking → Banking Feeds → Match
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Banking: 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

Connect a feed row to an existing Accounting transaction such as a customer payment, supplier payment, transfer or manual entry. 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 includes match_transactions, match_transaction_save, unmatch and candidate-data actions. It also provides automatic matching and a closest-date window setting in the feed workflow.

Matching does not create a second ledger entry; it associates the bank evidence with the existing Accounting transaction.

When a single bank settlement covers several source transactions, use the supported bulk-match workflow and confirm the summed amount.

Step-by-step workflow

  1. Open Match on the feed row.
  2. Review automatic candidate suggestions.
  3. Compare amount, direction, date, reference, customer or vendor.
  4. Select the correct existing transaction.
  5. Save the match.
  6. Open both records and verify the connection.
  7. Include the matched line in bank reconciliation.

Important fields and decisions

Feed amount and directionMust be compatible with the candidate transaction.
Date windowCandidate matching can use a closest-date window.
Reference and payeeSupport identification.
VarianceExact, under or over differences require review.
Matched transactionShould represent the same economic event.

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

  • Do not match solely on amount.
  • Do not combine unrelated transactions unless the supported bulk logic represents the settlement.
  • Investigate variances.
  • Unmatch through the supported action if evidence changes.
  • 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:invoicepaymentbankingreconciliationtransfersupplier billvendorcheckreportapprovalmappingdouble-entryPlaidcustomers
Bulk match bank transactions →Unmatch or correct a bank transaction →Reconcile a bank account →Convert invoice payments to Accounting →Banking workspace overview →Create and manage an Accounting bank account →