Purchase invoices and payments

Create a purchase invoice

Create a vendor invoice with source links, lines, tax, totals and due/payment information.

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

Exact navigationAdmin Area → Purchase → Invoices → New Invoice

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

Create a vendor invoice with source links, lines, tax, totals and due/payment information. 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 Invoice.
Choose the New, Add, Create or Start action exposed on that screen.
Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
Save or submit the form once; correct any validation message rather than bypassing it.
Open the resulting record and verify its number, status, totals, files, activity and downstream links.

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.

Code-backed validations and workflow rules

Purchase-invoice status changes require the dedicated invoice status capability.
Payment labels include Unpaid, Partially paid and Paid.

Expected result and verification

The supported create a purchase invoice 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.