Purchase invoices and payments

Link a purchase invoice to a contract

Select the related vendor contract.

Audience: Purchasing staffPermission: purchase_invoices capability and invoice status capability where applicableModule v1.7.9

Exact navigationAdmin Area → Purchase → Invoices → New/Edit → Contract

Before you begin

Use an account with purchase_invoices capability and invoice status capability where applicable 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

Select the related vendor contract. 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 → Invoices → New/Edit → Contract.
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.
Verify the resulting record, status, file, notification or integration effect.

Fields, choices and supported possibilities

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.

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.

Code-backed validations and workflow rules

Contract actions are governed by purchase_contracts capabilities.
Signature/send flows depend on the stored signer/email and configured email/SMS services.
Purchase-invoice status changes require the dedicated invoice status capability.
Payment labels include Unpaid, Partially paid and Paid.

Expected result and verification

The supported link a purchase invoice to a contract 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.