The quick answer
Check the bill, acting user, row IDs, action dates and reasons together. In this historical ZoneApprovals example, one configured super approver rejects the bill. The historical view then displays all three approval rows as Rejected, including two previously shown as Approved. Those labels do not prove that every assigned employee personally rejected it.
Bill 4827 for Harbor Power Supply is 15,061.03 EUR. Alex Morgan acts as the configured super approver while Casey Lane remains the final assigned approver. The illustrations reconstruct a December 2022 vendor demonstration with fictional records. They do not demonstrate a current ZoneApprovals installation or its current behavior.
Before you start
Use an installed and configured ZoneApprovals SuiteApp, permission to view the bill and its approval logs, and authorization to perform the rejection. Alex's Super Approver setting is already configured in this example. Employee access alone does not authorize an override.
Labels, fields and rejection behavior can differ by SuiteApp version, form and configuration. This walkthrough stops at the rejected bill and its displayed historical rows. It does not resubmit, delegate, pay or inspect GL posting.
01 · Review the pending bill
Open Bill 4827. Match its vendor and amount, then confirm Pending Approval and Next Approver = Casey Lane. The Reject action belongs to the configured actor Alex, even though Casey is assigned next.
Open Zone Approvals > Active Approval Logs. IDs 381 and 382, assigned to Alex and Jordan Reed, show Approved. ID 383, assigned to Casey, shows Pending Approval. Note the existing approval reason on Jordan's row before entering a rejection reason.
02 · Reject with a reason
Select Reject. In Rejection Reason, enter The line is not supported by the agreed purchase specification. in required Edit Reason, then select Ok. Wait for the bill's result.
The recorded action is Alex's. Do not attribute it to Casey because Casey appears in Next Approver.
03 · Verify the rejected bill
Recheck the same bill number, vendor and amount. Its badge and Approval Status now show Rejected. Submit for approval is visible; leave it untouched. Its presence does not establish what another submission would do.
Next Approver = Casey Lane remains displayed after rejection. That retained value does not prove Casey still has an actionable pending approval.
04 · Compare the historical rows
Open Zone Approvals > Historical Approval Logs. Find the same displayed IDs 381, 382 and 383. All three now show Rejected in this historical configuration.
Scroll horizontally to read Date Approval Action, Overruled By, Rejection Reason and Approval Reason. Alex's first row carries the rejection reason and Alex under Overruled By. Jordan's second row retains its earlier approval reason. Casey's final assigned row has no displayed action date.
A blank date does not establish Casey's complete activity history. Likewise, the same displayed IDs do not establish whether the underlying records were updated, reused or stored through another mechanism. Historical Approval Logs is the view's label, not proof of immutable per-person decisions.
The summary still displays Remaining Approval Logs = 1, while the displayed total approval time changes from 1.55 to 4.69. Read these fields alongside the rejected bill and detailed rows. Do not treat the retained count as proof of another actionable step.
Common questions
Why do earlier rows show Rejected after a later rejection?
That is the displayed result in this configured historical example: the three IDs appear under Historical Approval Logs with Rejected status. It does not establish a universal ZoneApprovals rule or a separate rejection by each person.
Does Overruled By replace the assigned approver?
They are separate columns. Read the assignment, acting-user evidence, date and reason together. Casey remains assigned in the demonstrated row; the rejection action was performed by Alex.
Why does an approval reason remain on a rejected row?
The earlier reason remains visible in its own Approval Reason column in this example. It should not be confused with the Rejection Reason on the acting user's row or treated as proof of an immutable decision history.
Does Submit for approval prove the bill can be resubmitted successfully?
The button is visible after rejection. This walkthrough does not select it, so a new cycle, changed approvers, reset logs and successful resubmission remain unverified.