Debit notes, refunds and statements

View a purchase debit note

Review status, totals, applications, refunds, files and reminders.

Audience: Purchasing staffPermission: purchase_debit_notes capabilityModule v1.7.9

Exact navigationAdmin Area → Purchase → Debit Notes → open note

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

Review status, totals, applications, refunds, files and reminders. 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 → open note.
Select the relevant record, filter, report, model or configuration described below.
Use the displayed action or read the current values without altering unrelated data.
Compare the output with the code-backed rules and expected result in this guide.
Record or correct any mismatch before relying on the output in production.

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 view 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.