Purchase invoices and payments

Edit a purchase invoice

Follow this guide to update an editable vendor invoice. 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_invoices capability and invoice status capability where applicableModule v1.7.9

Jump to steps

Where to goAdmin Area → Purchase → Invoices → open invoice → Edit

Before you start

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 you’ll accomplish

Update an editable vendor invoice. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

Go to Admin Area → Purchase → Invoices → open invoice → Edit.
Go to the intended record from the list or preview.
Select Edit and change only the required fields.
Save once and resolve any validation or permission message.
Reopen the record and verify the update, status and audit/activity evidence.

Fields and options to review

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.

Rules the system enforces

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

How to confirm it worked

The supported edit 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.

Was this guide useful?Your response is stored only in this browser.