Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Contracts, templates and signatures

Filter purchase contracts

Follow this guide to filter by vendor, department, project and purchase order. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Purchasing staffPermission: purchase_contracts capabilityModule v1.7.9
Jump to steps
Where to goAdmin Area → Purchase → Contracts
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 you’ll accomplish

Filter by vendor, department, project and purchase order. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Admin Area → Purchase → Contracts.
  2. Select the exact record or option described in this guide.
  3. Complete the displayed fields or action using the rules below.
  4. Save or submit once and resolve any validation response.
  5. Check the resulting record, status, file, notification or integration effect.

Fields and options to review

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 the system enforces

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

How to confirm it worked

  • The supported filter purchase contracts 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.
Use SMS when a vendor signs a contractView project-linked purchase contractsCreate a purchase contractCreate a purchase order returnCreate a purchase invoiceBrowse all Purchase Management guidesExpenses FinanceInvoices PaymentsContracts Documents