Purchase requests

Troubleshoot purchase-request validation

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

Resolve missing department/requester, invalid items, numbering, totals, permissions or approval state.

Audience: Purchasing staffPermission: purchase_request capability and status capability where applicableModule v1.7.9

Jump to steps

Where to goAdmin Area → Purchase → Purchase Request → New/Edit

Before you start

Use an account with purchase_request capability and 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 this guide helps you do

Resolve missing department/requester, invalid items, numbering, totals, permissions or approval state. 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 → Purchase Request → New/Edit.
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 and options

Request headerRequest code/name, requester, type, department, project, related sales estimate/invoice, currency and rate.

Request linesItems, description, quantity, unit, tax, price, discount, subtotal and total.

SourcingSelected vendors, attachments, public share/request-for-quotation actions and approval status.

Rules and limits

Purchase-request status changes use the dedicated purchase_request status capability in addition to record access.
Department can be mandatory when pur_department_required_condition is enabled.

Check it worked

The supported troubleshoot purchase-request validation 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.