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

Add a bank transaction from a feed

Create a new Accounting transaction from a bank-feed row when no existing CRM or ledger transaction represents the movement.

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

Create a new Accounting transaction from a bank-feed row when no existing CRM or ledger transaction represents the movement. 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 banking controller provides add_transaction_save and related feed actions. Adding from the feed creates local accounting data based on the external transaction.

This workflow is suitable for bank charges, interest, direct debits or other movements not already recorded elsewhere, subject to policy.

If the movement belongs to a customer invoice or supplier bill, record the operational payment and match it instead so subledgers remain correct.

Step-by-step workflow

  1. Confirm no invoice payment, bill payment, expense, transfer or journal already exists.
  2. Select Add on the feed row.
  3. Review bank account, date and amount.
  4. Choose the correct offset account and classification.
  5. Add payee, description and reference.
  6. Save and inspect the generated double-entry transaction.
  7. Keep the row matched to the new transaction for reconciliation.

Important fields and decisions

Bank sideThe selected feed account and deposit or withdrawal amount.
Offset accountThe income, expense, liability, asset or equity account explaining the movement.
Payee and descriptionProvide audit context.
Date and referenceRetain statement identity.
Class or payment methodComplete where supported and required.

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 add duplicates.
  • Do not use suspense accounts without a resolution plan.
  • Use Transfer for movement between owned bank accounts.
  • Use source CRM workflows when a customer or supplier record should be updated.
  • 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:invoicepaymentexpensebankingreconciliationtransfersupplier billvendorcheckreportapprovalmappingPlaiddouble-entry
Match a bank transaction →Create a bank transfer →Pay a supplier bill →Convert invoice payments to Accounting →Banking workspace overview →Create and manage an Accounting bank account →