Invoice Currency

Overview

Invoice currency is the currency in which an invoice’s commercial amount and balance are denominated. It can be a fiat currency, cryptocurrency, stablecoin, or another agreed unit, but the code and precision must be explicit. The invoice currency can differ from the payer’s chosen asset, display currency, settlement currency, and the merchant’s reporting currency. For teams linking Invoice Currency to Invoice Base Currency, merchant interfaces should expose only combinations that can be processed and should handle suspensions, migrations, and unsupported representations explicitly.

Line items, tax, discounts, and credits are calculated in the invoice currency unless the document states another basis. Currency symbols alone are insufficient because the same symbol can represent several currencies.

When payment occurs in another asset, the system creates a conversion quote. The invoice remains denominated in its original currency while the payment record stores the rate and received asset.

A crypto-denominated invoice can avoid quote expiry but exposes the commercial price to token volatility. A fiat-denominated invoice stabilizes the obligation but requires conversion at payment time.

Risks include wrong decimal precision, inverted rates, mixed-currency line items, inconsistent tax, and refunds based on settlement currency instead of invoice currency.

Systems should store currency code, precision, original amount, payment quotes, settlement conversion, accounting translation, and revision history.

For Invoice Currency, the operational boundary with Invoice Base Currency and Invoice Pay Currency should be explicit. Identifiers for Invoice Currency should connect those records without allowing either linked status to overwrite its own state.

The support record for Invoice Currency should distinguish display or pricing units from the asset and network actually accepted for transfer and from the asset used for merchant settlement. When Invoice Currency interacts with Invoice Base Currency, token symbols are insufficient when several contracts or bridged representations share a name; the allowlist should use chain, contract or native-asset identifier, decimals, minimums, and current availability.