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

Convert Omni Sales returns and refunds

Account separately for goods returned through Omni Sales and the related money refunded to the customer.

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

Account separately for goods returned through Omni Sales and the related money refunded to the customer. 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 has separate return-order and refund transaction tables and an Omni Sales automatic-conversion setting. This preserves the distinction between physical or commercial return and payment.

Mappings determine sales return, inventory, cost, tax and refund accounts.

Use source references to prevent a refund from being matched to the wrong return.

Step-by-step workflow

  1. Open Omni Sales Return Orders.
  2. Confirm returned items, quantities, values and status.
  3. Review and convert the return entry.
  4. Open Omni Sales Refunds.
  5. Confirm refund amount, method and reference.
  6. Convert the refund entry.
  7. Reconcile the inventory, sales-return and payment accounts.

Important fields and decisions

Return orderReverses revenue, tax, inventory and cost effects according to source data and mappings.
RefundRecords the cash, bank or gateway clearing payment.
StatusControls whether each action is eligible for conversion.
Source referenceLinks the return and refund to the original sale.

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 treat a return request as a completed return.
  • Do not treat a return as proof that cash was refunded.
  • Check tax reversal and item values.
  • Match gateway settlements separately.
  • 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:invoicepaymentbankingreconciliationcheckreporttaxwarehousemanufacturingapprovalmappingdouble-entrycredit noteexpense
Configure Manufacturing and Omni Sales mappings →Configure payment mode account mappings →Reconcile a bank account →Use transaction and account audit reports →Accounting transaction centre overview →Convert sales invoices to Accounting →