Multi-Currency Handling in the Accounting API

How the Unify Accounting API handles currency data when syncing invoices from ERP systems.

Unify acts as a pass-through for currency data. The platform does not perform currency conversion, FX calculations, or amount normalization. Each invoice carries exactly two currency-related fields:

All monetary fields (total, sub_total, total_tax, balance, deposit) represent the amount in the currency indicated by the currency field. There are no separate base-currency amount fields.

Yes, for the vast majority of connectors. The currency field contains the transaction currency as recorded in the ERP, and all amounts correspond to that currency.

Exception - Sage Intacct: Sage Intacct returns the company's home/base currency rather than the transaction currency. For multi-currency Intacct companies, the currency field may not reflect the actual invoice denomination. See section 4 for details.

Yes. Each invoice has its own independent currency field, so a customer can have invoices in USD, EUR, ZAR, or any other currency simultaneously - as long as the underlying ERP supports it. Unify imposes no restriction on this.

No. Only the transaction currency amounts are returned. There are no base_total, home_currency_amount, or equivalent fields in the unified schema.

If you need base-currency equivalents, you can calculate them using the currency_rate field where available.

No. All amounts are passed through from the ERP exactly as received. Unify does not apply exchange rates, convert between currencies, or source FX rates from any external provider.

The currency_rate value, when present, is whatever the ERP recorded at the time of the original transaction.

Invoices are never excluded due to unrecognized currencies. The invoice will always be returned, but the currency field may be null, UNKNOWN_CURRENCY, or the raw unrecognized value depending on the connector.

The currency field accepts all standard ISO 4217 codes (approximately 170), plus BTC, ETH, and UNKNOWN_CURRENCY as a fallback for unrecognized values.

Sage Intacct is the only connector where the currency field represents the company's home/base currency rather than the transaction currency.

For single-currency Intacct companies this makes no difference. For multi-currency companies, be aware that the currency field reflects the home currency, and the monetary amounts (total, balance, etc.) are expected to reflect base-currency values, though this is best verified against a live multi-currency Intacct account.

The currency_rate value is provided by the ERP and reflects the rate at the time of the transaction. The direction of the rate (e.g. "1 USD = X EUR" vs "1 EUR = X USD") depends on the ERP's own convention and is not normalized across connectors.

A few connectors return currency data only on single-record fetches, not on list endpoints:

• Procountor: Both currency and currency_rate are only available when fetching a single invoice

• Visma Netvisor: currency_rate is only available on single-record fetches

• Accounting API — Invoices reference

• ISO 4217 currency codes