Delete a purchase-order payment
Remove a recorded PO payment through the supported action. 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.
Where to goAdmin Area → Purchase → Purchase Order → open order → Payments → Delete
Before you start
- 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 you’ll accomplish
Remove a recorded PO payment through the supported action. 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 → Purchase Order → open order → Payments → Delete.
- Go to the exact record and review linked documents, payments, approvals, files and portal visibility.
- Select the supported Delete, Remove, Void or Cancel action.
- Verify the action only after checking the consequence described below.
- Return to the list and verify whether the record was removed, retained with a status, or blocked by a code-backed restriction.
Fields and options to review
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.
Rules the system enforces
- 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.
How to confirm it worked
- The supported delete a purchase-order payment 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.