HubSpot forecast setup problems

Why it matters

A forecast type reads an amount property and a date property from deals. If either is restricted for some users, reps and managers can see different numbers in the same forecast without knowing why.

If a forecast type points at a property that no longer exists or cannot be read, its totals may be wrong or empty. This often follows a custom property being retired or renamed.

Submissions are how owners and teams commit a number. A submission with no amount, period, or owner cannot be compared with actual results, so forecast accuracy cannot be measured.

How to find it in HubSpot

1. 1If your subscription includes the forecast tool, open it and review each forecast type in use.
2. 2In Settings, open the forecast settings and note the amount and date property each forecast type uses.
3. 3In Settings, open Properties for deals and confirm each of those properties exists and check its field-level permissions.
4. 4Review recent forecast submissions and check that each has an amount, a period, and an owner or team.
5. 5Ask a rep and a manager to open the same forecast and compare what they see.

How to fix it safely

1. 1For restricted properties, decide with the forecast owner who should see amounts and dates, and handle any access change through your normal least-privilege review.
2. 2Point forecast types at properties that exist and are filled in, and check currency behavior before relying on totals.
3. 3Ask owners to resubmit incomplete forecasts in HubSpot with an amount, period, and owner or team.
4. 4Test forecast totals with representative sales roles after any change.

Before you change anything: Changing property permissions or forecast types affects what every sales user sees. Agree changes with the forecast owner first, and keep access decisions in your manual permission review.

How Ancil checks this

Rule

SALES-010, SALES-011, SALES-012, SALES-013

What it looks for

Ancil reads forecast types and up to 100 forecast submissions through HubSpot’s read-only beta forecast API, when your connection allows it. SALES-010 flags forecast types that HubSpot marks as using an amount or date property restricted for non-super-admin users. SALES-011 flags forecast types whose amount or date property is not in the deal property list Ancil read. SALES-012 flags submissions that reference a forecast type not returned in the settings. SALES-013 flags submissions with no amount, milestone, or year, or with neither an owner nor a team.

Severity

SALES-011 is a warning. SALES-010 and SALES-012 are info. SALES-013 is info, or a warning when every submission read is incomplete.

Evidence shown

Forecast type IDs, names, and the properties involved, and submission IDs with their amount, milestone, year, owner, and team.

Governed fix

Not automated. Ancil reports the evidence and does not change forecasts, properties, or permissions. The forecast API is read-only, so your team, or an INSIDEA expert, makes corrections in HubSpot.

Related checks