Link a CRM expense to a vendor | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/link-a-crm-expense-to-a-vendor Publisher: Pixie Technologies LLC Files, notes, comments and CRM links Link a CRM expense to a vendor 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 vendor field added by Purchase Management to supported expense flows. Audience: Purchasing staff; Permission: Capability of the related Purchase record; Module v1.7.9; Where to goAdmin Area → Expenses → New/Edit → Vendor Before you start - Use an account with Capability of the related Purchase record 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 vendor field added by Purchase Management to supported expense flows. 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 → Expenses → New/Edit → Vendor. - Select the exact record or option described in this guide. - Complete the displayed fields or action using the rules below. - Save or submit once and resolve any validation response. - Check the resulting record, status, file, notification or integration effect. Fields and options Vendor identityCompany/name, code, tax/VAT, phone, website, category/group, address and status as exposed by the vendor form. Contacts and accessVendor contacts, vendor administrators, portal status, language and welcome/notification settings where applicable. Rules and limits - Vendor actions are capability-gated; portal functions also depend on the vendor-portal setting and contact authentication. Check it worked - The supported link a crm expense to a vendor 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 Use Purchase project tabs (https://pixiecrm.com/help-centre/use-purchase-project-tabs)Use optional Warehouse integration for returns (https://pixiecrm.com/help-centre/use-optional-warehouse-integration-for-returns)Download a Purchase Management file by folder and attachment ID (https://pixiecrm.com/help-centre/download-a-purchase-management-file-by-folder-and-attachment-id)Run the imported-goods report (https://pixiecrm.com/help-centre/run-the-imported-goods-report)Understand the Purchase Management cron sequence (https://pixiecrm.com/help-centre/understand-the-purchase-management-cron-sequence)Browse all Purchase Management guides (https://pixiecrm.com/help-centre/category/purchase-management)Expenses Finance (https://pixiecrm.com/help-centre/category/expenses-finance)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)Contracts Documents (https://pixiecrm.com/help-centre/category/contracts-documents)