Why a won deal with the wrong close date is a finance problem
Closed Won is the moment your CRM commits revenue to a specific time period. The close date is what tells finance — and your dashboards, and your forecast — when that revenue counts.
When a deal is marked won but the close date is wrong, the impact cascades:
- Wrong period revenue. A deal won today with a close date of
next quarterlands in next quarter's revenue. Your current quarter looks short; next quarter looks fat. Both are misleading. - Missing close date entirely. The deal is won. The amount is set. But the close date is null. Some HubSpot reports filter out deals with no close date, so the revenue silently disappears from period sums.
- Close date set to a far-future date as a placeholder. Reps sometimes set close date to
12/31/2099or similar to "save the deal for later" — then mark it won without fixing the date. The deal counts as revenue, but in 2099.
All three break the close-date integrity that finance and forecasting rely on. Catching them is part of the basic monthly close process, but most teams catch them only when finance does the reconciliation and asks awkward questions.
What three filter conditions actually surface
Three filter conditions:
- Deal stage is Closed Won.
- Close date is unknown OR after today.
- (Optional) Closed-won timestamp is recent — to focus the audit on currently-actionable deals.
The "after today" check is the easy half. The "unknown" half catches the silent revenue disappearance.
Why required-property rules can't fully prevent this
Required-property rules at the stage level are partial protection:
Workflow-advanced deals skip the check. A workflow that sets Deal stage = Closed Won based on payment received from Stripe doesn't trigger the required-property check. The deal advances; close date stays null.
Imports skip the check. A spreadsheet upload setting Closed Won on a batch of deals doesn't enforce close date. Whatever's in the spreadsheet column lands directly.
The "before today" validation isn't natively enforceable. HubSpot lets you mark a property required, but doesn't natively let you say "this date must be in the past." You can build a workflow that catches it post-hoc and alerts the rep, but the bad data has already been created.
The deeper issue is that close date sometimes legitimately should be in the future at the moment a deal is won — common in subscription deals where the contract starts on a future activation date. Some teams use a separate Effective date property and keep Close date as the moment the contract was signed. That's the right structure but requires sales-ops education to enforce. The native field is just Close date, and what it means in your portal is whatever your team has decided it means.
The exception view (this rule's check) catches the cases that slipped through prevention. Run it monthly as part of the close, and the count stays manageable. Skip a quarter, and the cleanup gets painful.
The manual HubSpot recipe
Two filters, columns including Closed-won date for cross-reference. Monthly cadence, paired with a finance reconciliation review.
- Open Sales → Deals → Create viewNavigate to Sales → Deals. Click 'Create view' in the top right.
- Add filter: Deal stage is Closed WonFilter by Deal properties →
Deal stage→ 'is any of' → 'Closed Won'. - Add filter: Close date is unknown or after todayAND group →
Close date→ 'is unknown' OR 'is after' → today. Catches both the null-date case and the future-date case. - Add columns: Close date, Amount, Deal owner, Closed-won dateThe
Closed-won datecolumn is critical — it's the actual commit timestamp. Compare againstClose dateto spot the misalignment. - Sort by Closed-won date, descendingMost recently won deals at the top — those are the most recoverable. Older bad-date deals usually mean the rep's gone or the lookup is hopeless.
- Save as 'Won deals — bad close date'Pin to finance / sales-ops shared dashboard. Run monthly as part of the close.
What Bloated does instead
Bad close dates — null, future, or misaligned with the close-won timestamp.
Bloated catches all three flavors of bad close date AND **cross-checks Close date against Closed-won date** — flagging deals where the two are more than 7 days apart, which usually means the rep set close date as a placeholder and forgot to update it. Pair with the suggested action: update to the actual close date, archive as legacy, or split into a separate Effective date field for subscription deals.
closedate · HubSpot deal property