For a foreign-currency invoice, confirm the agreed currency and obtain payment instructions suitable for that arrangement. Keep the currency of the invoice, the account destination and any conversion agreement distinct. Selecting a currency in the creator does not confirm that an account can receive it or convert the amounts.
The payment preparation workflow starts with the accepted commercial agreement. The current creator supports a single selected invoice currency and readable payment fields. It does not retrieve exchange rates, verify banking capabilities or initiate an international transfer.
Confirm the amount being requested
Check the accepted quote or order for the invoice currency. A customer in another country may still have agreed to pay in your usual currency. Conversely, a domestic customer may have agreed another denomination. Country and currency should not be treated as interchangeable clues.
Read the code with every amount during review. USD 500.00 and EUR 500.00 contain identical digits but have different monetary meanings. An unchanged preview total after changing the currency selector is not evidence that any exchange-rate calculation occurred.
If prices must be converted, establish the appropriate rate, date, source and rounding basis outside the creator. Preserve that evidence and review the resulting unit prices against the app’s two-decimal limit. Do not change quantities merely to compensate for lost price precision.
Obtain the right account instruction
Ask the authorised account holder for the instructions that apply to this currency and payment route. A business may use different destinations or instructions for different arrangements. Do not assume the account copied from an old domestic invoice is suitable.
Keep the account name, relevant identifiers and any required institution information clearly labelled in the preparation record. Preserve exact values rather than constructing them from a bank name. The creator cannot determine whether those instructions are current or authorised.
Confirm any unexpected change through an established contact route. A message containing new bank details is not independent verification of itself. Record the approval outside the invoice where appropriate, while including only the necessary customer-facing instruction in the document.
Separate invoice currency from receiving currency
An account’s ability to receive several currencies does not establish which currency the customer owes. Likewise, an arrangement involving bank conversion does not automatically change the invoice’s denomination. Confirm what the agreement and payment provider actually require.
Do not add contradictory prose such as “pay the equivalent in your currency” unless there is a clear agreed process and a suitable final representation. The creator cannot select a future rate, calculate a floating balance or reconcile the eventual converted receipt.
If the destination needs a separate tax accounting currency or other structured monetary role, use software that implements it. That is different from providing bank-transfer instructions. A note naming another currency does not create the required calculation or typed fields.
Review transfer-specific details
Obtain any additional information required by the authorised provider for the actual route. Do not infer intermediary instructions, charges or special references from an unrelated sample. Keep the source and intended meaning of every supplied value.
The guide to IBAN and BIC information explains why account and institution identifiers are distinct. Their presence on the page does not establish ownership, destination suitability or a successful transfer. Those are separate questions for the appropriate banking process.
Avoid collecting credentials or authentication codes. The invoice editor needs no bank login access to display instructions. Include only information appropriate for a document that may circulate through several customer departments and be retained in accounting records.
Check the whole payment section
Compare the selected currency, total, method, reference and instructions with the agreement. Read notes for old currency statements or account details copied from another draft. Numeric recalculation does not rewrite free text.
A practical review table can show the agreed invoice currency, confirmed destination, authorisation source and any external conversion responsibility. Leave unresolved items clearly marked. A clean preview should not conceal the absence of a decision about which party handles conversion or how the amount is settled.
If another system produces the final standards document, preserve the currency and instruction roles during transfer. Inspect its output rather than assuming a similar label means it implemented the required mapping. The current application JSON is its own schema, and line-item CSV is not a complete payment instruction record.
Keep the final version traceable
After correcting currency or payment text, export a fresh version and distinguish it from earlier files. A previously downloaded invoice does not update when the selector or account instruction changes. Check any cover message prepared outside the app for the same consistency.
Retain the accepted monetary agreement and authorised payment instruction with the final record. The creator can help prepare supported data locally, but it does not process conversion, verify accounts, track settlement or guarantee acceptance. Complete those operational and formal-format requirements through the appropriate implemented workflow before delivery.
A practical final check
For a fictional review table, record the agreed invoice currency, the confirmed account instruction and the person responsible for any conversion. Check each fact against its source before comparing the final payment paragraph.