Upload a purchase-request file in the vendor portal | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/upload-a-purchase-request-file-in-the-vendor-portal Publisher: Pixie Technologies LLC Vendor portal and authentication Upload a purchase-request file in the vendor portal Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Attach a file using the authorised request hash. Audience: Vendor contacts; Permission: Authenticated active vendor contact and enabled portal; Module v1.7.9; Where to goVendor Portal → Purchase Request → open request → Upload Before you start - Use an account with Authenticated active vendor contact and enabled portal 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 Attach a file using the authorised request hash. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow. Follow these steps - Go to Vendor Portal → Purchase Request → open request → Upload. - Download or inspect the supported template/field requirements before preparing the file. - Select the Import or Upload action and select the intended file only. - Run validation and correct rejected rows, file types or required values. - Complete the import/upload and review the created records, attachments and any error file. 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 upload a purchase-request file in the vendor portal 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 Open a shared purchase request in the vendor portal (https://pixiecrm.com/help-centre/open-a-shared-purchase-request-in-the-vendor-portal)Delete a purchase-request file in the vendor portal (https://pixiecrm.com/help-centre/delete-a-purchase-request-file-in-the-vendor-portal)Open the vendor portal (https://pixiecrm.com/help-centre/open-the-vendor-portal)Create a vendor (https://pixiecrm.com/help-centre/create-a-vendor)Create a purchase item (https://pixiecrm.com/help-centre/create-a-purchase-item)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)