Run the purchase-invoice report
Review vendor invoices and payment status.
Exact navigationAdmin Area → Purchase → Reports → Purchase Invoice Report
Before you begin
- 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 this guide covers
Review vendor invoices and payment status. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Purchase → Reports → Purchase Invoice Report.
- 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, choices and supported possibilities
Invoice headerVendor, contract, purchase order, invoice number, date/due date, currency/rate and payment status.
Invoice linesItems, quantity, rate, tax, discount and totals.
SettlementPayments, batch payments, attachments, recurrence where exposed, expiry notification and linked debit applications.
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.
Code-backed validations and workflow rules
- Purchase-invoice status changes require the dedicated invoice status capability.
- Payment labels include Unpaid, Partially paid and Paid.
- Reports require purchase_reports view capability.
- Figures depend on stored currency/rate, status and date values; reconcile against source records.
Expected result and verification
- The supported run the purchase-invoice report 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.