Key takeaway
Agree the rejection outcome: restart, return to a step, request a supplement, or close. Preserve versions and define which approvals need renewed review when critical fields change. Do not automatically retain or invalidate every prior approval; the scope follows agreed business rules.

Consider a hypothetical case. Finance clicks reject and writes "amount is wrong." The request leaves their queue and shows up for the drafter as rejected. The drafter fixes the number and submits again. The department lead has to approve something they already approved last week, or the system skips that lead and finance still sees the old explanation. Both feel like a broken workflow. What is usually missing is a decision made in advance: when approval fails, where does this record go?
Pick the outcome before the click is allowed. Send it back to the drafter and restart, return it only to a named step, keep it here and ask for a supplement, or close it and forbid resubmission on the same record. If the amount, the payee, or the scope changed, earlier approvals should be void. A typo should not make everyone sign again.
The payment-request examples illustrate state design, not a universal approval policy. Decide which steps need renewed review from agreed change-impact rules; a full restart is one possible configuration.
Four outcomes, not one reject button
- Return and resubmit
- Return to a named step
- Keep the step and request details
- Close the record
Agree review scope and routing under the actual business policy; these are not universal approval rules.
Send back and restart when the request itself changed. A new amount, supplier, scope, or discount means earlier people agreed to a different request. After the drafter edits it, submission starts again at the first approver.
Return to a named step when only that step was wrong, or the missing material matters only there. The department lead picked the wrong expense category and finance has not reviewed it yet. After the correction, continue from the department lead. Do not mint a new request, and do not assume finance is the right return point.
Asking for a supplement is not a rejection. The invoice copy is missing or the contract number is blank, and the amount and payee are unchanged. The request should stay in the current approver's queue, still in review. The drafter may add only the named field or file. The approver cannot pass it until that arrives, and should not lose it from the queue. If the only buttons are approve and reject, people will reject in order to ask for an attachment, and the whole chain gets knocked backward.
Reject and close when this request should not continue. A duplicate payment, a wrong party that will not be corrected, a drafter withdrawing. The closed record is read-only. If the work comes back later, create a new request and link it. Do not quietly edit a closed record and submit it again.
These four are not the table of who may approve. Who may approve, and up to what amount, belongs in permissions. This article only fixes where the record goes once the answer is no.
Which edits void an approval that already passed
Write down the critical fields first. On a hypothetical payment request they might be: amount, currency, payee, linked order, expense category. If any of those change after a return, every step that had already passed is void and the chain restarts.
Non-critical edits need not restart everyone. A typo in a note, an attachment that was explicitly requested, a planned payment date moved inside an allowed window: usually only the step that was returned needs another look, or the current approver simply confirms the supplement.
Write the boundary down. Otherwise finance hears "the amount changed, so of course we restart," and the drafter hears "I only changed a number everyone had already accepted."
Do not grow the order's or project's own progress statuses from rejection reasons. A returned payment request does not require the order to gain a status called "approval failed." The request has versions and a path. The order stays on its business step.
A hypothetical path table for a payment request
This is hypothetical, not a company policy. There are three steps: the drafter submits, a department lead agrees, finance reviews. In the example, finance must review amounts above 20,000. That threshold is an example too.
Why it did not pass | Outcome to choose | Who may edit | Earlier approvals | Where the next submission starts | Current approver's queue |
|---|---|---|---|---|---|
Amount, payee, or order number is wrong | Back to the drafter and restart | Drafter | Void | Department lead | Remove from finance |
Wrong expense category, amount unchanged | Back to the department lead | Lead or drafter, as you agree | The submit still counts; the lead's approval is void | Department lead | Remove from finance |
Invoice missing, other fields unchanged | Supplement | Drafter may add only the file | All remain valid | No new submission; the file returns to the current approver | Keep in finance, marked waiting for supplement |
Duplicate, or payment will not happen | Reject and close | Nobody | Unused | Resubmit on this record is disallowed | Remove, status becomes closed |
The comment is empty, or the click was a mistake | Do not accept it as a rejection | Not applicable | Unchanged | Not applicable | Stays with the current approver |
The last row should be a system rule: a reject, return, or close requires a comment and a reason type from this table. Without a type, the system cannot choose a path.
A supplement needs a time limit, but the limit is a business choice. Do not copy a generic number of days. When time runs out, either return the request to the drafter or leave it with the approver and remind them. Pick one and put it in the same table.
Resubmission is a new version, not an overwrite
When the drafter submits again, do not paint over the previous amount and comments. Keep at least:
- A version number, starting at 1.
- The old and new values of the critical fields on this version.
- Who chose which outcome, when, and the comment text.
- Which passed steps were voided and which still stand.
- Who the current step is now.
The approver opens the latest version and can still read the previous comment. Without that, a restart looks like "why is this back?" A fuller audit trail of every click is a separate field list. The approval screen itself still has to show the version diff.
Say who owns the record during the wait. After a return to the drafter, the drafter is the owner, not finance. During a supplement, the approver is still the owner; the drafter has only been asked to add something. If that is unstated, both sides will fail to find it, or each will assume the other is holding it.
Who receives the task when an approver is away is a delegation question. This article assumes the approver is present and only defines where a no sends the record.
A checklist for return paths
[Approval return checklist]
1. Paths
- Reason types for a no:
- For each reason: restart, return to a named step, supplement, or close:
- During a supplement, whose queue holds the record, and what is the status called:
- After close, is edit-and-resubmit on the same record forbidden:
2. Critical fields
- Which fields void earlier approvals when changed:
- Which edits are non-critical and do not need a full re-sign:
- Who confirms that field list:
3. Versions
- Does resubmission create a version, with the old comment still readable:
- Is a comment required, and must a reason type be chosen first:
- Can the screen show old and new values of critical fields:
4. Ownership
- Who is the owner after a return:
- How long may a supplement wait, and which path runs on timeout:
- Is it explicit that the order or project status does not change because of the rejection reason:Fill in the table before drawing an approval canvas. A canvas with a single reject arrow will be interpreted differently by every user after launch. Existing paper or chat examples of returns can go into the system preparation guide, then be set next to how business system development treats process and records.
If the question is whether an AI agent needs a person before it reads, changes data, or sends something outward, that is permissions, approval, and handoff for AI agents. If the question is who is accountable after an agent makes a mistake, that is logs, approval, and the responsibility chain. Neither says where a rejected payment request should land.