Revenue Hub for Southeast Asia.

Regional sales teams in Southeast Asia rarely sell in one currency. A deal priced in Singapore dollars, invoiced to a Philippine subsidiary and reported to a Malaysian head office in ringgit is ordinary here. That makes the quote-to-cash process one of the most fragile parts of the revenue engine, and one of the most valuable to fix.

HubSpot's Revenue Hub is designed to bring that process into the CRM.

What is Revenue Hub?

HubSpot describes Revenue Hub, formerly Commerce Hub, as its “connected system for quoting, contracts, billing, and payments”, built into the same platform as customer data (HubSpot). On the same page, HubSpot lists:

• Quotes and CPQ: build quotes, apply pricing rules and add discount guardrails from the deal record.
• Contracts: signed quotes become structured contract records.
• Subscriptions and billing: recurring billing, including mid-contract changes.
• Invoices: branded invoices connected to the customer record.
• Payments: credit card, ACH, recurring payments and payment links.
• Revenue Agent (beta): chases overdue invoices on the team's behalf.

How does HubSpot handle multiple currencies?

HubSpot's knowledge base says multiple currencies need a Starter, Professional or Enterprise subscription. You set a company currency, add others with an exchange rate to that company currency, and update rates manually or automatically. Open deals use the most recent rate; closed deals lock the rate in effect at the close date, which feeds the “Amount in company currency” property used in reports (HubSpot Knowledge Base).

One rule shapes every regional design. HubSpot states that “an invoice, payment link, quote, legacy quote, or subscription, can only have one set currency and all line items must be in that currency” (HubSpot Knowledge Base). If you sell a bundle priced in two currencies, split it or choose one.

Where can you collect payments inside HubSpot?

This is where Southeast Asia differs from the markets HubSpot's marketing is written for. HubSpot's knowledge base states that “HubSpot payments is only available to companies based in the United States, the United Kingdom, and Canada” (HubSpot Knowledge Base). The Revenue Hub page says the Stripe integration is “available in most countries Stripe supports, with a few exceptions” (HubSpot).

The exceptions matter here. HubSpot's Stripe documentation lists countries where Stripe processing through HubSpot is unavailable, and that list includes Malaysia, Indonesia, Thailand and India. The same page notes a platform fee, that each HubSpot account can connect one Stripe account, and that invoices and subscriptions created in HubSpot are not created in Stripe (HubSpot Knowledge Base). Check that page for your entity before you design the process, because availability can change.

In practice that gives three patterns for regional groups:

1. Collect in HubSpot through Stripe for entities in supported markets, such as many Singapore and Philippine entities, after confirming eligibility.
2. Quote and invoice in HubSpot, collect elsewhere for entities in markets where neither option is available, recording payment status back on the record.
3. Let the ERP own billing where finance already invoices from an ERP, with HubSpot holding the quote and contract and receiving invoice and payment status through integration.

Many groups run more than one pattern at once, by entity. That is fine, as long as the customer record shows one consistent status.

What should you design before you switch it on?

• Entity and currency map. Which legal entity sells in which currency, and which pattern each uses.
• Product library. Prices per currency, maintained by one owner, not converted on the fly by reps.
• Discount guardrails. Who can approve what, by market. CPQ rules enforce it; leadership decides it.
• Tax and invoice rules. Local tax and invoice requirements differ by market. Confirm them with your finance and tax advisers, and decide whether HubSpot or the ERP issues the legal invoice.
• Finance integration. How invoices, payments and credit notes reach the ledger. Our ERP integration work usually starts here.

Where does the Revenue Agent fit?

Once invoices live in HubSpot, the Revenue Agent can follow up on overdue ones. Treat it like any other agent: a finance owner, written limits on tone and escalation, and a measure of days to collect against your own baseline. Our agent operating model applies directly.

How should a regional group roll it out?

Not all at once. Quote to cash touches sales, finance, legal and customers, so mistakes are visible and expensive. We sequence it in three steps.

1. Quotes first. Move quoting into HubSpot for one entity, with the product library, currencies and discount rules in place. Sales sees the benefit quickly, and finance gets cleaner deal data without changing its own process.
2. Contracts and invoices next. Once quotes are reliable, generate contracts and, where HubSpot will issue them, invoices. Agree with finance which system is the record for each document.
3. Payments and agents last. Add payment collection where your market allows it, then the Revenue Agent, once there is a clean history of invoices to work from.

Each step is repeated entity by entity. The first entity sets the pattern; the rest follow faster.

Is it worth it?

When quotes, contracts and invoices sit on the same record as the deal, sales can see what was billed, finance can see what was promised and leadership sees revenue in one currency. That alone removes a large amount of reconciliation. Payments inside HubSpot are a bonus where available, not a precondition. Start with the entity and currency map.