Multi-currency invoicing
Asking a client to convert before paying you adds friction and gives them a reason to delay. VegaPal lets each document carry its own currency — USD, AED, EUR, SAR, CNY, RUB, INR, or USDT, USDC, BTC and ETH — with payment instructions that match.
Fiat options cover the US dollar, UAE dirham, euro, Saudi riyal, Chinese yuan, Russian ruble and Indian rupee. Crypto options cover USDT, USDC, BTC and ETH, each with the network attached to the wallet you receive on.
Currency is set per document, not per account, so one client can be billed in AED and the next in USDT without changing any global setting.
There is no point invoicing in euros if the only account on the document takes dirhams. Attach the bank account that can actually receive the invoiced currency, and name the currency in the bank details so the client's bank does not guess.
For stablecoin invoices the equivalent step is the network. USDT on the wrong chain is a support ticket, not a payment.
VegaPal does not convert money or lock in an exchange rate — the invoice is denominated in the currency you chose. For accounting, record the value in your reporting currency using the rate on the date the payment lands.
If a client wants a reference figure in their own currency, add it as a note on the invoice and make clear which amount is payable.
Businesses invoicing from Dubai often quote in AED for local clients, USD for regional ones and USDT where transfers are slow — three currencies, one workflow, no separate templates.
Whatever mix you use, keep numbering in a single series per document type. Currency is a field on the invoice, not a reason to start a new set of books.
Bill locally in AED and internationally in USD without maintaining two systems.
Issue in the currency of the contract and attach the account that can receive it.
Invoice in USDT where bank transfers are slow, and in fiat where they are not.
Choose the one you use most so new documents start in the right place.
Pick the currency this particular client pays in when you create the document.
Select the bank account or wallet that can receive that currency, and label it clearly.
When payment arrives, note the value in your reporting currency for your own books.
Invoice generator for bank transfer and crypto payments
Bank transfer invoicesBank transfer invoices with details a client can actually use
USDT invoicingUSDT invoices with the network stated clearly
Invoice templateInvoice template: the fields that matter and why
Freelance invoicingFreelance invoices that get approved and paid
Prefer background reading first? The VegaPal Learn guides cover invoicing and payments in more depth, and pricing lists what each plan includes.
No. Each invoice is denominated in the currency you select and the payment arrives in that currency. Conversion, if any, happens at your bank or exchange.
One payable amount in one currency keeps things unambiguous. If a client needs an indicative figure in another currency, add it as a note.
The one they hold, if you can receive it. Reducing their conversion work is one of the cheapest ways to get paid faster.
Yes, apart from the payment block. Crypto documents carry the asset, network and address; fiat documents carry the bank fields.
The free plan covers 3 documents a month, with PDF downloads and shareable payment pages included.