Understand onboarding invoices and downstream records
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 review any invoice/contract/customer/property records created by the workflow.
- Use an account with Authorised reviewer with target-record 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
Review any invoice/contract/customer/property records created by the workflow. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Onboarding workspace → Linked Records.
- 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
Rules and limits
- Verify exactly one intended downstream record exists and values match the approved terms.
- Public application and onboarding actions use token/record checks and explicit workflow states.
- Do not advance a workflow until the required party, property, dates, financial terms and consent/evidence are complete.
- 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 understand onboarding invoices and downstream records 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.
