Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Debit notes, refunds and statements

Validate a purchase debit-note number

Resolve duplicate or invalid numbering. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Purchasing staffPermission: purchase_debit_notes capabilityModule v1.7.9
Jump to steps
Where to goAdmin Area → Purchase → Debit Notes → New/Edit → Number
Before you start
  • Use an account with purchase_debit_notes capability and confirm the intended record or setting before making a change.
  • Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
  • Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What you’ll accomplish

Resolve duplicate or invalid numbering. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Admin Area → Purchase → Debit Notes → New/Edit → Number.
  2. Select the exact record or option described in this guide.
  3. Complete the displayed fields or action using the rules below.
  4. Save or submit once and resolve any validation response.
  5. Check the resulting record, status, file, notification or integration effect.

Fields and options to review

Debit-note headerNumber, vendor, dates, currency and status.
AmountsItems/tax/totals, applications to purchase invoices and refund records.
OutputPDF, email recipients/attachment choice and vendor statement links.

Rules the system enforces

  • Debit notes support open/void state actions, invoice applications and refunds through separate controller paths.

How to confirm it worked

  • The supported validate a purchase debit-note number flow completes without bypassing permission or validation checks.
  • The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
  • Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

  • Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
  • Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
  • Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
  • Test settings and automated jobs with controlled records before production-wide use.
Delete a purchase debit noteChoose a vendor for a debit noteCreate a purchase debit noteCreate a purchase invoiceOpen Purchase currency ratesBrowse all Purchase Management guidesExpenses FinanceInvoices PaymentsContracts Documents