Invoice Exchange Rate

Overview

Invoice exchange rate is the rate used to convert an invoice denomination into another currency or cryptoasset for payment, display, settlement, or accounting. The rate must include its direction, source, timestamp, precision, spread, and validity period. One invoice can use different rates for customer quote, processor conversion, merchant settlement, and financial reporting. For teams linking Invoice Exchange Rate to Invoice Denomination, implementations should preserve the issued version, due balance, denomination, tax treatment, payment instructions, and every later adjustment or settlement event.

For a USD invoice paid in BTC, the quote can express BTC per USD or USD per BTC. Systems should store the actual mathematical relationship rather than rely on a label that can be interpreted both ways.

The rate can be locked for a payment lifetime or refreshed until the payer selects an asset. Once a transaction is submitted, the applicable quote should remain linked to that attempt.

Provider spreads and fees can be embedded in the rate or charged separately. Merchants need enough detail to reconcile the customer’s expected amount with the merchant’s settlement.

Risks include stale or manipulated feeds, inverted pairs, inconsistent decimal precision, unavailable markets, and refunds calculated with a later rate.

Systems should preserve base and quote currencies, numeric rate, source, timestamp, expiry, spread, pay amount, received amount, settlement rate, and refund policy.

For Invoice Exchange Rate, the operational boundary with Invoice Denomination and Invoice Lifecycle should be explicit. Identifiers for Invoice Exchange Rate should connect those records without allowing either linked status to overwrite its own state.

Operational controls for Invoice Exchange Rate should reconcile the requested balance with every accepted payment, fee, conversion, refund, write-off, and credit. When Invoice Exchange Rate interacts with Invoice Denomination, the system should distinguish document status from payment status, preserve who changed each field and why, and define how expired instructions, partial payments, excess payments, disputed items, and transactions received after cancellation are handled.