Your client’s affiliate paid you: explain the third-party receipt

Keep the buyer, payer and processing intermediary distinct when a foreign receipt comes from another name.

A different payer name is a fact to explain, not an error to conceal. A customer’s affiliate, a payment processor and an unrelated third party can have different roles. Your evidence should identify who bought the service, who sent the money and why those names differ.

Map each party’s role

Use the contract and invoice to identify the buyer. Use the payment evidence to identify the remitter and processing route. Add a short explanation supported by correspondence or an agreement where available. Do not overwrite the buyer’s name with a processing bank or platform simply because that is the name visible on the account statement.

Ask what evidence supports the arrangement

Give the bank the party map and relevant references through its verified channel. Ask what additional documents it wants and how to show the receipt in its accepted format. If the payer relationship is not known, contact the customer before making a declaration about it. Keep the bank’s response and any customer confirmation together so a later reviewer can understand the payment path.

Build a party map from documents, not assumptions

List the exporter, contractual buyer, actual remitter, provider and processing bank where relevant. For each, state the role and the document identifying it. Similar company names may suggest an affiliation but do not prove it. Ask the customer for an explanation when the remitter differs from the buyer and retain their response through your normal verified relationship.

Do not substitute a bank narration for the complete commercial record. A processing institution’s name can appear even when it is not the customer or ultimate payer. Explain that uncertainty in the enquiry. Keep the original invoice unchanged while the payment path is assessed. The purpose of the party map is to make the facts visible, not to manufacture a relationship that the documents do not support.

Request evidence appropriate to the actual difference

Describe the mismatch precisely: an affiliate name, a group treasury entity, a marketplace or an unknown remitter. Ask the bank what evidence it wants for that arrangement. A request that names the exact parties and reference is more useful than attaching a generic third-party declaration with unsupported statements. Do not sign that a relationship exists merely because a sample template includes the sentence.

Keep customer correspondence and any relevant agreement connected to the payment reference. Where the bank asks for a specific form or declaration, obtain its current accepted version and review every assertion before use. If the customer cannot explain the payer, say so and seek further instructions. An unresolved relationship is a fact that should remain visible.

Maintain the explanation across repeat receipts

A confirmed payer arrangement may recur, but check that the later transaction follows the same documented route and contracting structure. Record which invoices the explanation covers. If the customer changes its paying entity or the transfer comes from another name, review the supporting evidence again rather than applying an old explanation automatically.

Keep a concise note for your team identifying the accepted evidence and the bank response. Distinguish a response that acknowledges the enquiry from one that assesses the arrangement. If another institution handles later receipts, confirm its process separately. A helpful party map can be reused as factual background, while acceptance remains tied to the relevant bank, transaction and scope.

A fictional example

An invoice names Cedar Advisory Ltd, while the remittance comes from Cedar Group Services Ltd. The exporter obtains a payment explanation from the customer and asks the bank about the supporting evidence rather than changing the invoice issuer or customer.

Preparation checklist

Keep buyer and payer fields distinct.
Document the relationship instead of guessing it.
Preserve the bank’s acceptance response.

Is every platform settlement a third-party payment in the same sense?

Do not assume so. Explain the actual contractual and processing roles and ask the bank how it treats your route.

FICTIONAL WALKTHROUGH

A group treasury company pays two affiliates

A fictional exporter invoices two different overseas buyers in the same corporate group. One treasury entity sends a combined payment. The exporter retains both invoices and asks the customers for written allocation and payer explanations rather than replacing both buyers with the treasury name.
The party map lists the two buyers, actual remitter and processing route. An allocation schedule shows the amount linked to each invoice. The bank enquiry asks what further evidence is needed and does not claim an agreement exists unless the exporter actually holds it.
The bank response and supporting correspondence are stored with both invoice references. A later payment from a different entity triggers a new evidence check. The exporter keeps the same commercial identities and updates only the receipt facts supported by the new documents.

Your next step

Prepare the party explanation

Sources and scope

Sources reviewed 9 October 2026. The routines and fictional examples are editorial preparation suggestions. They do not confirm your bank’s acceptance, classification or transaction status.