Release Notes

Order field coverage expansion (both directions) Enhancement

The HubSpot Order ↔ Fortnox Order sync now covers the full set of header fields shown in the integration spec — labels, payment/delivery terms, PO number, invoice email, delivery date, references, and both billing & shipping addresses — in both directions.

These are added automatically (alongside the existing create_order_in_fortnox and order_number_in_fortnox) the first time the Fortnox-order sync runs after upgrade, or on next (re-)authentication:

• fortnox_labels — multi-select; allowed values internal, external, warranty, order
• fortnox_terms_of_payment — Betalningsvillkor
• fortnox_your_order_number — PO Number (Fortnox YourOrderNumber)
• fortnox_invoice_email — invoice email recipient
• fortnox_delivery_date — Leveransdatum
• fortnox_way_of_delivery — Leveranssätt
• fortnox_terms_of_delivery — Leveransvillkor
• fortnox_your_reference — Er referens (overrides the contact-derived default)
• fortnox_billing_address_street, fortnox_billing_address_city, fortnox_billing_address_postal_code, fortnox_billing_address_country — Faktureringsadress (HubSpot Order has no native billing address)

Leveransadress reuses the standard HubSpot Order shipping fields: hs_shipping_address_street, hs_shipping_address_city, hs_shipping_address_postal_code, hs_shipping_address_country.

On every order sync, the new HubSpot Order properties are populated from Fortnox: Labels[].Description, TermsOfPayment, YourOrderNumber, EmailInformation.EmailAddressTo, DeliveryDate, WayOfDelivery, TermsOfDelivery, YourReference, Address1/City/ZipCode/Country (Faktureringsadress) and DeliveryAddress1/DeliveryCity/DeliveryZipCode/DeliveryCountry (Leveransadress). Empty Fortnox values clear the corresponding HubSpot property. Cancelled and pipeline-stage handling are unchanged.

• Header fields: fortnox_terms_of_payment, fortnox_your_order_number, fortnox_way_of_delivery, fortnox_terms_of_delivery, and fortnox_delivery_date are mapped onto the Fortnox order payload when set.
• YourReference precedence: fortnox_your_reference on the Order overrides the default (first associated contact name).
• EmailInformation: fortnox_invoice_email on the Order is preferred; falls back to company billing_email.
• Faktureringsadress: order-level fortnox_billing_address_* is used first; missing fields fall back to the company's address (address/city/zip/country). Empty fields are omitted so Fortnox keeps the customer-record defaults.
• Leveransadress: taken from the HubSpot Order standard hs_shipping_address_* fields.

📚 Get Started — Syncing Fortnox Orders to HubSpot Orders · Get Started — Create a Fortnox Order from a HubSpot Order

HubSpot Order → Fortnox Order New capability

HubSpot Orders can now create Fortnox orders, completing the symmetry with Deal → Invoice and Quote → Offer. Trigger by setting the order property Create order in Fortnox to Yes; the Fortnox document number is written back to order_number_in_fortnox for idempotency.

• App setting: Enable HubSpot order to Fortnox order.
• Order properties: create_order_in_fortnox (trigger) and order_number_in_fortnox (written on success). Both are created automatically on (re-)authentication if missing.
• CRM subscription: a single subscription on POST /hubspot_event_subscriptions handles both order.propertyChange and the modern object.propertyChange payload.

HubSpot does not allow adding line items to orders created manually in the Orders UI — line items can only be set when an order is created via integration/API or rolled up from a Deal. To still cover the manual case, the integration falls back to the associated Deal:

• If the Order has no line items but is associated with exactly one Deal, the Deal's line items are used.
• If the Order also has no associated company, the Deal's company is used.
• If 0 or more than 1 Deals are associated, the run fails with “Order has no line items.”

• Idempotent: the create is skipped if order_number_in_fortnox is already set.
• Validation: exactly one company with a Fortnox id, line items in a single currency, no recurring line items, and articles that exist in Fortnox.
• Mapping: POST /3/orders/ with OrderRows using DeliveredQuantity (identical to invoice rows).

📚 Get Started — Create a Fortnox Order from a HubSpot Order

Fortnox invoice PDF attached to HubSpot deal New capability

When a Fortnox invoice is synced into a HubSpot deal, the invoice PDF is now also attached to the deal as a Note engagement, visible in the deal's activity timeline.

• First import: the PDF is downloaded from Fortnox and attached when a HubSpot deal is created from a Fortnox invoice.
• State transitions: when an existing deal is updated and its deal stage changes (e.g. Unpaid → Paid in full, Unpaid → Credited, Unpaid → Overdue), the latest PDF is fetched and a fresh Note is added.
• No change: if the deal stage didn't change on a re-sync, no new PDF is uploaded.
• Direction: this only applies to the Fortnox → HubSpot direction. PDFs are not uploaded back to Fortnox when a deal triggers a HubSpot → Fortnox flow.

• Files are stored in HubSpot Files under /fortnox-invoices/<portalId>/ with access set to Private, so only authenticated CRM users can view them.
• Each transition produces a new Note on the deal so you keep a timeline of state changes; the underlying file is overwritten when the same invoice is re-uploaded.

If downloading the PDF or uploading to HubSpot fails, the deal sync still succeeds. The error is logged so the attachment can be re-tried on the next state change.

📚 Get Started — Invoice PDF attached to the deal

Fortnox deal & order pipelines: automatic recovery on sync Change

When you import Fortnox invoices to HubSpot deals or Fortnox orders to HubSpot orders (with the optional order pipeline feature enabled), the app now checks the HubSpot pipeline before processing. If the default pipeline is missing, it runs the same “enable pipeline” flow as the app setting so the job can create or re-link it, then continue.

• Invoices (deals): If import is on but the deal pipeline in HubSpot is missing or not valid, the app attempts the same create/re-enable path as the Fortnox-invoice-pipeline toggle. If the app still cannot match stages (e.g. manual HubSpot changes), the import is skipped and the setting may be turned off, as before.
• Orders: If the Fortnox order order pipeline is enabled in the app but invalid in HubSpot, sync attempts to restore the default Fortnox order pipeline. If you disabled the order-pipeline feature in the app but old pipeline/stage IDs remain stored, the app does not auto-recreate until you re-enable the feature in settings.

📚 Get Started — Syncing invoices to deals · Fortnox order pipeline

Fortnox Way of Delivery: send invoice via API Change

The deal property Fortnox Way of Delivery (fortnox_way_of_delivery) updates the Fortnox customer default invoice delivery before create (when PRINT / EMAIL / PRINTSERVICE) and triggers Fortnox invoice send (GET …/print, …/email, …/eprint, or …/einvoice) after the invoice is created.

• Before POST /3/invoices: for PRINT, EMAIL, or PRINTSERVICE, PUT /3/customers/{id} with DefaultDeliveryTypes.Invoice (and EmailInvoice when EMAIL). E-INVOICE skips this step (same as April 16—configure lev.sätt in Fortnox if needed).
• After create: PRINT → GET …/print, EMAIL → GET …/email, PRINTSERVICE → GET …/eprint, E-INVOICE → GET …/einvoice.
• Optional bookkeep (fortnox_bookkeep_after_create) runs after send, when enabled.
• EMAIL uses the company billing email on the invoice as EmailInformation at create time.

Customer default delivery details: April 16, 2026.

📚 Get Started — Create an Invoice

Fortnox price lists & multi-currency product prices New Feature

Product sync can read Fortnox price lists and fill HubSpot’s company-currency product price plus optional hs_price_<currency> fields—instead of relying only on the single SalesPrice field on the article.

• The Fortnox integration must include the Pris (price) OAuth scope. Enable it in the Fortnox developer app, then reconnect Fortnox from HubSpot so new tokens include the scope.
• APIs used: GET /3/pricelists and GET /3/prices/{PriceList}/{ArticleNumber} per article during product sync.

When list names or codes do not clearly indicate a currency (e.g. “Prislista A”), operators set settings.fortnoxPricelistCurrencyMap on the portal’s token document (Fortnox list Code → ISO currency, e.g. {"A":"SEK","B":"EUR"}). An optional deployment default FORTNOX_PRICELIST_CURRENCY_MAP can be merged in; per-portal settings override by list code.

If you only map some lists (e.g. only EUR), other currencies still fall back to SalesPrice for the primary HubSpot price when no list price applies for the portal’s company currency.

Installations whose Fortnox token does not yet include price keep previous behavior: no price-list calls; primary product price from SalesPrice.

If Fortnox updates list prices without bumping article lastmodified, product sync can miss updates until you enable full article enumeration via FORTNOX_ARTICLE_LIST_IGNORE_LASTMODIFIED (see README / .env.template)—higher Fortnox API load.

📚 Get Started — Product pricing (multi-currency)

Fortnox Way of Delivery (deal) → customer default invoice delivery Improvement

When you create a Fortnox invoice from a HubSpot deal, an optional deal property can align the Fortnox customer’s default invoice delivery with the deal—using the correct Fortnox API fields.

• If Fortnox Way of Delivery (fortnox_way_of_delivery) is PRINT, EMAIL, or PRINTSERVICE, the app updates the linked Fortnox customer (before POST /3/invoices) with DefaultDeliveryTypes.Invoice. For EMAIL, it also sets EmailInvoice from the HubSpot company billing email.
• E-faktura (E-INVOICE) is not set via the API: Fortnox’s customer Way of delivery (lev.sätt) uses tenant-specific codes, not the same values as default delivery types.
• The app does not send customer WayOfDelivery with values like EMAIL—that caused Fortnox error 2001312 (Ogiltigt leveranssätt) because those strings are not valid lev.sätt codes in Fortnox.

If the customer update fails, logs include Fortnox ErrorInformation, full response body, and the request payload for easier diagnosis.

📚 Get Started — Create an Invoice

Bookkeep after create & credit invoices (deal properties) New Feature Fix

From a HubSpot deal you can optionally bookkeep a newly created Fortnox invoice, or create a kreditfaktura by crediting an existing debit invoice—without building line items for the credit path.

• Fortnox bookkeep after invoice create (fortnox_bookkeep_after_create) — When Yes, after a successful new invoice create from the deal, the app calls Fortnox to book that invoice. When No, the document is left unbooked (same as before).
• Fortnox kreditfaktura (fortnox_kreditfaktura, values NEJ / JA) — NEJ: create a normal invoice from deal line items. JA: create a credit invoice in Fortnox by crediting the debit document given in the reference field (deal line items are not used for this flow). Values are matched case-insensitively.
• Fortnox document to credit (invoice number) (fortnox_credit_invoice_reference) — Fortnox document number of the debit invoice to credit. Required when kreditfaktura is JA. The resulting document number is written to Invoice number in Fortnox (invoice_number_in_fortnox) after success.

• New invoice: POST /3/invoices as today; optional PUT …/invoices/{id}/bookkeep when bookkeep after create is enabled.
• Credit invoice: PUT …/invoices/{debitDocumentNumber}/credit — Fortnox creates the credit document from the referenced debit invoice.

Fortnox may return error 1000031 if bookkeep or credit requests omit a JSON content type. The app now sends Content-Type: application/json (with an empty JSON body) for those PUT calls.

📚 Get Started — Create an Invoice

Fortnox PaymentWay (deal property) New Feature

Control which payment method Fortnox uses when creating an invoice—directly from HubSpot deals.

• Fortnox betalsätt (PaymentWay) (fortnox_payment_way) — Kontant (CASH), Kort (CARD), or Autogiro (AUTOGIRO) sets Fortnox PaymentWay. Use Kort for card (e.g. Diners) instead of default cash. Default/unset omits PaymentWay.

📚 Get Started — Create an Invoice

HubSpot Quotes → Fortnox Offers; Fortnox Orders → HubSpot Orders & CRM webhook compatibility New Feature

For a consolidated product overview of quote → offer and Fortnox order → HubSpot Order (including prerequisites and “why this matters”), see April 22, 2026 — HubSpot Quotes → Fortnox offers & Fortnox orders → HubSpot Orders. This entry keeps the March 20 technical detail: webhook payload shapes, event keys, and scope/install notes as shipped in that release.

End-to-end flow between HubSpot Quotes, Fortnox Offers (offert), and HubSpot Order records: create a Fortnox offer from a Quote, store the document number on the Quote, embed the Deal id in Fortnox Remarks for traceability, then optionally sync Fortnox orders back into HubSpot Orders and associate them to the Deal. CRM property webhooks are aligned with HubSpot’s current object.propertyChange payload shape.

• App setting: Enable HubSpot quote to Fortnox offer so queued jobs are allowed to run.
• Quote properties: create_offer_in_fortnox (trigger) and fortnox_offer_document_number (filled after a successful create).
• Trigger: A CRM subscription to POST /hubspot_event_subscriptions when create_offer_in_fortnox becomes Yes (same endpoint as for companies and deals).
• Data: The app loads the Quote with line items, resolves the linked Deal and primary Company (fortnox_id), and builds a Fortnox Offer (rows mirror the invoice-from-deal logic: article, quantity, price, discount, VAT, etc.).
• Remarks: Fortnox Offer Remarks include HUBSPOT_DEAL_ID:<dealId> so the return path can link a Fortnox order to the right HubSpot Deal when remarks carry over or are set on the order.

• App setting: Enable Fortnox orders to HubSpot orders so background jobs may create or update HubSpot Order records from Fortnox.
• Scheduled fetch: Optional env REPEATABLE_JOB_ORDERS_TO_HUBSPOT_PATTERN registers a repeatable job (same pattern as other REPEATABLE_JOB_* cron variables) to list orders from Fortnox.
• Matching: For each Fortnox order, the app looks up or creates a HubSpot Order by hs_external_order_id (Fortnox document number) and sets name, currency, total, etc.
• Association: If Remarks contain HUBSPOT_DEAL_ID:<id> (as set when the order was created from a Quote), the HubSpot Order is associated to that Deal and related records; otherwise the HubSpot Order is still synced but not linked to a Deal.

• HubSpot often sends subscriptionType: "object.propertyChange" with objectTypeId (e.g. 0-14 for Quotes) instead of legacy quote.propertyChange / deal.propertyChange / company.propertyChange. The app accepts both normalized event keys for quotes (e.g. objectPropertyChangeCreateOfferInFortnox alongside quotePropertyChangeCreateOfferInFortnox) when the quote property create_offer_in_fortnox changes.
• Deals & companies: The same compatibility applies to objectPropertyChangeCreateInvoiceInFortnox and objectPropertyChangeCreateCustomerInFortnox.
• Property values: propertyValue may be JSON boolean true or string "true" for checkbox-style properties.

• Re-authenticate status page: The checklist includes quotes (e.g. Create offer in Fortnox, Fortnox offer document number), not only companies and deals.
• Post-install property creation: Missing HubSpot custom properties can be created for quotes together with companies and deals where applicable.

📚 Get Started — CRM webhooks · Quote → Fortnox Offer · Fortnox Orders → HubSpot Orders

Cost Center Uppercase Normalization Enhancement

The Fortnox Cost Center field now automatically normalizes input to uppercase for Fortnox compatibility, preventing errors when cost center codes are entered in lowercase.

• The "Fortnox Cost Center" company property (fortnox_cost_center) – input is now normalized to uppercase when creating customers and invoices in Fortnox.
• Case-insensitive input: You can enter values in any case (e.g. "avd1", "Avd1", "AVD1") – the app converts them to uppercase before sending to Fortnox.
• Fortnox expects cost center codes in uppercase; previously, lowercase could cause errors (e.g. "Kunde inte hämta/hitta valuta" or similar).

1. On the HubSpot company, set Fortnox Cost Center to any cost center code (e.g. "avd1" or "AVD1").
2. When creating a customer or invoice in Fortnox, the app automatically converts the value to uppercase (e.g. "AVD1").
3. This applies to both customer creation and invoice creation from deals.

📚 See Get Started Guide for cost center field mappings.

Amounts Include VAT (Deal property) Enhancement

Opt in to treat HubSpot deal amounts as VAT-inclusive when creating Fortnox invoices, preventing double VAT when your amounts already include VAT.

• A new HubSpot deal property "Amounts include VAT" (amounts_include_vat) is created and managed by the app.
• Default behavior is unchanged – the app does not send VATIncluded, so Fortnox uses its default (amounts treated as VAT-exclusive, VAT added on top).
• When your HubSpot amounts are VAT-inclusive, set the property to Yes – the app will send VATIncluded: true so Fortnox does not add VAT on top, preventing double VAT.

1. On the HubSpot deal, set Amounts include VAT to:
   • No or empty (default) – Original behavior. The app does not send VATIncluded; Fortnox treats amounts as VAT-exclusive and adds VAT.
   • Yes – HubSpot amounts include VAT. The app sends VATIncluded: true so Fortnox does not add VAT on top.
2. When an invoice is created in Fortnox from the deal, the app only sends VATIncluded: true when you explicitly set the property to Yes.

📚 See Get Started Guide for field mappings between deals and Fortnox invoices.

Invoice vs Delivery Note & Cash Invoice (Deal controls) New Feature

Control whether Fortnox creates a regular invoice, a delivery note, or a cash invoice (kontantfaktura) directly from the HubSpot deal.

• A new HubSpot deal property "Fortnox document type (print template)" (fortnox_print_template) is created and managed by the app.
• The property lets you choose between Faktura and Följesedel when creating a Fortnox document from a deal.
• The property is optional – if you leave it empty, Fortnox uses its own default template (normally invoice).
• A second HubSpot deal property "Fortnox invoice type" (fortnox_invoice_type) lets you explicitly request a cash invoice (kontantfaktura) when needed.

1. On the HubSpot deal, set Fortnox document type to:
   • Faktura (value: st) – standard invoice.
   • Följesedel (value: ps) – delivery note.
2. Optionally, set Fortnox invoice type:
   • Standard invoice (Fortnox default) (value: INVOICE) – normal invoice type, handled as today.
   • Kontantfaktura (cash invoice) (value: CASHINVOICE) – Fortnox creates a cash invoice instead of a standard invoice.
3. When an invoice is created in Fortnox from the deal:
   • If the value is ps, the app sets Invoice.PrintTemplate = "ps" so Fortnox creates a delivery note.
   • For any other value (including empty), the app does not send PrintTemplate at all – Fortnox then applies its own default template (normally invoice).
   • If fortnox_invoice_type is set to CASHINVOICE, the app sets Invoice.InvoiceType = "CASHINVOICE" so Fortnox creates a cash invoice.
   • For INVOICE or when the field is empty, the app does not send InvoiceType – Fortnox uses its own default (standard invoice).

📚 See Get Started Guide for field mappings between deals and Fortnox invoices.

Product Status Sync from Fortnox New Feature

HubSpot product Status (Active/Inactive) is now automatically synced from the Fortnox product registry

• Product Status Mapping: The HubSpot product Status property (hs_status, values: active/inactive) is now synced from Fortnox articles during product sync
• Fortnox Fields: Uses the Active and Expired flags from Fortnox article details
• Automatic Sync: Works with the existing 30-minute product sync - no configuration needed
• Active products in Fortnox appear as Active in HubSpot; inactive or expired articles appear as Inactive

The app maps Fortnox article status to HubSpot's product Status property (hs_status):

• Active in HubSpot: When Fortnox article has Active = true and Expired = false
• Inactive in HubSpot: When Fortnox article has Active = false or Expired = true

This ensures that product availability is consistent between Fortnox and HubSpot. Inactive products in Fortnox will no longer appear as available when creating line items in HubSpot.

📚 See Get Started Guide for product sync field mappings

Order Number Mapping and Price Handling Improvements New Feature Enhancement

Enhanced invoice and product sync with order number mapping from Fortnox invoices and improved null price handling

• Order Number Mapping: Customer order numbers from Fortnox invoices are now automatically synced to HubSpot deals in the order_number field
• Null Price Handling: Products with null or missing sales prices from Fortnox now default to 0 instead of undefined
• Pipeline Recovery: Improved error handling when creating HubSpot pipelines - automatically recovers from duplicate pipeline errors

When Fortnox invoices are synced to HubSpot deals, the YourOrderNumber field from Fortnox is now automatically mapped to the order_number property on the HubSpot deal.

Product sync from Fortnox now handles missing or null sales prices more gracefully by defaulting them to 0.

• Better order tracking with customer reference numbers flowing from Fortnox to HubSpot
• More reliable product data with consistent price values
• Enhanced data integrity across both systems

📚 See Get Started Guide for more details on invoice and product sync

VAT Support for Line Items New Feature

Automatically include VAT codes for line items when creating Fortnox invoices from HubSpot deals, with automatic enrichment from Fortnox articles

• VAT codes from HubSpot line items are now automatically included in Fortnox invoice rows
• Automatic enrichment: If a line item doesn't have a VAT code, the app automatically fetches it from the Fortnox article (when the line item has a SKU)
• The app uses the tax property on line items, which contains the VAT code synced from Fortnox articles
• VAT is only included when present - if a line item doesn't have a VAT code and the Fortnox article also doesn't have one, the invoice row is created without VAT
• VAT values are automatically trimmed of whitespace for clean data

1. When products are synced from Fortnox to HubSpot, the VAT code from the Fortnox article is stored in the product's tax property
2. When you add a product to a deal, the VAT code is available on the line item's tax property
3. When creating an invoice in Fortnox from a HubSpot deal, the app checks each line item for a VAT code
4. If the line item has a tax property: It uses that VAT code directly
5. If the line item doesn't have a tax property but has an SKU: The app automatically fetches the Fortnox article and uses its VAT code
6. If a VAT code is present (and not empty/null), it's automatically included in the invoice row
7. The VAT code is set directly on the invoice row in Fortnox

📚 See Get Started Guide for more details on invoice creation and field mappings

Remarks Field Enhancements New Feature

Enhanced Fortnox invoice Remarks field with agreement dates, featuring automatic localization based on deal currency

• Agreement Dates: Two new custom properties added to all HubSpot deals: "Agreement Start date" and "Agreement End date"
• Agreement dates are automatically formatted and added to the Remarks field in Fortnox invoices
• Localized formatting: Agreement dates are automatically localized based on the deal's currency code
• Swedish (SEK): "Avtalsstartdatum {date} och slutdatum {date}" - Dates formatted as YYYY-MM-DD
• English (other currencies): "Agreement start date {date} and end date {date}" - Dates formatted as MM/DD/YYYY
• Smart ordering: The Remarks field is built in this order: Agreement Dates → Description
• All fields are automatically created when the app is installed or updated

1. Agreement Dates: Add agreement start and/or end dates to any HubSpot deal using the new custom properties
2. The system automatically determines the locale based on the deal's currency code
3. When you create an invoice in Fortnox from that deal, the content is formatted and included in the Remarks field
4. If both start and end dates are provided, they appear together in one text string
5. If only one date is provided, only that date is included
6. Agreement dates appear before the deal description in the Remarks field

📚 See Get Started Guide for more details on invoice creation and Remarks field structure

Order Number Sync to Fortnox Invoices New Feature

Sync order numbers from HubSpot deals to Fortnox invoices for better order tracking and reference management

• A new "Order number" custom property has been added to all HubSpot deals
• Order numbers from HubSpot deals are automatically synced to the YourOrderNumber field in Fortnox invoices
• The field is automatically created when the app is installed or updated
• Perfect for maintaining order references between HubSpot and Fortnox

1. Add an order number to any HubSpot deal using the new "Order number" custom property
2. When you create an invoice in Fortnox from that deal, the order number is automatically included
3. The order number appears in the YourOrderNumber field in Fortnox

📚 See Get Started Guide for more details on invoice creation

Billing Email for Fortnox Invoices New Feature

Automatically set billing email addresses on invoices created in Fortnox from HubSpot deals, with automatic sync from Fortnox customers

• A new "Fortnox Billing Email" field has been added to all HubSpot companies
• Automatic sync: Billing email is now automatically synced from Fortnox customers to HubSpot companies every 2 hours
• The app prioritizes the EmailInvoice field from Fortnox, falling back to the Email field if EmailInvoice is not available
• Billing email from the company is automatically included when creating invoices
• Email is set directly on each invoice - perfect for ensuring the right person receives it

1. Automatic: Ensure your Fortnox customers have EmailInvoice or Email set - it will sync automatically
2. Manual: Open any company in HubSpot, find the "Fortnox Billing Email" field (in Company Information section), and add the customer's billing email address
3. When you create an invoice from a deal with that company, the email is automatically set on the invoice

Enhanced Line Item Description Mapping Enhancement Superseded

Major enhancement to improve invoice creation with richer line item descriptions

This release introduced the ability to combine both name and description fields in line items. The feature was later simplified to use only product names for cleaner, more consistent invoices.

During this period, the app combined both name and description fields to create rich, contextual descriptions.

Intelligent Handling:

Based on user feedback and to align with standard invoice practices, the feature was simplified in December 2025 to use only product names. This provides cleaner, more readable invoices with consistent formatting.

📚 See Get Started Guide for more details on invoice creation

Deal Owner Information in Fortnox Invoices New Feature

Automatically include HubSpot Deal Owner information in Fortnox invoices for better tracking

The HubSpot Deal Owner's name is now automatically included in the "Our Reference" field when creating invoices in Fortnox. This makes it easier to track which team member is responsible for each deal.

• When a deal is converted to a Fortnox invoice, the system looks up the deal owner in HubSpot
• The owner's full name (First Name + Last Name) is added to the invoice's "Our Reference" field
• If there's no deal owner assigned, the invoice is created normally without the reference

1. Re-install the app in your HubSpot portal to grant the new permission
2. The new permission is crm.objects.owners.read (read-only access to owner information)
3. Once re-authorized, the feature works automatically for all new invoices

• Better invoice tracking and accountability
• Automatic owner information without manual entry
• Seamless integration between HubSpot and Fortnox
• No disruption to existing functionality