Generate contract, invoice and payment PDFs
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 use the supported core-derived outputs in broker workflows.
Where to goBroker Portal → open contract/invoice/payment → PDF
Before you start
- Use an account with Relevant access 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
Use the supported core-derived outputs in broker workflows. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Broker Portal → open contract/invoice/payment → 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
Exact actionGenerate contract, invoice and payment PDFs
Exact navigationBroker Portal → open contract/invoice/payment → PDF
Module version1.0.0
Access ruleRelevant access
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Financial recordClient/vendor/landlord, linked property/request/contract, date/due date, currency, items, taxes, discounts, totals and status.
Payment evidencePayment mode, amount, transaction ID, note/comments, date paid and email/PDF choices where exposed.
Rules and limits
- Reconcile totals and branding to source records.
- Verify linked CRM invoice/payment records before changing a real-estate payment or payout status.
- The module hooks after_payment_added to write property-related activity when the payment is linked.
Check it worked
- The supported generate contract, invoice and payment pdfs 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.
Related guides
Was this guide useful?Your response is stored only in this browser.