Contracts, templates and signatures

Generate a purchase-contract PDF

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

Render the contract PDF.

Audience: Purchasing staffPermission: purchase_contracts capabilityModule v1.7.9

Jump to steps

Where to goAdmin Area → Purchase → Contracts → open contract → PDF

Before you start

Use an account with purchase_contracts 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

Render the contract PDF. 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 → Contracts → open contract → PDF.
Select the New, Add, Create or Start action exposed on that screen.
Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
Save or submit the form once; correct any validation message rather than bypassing it.
Go to the resulting record and verify its number, status, totals, files, activity and downstream links.

Fields and options

Contract headerContract name, vendor, purchase order, project, department and service category.

Commercial termsPayment terms, payment amount, payment cycle, contract value, notes and description/content.

SigningSigner, email, signed status, drawn/uploaded signature, send recipients, attach-PDF choice and SMS option where enabled.

Rules and limits

Contract actions are governed by purchase_contracts capabilities.
Signature/send flows depend on the stored signer/email and configured email/SMS services.

Check it worked

The supported generate a purchase-contract pdf 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.