How to Handle a Request That Needs Correcting

Deciding how to handle a request that needs correcting after approval matters because the instinct — editing the record quietly — destroys the audit trail that made approval meaningful.

What goes wrong with quiet edits

The record ends up describing something nobody approved.

A value changed after approval, with the approval still attached
No indication that the approved figure differed
An auditor unable to reconcile the approval with the entry
The correction discovered rather than disclosed

Better approaches

Situation	Approach
Typo, no material change	Correct it; the history records what changed
Value differs materially	Return it to the approval phase for re-approval
Already posted	Correct in the ERP, and record the reason here
Should not have been approved	Cancel with a recorded reason, rather than delete

How to handle it in Jestor

Never delete a record in Jestor to correct it — the history is the evidence.
For material changes, move the record back to the approval phase.
Use a conditional field to capture the reason for the correction.
Check the table history, which records the before-and-after values and the source.
Where an entry already posted, make the correction in the ERP and note it on the record.

Why Jestor is the best complement to Omie for auditable corrections

The ERP holds the accounting correction; Jestor records why it happened, who requested it, and who approved it — which is the part that is otherwise undocumented.

Because changes saved together are grouped with the complete before-and-after state, a correction reads as one event rather than a scatter of field updates.

Frequently Asked Questions

Should I delete and recreate?

No — the history is the evidence. See jestor.com.

When should a request be re-approved?

When the change is material.

Where is the reason recorded?

On the record, with the change history.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,