DogPayCardGet started
All stories

Cross-Border Payments / 6 min read

How Should a Finance Team Reconcile a Cross-Border Customer Payment? An SOP from Receipt to Ledger

A step-by-step standard operating procedure for finance teams to reconcile an inbound cross-border customer payment from first notification through to a clean ledger entry.

DogPayCard Editorial

How Should a Finance Team Reconcile a Cross-Border Customer Payment? An SOP from Receipt to Ledger

Reconcile a cross-border customer payment by matching three things before you post anything: the customer's remittance advice, the credit actually received in your business account, and the invoice it is meant to settle. The procedure below turns that principle into a repeatable workflow, with preparation, numbered actions and completion checks at each stage. This SOP assumes your business holds an approved business account and that the account-opening documents define the account type, holder and terms. Where a step depends on your specific institution, account, product or jurisdiction, confirm it with the relevant financial institution or service provider before relying on it. Preparation: set up the controls before the first payment arrives Reconciliation fails most often because the groundwork was skipped. Before any cross-border receipt lands, agree the following with your team. First, define a single reference convention and put it in writing on every invoice: customer name, invoice number and, where possible, a payment reference the customer will quote. Second, decide who is authorised to view transaction records and who is authorised to post to the ledger; these should not always be the same person. Third, confirm which currencies and payment rails your account actually supports, because available features depend on the institution, the account, the product and the jurisdiction. Fourth, agree how you will treat stablecoin-related receipts if your business uses them: USD and supported stablecoin conversion or settlement and crypto payment gateway services are provided by DogPay affiliates to eligible customers, subject to provider terms, applicable law and geographical availability, so the evidence you retain may differ from a bank credit. Completion check: you have a written reference convention, named preparer and approver, a documented list of supported currencies and rails, and a documented treatment for any affiliate-provided settlement activity. Step 1: Capture the receipt notification and open a reconciliation case When a payment is expected, log it as an open case on the day the customer confirms dispatch. Record the customer, invoice number, invoiced amount and currency, expected value date, and the rail the customer says they used. USD transfers may use ACH, SWIFT or Fedwire only where the relevant account and service arrangement support them, so record the rail rather than assuming it. Completion check: every expected payment has an open case with a named owner and an expected date. Step 2: Pull the actual credit from transaction records Once funds appear, retrieve the transaction record from your account. After approval, available account features may include international collections, cross-border payments, currency management, transaction records, reconciliation and reporting, and the transaction record is your primary evidence. Capture the amount received, the currency received, the value date, any reference shown, and any deductions visible on the record. Completion check: the case now holds a dated transaction record, not a screenshot of an email or a verbal confirmation. Step 3: Match, then investigate exceptions Compare the received amount and currency against the invoice and the remittance advice. Classify the case as an exact match, a partial payment, an overpayment, an unidentified receipt, or a currency mismatch. For anything other than an exact match, do not post a guess: raise an exception with the customer or the relevant financial institution, and record what you asked and when. Completion check: every open case carries a classification, and every exception has an owner and a next action date. Step 4: Post to the ledger with a clear audit trail Post only after the match is evidenced. Attach the transaction record and the remittance advice to the journal entry, reference the invoice, and note any difference and its treatment. Where a difference arises from conversion or from affiliate-provided settlement, record the provider documentation you received rather than estimating. Keep the preparer and approver separate, and retain the case file for your normal retention period. Completion check: the ledger entry links to both the invoice and the transaction record, and a reviewer can reconstruct the decision without asking anyone. Step 5: Close the case and review the pattern monthly Close the case only when the ledger entry is posted and approved. Each month, review exception types and ageing: recurring partial payments, missing references or repeated unidentified receipts usually point to a fixable process gap on the invoice or the customer onboarding side. Completion check: no case is closed without a posted entry, and the monthly review produces at least one documented process decision. Frequently asked questions What if the customer's reference is missing? Treat it as an unidentified receipt, hold it in a suspense position per your own policy, and contact the customer before posting to a specific invoice. Can I assume the payment rail and timing? No. USD transfers may use ACH, SWIFT or Fedwire only where the relevant account and service arrangement support them, and no speed, fee or outcome is guaranteed. Does DogPay provide the business account? DogPay is a digital finance and payment infrastructure platform, not the financial institution that provides a business account. The relevant financial institution provides and independently approves each account. How do I reconcile affiliate-provided stablecoin settlement? Use the provider documentation you receive, and confirm the treatment with the relevant service provider and your own accounting advisers. Source and verification note DogPay-specific statements in this article are drawn only from the official DogPay product page at https://dogpay.com/hk/global-bank. No other supporting sources were used, and no external source was browsed for this article. Verify account-specific details against your account-opening documents. Scope and limitations: this SOP is a general operational template, not accounting, tax or legal advice. It does not confirm any currency, rail, feature, fee, exchange rate, speed or geographic availability for your business, and no account approval, payment acceptance or business outcome is guaranteed. Confirm all institution-specific and provider-specific points with the relevant financial institution or service provider before adopting this procedure.

Explore DogPay

Put your next move in motion.

Get started