Guide
From quote to invoice in HubSpot – Revenue Hub or a Fortnox integration?
Revenue Hub puts quotes, contracts and invoices in HubSpot. How Swedish B2B companies choose between it and an integration with Fortnox or Visma.
By Viktor Olsson, founder and RevOps consultant
Guide · Sales· Updated · 16 min read
Revenue Hub is enough when you want the whole path from quote to payment in HubSpot. It assumes your invoices can get into the books easily, for example because you have few of them and take card payments through Stripe. If you already invoice in Fortnox or Visma, an integration is usually the better choice. The quote and the deal stay in HubSpot, the invoice is created in the accounting system, and the payment status is written back to the customer in HubSpot. If you sell annual contracts or subscriptions, it often ends up as a combination: quote and contract in Revenue Hub, invoice and bookkeeping in the accounting system.
The gap between the deal and the invoice
At many Swedish B2B companies the deal lives in HubSpot and the invoice in Fortnox or Visma. In between sits a person. The rep wins the deal and emails the quote to finance, who type the customer, the products and the prices into the accounting system by hand. That works until someone copies the wrong version.
A common example: finance copies an older version of the quote, and the invoice goes out for 30 licences instead of 25. There is already a connection to Fortnox, but it only goes from Fortnox to HubSpot. Earlier, when the customer got its first invoice, the connection created a new company in HubSpot without noticing that the customer already existed. Now the customer is in HubSpot twice. This is what happens next:
- The customer's CFO emails support about the invoice. The ticket ends up on the second record, where the rep can't see it.
- The next day the rep sends a quote for an upgrade, without knowing anything about the invoice.
- The customer doesn't pay the invoice until it is corrected, and that takes three weeks.
An invoice copied by hand turns into three weeks of waiting for the money and an irritated CFO. There are two ways to close the gap: move invoicing into HubSpot, or connect HubSpot to the accounting system.
What Revenue Hub is
Revenue Hub is HubSpot's product for quotes, contracts, invoices and payments. It was called Commerce Hub until June 2026. HubSpot expanded it in its autumn release in September 2026. The quote is now written from what's already on the deal, and HubSpot is meant to keep track of the revenue after the customer has signed too.
What's included:
- Quotes from the deal. The rep can ask Breeze Assistant to build the quote straight from the deal. The customer reviews, signs and pays in one place.
- Price books and quote rules. Quote rules warn about or block a quote that breaks your rules, for example a discount that's too high. They need Enterprise.
- Contracts. When the customer accepts the quote, a contract is created in HubSpot with its value, MRR, ARR and renewal date. Upgrades and renewals are done with new quotes on the contract. Letting the contract run billing and payments is still in beta.
- Invoices and subscriptions. An invoice can be created from a quote or straight from the customer.
- A billing portal for the customer (Professional and Enterprise), where they see and pay their invoices, see their subscriptions and update payment methods.
- Revenue Agent, an AI agent in beta that follows up on overdue invoices. More on HubSpot's agents in AI in HubSpot.
- Reports on revenue per contract. Breeze Assistant can also answer questions about revenue, such as booked MRR (beta). Service Hub has reports on how much revenue you keep, gross and net (GRR and NRR).
The free version has invoices, payment links and subscriptions. Quotes, contracts and e-signatures are in Professional, and price books and quote rules in Enterprise.
What works differently in Sweden
HubSpot says quoting and billing work worldwide. They do, but several things around the invoice are built for the US, the UK and Canada.
- Payments. HubSpot Payments is only available to companies in the US, the UK and Canada. A Swedish company connects its own Stripe account instead. Customers can then pay online in Swedish kronor, and you pay the fees you've agreed with Stripe.
- Buy now, pay later. Klarna and Affirm in HubSpot are only available in the US and Canada.
- VAT. Automated sales tax is built for companies in the US and Canada. Instead, you set up VAT yourselves as tax rates in HubSpot, for example 25%. If you sell to customers in other countries, other VAT rules often apply, and someone has to keep track of them.
- Invoice requirements. The Swedish VAT Act sets out what an invoice must contain. HubSpot itself says requirements vary between countries and that you should ask your legal or tax advisors whether HubSpot's invoices are enough. Go through an invoice with your accountant before you send the first one.
- E-invoices to the public sector. Invoices following a public procurement must be e-invoices that meet the European standard (Swedish law SFS 2018:1277), in practice usually sent through Peppol. HubSpot's own Peppol e-invoicing is only available to companies in Belgium and Germany (beta).
- Bookkeeping. Every invoice and payment has to be booked. HubSpot mentions connections to QuickBooks, Xero, NetSuite and Stripe, but not to Fortnox or Visma. If you invoice in HubSpot, the invoices and payments still have to be moved into the accounting system, by hand or with an integration.
None of this makes Revenue Hub unusable in Sweden. It does mean finance gets one more system to keep in order.
How an integration with Fortnox or Visma works
With an integration, reps keep working in HubSpot and finance in Fortnox or Visma. The data moves between the systems automatically, so nobody types the same thing in twice.
1 · HubSpot
Quote and deal
The rep builds the quote with products and prices from Fortnox. The customer signs and the deal is won.
2 · Fortnox
Customer and invoice
The integration creates or updates the customer and adds the invoice with the deal's line items.
3 · Fortnox
Sent and booked
Finance reviews and sends the invoice. It's booked with VAT as today, and the customer pays to your bank account.
4 · HubSpot
Payment status
Invoice number, due date and payment are written back. The rep and the customer success manager see whether the customer pays on time.
The flow in four steps: the rep makes the quote in HubSpot and wins the deal. The integration creates the customer and the invoice in Fortnox. Finance sends and books the invoice there. When the customer pays, the payment status is written back to HubSpot. This is how the data moves, with Fortnox as the example:
| Data | Direction | When |
|---|---|---|
| Products: product number, name, price and VAT | Fortnox → HubSpot | When a product is added or changed |
| Customer: name, organisation number, billing address and invoice email address | HubSpot → Fortnox | When the deal is won, and when the details change |
| Invoice basis: line items, quantity, price, discount, period and the customer's reference | HubSpot → Fortnox | When the deal is won |
| Invoice number, amount and due date | Fortnox → HubSpot | When the invoice is created |
| Payment status: paid, partly paid or overdue | Fortnox → HubSpot | When the payment comes in, or once a day |
Every piece of data has one system that owns it. Products are owned by finance and set up in Fortnox, with the VAT rate and bookkeeping account. Reps can then only put products on a quote that finance can invoice. Customer details are owned by sales and filled in in HubSpot. Neither system overwrites what the other one owns.
Customers are matched on organisation number. A company in HubSpot is linked to the right customer in Fortnox through its organisation number. A product is linked through its product number. If the organisation number is missing, or the company exists twice in HubSpot, you get duplicates in Fortnox too. In the other direction, a one-way connection from Fortnox can create a second record for the customer in HubSpot, as in the example above. So clean up HubSpot first. More on that in our article on how to clean up HubSpot before AI agents.
The invoice can start as a draft. We recommend letting the integration first add the invoice to Fortnox as a draft that finance reviews and sends. Once the flow has worked for a while, it can be sent straight away.
The customer success manager (CSM) sees the payments. When the payment status comes back, the company record in HubSpot gets fields such as "Overdue amount" and "Invoices paid on time". The second one is the same criterion that's worth 10 points in the health score. A workflow can also alert the CSM and the rep when an invoice becomes overdue. Then nobody sends an upgrade quote to a customer who's waiting for a corrected invoice.
Ready-made app or custom integration
HubSpot's marketplace has ready-made apps for Fortnox. The ones we've found are built by companies other than HubSpot and Fortnox and cost a monthly fee. Check these things before you pick one:
- Which fields come across to the invoice, such as the customer's reference and order number?
- Does a change to the deal come across after the invoice has been created?
- Does the payment status come back to HubSpot?
- Does it work when a deal has several companies or contacts?
- Which Fortnox plan does the app require?
For Visma, what's available depends on which of Visma's systems you use, so search for your system specifically. If no app fits, the integration is built against the accounting system's API. Fortnox has a documented API, and that's what we build against when a ready-made app isn't enough. You get a fixed price or an estimate after the first call, and you own the code.
The workflow: from closed won deal to invoice
The integration needs to know when to create the invoice. The simplest way is a workflow in HubSpot that starts when the deal is won, checks that everything is there, and then sets a field the integration reads.
Deal reaches the Closed won stage
Are the invoice details complete?
Organisation number, billing address, line items and the customer's reference are filled in
Invoice status = Send to Fortnox
Wait until Invoice status = Invoiced
Notify the CSM: invoice sent, with invoice number and due date
Complete the invoice details. Rep, due today
Notify finance: an invoice is waiting for details
Swipe sideways to see the whole flow.
The workflow step by step:
- Start. The workflow starts when the deal reaches the Closed won stage.
- Check. The branch checks that the company has an organisation number and a billing address, and that the deal has line items and the customer's reference. Fields on the deal can be made required before it can be closed, as we describe in One customer, one place. Fields on the company aren't covered by that, which is why the check is needed.
- To Fortnox. The Invoice status field is set to "Send to Fortnox". The integration reads the field and creates the customer and the invoice. With a ready-made app, this step can be the app's own workflow action instead.
- Wait. The workflow waits until the integration has written back the invoice number and set Invoice status to Invoiced.
- Notification. The CSM gets a notification with the invoice number and due date, and knows the invoice has gone out before onboarding starts.
- Something is missing. The rep gets a task to complete the details the same day, and finance is told an invoice is waiting. Turn on re-enrollment when the invoice fields change, so the deal goes through the check again once they're filled in.
- When the invoice is overdue. A separate workflow starts when the payment status changes to Overdue. It notifies the CSM and the rep and creates a task to contact the customer.
Revenue Hub, an integration or both
This is how the three options compare for a Swedish B2B company:
| Revenue Hub | Integration with Fortnox or Visma | Both | |
|---|---|---|---|
| Quote | From the deal, with price books, e-signatures and quote rules | In HubSpot, with products and prices from the accounting system | In Revenue Hub |
| Contracts and renewals | Contract with value, MRR and renewal date | Contract details as fields on the deal and company | In Revenue Hub |
| The invoice | Created in HubSpot. Check the requirements with your accountant | Created in the accounting system, as today | Created in the accounting system |
| VAT | Your own tax rates, set up by hand | In the accounting system, as today | In the accounting system |
| E-invoices to the public sector | Peppol from HubSpot isn't available to Swedish companies | Through the accounting system, as today | Through the accounting system |
| Bookkeeping | Invoices and payments are moved to the accounting system | The invoice is already there | The invoice is already there |
| Payment | Online through your Stripe account, or recorded by hand | To your bank account, as today. Status back to HubSpot | As with the integration |
| Overdue invoices | Revenue Agent (beta) follows up | A workflow alerts the CSM and the rep | A workflow alerts the CSM and the rep |
| Reports | Revenue per contract, MRR and ARR | Invoiced and paid per customer | Contracts, MRR and payments in HubSpot |
| Cost | Revenue Hub licence and Stripe's fees | Monthly fee for an app, or a custom integration | Revenue Hub licence and the integration |
| Finance works in | HubSpot and the accounting system | The accounting system | The accounting system |
| Fits when | You have few invoices and take card payments | You invoice in Fortnox or Visma and have simple contracts | You sell annual contracts or subscriptions |
Revenue Agent isn't in the last column. It follows up on invoices in HubSpot. We haven't been able to confirm whether it can also follow up on invoices an integration has brought in from Fortnox.
How to choose
Revenue Hub is enough when you have few invoices, take card payments through Stripe, and your accountant has approved both the invoices and how they get into the books. It can suit a smaller software company selling monthly subscriptions online, for example.
Choose an integration when finance already invoices in Fortnox or Visma and you sell one-off deals or simple contracts. Finance keeps working where the books are, and reps no longer email quotes to finance.
Choose both when you sell annual contracts or subscriptions with upgrades and renewals. Contracts, MRR and renewal dates are then in HubSpot, where reps and CSMs work, and the invoice is in the accounting system. That's what we recommend for most Swedish B2B companies with contracts.
If you don't know where to start, connect HubSpot and the accounting system first. You need the customers, the products and the payment status in HubSpot whether or not you add Revenue Hub later.
How the invoice error would have been caught
Go back to the example, now with the quote and contract in HubSpot and an integration with Fortnox:
- The invoice is built from the deal. The integration sends the line items from the won deal to Fortnox: 25 licences. Nobody copies a quote, so the older version with 30 licences never gets into Fortnox.
- An error shows up where the rep works. Customers are matched on organisation number, so the customer exists once in HubSpot. If something still goes wrong, the high-priority ticket appears on the right company record. The rep sees it before the upgrade quote goes out. We describe how tickets like that can be handled in our article on customer support in HubSpot.
- An unpaid invoice raises an alert. If an invoice still becomes overdue, the CSM and the rep get a notification the same day.
- The health score counts the payments. The payment status from Fortnox fills in the "Invoices paid on time" criterion automatically. Without it in HubSpot, the score couldn't have seen that the invoice was unpaid.
How to get started
- Map the flow as it is today. Who types what, in which system, and when? Follow one won deal all the way to a paid invoice.
- Decide who owns what. Customers, products, invoices and payments, one system for each.
- Clean up first. Organisation numbers on every customer company, duplicates merged and product numbers on the products in HubSpot.
- Talk to your accountant about VAT, invoice requirements and whether the invoice should be reviewed before it's sent.
- Choose your route from the comparison above, and test it on a few real deals before you switch everything over.
- Build the workflows and fields so reps and CSMs see invoice status and payments on the customer.
Common questions
Can you invoice Swedish customers from HubSpot? Yes. Invoices in HubSpot can be issued in Swedish kronor, with VAT set up as your own tax rate. Online payments go through a Stripe account you connect. Check with your accountant that the invoice meets the requirements, and decide how invoices and payments get into the books.
Is there a Fortnox integration for HubSpot? HubSpot doesn't have its own. HubSpot's marketplace has ready-made apps from other companies that connect HubSpot and Fortnox. If they aren't enough, you can build a custom integration against the Fortnox API.
Can HubSpot be connected to Visma? Yes. Which ready-made apps exist depends on which of Visma's systems you use, so search for your system on HubSpot's marketplace. If there's no app, or it doesn't cover what you need, the integration is built against the system's API.
What is HubSpot Revenue Hub? HubSpot's product for quotes, contracts, invoices and payments, called Commerce Hub until June 2026. It comes in a free version and in Professional and Enterprise.
Does Revenue Hub replace Fortnox? No. Fortnox and Visma are accounting systems with bookkeeping. Revenue Hub has quotes, contracts, invoices and payments, but no bookkeeping. That's why most Swedish companies still need their accounting system with Revenue Hub.
How long does an integration between HubSpot and Fortnox take? A ready-made app can be up and running in a few days, including testing. A custom integration for customers, products, invoices and payment status usually takes a few weeks. Most of the time goes into the decisions beforehand: which system owns what, and how existing customers and products are matched.
What does an integration between HubSpot and Fortnox cost? A ready-made app costs a monthly fee to the company that built it. A custom integration depends on the scope. After a free first call you get an estimate or a fixed price, excluding VAT.
About the author
Viktor Olsson, founder and RevOps consultant
Viktor has worked with HubSpot for six years, with teams from 3 people to organisations with 30 sales reps across the Nordics. He also works in RevOps at an international SaaS company.