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
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
- Set your default currency and enabled currencies under Settings β Financial β Pricing Rules. See Configure and use multi-currency.
- Create the quote in the customerβs currency (New Quote β Currency, or the quote Settings panel).
- 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.
- 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:
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
- Configure and use multi-currency β default currency, enabled currencies, and choosing a quote currency
- HaloPSA Setup β connect HaloPSA, quote status mapping, and shipping product mapping
- HaloPSA opportunity custom fields and quotes β quote sync is one-way from Salesbuildr to Halo
- Monthly and annual quote terms and HaloPSA invoicing β sales orders after approval
- Quote Editor β creating quotes and the currency field
- Financial β Pricing Rules
- PSA Sync Issues β errors that appear when a sync fails
Was this helpful?
More in Integrations
IntegrationsPax8KPN / RoutITLeaderCloudStill need help? Ask the team