It's one of the first frustrations new ERPNext users run into. You submit an invoice, spot a mistake, and find you can't simply edit it. Other systems let you change anything at any time, so why doesn't ERPNext?
Because that's exactly what makes your books trustworthy.
What Happens Instead
When an invoice, payment or journal is submitted, it's final. To correct it, you cancel it and create an amended copy. Since version 13, ERPNext doesn't delete the original accounting entries when you cancel. It records reversing entries instead, so the ledger shows the original, the reversal and the correction, each with who did it and when.
Why That's a Good Thing
- Nothing disappears. Every figure that was ever posted can be traced, which is exactly what an auditor wants to see.
- Fraud gets harder. Nobody can quietly change last month's numbers.
- Reports stay consistent. A report you sent to the bank or GRA last month still matches the books today.
- Mistakes are visible. Patterns of corrections can show where training is needed.
What You Can Still Change
Not every field is locked. Details that don't affect the accounts, such as remarks or delivery notes, can be set up to allow changes after submission. And drafts can be edited freely until they're submitted, which is why a review step before submitting is worth building into your process.
Protecting Closed Periods
Once a month or year is closed, you can freeze the accounts up to that date, so nobody can post backdated entries into a period you've already reported.
Making It Work for Your Team
The answer to "I can't edit it" isn't to fight the system. It's a clear process: draft, check, approve, submit. With approval workflows in place, most mistakes are caught before anything is final.
Want accounts your auditors will trust? Book a discovery call and we'll set up the right controls for your team.