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

Import bank transactions from a spreadsheet

Use the supplied banking import format to load statement transactions when a connected feed is unavailable or inappropriate.

Audience: Accounting staffFeature: Bank importModule v1.4.5
Feature pathAccounting → Banking → Import Banking
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

Use the supplied banking import format to load statement transactions when a connected feed is unavailable or inappropriate. 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 sample banking workbooks, an import screen, import table and file-processing actions. It also supports importing edited feed spreadsheets separately.

Imported bank rows enter the review workflow and are not necessarily posted to the ledger. Add, match, ignore or apply rules after review.

Use statement totals and reconciliation to detect missing or duplicate lines.

Step-by-step workflow

  1. Download the banking sample file.
  2. Prepare a small date range from the official statement.
  3. Keep headers and date formats unchanged.
  4. Select the correct Accounting bank account.
  5. Upload and run the import.
  6. Review imported and rejected rows.
  7. Compare opening, closing and transaction totals with the statement.

Important fields and decisions

Sample workbookDefines the accepted columns and data format.
Bank accountDetermines which feed and register receive the imported rows.
DateMust match the statement transaction date.
Description, payee and referenceSupport rule and match logic.
Withdrawal and depositUse the correct direction.
Unique transaction dataHelps identify duplicates.

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 import the same statement range twice.
  • Do not reverse deposit and withdrawal columns.
  • Keep bank data confidential.
  • Correct rejected rows in a new controlled file.
  • 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:paymentbankingreconciliationcheckreportapprovalmappingdouble-entryPlaid
Review and edit banking feeds →Export, edit and re-import banking feeds →Reconcile a bank account →Create banking rules →Banking workspace overview →Create and manage an Accounting bank account →