Six releases that tighten the quote-to-cash motion
AI Invoice Prioritization graduated to general availability this month, making Breeze-powered invoice ranking and collection email drafting available to all portals. And the Revenue stack keeps building: five additional releases shipped across CPQ, Billing, and Payments in the last two weeks, from billing configuration controls to contract-to-project associations and a new public Payments Account API in public beta.
AI Invoice Prioritization (GA — August 7)
What is it? Users can now let Breeze rank their open invoices by revenue impact — directly from the invoice index page — and draft personalized collection emails for each. The prioritization engine scores invoices across three dimensions: revenue risk, customer risk, and invoice risk. Breeze surfaces its reasoning alongside each ranking, so reps can understand why a given invoice is flagged.
Why does it matter? AR teams historically approach collection manually — oldest invoice first, or largest balance first. That logic misses the picture: a $500 invoice from a customer who’s about to churn may matter more than a $5,000 invoice from a customer with perfect payment history. Breeze surfaces that nuance and removes the work of figuring it out. This marks Breeze’s first GA milestone in a billing workflow, laying the foundation for the agentic platform future.
Available for: All hubs and tiers.
Portal-level Billing Settings (Live — August 11)
What is it? A new Billing settings page under Settings → Revenue → Billing centralizes configurable defaults for connected quotes and contracts. Settings include: automatically emailing invoices to billing contacts on invoice dates, sending invoices ahead of bill dates, enabling billing for quotes and contracts, proration defaults, and collection defaults. Previously, these had to be configured per-object or weren’t configurable at all.
Why does it matter? Two categories of merchants have been blocked by the absence of these controls. The first: merchants who want invoices generated by HubSpot but not automatically emailed (for example, European customers who need HubSpot invoices as input to an e-invoicing system like Peppol, but send them through a compliant external pipeline). The second: merchants who want invoices sent before the bill date, giving their customers’ AP teams time to review, approve, and schedule payment. Both are now unblocked.
Available for: Connected CPQ, Billing, and Payments (public beta) portals with contracts-setting or subscription-write access.
Price Books (GA — August 4)
What is it? Price Books graduated from public beta to GA on August 4. The GA milestone also added Breeze-powered import: RevOps admins can now upload a spreadsheet of existing price books and let Breeze handle the import, rather than recreating catalog data manually. The import path shows up as a new option in the Create dropdown on the Price Books index page.
Why does it matter? GA signals stability — and a commitment to the pricing catalog as a durable part of the Revenue Hub data model. The Breeze import lowers the cost of adoption for teams that have pricing data already living in spreadsheets or another CPQ tool, which is most teams migrating to Revenue Hub CPQ.
Available for: Revenue Hub Professional and Enterprise.
Tax Registration Obligation Monitoring (Live — August 4)
What is it? Automated Sales Tax customers can now track their sales tax registration obligations inside HubSpot. The feature monitors revenue and transaction volume across U.S. states and Canadian provinces, and alerts merchants when they’ve crossed into the “economic nexus” or a threshold that requires them to register, collect, and remit sales tax.
Why does it matter? Post-South Dakota v. Wayfair (2018), economic nexus rules mean that selling above a revenue or transaction threshold in a state — even without a physical presence there — triggers a sales tax obligation. For growing merchants, this is a compliance risk that’s easy to miss until it becomes expensive. Having this surface inside HubSpot, where the transaction data already lives, means merchants don’t need a separate tax monitoring tool to stay ahead of it.
Available for: Revenue Hub Professional, Revenue Hub Enterprise
Project to Contract Associations (Live — August 11)
What is it? Contract records can now be linked to HubSpot Project records. The association is fully configurable — teams can modify association limits and create custom labels to define the relationship between a contract and the project it belongs to. Contracts carry the full commercial context (products, revenue, billing terms, renewal dates), while Projects carry the operational work, so this connection bridges the revenue and delivery sides of a customer relationship in the CRM.
Why does it matter? For teams that manage implementation or professional services alongside a contract — onboarding projects, deployment engagements, or any delivery work that’s attached to a sale — there was previously no native way to surface that operational context from the contract record, or vice versa. Now the handoff between “deal closed / contract signed” and “project kicked off” is visible in one place, reducing the manual tracking that typically lives in spreadsheets or separate project tools.
Available for: Revenue Hub Professional, Revenue Hub Enterprise
Payments Account READ API (Public Beta — August 3)
What is it? A new public API endpoint allows developers to retrieve a HubSpot account’s payment status including enrollment status, payment eligibility, and transaction capabilities.
Why does it matter? Partners and developers building on top of HubSpot Payments previously had no programmatic way to check whether an account was enrolled and eligible to transact. That’s a practical gap for integration logic. For example, an ISV that gates a payments feature based on account status, or an onboarding tool that checks payment readiness before routing a merchant through setup. This API closes that critical gap.
Available for: All HubSpot hubs and tiers.
Questions or feedback? Please share in the comments! Your input goes directly to the product team 