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

Accounting transaction centre overview

Review operational records by source type, see conversion status and open the accounting details created from each record.

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

Review operational records by source type, see conversion status and open the accounting details created from each record. 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 transaction controller has dedicated tables for invoices, payments, credit notes, applications, refunds, expenses and each supported integration. The visible groups are code-controlled.

Conversion records link the operational source to ledger lines. Deleting a conversion is different from deleting the CRM source and should follow the module's supported action.

When a group is empty, verify date filters, source status, module activation and permissions.

Step-by-step workflow

  1. Open Accounting → Transactions.
  2. Choose Sales, Expenses or an available optional-module group.
  3. Apply status, date or source filters.
  4. Open an unconverted record and check mappings and source status.
  5. Convert through the supported action where manual conversion is available.
  6. Open the accounting detail and verify balanced lines.
  7. Use reports to confirm the period totals.

Important fields and decisions

Source groupSales and Expenses are always available; optional groups depend on active modules.
Converted statusShows whether an Accounting transaction has been created.
Source statusControls whether a record is eligible for conversion.
Accounting detailShows debit and credit lines linked to the source.
Bulk actionsAvailable only for supported types and permissions.

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 convert the same economic event through both a source hook and a manual journal.
  • Investigate deleted or cancelled sources.
  • Keep source dates and currencies correct.
  • Use bulk actions only after testing a sample.
  • 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:invoicepaymentcredit noteexpensereconciliationjournal entrycheckreportcurrencypurchasewarehousepayrollmanufacturingapproval
Convert sales invoices to Accounting →Convert invoice payments to Accounting →Convert credit notes, applications and refunds →Convert expenses and recurring expenses →Review, correct or delete converted transactions →Troubleshoot unconverted or incorrectly mapped transactions →