Debit notes, refunds and statements

Delete a purchase debit note

Remove a debit note through the supported action.

Audience: Purchasing staffPermission: purchase_debit_notes capabilityModule v1.7.9

Exact navigationAdmin Area → Purchase → Debit Notes → Delete

Before you begin

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 this guide covers

Remove a debit note through the supported action. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

Open Admin Area → Purchase → Debit Notes → Delete.
Open the exact record and review linked documents, payments, approvals, files and portal visibility.
Choose the supported Delete, Remove, Void or Cancel action.
Confirm the action only after checking the consequence described below.
Return to the list and verify whether the record was removed, retained with a status, or blocked by a code-backed restriction.

Fields, choices and supported possibilities

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.

Code-backed validations and workflow rules

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

Expected result and verification

The supported delete a purchase debit note 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.