Posted documents cannot be edited or deleted — by anyone, including administrators. This is not stubbornness; it is what makes the books auditable. A posted invoice has been printed, sent, perhaps paid against. If it could quietly change afterwards, no statement, report, or audit could ever be trusted. So BlossomERP corrects history the way accountants always have: with more history.
- A wrong posted document is reversed. Reversing creates a new, linked document (or ledger batch) that exactly cancels the original's effect, and the pair stay linked forever: the original, the reversal, and — when you raise it — the corrected replacement. Anyone auditing later sees the whole story, not a gap.
- An order that will not proceed is closed, not deleted. Closing records that the promise ended; the order stays readable.
- A document approved but never posted can be voided — removed cleanly, precisely because it never touched the books or the stock. Voiding is restricted to platform administrators, so if you need an approved document voided, escalate it rather than working around it.
- Drafts are the only freely disposable stage — and even draft deletion is an administrator action, so treat drafts as shared paperwork, not private scratch paper.
One protection runs the other way: if an approval or posting cannot complete — the accounting period is closed, the bank balance will not cover a payment under your overdraft policy — the application refuses and says why, and the document stays exactly where it was. Nothing is ever half-posted.