The quick answer
Read the original approver’s saved delegation, check the affected purchase order’s current approver and pending status, then open System Information > System Notes. Compare the approver field’s old and new values, date, actor and context. Context: Workflow identifies the execution context recorded for that System Note; it does not identify the originating workflow, action or delegation rule. Matching delegate names and dates give you a lead to confirm in the installed workflow’s definition and execution history.
The screenshots use fictional people and company data. This example reviews an existing configuration and purchase order without editing or approving either record.
Before you start
Use a role authorized to view the employee, purchase order and System Notes. This example uses an account-specific Advanced Approvals configuration. P2P Receiver/Approver PTO, Approval Delegate, Delegate From, Delegate To, First Approver Name, PO Approval Status, Next Approver/s and Pending Dept Approval are custom or implementation-specific fields, sections and values. Your installed approval solution or form may differ.
Riley Chen has a saved delegation to Jordan Patel from 10/12/2026 to 10/20/2026. The affected purchase order is PO8724, totaling 1,260.00. Read the actual employee, order and dates in your account; interpret audit timestamps in the account’s configured time zone.
01. Read the saved delegation
On this example’s employee form, open Riley’s record and select Human Resources. In its Purchasing | Journal Entries section, check First Approver Name and Purchase Approval Limit. The displayed limit is 15,000.00. This saved value alone does not establish which approval route the order used.
In P2P Receiver/Approver PTO, read Approval Delegate: Jordan Patel. Leave the record in view mode.
Read Delegate From and Delegate To together. Keep the interval available for comparison with the audit timestamp.
02. Check the pending purchase order
Open PO8724 and confirm the transaction number and 1,260.00 total. In Approval Process, read PO Approval Status: Pending Dept Approval.
Read Next Approver/s: Jordan Patel. Compare this with the saved delegate. A current approver name is a routing observation; it does not show that Jordan received a notification or approved the order.
03. Trace the recorded change
On the same order, select System Information, then System Notes, the standard transaction audit area. The visible fields and accessible history depend on the form, role and account configuration. Find the Next Approver/s change at 10/14/2026 9:18 am. Read the complete row, including Set by: -System-, Context: Workflow and Type: Change.
The row’s Old Value is Riley Chen and New Value is Jordan Patel. Compare the new value with the current approver field and the employee delegation.
October 14 is inside the displayed October 12–20 interval, and the order remains Pending Dept Approval. Compare dates and timestamps in the same applicable time zone. Confirm how the custom solution evaluates date-only or date-time fields and whether the end date is inclusive. These observations are consistent with the intended delegation; they do not prove that the PO matched its subsidiary, department or approval rules, that it was evaluated while delegation was active, or that the workflow read these fields. To establish that delegation caused the change, inspect the installed workflow’s definition and any available workflow or execution history, including other actions that can write the field. This review does not demonstrate an approval, automatic expiry or a delegate’s permission to act.
Common questions
Does Workflow context identify the workflow that changed the approver?
No. Read it as the recorded execution context for that System Note. Use the workflow definition and available execution history to investigate the specific workflow and action. The -System- actor does not identify the workflow by name.
Does the delegate’s name mean the order is approved?
No. The example still shows Pending Dept Approval. Verify the transaction’s approval status and any approval history separately.
What if my employee record does not have these delegation fields?
Check the employee form, role permissions, feature configuration and installed approval solution with your administrator. These custom fields are not universal NetSuite fields. Another implementation may delegate authority while retaining the original approver in its routing field.
What if System Notes does not show the change?
Confirm the purchase order, field, displayed view, filters and your access. The row may be absent, inaccessible to the role, or missing because the field or write mechanism did not produce the expected audit entry. Record the missing evidence and ask an authorized administrator to investigate. An incomplete or inaccessible history does not establish that a change did or did not occur.
Will the original approver return automatically after Delegate To?
This example does not verify expiry behavior. Changing saved delegation does not necessarily recalculate pending orders. Check the installed solution’s configuration; validate boundary dates, existing pending orders and new orders as solution-specific tests.