When a private medical practice pays an overseas equipment supplier or administrative-services vendor, sending the money is only part of the job. The practice also needs to establish which invoice was paid, which entity paid it, what currency the vendor should receive and how the bank transaction connects to the accounting records.
A payment can leave the practice’s account without giving the vendor enough information to apply it correctly. That creates avoidable follow-up: an invoice still appears unpaid, staff consider sending a duplicate payment, or the bookkeeper cannot explain the difference between the invoice and the bank debit.
ISO 20022 is relevant because it provides a standard for organizing financial messages, including payment information. But an owner’s practical question is not simply, “Does our bank use ISO 20022?” It is: “Will our invoice reference and beneficiary details reach the recipient, and what evidence will we receive to reconcile the payment?”
What ISO Payment Standards Do—and Do Not Do
ISO 20022 provides a common framework for financial messaging. In payment workflows, it can support separately identified information about parties, amounts, currencies and remittance details rather than relying entirely on an unstructured note.
Other standards identify different parts of a payment. A BIC identifies an institution; an IBAN identifies a bank account in countries that use that system. Neither replaces the invoice reference needed to explain what the payment settles.
| Item | What it addresses | What the practice should confirm |
|---|---|---|
| ISO 20022 | How financial-message information is organized | Which customer-facing fields the bank supports and passes onward |
| BIC | Identification of an institution | Whether it is required for the selected payment route |
| IBAN | Standardized account identification where used | Whether the destination uses it and which account details are required |
| Remittance information | The commercial reason for the payment, such as an invoice reference | What the beneficiary can actually see |
| Bank confirmation or transaction reference | Evidence and identification of the payment instruction or transaction | What the confirmation establishes and how to obtain later status information |
A payment-message standard is not a security certification or proof of legal compliance. ISO 20022 adoption does not establish that a vendor is legitimate, bank details are correct, funds have arrived, or a transaction satisfies every applicable requirement. It also does not establish HIPAA compliance.
Your bank or payment provider must explain the requirements for the actual transaction. Supported formats and required fields depend on the payment channel, destination, currency and provider—not just the standard used somewhere in the banking network.
Start With the Payment Channel Your Staff Actually Use
A bank may use ISO 20022 within its payment infrastructure while offering the practice a portal with only a few entry boxes. Another channel might accept a payment file with more detailed fields. Those experiences are not interchangeable.
Before changing an accounts-payable process, identify whether staff initiate overseas payments through a bank portal, a file upload or a payment provider. Then ask the provider to explain that specific channel.
Confirm:
- Which beneficiary details are mandatory, including name, address and account identifiers.
- Whether remittance information is structured, free text or a combination.
- Whether the invoice reference has a dedicated field.
- Whether characters or reference lengths are restricted.
- Whether any information is shortened, combined or omitted before reaching the beneficiary.
- Which details appear in downloadable confirmations and account activity.
Do not assume that a field labeled “reference” reaches the vendor. It might be an internal reference visible only to your practice. Likewise, a note stored in the bank portal may not appear on the beneficiary’s statement.
The goal is a documented field map, not a technical implementation project. Most practice owners need clear entry instructions and usable payment evidence, rather than a specification for building payment messages.
Map the Invoice to the Payment and the Books
Build a short payment worksheet that connects the approved invoice to the bank instruction and accounting entry. Keep internal bookkeeping details separate from the information that must travel with the payment.
Illustrative example: A US private medical practice is paying a fictional overseas equipment-maintenance vendor an invoice for EUR 2,400. The identifiers below are invented examples, not valid banking instructions or prescribed ISO field names.
| Source information | Illustrative value | Where it belongs | What to check afterward |
|---|---|---|---|
| Paying practice entity | Harbor Medical Practice LLC | Internal payment approval and selection of the entity’s bank account | The debit belongs to the correct entity |
| Beneficiary legal name | Example Equipment Services Ltd | Beneficiary-name field | Confirmation matches independently verified vendor details |
| Beneficiary account and bank details | Verified details held in the vendor record | Bank-designated account, BIC or other routing fields, as required | Entered details match the approved vendor record |
| Invoice reference | EES-1048 | Provider-designated invoice or remittance field | Vendor can identify this reference in the information received |
| Invoice amount and currency | EUR 2,400 | Amount and currency fields | Instruction uses the intended payment currency |
| Internal location allocation | North location—equipment maintenance | Accounting record or internal worksheet | Cost reaches the appropriate location P&L |
| Practice payment reference | AP-EES-1048 | Internal reference field, if available | Connects the payment worksheet to the bank record |
| Bank transaction reference | Reference assigned after submission | Saved confirmation and accounting support | Allows staff to identify and inquire about this payment |
The bank’s transaction reference does not replace the vendor’s invoice reference. They answer different questions: one identifies a banking transaction; the other identifies the obligation being settled.
If the bank supports a structured invoice-reference field, ask which reference types it accepts and how an ordinary supplier invoice number should be entered. Do not place an invoice number into a specialized field merely because it looks suitable.
Keep shared-cost allocation out of the remittance message
An overseas vendor generally needs the paying customer’s identity and invoice reference, not the practice’s full allocation schedule. If a payment covers services used by multiple locations, retain the allocation in the accounting records with its basis and approval.
For multi-entity practices, confirm which entity owes the invoice and which account should pay it. If a different entity pays, have the finance team determine the appropriate intercompany treatment rather than recording the entire amount as an unexplained expense in the paying entity.
sbb-itb-17e8ec9
A Practical Overseas-Payment Workflow
1. Approve the invoice and verify the beneficiary
Match the invoice to the purchase approval, contract or other appropriate support. Confirm the vendor identity, invoice currency, amount and payment terms before preparing the bank instruction.
For new or changed bank details, use an independently established contact method to verify the change. A well-formed payment message cannot determine whether an emailed account-change request is genuine.
Where staffing permits, separate payment preparation from approval. For a smaller administrative team, the owner or designated manager can review the beneficiary, amount, currency and invoice reference before release.
2. Enter the reference where the provider says it belongs
Use the provider’s instructions for the selected channel. Check the beneficiary name and account details against the approved record, and confirm whether the amount represents the currency being sent or the amount intended for receipt.
If one payment covers several invoices, ask whether the channel supports multiple structured references. If it does not, agree on an alternative with the vendor, such as a separate remittance advice that clearly connects the payment to the invoice list. Do not assume a long list pasted into a note will arrive intact.
3. Review currency conversion and charges
Ask the provider how conversion and charges will be shown and whether charges may affect the beneficiary’s receipt. Avoid assuming that the practice’s account debit equals the vendor’s invoice amount expressed in another currency.
Save the available conversion details and fee information. Your bookkeeper needs enough support to explain the bank debit, invoice settlement and any separately identified charges or exchange differences.
4. Save the confirmation and understand its status
Retain the approved invoice, payment worksheet and available bank confirmation together. Record the bank transaction reference alongside the internal payment reference.
Read the status carefully. “Submitted” or “accepted” may describe processing of an instruction rather than receipt by the beneficiary. Ask the provider what each status means and what evidence is available if the vendor reports nonreceipt.
5. Reconcile and resolve exceptions
At reconciliation, connect the bank debit to the invoice and supporting confirmation. Check the entity, currency, fees and location allocation. An invoice marked paid internally is not enough if the bank record or vendor account remains unresolved.
IRS Publication 583 supports maintaining complete business records, keeping business accounts separate and reconciling bank records. The payment worksheet helps connect those records; ISO 20022 does not replace them.
Question Sheet for Your Bank or Payment Provider
Use this sheet for a discussion about the actual channel your practice uses. Request written instructions or a sample confirmation where available, rather than relying on a general statement that the provider supports ISO 20022.
| Topic | Question to ask | Answer to document |
|---|---|---|
| Channel | Which overseas-payment service are we using, and what input format does it accept? | Service name and entry or upload instructions |
| Required details | What beneficiary and bank fields are required for this destination and currency? | Field list and validation instructions |
| Invoice references | Which field should hold our supplier’s invoice number? | Exact field label and any format restrictions |
| Structured remittance | Does this channel accept structured remittance information, free text or both? | Supported options and reference types |
| Delivery of information | What information reaches the beneficiary, and could it be shortened or changed? | Known limits and visibility restrictions |
| Multiple invoices | How should we identify several invoices in one payment? | Supported method or alternative remittance process |
| Currency and charges | How are conversion and fees disclosed, and can charges reduce the amount received? | Available options and supporting records |
| Confirmation | What does each payment status establish? | Difference between submission, processing and receipt evidence |
| Reconciliation | Which references appear on confirmations, statements and downloads? | Fields available for matching to the books |
| Exceptions | How do we investigate a missing reference, rejection or reported nonreceipt? | Contact route, required information and next steps |
Handle Missing References Without Creating Duplicate Payments
When a vendor says an invoice remains unpaid, investigate before initiating another payment.
First, check the bank status and transaction reference. Then compare the beneficiary details, amount, currency and invoice reference with the approved instruction. Ask the vendor whether it received an unmatched payment, and provide an appropriate remittance advice through the agreed business channel.
If the reference was missing or incomplete, document where the information was lost. Was it omitted during entry, placed in an internal-only field, shortened in transmission or absent from the recipient’s reporting? The answer determines whether to change staff instructions, use another supported field or agree on separate remittance advice.
Keep an exception open until the payment’s disposition and invoice treatment are clear. Do not force a reconciliation match simply because the amounts look similar.
Keep Payment Information Focused on the Vendor Transaction
An overseas vendor payment ordinarily should not need patient names, dates of birth, diagnoses or other patient-identifiable information in its reference fields. Use supplier invoice numbers and internal business references instead.
If supporting documents contain patient information, have the practice’s privacy lead determine the appropriate handling process. Do not put patient-identifiable data into ordinary Slack messages or a general-purpose AI tool to investigate a reconciliation issue. A payment-message standard does not authorize that disclosure.
The Owner’s Decision: Improve the Handoff, Not Just the Format
For a staffed medical practice, the useful outcome is a reliable connection between the approved invoice, payment instruction, bank evidence and accounting record.
Start with one recurring overseas vendor. Confirm the required fields with your provider, document where the invoice reference belongs, and review the evidence from the next approved payment. Then use that tested workflow for similar payments, checking requirements again when the channel, destination or currency changes.
ISO 20022 can support richer payment information. Whether that information helps your practice depends on what your provider accepts, what reaches the beneficiary and what your team retains for reconciliation.