Accept or reject Copilot corrections
Copilot is part of our active development pipeline. If you don't see the chat bar at the bottom of the invoice detail page, that's expected. Your administrator or your Mod AI partner can let you know when it's enabled for you.
The diff view is the key safety mechanism in Copilot. Nothing changes on the invoice until you accept. This page covers how the diff works, what happens when you accept, and how to undo.
The diff view
After you submit a prompt in the Copilot chat bar (at the bottom of the invoice detail page), the diff view opens directly above the chat bar, between the chat bar and the rest of the invoice content. It shows:
- A summary at the top: N field changes proposed (where N is the count).
- Every field the agent proposes to change, listed as a row with the field name on the left.
- The current value, struck through.
- The proposed new value, in green (or whatever your build uses for additions).
- Two action buttons at the bottom-right of the diff: Reject (left) and Accept (right).
Fields not in the diff are not changing. If a field you expected to change is missing, the agent did not include it.
Accept
Click Accept. Every change in the diff applies immediately. The invoice updates and the activity log records:
- The Copilot prompt you submitted.
- Every field that changed.
- The user who accepted (you).
- The timestamp.
After accepting, the diff view clears and the chat bar resets, ready for the next prompt.
Reject
Click Reject. The diff is discarded. Nothing on the invoice changes. You can write a refined prompt and try again.
Rejecting does not "consume" anything. There is no penalty for rejecting often.
Undo the last accepted change
If you accept a change and then realize it was wrong, click the Undo link in the Copilot panel. Right after you accept a diff, an Undo link appears for a few seconds in the toast or at the top of the chat bar area, allowing you to reverse the change with one click.
Undo only works for the most recent accepted Copilot change. To revert further back, edit the fields manually or use Copilot to restore the prior values in one prompt (for example, "Set GL account on line 2 back to 5100.").
What gets applied
Accepted changes apply atomically. Either the whole diff applies or none of it does. If the agent could not actually apply one of the changes (for example, a validation rule blocks it), the entire diff fails and the invoice is left in its previous state. The Copilot panel shows the reason.
This atomicity matters for multi-field prompts. You will not end up with a half-applied change where vendor changed but coding did not.
What does not get applied
Even when the diff is accepted, Copilot will not:
- Bypass validation rules. Rules run after the change applies. If a rule fails, the diff is rejected.
- Change locked fields. Some fields lock after specific transitions (for example, after final approval). Copilot respects those locks.
- Apply changes outside the current invoice. Copilot operates on one invoice at a time.
After accepting
The invoice now reflects the accepted change. From there, the standard flow continues:
- Validation rules re-run on the updated invoice.
- Any new notices generated by the change appear in the notices panel.
- The activity log records the change.
- If the invoice was already in approval, current approvers are notified that the underlying invoice changed.