Every accounting team eventually hits the wall Odoo builds on purpose: once an account.move is posted, it locks. That is correct for audit integrity, but it turns routine month-end corrections into a slog. A mispicked journal, a wrong tax on a batch of entries, an imported opening balance that needs re-mapping, or a reversal that should never have gone through — each one has to be handled one record at a time, and the standard "Reset to Draft" is per-move, gated by the journal's inalterability setting and the accounting lock dates. When you are staring at three hundred entries from a bad import, that native path runs out of road fast.

Reset Journal Entries is a build-to-order Odoo tool that gives your controllers a governed, bulk state-transition action across selected account.move records — resetting them to draft, moving them to cancel, or re-posting them to posted — directly from the journal-entries and journal-items list views. It is not a magic bypass. We build it to respect (or, where your finance lead explicitly authorizes, to override with a mandatory logged reason) the lock-date checks in account.move._check_fiscalyear_lock_date, the hash-chain integrity flag on secured journals, and the reconciliation state of each line. Under the hood it is a proper Odoo module: a models.TransientModel wizard invoked from a server action that iterates the recordset, validates each move's preconditions with @api.constrains-style guards, calls the standard button_draft / button_cancel / action_post methods so no business logic is short-circuited, and rolls the whole batch back in a single transaction if any move fails validation. Every transition writes to mail.thread (the chatter) and to a dedicated audit log model, so you always know who reset what, when, and why.

Access is locked down with ir.model.access.csv plus record rules so the bulk action only appears for the accounting roles you nominate — typically a controller or finance-manager group, never a data-entry clerk. We wire the confirmation wizard to force a reason field before any override of a locked period, add an optional automated action to auto-unreconcile lines when a reset requires it, and expose the same operation over the XML-RPC / JSON-RPC API if you drive corrections from an external system or migration script. The UI is delivered as standard XML list-view buttons and an OWL wizard dialog, and where you use Enterprise we hook the operation into the accounting audit trail; on Community we ship an equivalent logging surface so nothing is silent.

Because this is made to order, delivery works around your environment rather than a shrink-wrapped download. After a short scoping call we confirm the exact target states, which roles get the action, how lock-date overrides should behave, and which Odoo version (17.0, 18.0, or 19.0) and edition you run. We then build against a copy of your database, validate the transitions on staging with your real data, and hand over installable source with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company setups, hashed/secured journals, deep lock-date override policies, or large-volume data-migration corrections increase the quoted scope.