Purchase invoices and payments

Choose purchase-invoice currency and rate

Set currency/rate before confirming lines and totals.

Audience: Purchasing staffPermission: purchase_invoices capability and invoice status capability where applicableModule v1.7.9
Exact navigationAdmin Area → Purchase → Invoices → New/Edit
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

Set currency/rate before confirming lines and totals. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

  1. Open Admin Area → Purchase → Invoices → New/Edit.
  2. Open the exact setting, option or record named in this guide.
  3. Enter or select the required value; leave unrelated options unchanged.
  4. Save the form and wait for the success response.
  5. Reload the page or open a controlled record to confirm the stored value is being used.

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.
Currency-rate recordCurrency/prefix code, stored rate, source/update action and log history.
ConversionThe selected document currency and currency_rate field affect purchase calculations.

Code-backed validations and workflow rules

  • Purchase-invoice status changes require the dedicated invoice status capability.
  • Payment labels include Unpaid, Partially paid and Paid.
  • Online retrieval depends on the configured external rate source and a successful HTTP response.
  • Review a rate before recalculating live financial documents.

Expected result and verification

  • The supported choose purchase-invoice currency and rate 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.