Sign a purchase quotation
Capture a drawn or uploaded signature. 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.
Where to goAdmin Area → Purchase → Quotations → open quotation → Sign
Before you start
- Use an account with purchase_quotations capability and quotation status capability where applicable 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
Capture a drawn or uploaded signature. 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 → Quotations → open quotation → Sign.
- Go to the record and review the current status, approval chain and supporting files.
- Select the supported status, approval, confirmation or signature action.
- Provide the required reason, decision, signature or attachment when prompted.
- Submit once and verify the new status, approval entry, notification and locked/unlocked actions.
Fields and options to review
Quotation headerNumber, vendor, linked request, dates, currency/rate and status.
Commercial linesItems, quantity, price, tax, discount, subtotal and total.
EvidenceAttachments, comments, signature/uploaded e-signature, PDF and send activity.
Rules the system enforces
- Quotation status changes require the dedicated quotation status capability.
- Automatic purchase-order creation occurs only when the relevant option is enabled and the quotation reaches the supported approval state.
How to confirm it worked
- The supported sign a purchase quotation 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.