Skip to main content
Integrations

How multi-currency quotes sync to HaloPSA

Quotes in a currency other than your account default reach HaloPSA as amounts in that default currency, converted at the exchange rate locked when you send. The PDF your customer sees stays in the quote currency.

Written By Bram Fofana

Last updated 10 days ago

When you quote in a currency other than your account default β€” for example a GBP quote on an AUD account β€” HaloPSA does not receive the quote-currency amounts. Salesbuildr converts each catalog line to your default currency using the exchange rate locked when you send the quote, then writes those converted amounts onto the Halo quotation. The proposal your customer sees stays in the quote currency.

This article is for HaloPSA accounts with multi-currency quoting enabled (Premium plan). ConnectWise and Autotask handle currency on quotes differently.

What your customer sees versus what HaloPSA shows

SurfaceCurrency
Customer portal, email, and Download PDFQuote currency (for example GBP)
Quote editorQuote currency (for example GBP)
HaloPSA quotation line prices, costs, and totalsYour Salesbuildr default currency (for example AUD)
HaloPSA sales-order and Add items to contract line pricesThe same converted default-currency amounts
Approved quote PDF attached to the Halo quotationQuote currency β€” the same PDF your customer received

After the quote is Approved, Salesbuildr attaches that PDF to the Halo quotation for your team. Halo portal users do not see that attachment; they are not the audience for it.

A GBP quote on an AUD account is the usual example: the customer is looking at pounds, while Halo is looking at Australian dollars for the same deal.

How the conversion is calculated

  1. Set your default currency and enabled currencies under Settings β†’ Financial β†’ Pricing Rules. See Configure and use multi-currency.
  2. Create the quote in the customer’s currency (New Quote β†’ Currency, or the quote Settings panel).
  3. Send or Mark as sent. Salesbuildr stores that day’s European Central Bank (ECB) rate on the quote. Later syncs reuse that locked rate, so Halo amounts do not drift when the daily rate changes.
  4. Salesbuildr converts each catalog line’s sell price from the quote currency into your default currency and writes those amounts to the Halo quotation.

Retracting a quote clears the locked rate. Sending again locks the rate on the new send date, so Halo amounts can change after a retract-and-resend.

Draft quotations in Halo (before the first send) use the latest daily rate. After send, the locked rate applies.

Does HaloPSA need its own multi-currency setup?

No. You do not need to turn on multi-currency in HaloPSA for this to work.

Salesbuildr always sends amounts in your Salesbuildr default currency. It does not set a currency on the Halo quotation, and it does not read a currency from the Halo client. Halo treats the numbers as ordinary amounts in Halo’s usual currency.

Turning on Halo multi-currency does not make a GBP quote appear as GBP in Halo. Halo would still receive the converted default-currency figures.

Keep Halo’s base currency the same as Settings β†’ Financial β†’ Pricing Rules β†’ Default currency. If those two defaults differ, Halo labels the amounts with Halo’s currency while the numbers are still your Salesbuildr default.

What is converted

These catalog lines are converted from the quote currency into your default currency at the locked send-time rate:

  • Product, service, and labour sell prices
  • Bundle child lines (the bundle parent is not sent to Halo)
  • Enabled add-on lines

The same converted unit prices are used when you later click Create sales order or Add items to contract. See Monthly and annual quote terms and HaloPSA invoicing.

Tax on the Halo quotation follows your tax settings. If tax is calculated in HaloPSA, Halo applies it to these converted default-currency amounts.

Line-level discounts (a lower unit price on the row) are already in that converted sell price.

What is not converted, or not sent

Halo quotation amounts are meant to match your default currency, not the PDF currency. These items do not go through the same quote-currency conversion as catalog sell prices:

AmountWhat HaloPSA receives
Line costStored in your default currency and sent as-is
Setup sell price and cost (extra Halo quotation lines named β€œ(Setup)”)Stored in your default currency and sent as-is
Shipping chargeStored in your default currency and sent as a Halo quotation line when a Shipping product is set under Settings β†’ Integrations β†’ Halo β†’ Products β†’ Defaults. Not added to the sales order. See HaloPSA Setup.
Quote-level discount (the discount on the whole quote, not a line)Not sent to Halo. The customer PDF still shows it. Halo’s quotation total can therefore be higher than the PDF total.
Quote currencyNot sent. Halo does not receive GBP, EUR, or any other quote-currency code.

Rounding to currency cents can also make a Halo total differ slightly from the PDF total converted by hand.

Other Halo quotation gaps that are not currency-specific still apply: per-line descriptions do not sync, and the shipping type name (for example β€œOrder”) is not copied into Halo. See HaloPSA Setup.

What you will see

Typical, expected signs:

  • A GBP quote’s Halo quotation lines are in AUD (or whatever your default currency is), while Download PDF is still in GBP.
  • The Halo quotation total does not match the PDF grand total, because the two documents are in different currencies β€” and because a quote-level discount is on the PDF only.
  • Enabling multi-currency in Halo does not change those Halo line amounts.
  • After you retract and send again, Halo amounts can change because a new rate was locked.

This is expected. Send (or Mark as sent) and Approve the quote in Salesbuildr. Use the attached Salesbuildr PDF when you need the customer-facing GBP (or other quote-currency) figures inside Halo.

See also