The month a deal counts in is the month of the date that specific tool uses, and that date is not the same field in every tool. Microsoft defines the forecast period as the schedule you add, such as the period from July 1 to June 30 of the following year.
The date field determines the month, not the contract
When you prepare for the forecast call, the dollar amount for a software deal lands in a specific month or quarter based on a date value stored in your sales tool. That date value is not universal. Each platform uses a different field or rule to place the deal in time. For a forecast that uses a selected date property, the month follows that property's value.
For Microsoft, the relevant concept is the forecast period. According to Microsoft, you create forecasts for a defined period, with the example given as the period from July 1 to June 30 of the following year. This is a schedule you add to the system. Microsoft requires you to add at least one forecast period before proceeding to the next step. A forecast period running from July 1 to June 30 defines the reporting interval.
Open one live deal in your tool. Find the date field that the tool uses to place the deal in a month. Write down the name of that field and its value. This is the date that determines the month. In Microsoft, a forecast period is a reporting interval, separate from an individual deal's date field. If you are using HubSpot, this is the date property. Pipedrive's deal forecast view uses expected close date; its Insights deal revenue forecast report uses expected close date for open deals and won time for won deals. In Close's Opportunity Pipeline View, the Close date filter selects Won Opportunities closed on the selected date.
Key takeaways for which month a software deal is counted
The month a deal counts in depends on which date field your specific tool uses for the forecast, and that field is not the same in every system. Before you present the weekly number, confirm which date drives the placement in your tool so the dollars land in the correct month or quarter.
- HubSpot: The revenue amount is realized on the date value of the selected date property, according to HubSpot.
- Pipedrive: The forecast view projects revenue by using the expected close date of the deal, according to Pipedrive.
- Close: For Won Opportunities, the Close date filter shows all Opportunities closed on the selected date, according to Close.
Each of these rules applies only to the named publisher and the specific page cited. Do not assume that the date field in one tool matches the date field in another. If you use multiple systems, the same deal may appear in different months depending on which tool’s date rule you are reading.
A filled table of the date each publisher uses to place a deal
The following table identifies the specific date mechanism each tool uses to assign revenue to a period.
| Publisher | Date Field or Rule Used for Month Placement | Source Context |
|---|---|---|
| Microsoft | Forecast schedule intervals; check the individual deal date separately | Microsoft |
| HubSpot | Selected date property value | HubSpot |
| Pipedrive | Expected close date of the deal | Pipedrive |
| Close | Opportunity Pipeline View: filters won opportunities by closed date | Close |
Microsoft allows users to create forecasts for specific periods, such as the period from July 1 to June 30 of the following year, according to Microsoft. HubSpot realizes the revenue amount on the date value of the selected date property, according to HubSpot. Pipedrive projects revenue by using the expected close date of the deal, according to Pipedrive.
Microsoft forecast periods are a schedule you add
The month a software deal counts in depends on the specific date field the tool uses, which varies by platform. The "Define and schedule a forecast model | Microsoft Learn" page requires adding at least one forecast period before proceeding. You must add at least one forecast period to go to the next step, according to Microsoft. Treat the forecast schedule and the date on an individual deal as separate items to check.
When setting up this schedule, the "Define and schedule a forecast model | Microsoft Learn" page provides a concrete example of how to structure the dates. The documentation states, "Let's say your organization's fiscal year runs from January 1 to December 31," according to Microsoft. This specific date range is Microsoft's example for illustrating the setup process. It is not a statement that your organization's fiscal year starts in January or ends in December. You should treat this as a sample input for the scheduling interface, not as a rule for your own company's calendar.
The same documentation explains how to apply this to a specific year. The monthly scheduling example uses fiscal year 2023, according to Microsoft. This instruction guides you through the input fields for that specific example year. The "Manage forecast periods | Microsoft Learn" page also sets a boundary for these periods. Forecast periods can only span up to one year, according to Microsoft. This limit applies to the "Manage forecast periods | Microsoft Learn" tool specifically.
Another aspect of the scheduling format is described in the "Forecast period rules and scheduling formats | Microsoft Learn" page. Microsoft describes a Gregorian calendar scheduling format with 12 weeks in each quarter, according to Microsoft. The 12-week quarter structure belongs to Microsoft's scheduling example. It is not a claim that your own calendar uses 12-week quarters. Do not assume this scheduling format's quarter length applies to your organization's internal reporting periods.
HubSpot places the amount on the date property
In HubSpot, the month a deal’s dollars appear in is determined by the date property value selected for the forecast. The default sales forecast uses Deal Amount and Close Date, according to HubSpot. This means the system places the full amount on that specific Close Date value. If you adjust the date property, the amount moves to the month containing that new date.
A critical rule for your forecast call is that the amount does not spread across multiple months. HubSpot states, “It will not recur prior to or after that date,” according to HubSpot. This applies to the realized revenue in the forecast view. Even if a deal has a recurring billing structure, the forecast tool treats the amount as a single realization event on the selected date. It does not add a portion of that amount to the month before or the month after.
You can submit a custom forecast for the month or quarter to give your stakeholders an estimate of how much you think you'll close during that time, according to HubSpot. For month placement, check the forecast's selected date property separately from submitting your custom estimate. The revenue amount is realized on the value of the date property selected for the forecast.
Check the date property name in your HubSpot forecast settings. If it says “Close Date,” the amount lands in the month of the Close Date. If it says another field, the amount lands in the month of that field. Verify that no other date fields are being used to split the amount. The amount is realized on the selected date and does not recur before or after it.
Pipedrive and Close: expected close, won date, and the close-date filter
In Pipedrive's Insights reports: deal revenue forecast, month placement depends on whether the deal is open or won. The platform distinguishes between these two states when displaying revenue forecasts. For deals that are currently open, the system uses the expected close date to place the amount in a specific month. When a deal is marked as won, the system switches to using the won time for that placement. This distinction is critical for the forecast call because a deal that slips from one month to the next while open changes its month based on the expected close date, whereas a deal that is won lands in the month of its won time.
You can also drag-and-drop deals from one column to another, allowing you to update the deal’s expected close date, according to Pipedrive. This interaction directly affects which month the deal’s value appears in, as the drag-and-drop action updates the specific date field that drives the monthly aggregation. If you move a deal to a later column, you are effectively changing the expected close date, which shifts the deal’s placement in the forecast.
Open deals are shown by the expected close date; won deals are shown by the won time, according to Pipedrive. This rule applies specifically to the Insights reports: deal revenue forecast view. It means that if you are reviewing a report that includes both open and won deals, the two groups are calculated using different date fields. You cannot assume that the expected close date remains the anchor for a deal once it is won; the won time takes over.
For Close, the tool uses a close-date filter. If your tool uses a close-date filter, you must verify whether that filter applies to the expected close date for open deals and the actual close or won date for won deals.
Open one live deal and write down the date field your tool uses for the month, using the name that tool already shows.
A blank month check for one live deal
Open one live deal in your tool. Write down the date field name it shows and the value on that deal. The resulting month is the month of that date. Use the name the tool already displays. Do not rename the field. Record the value exactly as it appears. This check isolates the single date that places the deal in a month. It prevents mixing dates from different fields. If the deal is open, note the expected close date if your tool uses it. If the deal is won, note the won date if your tool uses it. The month is determined by the specific date field your tool applies. Fill in this blank month check: tool or view: _; date field: ; date value: _; resulting month: . This blank worksheet is for your specific tool. Fill it in before the forecast call.
Related guides
FAQ: Which month a software deal is counted
Which date puts a HubSpot deal in a month?
The revenue amount is realized on the date value of the selected date property. This rule applies specifically to the forecast creation process described in the documentation.
Does a HubSpot recurring amount repeat in later months?
No, the amount does not recur prior to or after that date. The revenue is realized on the selected date value and does not repeat in other months.
What date does Pipedrive's forecast view use for an open deal, and for a won deal?
Open deals are shown by the expected close date. Won deals are shown by the won time. These date rules apply to Pipedrive's Insights deal revenue forecast report.
What does Close's close-date filter show for a won opportunity?
For Won Opportunities, the Close date filter shows all Opportunities closed on the selected date. This filter isolates deals based on their closed status and date.
Are Microsoft's July and FY2023 dates your fiscal year?
These dates are examples from the documentation and do not define your fiscal year. You can create forecasts for the period from July 1 to June 30 of the following year, as shown in the example.