Automation, notifications, security and troubleshooting

Send a purchase debit-note email

Verify recipients and attached PDF option.

Audience: Purchasing staffPermission: Administrator or relevant Purchase capabilityModule v1.7.9

Where to goAdmin Area → Purchase → Debit Notes → open note → Send

Before you start

Use an account with Administrator or relevant Purchase 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

Verify recipients and attached PDF option. 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 → Send.
Go to the source record and verify its recipient, status, totals and attachments.
Select the Send, Email, Share or Request action described in the guide.
Select recipients and attachment/signature options shown by the form.
Submit once and verify the activity, delivery metadata, public link or approval request created by the module.

Fields and options

ActionSend a purchase debit-note email

Exact navigationAdmin Area → Purchase → Debit Notes → open note → Send

Module version1.7.9

VerificationVerify the saved record, status, output or setting in the same workspace and review any linked activity, file or notification.

Rules and limits

The action is available only when the module, current record state and required capability allow it.
Use the displayed validation response to correct the record; do not bypass controller or model checks.
Verify downstream files, notifications, linked records and status changes after saving.

Check it worked

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