Settings, numbering, PDFs and vendor-portal options

Configure purchase-invoice expiry notice days

Set how many days before expiry the module should notify selected staff.

Audience: Purchasing staffPermission: purchase_settings: EditModule v1.7.9
Exact navigationAdmin Area → Purchase → Settings → Purchase Order Setting
Before you begin
  • Use an account with purchase_settings: Edit 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 how many days before expiry the module should notify selected staff. 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 → Settings → Purchase Order Setting.
  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.

Code-backed validations and workflow rules

  • Save through the module settings form and test with a controlled transaction.
  • Do not change unrelated purchase options during a scoped configuration update.
  • Purchase-invoice status changes require the dedicated invoice status capability.
  • Payment labels include Unpaid, Partially paid and Paid.

Expected result and verification

  • The supported configure purchase-invoice expiry notice days 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.