Understand saving, validation, undo, and redo
Know when edits save, when validation runs, and how recoverable edit history behaves.
Saving follows the edit
Editable fields save through the workspace’s current interaction. Watch the save indicator and keep the page open until it confirms success or shows a recoverable error. Saving an edit does not approve the invoice or return it to AP; those require a separate action.
Bulk edits and line-type edits use the same save indicator as other invoice edits. Do not submit while saving or validation is running.
If someone changes the same field while you are editing, Clerked keeps your unsaved values and shows a conflict. Review the latest invoice before choosing Retry: Retry saves your retained values against that refreshed invoice. If you do not want to replace the newer values, leave without saving your draft and reopen the invoice.
If you try to leave while edits, Undo, or Redo are still saving, Clerked warns you about unsaved changes. Stay on the invoice until saving finishes; leaving anyway can lose a change that has not reached the server.
Validation follows current state
Validation can run after you make a change. A new validation issue may be the expected result of checking the updated invoice rather than a failed save. Read the current check result before taking the next action.
Export readiness can also depend on the source PDF or another requirement outside the invoice fields. Saving a change does not clear an unresolved export-readiness message. After the cause is repaired, retry the available submission, approval, or export action to check it again.
Undo or redo a recent edit
When Undo or Redo appears, it applies to the recent saved changes currently available to your account on that invoice. Clerked verifies that history against the latest record before applying it; another person’s edit can make an earlier command unavailable. Check the changed field and save indicator before repeating a command.
Undo and Redo are unavailable while a Clark proposal is pending or applying. A finished proposal marked stale does not prevent ordinary editing or Undo and Redo. Undo and Redo restore the recorded values together with their dependent coding. If the recorded change conflicts with current rules or newer work, Clerked refuses it and shows an explanation.
Discard a saved change after refreshing
During approval or eligible export recovery, the field’s Changed control shows its previous and current values. In the expense table, use the small colored marker inside the field’s corner. Choose Discard change to restore that field, or open the document’s changes chip and choose Restore available changes to restore the supported changes together. These controls use the saved approval basis, not the recent Undo history.
Discard applies immediately without a confirmation dialog and can recalculate dependent values. It does not make an approval decision. If a previous value is unavailable or current rules prevent restoration, that change remains listed with an explanation. Review the remaining changes after restoring.