Debit notes, refunds and statements

Edit a debit-note refund

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to update refund amount, mode or note.

Audience: Purchasing staffPermission: purchase_debit_notes capabilityModule v1.7.9

Jump to steps

Where to goAdmin Area → Purchase → Debit Notes → open note → Refunds → Edit

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 this guide helps you do

Update refund amount, mode or note. 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 → Refunds → Edit.
Go to the intended record from the list or preview.
Select Edit and change only the required fields.
Save once and resolve any validation or permission message.
Reopen the record and verify the update, status and audit/activity evidence.

Fields and options

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 and limits

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

Check it worked

The supported edit a debit-note refund 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.