Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Reports, dashboard and analysis

Filter Purchase reports by period

Follow this guide to choose month, year, custom date range or report-time option where exposed. 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_reports: ViewModule v1.7.9
Jump to steps
Where to goAdmin Area → Purchase → Reports
Before you start
  • Use an account with purchase_reports: View 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

Choose month, year, custom date range or report-time option where exposed. 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 → Reports.
  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

FiltersReport type, period/month/year/date range, currency, status and vendor/project filters where displayed.
OutputTable/chart totals derived from purchase records visible to the authorised user.

Rules the system enforces

  • Reports require purchase_reports view capability.
  • Figures depend on stored currency/rate, status and date values; reconcile against source records.

How to confirm it worked

  • The supported filter purchase reports by period 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.
Run purchase-order statistics by typeFilter Purchase reports by currencyRun the imported-goods reportOpen Purchase currency ratesDownload a Purchase Management file by folder and attachment IDBrowse all Purchase Management guidesExpenses FinanceInvoices PaymentsContracts Documents