Purchase orders, delivery and payments

Set purchase-order Incoterm and days owed

Store delivery/payment commercial terms.

Audience: Purchasing staffPermission: purchase_orders capability and purchase-order status capability where applicableModule v1.7.9
Exact navigationAdmin Area → Purchase → Purchase Order → New/Edit
Before you begin
  • Use an account with purchase_orders capability and purchase-order 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

Store delivery/payment commercial terms. 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 → Purchase Order → 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

Order headerOrder name/number, vendor, linked request/quotation, department, project, type, buyer and optional linked clients/sales invoices.
Commercial dataCurrency/rate, items, tax, discount type/value, shipping fee, days owed and totals.
Delivery dataShipping address/country, Incoterm, vendor note, terms, delivery date/status, files and payments.

Code-backed validations and workflow rules

  • Purchase-order status changes require the dedicated purchase_order status capability.
  • Delivery states include Undelivered, Pending delivered, Partially delivered and Completely delivered.
  • Project can be mandatory when pur_order_project_required_condition is enabled.

Expected result and verification

  • The supported set purchase-order incoterm and days owed 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.