The quick answer
Open the saved bill, read its custom Approval Tracking entries in date and time order, then compare them with the bill’s Communication area and its Messages list. Match the bill reference, action, displayed time at the precision shown, and displayed recipient. In this example, custom status Approved coexists with a retained rejection reason and a populated next-approver list.
A retained rejection reason can be useful context after a bill is approved. It can also be misleading if you read it without the current status and history. This walkthrough compares the fields and records visible on one bill after a rejection and resubmission.
The example uses an installed custom approval solution. Its Approval Tracking subtab is distinct from native System Notes. Screenshots use sample data and fictional person and operating-company names.
Before you start
Use a role that can view the saved bill, the custom Approval Tracking subtab and its associated messages. Your form and installed approval solution must expose these surfaces; another account may use different tabs and fields.
Start with an existing bill that has the history you need to investigate. This example uses BV-9281, Northline Services, 460.00, dated 10/22/2026. The review reads existing records. It leaves approval actions, Edit links, message buttons and attachments untouched.
01. Read the saved bill
Open the bill through your account's bill list, search or recent-record link. Confirm the transaction number, vendor, amount and date before comparing its history.
Read the native transaction status Open separately from the custom Approval Status band showing Approved. Those are two displayed values; the custom status alone does not establish posting, payment or accounting finality.
In Approvals, read Approved Comments and Reject Reason together. Here they show Receipt checked; amount accepted. and Training charge needs a receipt. Both are populated on this saved example with custom status Approved.
The Next Approver list still contains Sam Rivera, Dana Chen and Lee Campbell. A populated list alone does not establish that this approved bill is waiting for another action.
02. Read Approval Tracking
Open Approval Tracking. Read Set By, Action, Date and Rejection Reason together, leaving the visible Edit links untouched.
All four entries are dated 10/22/2026:
- 10:14:07 am: Alex Morgan — Submitted for Approval.
- 10:17:31 am: Nora Patel — Rejected.
- 10:21:10 am: Alex Morgan — Resubmitted for Approval.
- 10:25:52 am: Sam Rivera — Approved.
Compare the rejected entry's reason with the retained Reject Reason on the bill. Both show Training charge needs a receipt.
Describe Set By names as displayed values. This review does not establish how those names were authenticated or entered. The table and its Edit links also do not demonstrate immutable or complete history.
03. Compare message records
Open the bill’s Communication subtab and read its Messages list. The newest row appears first. Read the dates, recipients and subjects without opening a message:
- 10:25 am: Approved notification to alex.morgan@example.com.
- 10:21 am: Awaiting Your Approval to the displayed approver recipient addresses.
- 10:17 am: Rejected notification to alex.morgan@example.com.
- 10:14 am: Awaiting Your Approval to the displayed approver recipient addresses.
Each subject identifies Bill BV-9281 and Northline Services. The subjects and displayed minutes correspond to the tracking sequence. Tracking includes seconds; this message list shows minutes. Keep that difference when describing a match.
If columns extend beyond the panel, scroll the message list horizontally to read Type, Files, Attachments and Internal Only. The example shows Email records and attachment metadata. A listed email or file does not prove delivery, reading or the exact cause of message creation.
04. Recheck retained values
Return to Approvals and record that the saved bill currently displays Submission Date as 10/22/2026, custom status Approved, and the rejection reason and approval comment. Submission Date is date-only here. It does not have the same precision as the tracking timestamps, and this review does not establish its update rules across resubmissions.
Leave the saved bill unchanged. Record the observed summary, four tracking entries and four message rows. If a reference, date or reason differs, record the discrepancy and investigate the configured solution before inferring what happened.
Common questions
Why does an approved bill still show a rejection reason?
This custom example retains the earlier reason alongside Approved Comments and custom status Approved. That coexistence is visible on this bill. Retention behavior depends on the installed solution; the example does not establish a rule for every approval workflow.
Is Approval Tracking the same as System Notes?
No. Approval Tracking in this example is a custom solution subtab. This procedure does not inspect native System Notes or establish equivalence between the two.
Does Set By prove who approved or rejected the bill?
It shows the name stored in the displayed entry. This review does not establish the authentication or identity checks behind that value.
Do the message rows prove that notifications were delivered?
No. The list shows associated message records, subjects, recipients and displayed dates. It does not establish delivery or reading. No message body is opened in this walkthrough.
Does a populated Next Approver list mean approval is pending?
Not by itself. This bill retains three names while its custom status is Approved. Read the current custom state and the history together, and check your solution's configured meaning before treating the list as pending work.
Is Submission Date the latest approval timestamp?
That is not established here. The displayed Submission Date is date-only, while tracking entries show date and time. Read each field at its displayed precision and verify its configured update rules separately.