Log every stage, term, or invoice balance change on a closed deal with its date, reason, and approver. The stage gets corrected, the term is extended or shortened, and the invoice balance shifts when a credit or adjustment lands. Each move can change the numbers a revenue leader sees in a review. If nobody wrote down why it happened, the review turns into a debate about who remembers what.
Key takeaways
- For any stage move, record the old stage and the new stage.
- Record the date of the change and the person who made it.
- Note the prerequisite step, if your process has one, and whether it was completed first.
- Write a one-sentence reason someone outside sales could read. "Fixing" is not one.
This post covers three changes worth logging. For each one, I explain what to capture, why it matters, and where a platform's documentation gives you a concrete reference point. The goal is not a perfect audit system. The goal is making sure that when someone asks why a closed deal looks different than it did last month, the answer is in the record and not buried in a chat thread.
Nothing here replaces your finance team's policies. Check your own rules for revenue timing, approvals, and who may edit closed records before you change how your CRM or billing system works. The examples below are illustrations of what a good log contains, not instructions for any particular tool.
Change 1: Log every stage move after Closed Won
Most teams treat Closed Won as the end of the story. In practice, a closed deal can be reclassified. It may turn out to duplicate another opportunity, it may have been attached to the wrong account, or it may need a different outcome after a finance review. Each of those reasons is legitimate, and each one changes what the pipeline report says about that deal. For a related view of how deals are grouped in a forecast, see forecast categories explained.
GitLab's sales order processing handbook includes exactly this kind of move. It says to change the stage from Closed Won to 10-Duplicate, and it adds a warning: if you do not perform the first step, you will run into a validation rule. GitLab's order processing page Check your own version of the process to see what that first step is before you copy the stage name or the order of steps. The useful lesson is that a stage change can depend on an earlier step, and the system may block you if you skip it.
That has a direct logging consequence. A log that shows only the final stage cannot tell you whether the required order was followed.
Decide in advance who may make a stage move on a closed deal. Sales operations, finance, and the account owner often have different views of the same deal, and a clear owner for each type of move prevents two people from changing the same field for two different reasons. If a move is an error correction rather than a real change in the deal's outcome, label it that way. Reviewers treat a correction and a business change differently, and the log should make the difference visible.
Do not overwrite the old value. Add a new entry that points back to the previous one. When a finance reviewer asks why a deal moved from won to a different outcome, the answer should be a sequence of dated entries, not a field that now says something else with no trace of what it used to say. For the same approach applied to dates, see Close date change log: why the date moved.
Change 2: Log term and billing-schedule changes as dated phases
The second change is the term. A closed deal's term changes when a customer extends, shortens, or restructures the agreement. The record may still show the original term even though the customer is now on a different schedule, and that gap is where confusion starts.
One way to handle this is to describe changes as a schedule rather than a rewrite. Stripe's subscription schedules documentation puts it plainly: "Use the phases attribute to define the changes you want to make to the subscription." Stripe's subscription schedules guide That is a good model for your own log. Each change becomes a dated phase with a start point, so the earlier term remains visible when someone needs to know what applied at a given time.
Chargebee's subscriptions guide shows a similar concern for multi-year deals. It includes a question about setting up a 3-year subscription with annual billing, so multi-year terms billed on a shorter cycle are a case the platform's documentation addresses. Chargebee's subscriptions guide For your log, store three separate fields: total term, billing frequency, and number of billing cycles. Do not combine them into a phrase like "3 year annual." Separate fields let you check the arithmetic later, and they let a reviewer spot a mismatch at a glance.
The same guide also asks what happens when the number of billing cycles is 0. You should test that case in your own setup rather than assume how it behaves. A zero can mean different things depending on how a system reads it, and an unclear value in the log is a common source of later disagreement. If your records can hold a zero, write down what it means in your team's terms.
Renewal is where term changes tend to surface. Otherwise you cannot show which term applied when the renewal ran.
Sometimes a term change does not replace the old term. It follows it, starting after the current period ends. Your log should say which kind of change occurred. "Replaces the current term" and "begins after the current term ends" lead to different revenue questions, and a single word like "updated" hides the difference.
Keep term history available long after close. The same guide also asks how to fetch historical subscription data that is more than 12 months old. Chargebee's subscriptions guide Whatever platform you use, the lesson is the same: do not rely on current values alone. A closed deal can be reviewed long after it closed, and the record needs to answer questions about the term as it stood back then.
Here is a short checklist for term entries:
- Original term, billing frequency, and cycle count, each in its own field.
- Each change as a separate entry with its effective date, its approver, and whether it replaces or follows the current term.
- The renewal date and the term that applies on that date.
- A pointer to the phase or schedule entry that recorded the change.
Change 3: Log invoice balance moves and credits
The third change is the invoice balance. A closed deal can show an open amount after the close because of a credit, an adjustment, or a partial payment. If the only thing your report shows is the current balance, a reviewer has no way to tell whether the customer paid, a credit was applied, or someone corrected an invoice.
Stripe's revenue recognition guide walks through a case with a credit balance. It states: "The customer has -11 USD in their customer credit balance." It then says: "Stripe automatically applies -11 USD to the invoice and adjusts the customer credit balance to 0 USD." Stripe's revenue recognition guide
Read those two sentences as a pair. The credit moved from the customer's balance onto the invoice, and the customer balance ended at 0 USD. If your log records only the final invoice total, you lose the credit that reduced it, and a reviewer sees a lower number with no explanation. Log both sides of the movement: where the credit came from, which invoice it reduced, and what the customer balance was before and after.
The table below compares what the sources say with the field each one suggests you log. The first column names the source, the second states what the quoted page says, and the third gives the field to capture.
| Source | What the quoted page says | Field to log |
|---|---|---|
| Stripe, revenue recognition guide | The customer has -11 USD in their customer credit balance | Credit amount with its sign, and the customer balance before application |
| Stripe, revenue recognition guide | Stripe automatically applies -11 USD to the invoice and adjusts the customer credit balance to 0 USD | Invoice ID and the customer balance after application |
| Stripe, subscription schedules | Use the phases attribute to define the changes you want to make to the subscription | Each term change as a dated phase |
| Chargebee, subscriptions guide | On the day of your subscription's renewal, Chargebee initiates the renewal process | Renewal date and the term in force that day |
| GitLab, order processing | Change the stage from Closed Won to 10-Duplicate; if you do not perform the first step, you will run into a validation rule | Whether the prerequisite step was completed, and the new stage |
Balance moves have several common causes, and the log should name the cause rather than just the amount. A credit applied from a previous overpayment is different from a discount agreed during renegotiation, and both are different from an invoice that was voided and reissued. Each cause affects how a reviewer reads the deal, so each one needs its own label.
For every invoice balance change, capture:
- The credit or adjustment amount and currency, with its sign kept exactly as the system records it.
- The invoice that received the credit.
- The customer balance before and after the application.
- The cause, in plain words, and who applied it.
- Whether the change happened before or after the close date. This matters when a review asks what the deal looked like at close.
Keep the sign convention the same across the whole log. A negative credit and a positive charge mean different things, and a review that mixes conventions will misread them. Pick one convention, write it at the top of the log, and apply it to every entry.
Illustrative example: one deal, three changes
Consider a deal marked Closed Won at signing. Soon after, the account owner finds that the same customer already had an opportunity for the same product, so the deal duplicates it. The log records the old and new stage, the date, the approver, and a reason that names the original opportunity. The old value stays in the history.
Later, the customer extends the term. The billing team records it as a phase that begins after the current term ends, with the term, billing frequency, and cycle count in separate fields.
Finally, a credit is applied to the next invoice to fix a billing error. The log captures the credit amount and sign, the invoice it reduced, and the customer balance before and after. The cause is labeled as a correction, and the person who applied it is named.
In a revenue review months later, every answer is in the log, in order, with dates.
Common mistakes to avoid
The most common mistake is overwriting a field. It feels tidy, but it destroys the trail.
The second mistake is logging the final state only. A stage, a term, or a balance can look correct at the end and still hide a sequence that mattered. If a reviewer cannot rebuild the order of events, the log is incomplete even if the current values are right.
The third mistake is putting the reason in a chat message or a meeting note. Those places are hard to search and easy to lose. The reason belongs in the record next to the change it explains.
The fourth mistake is mixing effective dates with entry dates. The date someone typed a change into the system is not always the date the change took effect. A renewal review needs the effective date. An audit of who did what needs the entry date. Store both.
The fifth mistake is trusting reports built only on current values. A report that reads the current record will show the deal as it is now. A report that reads the log can show it as it was at close, at renewal, or at any point in between. Use both, and know which one a given number came from.
The sixth mistake is treating a correction as a business change, or the reverse. When both look the same in the log, reviewers will argue about the deal instead of the process. Label each entry so the difference is clear.
Putting the three changes into one log
Closed deals keep moving after the signature. The teams that handle that well are not the ones that avoid changes. They are the ones that can explain each change, in order, with a reason and a name attached.
A shared format means a revenue leader can filter for all term changes on a given deal, or all balance changes in a period, without reading free-text notes. For tool-specific limits on deal change records, see that guide.
Set a simple review rhythm. Before a closed deal appears in a review, check whether any of the three record types changed since close. If one did, confirm that a log entry exists and that it matches the current record. If the current record and the log disagree, treat that as a finding to investigate, not as an error to fix quietly. A quiet fix hides the reason the two diverged, and that reason is often the thing the review needs to know.
Today, test the log with a real example. Pick one closed deal whose stage, term, or balance moved, and try to rebuild its history from the log alone, without asking anyone. If you can explain every change in order, the log works. If you cannot, the gap is the first thing to fix.
Frequently asked questions
What should a stage change entry include?
It should include the old and new stage, the date, the person who made the change, and a one-sentence reason.
Should I overwrite an old value on a closed deal?
No. Add a dated entry that points back to the previous value, so the history stays readable.
What does a credit entry need?
It needs the credit amount with its sign, the invoice it reduced, and the customer balance before and after the application.