Build a Journal Entry Reversal Register Before the November Close

Published November 2, 2026

Month-end journal entries are usually created with care and then left alone. The trouble starts when one of them has to come back out. A reversal can be completely legitimate and still leave the file hard to explain, because the original entry, the reversing entry, and the replacement entry each carry only part of the story. A reversal register pulls those pieces into one place before the close package reaches the reviewer.

The register is not a second ledger. It is a short, dated list that answers a simple question: for every reversal in the period, can another person see what changed and why? That question matters more than the number of reversals, because a small set of undocumented reversals can undermine confidence in otherwise solid work.

Why reversals deserve their own record

Most accounting systems keep an audit trail that shows when an entry was posted or changed. An audit trail is excellent for proving that something happened. It is much weaker at explaining intent. Two reversals can look identical in the system while one corrects a duplicate accrual and the other removes an entry that was never approved.

When the reviewer asks about a balance, the team often has to reconstruct the answer from email, chat, and memory. That reconstruction is slow and it invites disagreement. A register gives the team a prepared answer, and it gives the reviewer a consistent place to look.

The register also protects the person who prepared the entry. If an accrual was reversed because the invoice arrived after the cutoff, the register says so. Without that note, a later reviewer may assume the reversal was an attempt to hide an expense rather than a normal timing correction.

Define what counts as a reversal

Not every negative entry is a reversal. The team needs a working definition before the register means anything. A useful definition is: an entry that offsets all or part of a previously posted journal entry, whether by using the reverse function or by posting an opposite entry manually.

Write down which events are in scope. Reversing accruals at the start of a new period usually belong in the register. Correcting a duplicate journal entry belongs in the register. Reclassifying an amount from one account to another may belong in the register if it removes the original treatment rather than adjusting it. A routine recurring entry that was simply posted again is a different problem and should be handled through the recurring transaction review instead.

The definition should also say what is out of scope. Bank-feed edits, invoice voids, and bill deletions are separate workflows with their own evidence. Mixing them into the reversal register makes the list noisy and hides the journal entry issues the reviewer actually needs to see.

Capture the fields that make the entry explainable

A register with too many columns will not be maintained. A register with too few will not answer the reviewer's question. Start with seven fields and add more only when the team can show they are used.

The first field is the original entry reference: the journal number, posting date, amount, and accounts affected. The second is the reversal reference, including its posting date. The third is the reason, written as a short sentence rather than a code alone. The fourth is the approver, named as a person rather than a team or inbox.

The fifth field is the replacement. A reversal usually exists because something else should take its place. Record the replacement entry reference, or record that no replacement was needed. The sixth field is the evidence link: the invoice, the schedule, the approval message, or the reconciliation note that supports the decision. The seventh field is the status, using a small set of labels such as prepared, approved, posted, or carried forward.

If the reversal affects a closed period, add a separate note about the reopening or the correcting entry in the current period. Do not bury that detail in a free-text comment where the next reviewer will miss it.

Keep the reversal separate from the correction

One of the most common weaknesses is combining the reversal and the correction into a single step. The original entry is removed and a new entry is posted, but only the final result is documented. The reviewer can see the ending balance and cannot see the path.

Keep the two events distinct even when they happen on the same day. The reversal should reference the original entry. The correction should reference the reversal and the evidence that justified the new treatment. If the team uses an automatic reversing entry, note the date the system will reverse it and confirm that the reversal actually posted.

This separation also helps when a correction is later questioned. The team can show that the first entry was removed for one reason and the second entry was added for another, with a named approver for each decision. That is a stronger record than a single edited entry with no history.

Set a review cadence that fits the close

Review the register at three points. First, when a reversal is proposed, confirm that the original entry and the reason are recorded. Second, before the close package is assembled, confirm that every reversal has an approver and a replacement decision. Third, after the close, check whether any reversal created a new exception that needs follow-up.

The pre-close check should be short. Sort by status, look for rows without an approver, and look for reversals that reference an entry outside the current period. Those are the rows most likely to cause a question.

The post-close check should look for patterns. Several reversals in the same account may point to a recurring timing problem. Repeated reversals by the same preparer may point to a missing instruction rather than an individual error. The register is a process signal, not a performance score.

Test the register with three real cases

Before relying on the register, test it against three reversals from the prior period. Pick one routine accrual reversal, one duplicate entry correction, and one reversal that led to a replacement entry. For each, ask whether a reviewer who was not involved could explain the change using only the register and its evidence links.

If the answer is no, the missing field is usually the reason or the replacement reference. Fix the template before the next close rather than adding narrative after the fact. A register that is tested on real cases is far more likely to survive review than one designed only in theory.

Close with a summary the owner can read

At the end of the close, add a short summary above the register. State the number of reversals, the total amount reversed, the accounts most affected, and the open items that still need a decision. Keep the summary factual and avoid characterizing every reversal as an error.

The goal is not to eliminate reversals. Some reversals are the correct response to new information. The goal is to make each one visible, approved, and connected to the evidence that explains it. On November 2, a clean reversal register gives the reviewer a clear path through the month-end entries and gives the team a record it can defend without rebuilding the story from memory.