What This Update Actually Is
Before this update, the Payments object in HubSpot was essentially locked behind a payment processor. You could only create and view payment records if you'd connected HubSpot Payments or a Stripe account.
Now, any HubSpot customer can create payment records manually, import them in bulk, or even trigger record creation through workflows. No processor. No third-party account. Just your data, in your CRM.
One important caveat to know upfront: during the public beta, two features are temporarily disabled for the Payment object if you haven't set up HubSpot Payments or Stripe. Custom Reports and Automated Workflows are off limits until the beta ends. Those features will return. But you should factor that into how you plan to use this right now.
Why HubSpot Shipped This
Here's the gap this solves: most businesses don't process 100% of their revenue through a single digital payment tool. They collect checks from enterprise clients. They wire money for large contracts. They receive cash. And none of that ever made it into HubSpot.
The result was a CRM that looked at your sales pipeline and reported something that didn't match your actual bank account. Sales said the deal closed. Finance had a different number. Nobody could reconcile the two inside HubSpot.
HubSpot shipped this to close that gap. The goal is a complete revenue picture inside the CRM, not just the slice that runs through their payment tools. That's a meaningful shift for RevOps teams and for growing companies that use HubSpot as their source of truth.
How to Use It Step by Step
There are four ways to get external payment records into HubSpot. Use whichever fits your workflow.
- Navigate manually: go to Commerce, then Payments, then click Add Payments. Choose Collect a Payment and select Create a Manual Payment. Fill in the payment details and save.
- Record from a CRM record: open any contact, company, or deal record. Find the Payments CRM card and log the external payment directly from there. This keeps context tied to the right record without extra navigation.
- Bulk import: if you've got a backlog of offline payments, use HubSpot's import tool to bring in multiple payment records at once. This is the fastest path to getting historical data into the system.
- Create via Workflows: use the Create Records action inside a workflow to generate payment records automatically when certain conditions are met. Note: this method is limited during the beta if you're not connected to a payment processor.
Start with the CRM card method for one-off entries and the bulk import for any backlog. Once the beta ends and workflow automation is fully available, that's where you'll build real efficiency.
What It Touches in Your HubSpot Strategy
This update lands squarely in the Commerce Hub and the Smart CRM, but its ripple effects go wider than that.
On the CRM side, payment records are now a first-class object that any team can see alongside contacts, companies, and deals. That means your sales reps don't have to leave HubSpot to confirm whether a payment came through. Your customer success humans can see what was paid and when, right from the contact record they're already in.
Key Takeaway
Payment records are now a CRM object your whole team can access, not a feature locked to payment processor users. Log checks, wires, and cash the same way you'd log any other deal data.
For RevOps, the bigger win is pipeline-to-cash visibility. When payment records live in the same system as your deals and contacts, you can start connecting the dots between what your sales team closes and what finance actually collects. That's a conversation most RevOps humans have been having across spreadsheets and Slack for years.
On reporting and automation: the beta limits are real. Custom Reports and Automated Workflows for the Payment object require a connected processor right now. Plan to build those after the beta closes. In the meantime, use list views and manual tracking to get familiar with the data before you automate it.
This update pairs naturally with other commerce-layer work happening in HubSpot. If your team is thinking about programmatic commerce or has developers working with payment infrastructure, the Payment Links API update is a related layer worth reading alongside this one.
If you're thinking about revenue tracking holistically, it also connects to how you handle refunds and adjustments. The custom refund reasons update gives you another layer of data fidelity on the payment side of your CRM.
Key Takeaway
The beta restrictions on Custom Reports and Automated Workflows are temporary, but they matter. Don't build automation-dependent processes around this feature until the beta ends and full functionality is restored.
Strategically, this update is part of a larger pattern: HubSpot is pulling revenue operations data closer to the CRM core. If you want the full picture of what that means for your portal, the May 2026 updates roundup covers the broader theme well.
Who Should Care Most
This update is genuinely useful across roles and company sizes. Here's who should prioritize it.
- RevOps and Operations Managers who want a complete revenue picture inside HubSpot without forcing every payment through a digital processor.
- B2B companies with large contract values where payments often arrive as checks or wire transfers, not credit card transactions.
- Sales teams that close deals and then hand off to finance, and lose visibility into whether payment actually came through.
- HubSpot admins and portal managers who want to centralize data before building reports, so when reporting is unlocked post-beta, the data is already clean.
- Small and mid-sized businesses on any HubSpot tier, because this update is available at every level, including free.
George's Take
“Your CRM should reflect reality, not just the slice of revenue that ran through a payment processor. This update is HubSpot finally saying: all your money matters, not just the digital kind.”
I've been in dozens of HubSpot portals where the deal pipeline looked healthy but the actual cash collected was a mystery because checks and wires were tracked in a spreadsheet somewhere outside the CRM. The humans doing RevOps work were constantly context-switching between HubSpot and finance tools just to answer basic questions like "did they actually pay?" This update doesn't solve every problem, and the beta limitations on reporting and workflows are real friction you'll need to plan around. But the direction is right, and the fact that it's available on every tier means there's no reason to wait. Start logging your external payments now so your data is clean when full functionality lands.
If your team is ready to build a revenue tracking strategy inside HubSpot that actually reflects how your business collects money, we'd love to help. Book a strategy call with Sidekick and let's map out what a complete CRM revenue picture looks like for your portal.
Frequently Asked Questions
Do I need HubSpot Payments or Stripe to record external payments in HubSpot?
No. As of April 28, 2026, you can manually create payment records in HubSpot without connecting HubSpot Payments or a Stripe account. The feature is available on all hubs and tiers, including free. Note that Custom Reports and Automated Workflows for the Payment object are temporarily disabled during the public beta if you don't have a processor connected.
What types of external payments can I record in HubSpot?
You can record any external payment, including checks, wire transfers, cash, and invoiced payments collected outside of HubSpot's native payment tools. You enter the payment details manually or import them in bulk. HubSpot doesn't validate the payment method, so you can log whatever your business actually collects.
Can I automate external payment record creation in HubSpot?
Yes, but with a current limitation. During the public beta, the Create Records workflow action for the Payment object is only fully available if you have HubSpot Payments or Stripe connected. Once the beta ends, all workflow automation for payment records will be restored for all users regardless of processor status.
Where do manually recorded payments show up in HubSpot?
They appear in Commerce, then Payments, as well as on the Payments CRM card on any associated contact, company, or deal record. This means your sales, finance, and customer success humans can all see payment status from the CRM records they already work in daily.
Can I import historical payment records into HubSpot?
Yes. HubSpot supports bulk import of external payment records, making it straightforward to bring in historical data. This is especially useful if your team has been tracking offline payments in a spreadsheet and wants to centralize that data before building reports or automations post-beta.
Will Custom Reports work with manually recorded external payments?
Not during the current public beta, unless you have HubSpot Payments or Stripe connected. Custom Reports and Automated Workflows for the Payment object are temporarily disabled for non-processor users during the beta. HubSpot has confirmed these features will be fully restored once the public beta period ends.
