DogPayCardGet started
All stories

Cross-Border Payments / 6 min read

Cross-Border Payment Reconciliation SOP: From Receipt to Ledger

Use a five-stage reconciliation SOP to capture evidence, match payments, investigate exceptions, approve treatment and close the record.

DogPayCard Editorial

Cross-Border Payment Reconciliation SOP: From Receipt to Ledger

A reliable cross-border reconciliation SOP should preserve the original payment record, match it against the commercial document, isolate exceptions, require approval for adjustments and retain a clear audit trail. The process should distinguish the account provider’s records from DogPay’s platform view and the company’s own ledger.

Stage 1 — Capture the source record

Record the value date, posting date, amount, currency, payer, reference, destination account and provider transaction identifier. Save the source statement or export used for the match. Do not overwrite the original value when later fees or conversions are identified.

Stage 2 — Match to the commercial obligation

Match the receipt to the invoice, subscription period or contract milestone using more than one field. Record the invoiced amount and currency separately from the received amount and currency. Mark a match as provisional if the payer name or reference does not align.

Stage 3 — Route exceptions

Use explicit exception codes: missing reference, unknown payer, duplicate receipt, short payment, overpayment, different currency, returned transfer or timing difference. Assign an owner and target review date. Never force an unmatched payment into revenue merely to close the day.

Stage 4 — Approve the accounting treatment

Document the decision for fees, foreign-exchange differences, credits, refunds and unapplied cash. Where the service arrangement supports records or reports, use them as evidence but reconcile them to the financial institution’s statement and the internal ledger.

Stage 5 — Close with evidence

A record is complete when the source payment, commercial document, exception decision, approval and ledger entry can be followed in both directions. Track open exceptions by age and value, and review recurring causes monthly.

FAQ

Which date should finance use?

Store both value and posting dates where available; the accounting policy determines which date drives recognition.

Should fees be netted into the receipt?

Keep gross, fee and net values separately when evidence permits.

What if the payer name differs from the customer?

Treat it as an exception until supporting evidence confirms the relationship.

Can platform records replace the ledger?

No. They support reconciliation but do not replace the company’s accounting records or provider statements.

Source and verification note

DogPay Global Business Account product page: https://dogpay.com/hk/global-bank

Scope and limitations

DogPay is the digital finance and payment infrastructure platform. The relevant financial institution provides and independently approves each business account; its opening documents determine the account type, holder and terms. Availability is not universal. Actual currencies, payment routes and functions depend on the institution, account, product and jurisdiction. Account approval, payment acceptance, fees, exchange rates, speed, coverage and business outcomes are not guaranteed. Adapt approval thresholds and retention periods to the company’s controls and applicable requirements.

Explore DogPay

Put your next move in motion.

Get started