Debit notes, refunds and statements

Void a purchase debit note

Mark the note void rather than deleting it. 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 → open note → Mark Void

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

Mark the note void rather than deleting it. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

Go to Admin Area → Purchase → Debit Notes → open note → Mark Void.
Go to the exact record and review linked documents, payments, approvals, files and portal visibility.
Select the supported Delete, Remove, Void or Cancel action.
Verify 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 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 void 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.

Was this guide useful?Your response is stored only in this browser.