Understand the official scope of Revenue Hub

Revenue Hub is HubSpot's quote-to-revenue product. Its core functions include products and services, quotes, contracts, billing, invoices, payment processing, subscriptions, payment links, revenue reporting, and renewal or amendment management.

Deals, Projects or Services, Contacts, Companies, Customer Success, workflows, marketing tools, Data Hub, and integrations can connect to the process even when they belong to other parts of the platform.

Older documentation may refer to Commerce Hub, commerce tools, payments, CPQ, quotes, billing, or the Revenue menu. Use current product names and verify entitlements, seats, regional availability, and payment support in the specific portal.

See the relationship behind the revenue

A $5,000 transaction could be a gift, sponsorship, event table, grant installment, membership, pledge payment, program fee, matching gift, or restricted contribution. The payment alone does not explain the relationship.

Connected CRM records let staff review the donor, household, Company, foundation, opportunity, grant, Campaign, event, program, agreement, Invoice, Payment, Subscription, owner, communication history, and renewal activity together.

Use Deals to manage potential revenue

Deals can represent major-gift asks, corporate sponsorships, grants, government funding, event underwriting, memberships, planned gifts, multi-year pledges, program contracts, and institutional partnerships before money is committed or collected.

A grant pipeline might move from opportunity identification and eligibility through letter of intent, application, review, award or decline, agreement, and receipt of funds. The Deal can carry requested, expected, and awarded amounts; deadlines; funding periods; restrictions; program and funder associations; probability; next activity; owner; agreement; and reporting requirements.

A Deal represents the opportunity or commitment process. It is not automatically a payment, accounting entry, or bank deposit.

Create Quotes and proposals when the transaction fits

Quotes may support sponsorship packages, underwriting, training, memberships, group admission, facility rental, paid workshops, consulting, program participation, or cause-marketing agreements. They can include Products or Services, one-time and recurring amounts, billing terms, discounts, payment options, e-signature, and associated CRM records.

A Quote is not always the right format for a charitable gift. Consider donor expectations, solicitation rules, tax treatment, and whether an acknowledgment, pledge agreement, sponsorship agreement, or Invoice is more appropriate.

Use Contracts as records of committed revenue

Unlike Deals that represent opportunities, Contracts can support agreed Products or Services, one-time and recurring amounts, billing terms, amendments, renewals, changes over time, and committed-revenue reporting.

Nonprofit use cases may include corporate sponsorships, government service contracts, program delivery, institutional partnerships, venue rentals, training agreements, multi-year services, and cause-marketing partnerships. Philanthropic gift agreements may have different legal, accounting, and tax implications, so the document type must fit the transaction.

Create Invoices for specific payment requests

Invoices may be appropriate for sponsorships, dues, event tables, program fees, rentals, merchandise, training, institutional contracts, or pledge installments. They can display the amount, due date, terms, line items, associated records, payment status, and outstanding balance.

An Invoice does not automatically replace a charitable acknowledgment or tax receipt. The nonprofit may still need to document deductibility, fair-market value, goods or services received, and legally required information.

Use Payment Links for flexible collection

Payment Links create a shareable checkout without requiring a new webpage. Staff can distribute them through email, text, social media, QR codes, print, appeals, event signage, or direct outreach.

Each link still needs intentional fields, designations, consent language, acknowledgment rules, and reporting structure.

Represent recurring commitments accurately

Subscriptions can support monthly gifts, annual memberships, recurring sponsorship payments, program payment plans, installments, and ongoing service agreements while providing visibility into future billing, outstanding amounts, and renewal activity.

Distinguish a payment authorization, donor pledge, recurring gift, membership, legal Contract, soft credit, and scheduled grant installment. These may require different objects, properties, accounting treatment, and acknowledgment processes.

Track fulfillment after commitment

Payment is not the end of the process. The organization may still need to deliver sponsor benefits, complete a program, submit grant reports, recognize a donor, issue an acknowledgment, provide member benefits, schedule services, fulfill merchandise, report impact, and prepare for renewal.

Projects, Services, Tickets, tasks, workflows, and the Customer Success Workspace can support this work. A closed sponsorship Deal might initiate a fulfillment record, finance task, recognition approval, logo request, benefit assignment, Invoice, payment monitoring, onboarding, post-event reporting, and renewal preparation.

Bring external fundraising activity into the revenue picture

Specialized platforms may remain best for peer-to-peer fundraising, crowdfunding, giving days, text-to-give, auctions, donor-advised funds, workplace giving, stock gifts, in-kind contributions, planned giving, and complex forms.

A connected architecture can bring the donor, Campaign, transaction, designation, fundraising page, participant, soft credit, payment status, opportunity, owner, and next stewardship action into HubSpot without forcing every transaction through Revenue Hub.

Report across the complete revenue pipeline

Structured revenue data can show potential funding, requested and committed amounts, invoices, collections, overdue balances, active Subscriptions, sponsorship renewals, pending grants, growing revenue streams, Campaign-sourced payments, restricted funding, expected quarterly revenue, and opportunities without next steps.

Revenue Hub reporting can combine with CRM reports across Deals, Contacts, Companies, Campaigns, and activities.

Do not automatically replace accounting

Revenue Hub can improve operational visibility, relationship context, billing, and collection, but accounting or ERP systems may still own the general ledger, fund accounting, bank reconciliation, expenses, financial statements, audit controls, revenue recognition, restricted balances, tax reporting, budgeting, accounts payable, and financial close.

A sound architecture defines ownership: HubSpot may own the donor relationship and grant opportunity, Revenue Hub may generate the Invoice, the processor may execute payment, accounting may own the official entry, and a data warehouse may consolidate reporting.

Build finance controls into the process

Revenue workflows should account for approval authority, segregation of duties, refund and discount permissions, Contract and Invoice approval, reconciliation, write-offs, amendments, restricted-fund coding, document retention, audit history, and data access.

The same person should not necessarily be able to create an agreement, change payment terms, issue a refund, and reconcile the transaction without oversight.

Keep revenue data portable

Structured Objects, properties, associations, pipelines, activities, owners, Products, Line Items, Contracts, Invoices, Payments, and Subscriptions are easier to integrate or migrate than undocumented fields and disconnected records.

Maintain property definitions, object documentation, association rules, system-of-record decisions, integration maps, external IDs, retention policies, export procedures, reconciliation rules, and automation documentation.

Avoid common implementation problems

Revenue management becomes unreliable when Deals, Contracts, Invoices, and Payments are treated as interchangeable; the same money is counted repeatedly; every Payment is called a donation; grants lack pipelines; restrictions are ignored; renewals are missing; external data lacks stable IDs; finance is excluded; reconciliation is weak; acknowledgments are assumed; permissions are too broad; reports mix incompatible metrics; MCP is treated as migration; or workflows create financial records without review.

The technology should reinforce the nonprofit's financial controls, not work around them.

Revenue Hub depends on connected architecture

A useful nonprofit revenue architecture requires defined streams, appropriate CRM Objects, accurate associations, purpose-built pipelines, consistent amount fields, Products and Line Items where appropriate, Contracts and billing schedules, Payment and Subscription records, accounting integration, external IDs, renewal processes, stewardship workflows, permissions, approvals, reconciliation, and trusted reporting definitions.

When those pieces work together, HubSpot can show both sides of nonprofit revenue: the financial process and the human relationship that made it possible.