Direct answer: A procurement foreign-exchange and cross-border payment page is not a line saying "pay in USD by T/T". The page should state: currency/amount (contract currency, invoice currency, settlement currency, FX source/date, conversion/tolerance); payment channel (T/T, L/C, D/P, D/A, O/A, cross-border RMB, per contract/bank rules); FX/cross-border RMB (real trade background, documents, bank review, FX administration); FX risk (hedging/sharing/adjustment, natural hedge, accounting translation); documents/compliance (contract, invoice, packing list, B/L, customs declaration, origin/licence, sanctions/AML screening, tax/customs); bank charges (wire/intermediary/message/issuance/acceptance/discrepancy, who bears); reconciliation/evidence (payment instruction, bank receipt, SWIFT, FX confirmation, invoice, customs declaration); fraud/account change/high-risk countries; and what the website may and may not publish. On the policy basis: the Foreign Exchange Administration Regulations require real, compliant FX receipts/payments by domestic entities/individuals, with banks reviewing transaction documents; the PBOC Notice on Further Improving Cross-Border RMB Business and Trade/Investment Facilitation (Yin Fa [2018] No. 3) supports cross-border RMB settlement/facilitation; the Civil Code governs contract price/payment/breach. This article is current to 2026-11-09 and is a summary of public rules and page method, not FX/tax/legal advice; FX rules, bank review, contracts and customs/tax practice control.
This article is for procurement, finance, customs, legal and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby. It covers how to write and accept a procurement FX and cross-border payment page. The usual gap is "currency/FX, FX/cross-border RMB, documents, bank charges, reconciliation, account-change fraud, sanctions/AML", ending with a page that only says "T/T payment", while procurement, finance and the bank disagree at payment/reconciliation/audit.
First set currency/FX: contract, invoice and settlement currency, FX source/date, conversion/tolerance. Then set channel/documents: T/T/L/C/cross-border RMB, real trade background, contract/invoice/BL/customs declaration, bank review. Finally set charges/reconciliation/risk: who bears bank charges, receipt/SWIFT/FX confirmation, account change/sanctions/AML. "T/T payment" is not enough.
How does this page relate to payment terms, imported equipment, customs/HS, budget and contract pages?
The FX/cross-border payment page answers "which currency, how to pay, how the FX rate is set, which documents/bank review, who bears charges, how to reconcile"; the payment-terms/settlement page answers "prepayment/credit terms/acceptance/invoice/overdue"; the imported-equipment page answers "selection/acceptance/installation"; the HS/tariff page answers "classification/customs value/declaration"; the budget page answers "limit/encumbrance/execution"; the contract page answers "price/payment/breach". Cross-border payment is a combination of "currency—channel—documents—bank—reconciliation—risk" and cannot be replaced by a payment-terms page.
Common breaks: contract/settlement currency mixed; FX source/date not stated; T/T and L/C charges unclear; cross-border RMB treated as foreign currency; documents missing; bank review/real trade background not stated; customs declaration/invoice/contract amounts mismatch; intermediary charges unclear; account-change fraud; sanctions/AML not screened; the website publishes accounts/amounts. The page separates "currency—channel—documents—charges—reconciliation—risk—public boundary" so procurement/finance/customs/legal share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| FX/cross-border payment | Currency/FX/channel/documents/charges/reconciliation/risk | Currency, FX, T/T/L/C, documents, charges, reconciliation | Payment-terms/customs page |
| Payment terms/settlement | Prepayment/credit/acceptance/invoice/overdue | Milestones, credit, acceptance, overdue | FX/cross-border |
| Imported equipment | Selection/acceptance/installation | Technical, acceptance, installation | Payment channel |
| HS/tariff | Classification/customs value/declaration | HS, customs value, origin | Payment |
| Budget | Limit/encumbrance/execution | Budget, encumbrance, variance | FX risk |
| Contract | Price/payment/breach | Amount, currency, payment, breach | Bank review |
Page relationships are editorial; FX rules, bank review, contracts and customs/tax practice control.
How should currency, FX rate and amount be accepted?
State: contract/invoice/settlement currency (may differ); amount (VAT-inclusive/exclusive, freight/insurance/commission); FX source (central parity/bank quotation/contract) and date (signing/invoice/payment/customs); conversion/decimal; FX lock/forward/option (if used); FX fluctuation sharing/adjustment; tolerance/rounding; accounting translation/ FX gain/loss. Cross-border RMB should state "priced/settled in RMB", not foreign-currency payment; foreign currency should state "purchase/settlement" arrangements. Do not just write "at the day's rate"; state which bank, which day, which rate.
Acceptance checks: currency; amount basis; FX source/date; conversion/decimals; lock/hedge; sharing/adjustment; tolerance; accounting; cross-border RMB/foreign currency. Common gaps: currency mixed; VAT/freight mixed; FX source not stated; date not stated; no lock; no sharing; rounding unclear.
| Element | What to write | Evidence | Common gap |
|---|---|---|---|
| Currency | Contract/invoice/settlement currency | Contract/invoice | Mixed |
| Amount | VAT/freight/insurance/commission | Contract/invoice | Basis mixed |
| FX source | Central parity/bank/contract | FX record | Not stated |
| FX date | Signing/invoice/payment/customs | Record | Not stated |
| Conversion/decimals | Conversion, decimals, rounding | Calculation | Unclear |
| Lock/hedge | Forward/option/natural hedge | Agreement | No lock |
| Sharing/adjustment | Fluctuation sharing/adjustment | Contract | No sharing |
| Cross-border RMB | RMB pricing/settlement | Contract/documents | Treated as FX |
Currency/FX is editorial; contracts, bank quotations and FX rules control.
How should payment channels and documents be accepted?
Channels: T/T, L/C, D/P, D/A, O/A, cross-border RMB, per contract/customer/bank rules; state issuing/advising/negotiating bank, document requirements, discrepancies, charges; cross-border RMB uses RMB settlement (no FX purchase/foreign-currency payment) but still needs real trade background/documents. Documents: contract, invoice, packing list, B/L/air waybill, customs declaration, certificate of origin, licence/3C/CE (by goods), insurance, inspection/photos; amounts/currency/quantity/description must match; banks review real trade background; the company must retain records. Do not assume "T/T needs no documents": bank/FX/tax/customs must reconcile.
Acceptance checks: channel; issuing/advising/negotiating; documents; discrepancies; charges; cross-border RMB; document consistency; real trade background; retention. Common gaps: unclear channel; missing documents; amount/currency mismatch; discrepancies not handled; cross-border RMB as FX; no retention.
| Channel/document | What to write | Evidence | Common gap |
|---|---|---|---|
| T/T | Remitting bank/account/remittance info/charges | Receipt/SWIFT | Unclear account |
| L/C | Issuing/advising/negotiation, documents, discrepancies | L/C/documents | Discrepancy |
| D/P, D/A | Collecting bank, documents, acceptance/payment | Collection documents | Unclear |
| O/A | Credit terms, credit insurance/factoring | Contract/policy | No protection |
| Cross-border RMB | RMB pricing/settlement, documents | Contract/receipt | Treated as FX |
| Document consistency | Contract/invoice/packing list/BL/customs | Document pack | Amount/currency mismatch |
| Real trade background | Contract/order/logistics/customs | Evidence | No retention |
Channels/documents are editorial; contracts, bank rules and FX/customs/tax rules control.
How should bank charges, reconciliation and evidence be accepted?
Charges: wire/message/intermediary/correspondent/issuance/advising/negotiation/acceptance/discrepancy/confirmation/inquiry fees, who bears (OUR/SHA/BEN or contract); FX spread/purchase cost; return/amendment/inquiry fees. Reconciliation: payment instruction, bank receipt/SWIFT, FX confirmation, invoice, contract, customs declaration, receipt/acceptance; amount/currency/date/reference/remittance info mapping; prepayment/balance/retention split; FX gain/loss. Evidence: bank receipt, SWIFT MT103/MT202, cross-border RMB receipt/payment statement, FX declaration/tax evidence (if applicable). Do not rely on a "bank debit screenshot".
Acceptance checks: charge items; bearer; spread; return/amendment; payment instruction; receipt/SWIFT; FX confirmation; invoice/contract/customs; split; FX gain/loss; evidence. Common gaps: unclear charges; intermediary deduction dispute; missing receipt; missing FX confirmation; unclear split; FX gain/loss not recorded.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Charge items | Wire/message/intermediary/issuance/negotiation/discrepancy | Contract/bank | Unclear |
| Bearer | OUR/SHA/BEN or contract | Contract | Dispute |
| Spread/purchase | FX spread, purchase cost | Quotation | Not stated |
| Return/amendment | Cost, responsibility, timing | Record | Unclear |
| Payment instruction | Amount/currency/account/remittance info | Instruction | Unclear info |
| Receipt/SWIFT | Reference, MT103/MT202 | Receipt | Missing |
| Reconciliation | Contract/invoice/customs/receipt/payment | Reconciliation | Mismatch |
| FX gain/loss | Translation/gain/loss | Voucher | Not recorded |
Charges/reconciliation is editorial; contracts, bank tariff and finance policy control.
How should fraud, sanctions and risk be accepted?
Risks: bank-account-change fraud (email/IM impersonating the supplier), account inconsistent with contract, high-risk countries/regions, sanctions/export controls, AML/CFT, sharp FX movement, bank failure/sanctions cut-off, forged documents, title/BL fraud. Controls: account-change call-back verification (known phone/video/in person), contract/order/invoice three-way check, dual review, bank-channel verification, sanctions/AML screening, insurance/L/C/confirmation, contingency plan. Do not change an account based on an email/WeChat alone; do not accept a "temporary account change" without verification.
Acceptance checks: account-change verification; dual review; sanctions/AML; high-risk countries; bank risk; document authenticity; insurance/confirmation; contingency. Common gaps: email account change; no call-back; single-person payment; no screening; no high-risk assessment; no contingency.
| Risk | Control | Evidence | Common gap |
|---|---|---|---|
| Account change | Call-back/video/in-person verification | Verification record | Email change |
| Account mismatch | Contract/order/invoice three-way check | Check record | No check |
| Sanctions/AML | Screening, lists, escalation | Screening record | No screening |
| High-risk country | Assessment, insurance/confirmation, approval | Assessment | No assessment |
| Bank risk | Bank rating, diversification, contingency | Record | No contingency |
| Document forgery | Verification, BL check, logistics reconciliation | Verification | No verification |
| Payment approval | Dual review, authority | Approval record | Single-person payment |
Risk controls are editorial; AML/sanctions/FX/bank and company policies control.
How should the website page be written, and what must not be published?
Suggested sections: (1) currency/FX principles; (2) payment channels/documents; (3) charges/reconciliation; (4) fraud/sanctions/risk; (5) contact/update date. The public page explains "principles, channels, documents, boundaries" and does not publish bank accounts/SWIFT, specific amounts/prices, suppliers/customers, FX quotations, payment instructions, documents, sanctions/AML records or pending disputes; specifics are handled in finance/customs/legal controlled systems. Do not claim "best FX rate/zero fees/any currency payable" if you cannot prove it or it would mislead; do not publish account/instruction templates that could be used for fraud.
The English page should use consistent terms (foreign exchange, FX rate, settlement currency, T/T, L/C, D/P, D/A, O/A, cross-border RMB, bank charges, SWIFT, sanctions, AML, account-change verification) and state the cut-off date. It can link to payment terms, imported equipment, HS/tariff, budget and contract pages, but must not become a "T/T payment" line.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Currency/FX | Contract/invoice/settlement currency, source/date | Contract/record | Mixed currency |
| Channel/documents | T/T/L/C/cross-border RMB, documents | Contract/documents | T/T only |
| Charges/reconciliation | Charge items/bearer, receipt/SWIFT | Contract/receipt | Unclear charges |
| Risk | Account change/sanctions/AML/high-risk | Record | No screening |
| Public boundary | No accounts/amounts/instructions | Permissions | Publish all |
The page structure is editorial; public statements must be true and verifiable, and FX/bank/customs/tax rules and contracts control.
Go-live acceptance checklist
Nine checks: currency/amount; FX source/date; channel/documents; cross-border RMB/foreign currency; charges/bearer; reconciliation/receipt/SWIFT; account change/sanctions/AML; FX gain/loss/accounting; public boundary. Each needs evidence and a review date. The pass standard is not "the page says T/T payment", but that procurement/finance/customs/legal can judge which currency, how the FX rate is set, which channel, which documents, who bears charges, how to reconcile and how to prevent fraud.
Before go-live, run a tabletop exercise with a real (redacted) cross-border purchase: contract currency → FX rate → channel → documents → bank review → payment → receipt → reconciliation → FX gain/loss. Then simulate "supplier changes account at short notice", "L/C discrepancy", "cross-border RMB/foreign currency mixed" and "intermediary charge dispute" to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Currency/amount | Contract/invoice/settlement currency, VAT/freight | Contract/invoice | Add basis |
| FX rate | Source/date/conversion/tolerance | Record/calculation | Add rule |
| Channel/documents | T/T/L/C/cross-border RMB, document consistency | Contract/documents | Add documents |
| Charges | Charge items/bearer/spread | Contract/bank | Add clause |
| Reconciliation | Receipt/SWIFT/FX confirmation/invoice/customs | Reconciliation | Add reconciliation |
| Account change | Call-back/video/in-person verification | Record | Add verification |
| Sanctions/AML | Screening/lists/escalation | Record | Add screening |
| FX gain/loss | Translation/gain/loss/voucher | Voucher | Record |
| Public boundary | No accounts/amounts/instructions | Page/permissions | Take down |
The acceptance list is editorial; FX/bank/customs/tax rules and contracts control.
Who should read it, who should not, and what decisions does it support?
For procurement, finance, customs, legal and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "currency/FX, T/T/L/C/cross-border RMB, documents, bank charges, reconciliation, account-change fraud, sanctions/AML". Not for teams that do not involve cross-border procurement/payment, or that want one page to replace FX/tax/legal advice.
Read it if: building a cross-border payment page; only "T/T payment"; currency mixed; FX not stated; documents missing; charges unclear; reconciliation mismatch; account change not verified; sanctions/AML not screened; the website publishes accounts. Not suitable if: treating "T/T" as "all channels"; treating "cross-border RMB" as "foreign currency"; treating "email account change" as "supplier notice"; treating "bank debit screenshot" as "reconciliation complete". Supports: currency/FX, channel/documents, charges/reconciliation, account change/sanctions/AML and public-boundary self-checks.
FAQ
Can contract, invoice and settlement currencies differ?
Yes, but state the conversion rule, FX source/date, tolerance and who bears FX gain/loss; contract/invoice/customs/payment amounts and currencies must reconcile. Cross-border RMB should state "priced/settled in RMB"; foreign currency should state purchase/payment arrangements. Do not just write "at the day's rate"; state which bank, which day, which rate (central parity/quotation/contract).
How to choose T/T, L/C, D/P, D/A or O/A?
Consider transaction amount, credit, country/bank risk, document capability, cost and financing: T/T is simple but credit-dependent; L/C provides bank credit but has higher fees/document requirements; D/P and D/A use bank collection but still carry buyer/bank risk; O/A is convenient but carries high seller risk, often with credit insurance/factoring. Cross-border RMB can reduce FX purchase/exposure but still requires real trade background/documents. Choose per contract, bank rules and risk tolerance.
How should FX risk be handled?
Options include natural hedging, contractual FX lock, forwards/options, FX sharing/adjustment; state source/date, lock ratio/term, sharing range, accounting translation/FX gain/loss. Do not promise "best rate/zero risk"; hedging has cost/margin/default risk, and follows the company's risk management and accounting policy.
Who bears bank charges?
The contract should state charge items (wire/message/intermediary/correspondent/issuance/advising/negotiation/acceptance/discrepancy/confirmation/inquiry) and the bearer (OUR/SHA/BEN or contract); intermediary deductions often cause "short receipt", so agree on top-up/bearing; return/amendment/inquiry fees too. Do not just write "bank charges borne by the seller" without listing items.
How to prevent supplier account-change fraud?
Account changes require call-back verification (known phone/video/in person, not the new number in the email), dual review, contract/order/invoice three-way check and bank-channel verification; do not change an account based on email/WeChat/new business card alone. Screen high-risk countries/sanctions/AML; escalate large/abnormal payments; keep verification records. Do not publish account/payment instruction templates on the website.
What is the difference between cross-border RMB and foreign-currency payment?
Cross-border RMB is priced/settled in RMB, reducing FX purchase/foreign-currency payment steps, but still requires real trade background, documents, bank review/declaration; foreign-currency payment involves FX purchase/rate/FX administration/bank review. Do not mix them; contract/invoice/receipt currencies must match. PBOC/FX rules and bank rules control.
Should the website publish bank accounts, FX rates and payment instructions?
Usually not bank accounts/SWIFT, specific amounts/prices, suppliers/customers, FX quotations, payment instructions, documents, sanctions/AML records or pending disputes. The public page can explain currency/FX principles, payment channels/documents, charges/reconciliation, account-change/sanctions/AML risk tips and a contact window; specifics are handled in finance/customs/legal controlled systems. Do not publish account/instruction templates that could be used for fraud.
One-sentence takeaway
The procurement FX and cross-border payment page on a Changzhou manufacturer's website is not about "T/T payment"; it is about turning currency/amount, FX source/date, payment channel/documents, cross-border RMB/foreign currency, bank charges/bearer, reconciliation/receipt/SWIFT, account change/sanctions/AML, FX gain/loss/accounting and public boundaries into a checkable list, so procurement/finance/customs/legal can judge which currency, how the FX rate is set, which channel, which documents, who bears charges, how to reconcile and how to prevent fraud.
Research method and limitations
This article is a summary of public rules and page method, not FX/tax/legal advice. It uses no unpublished bank accounts, amounts/prices, suppliers/customers, FX quotations, payment instructions, documents, sanctions/AML records or pending disputes; the tables and acceptance items are editorial and not FX/legal conclusions. The Foreign Exchange Administration Regulations; PBOC Notice Yin Fa [2018] No. 3; the Civil Code; FX rules, bank review, contracts and customs/tax practice control. This article does not decide whether any specific currency/FX/channel/charge is compliant or optimal, and does not promise the best FX rate/zero fees; companies should check item by item against the transaction, bank and risk.
Sources and basis
Current to 2026-11-09; the official pages below control.
- Foreign Exchange Administration Regulations of the People's Republic of China (State Council Order No. 532): Gov.cn. FX receipts/payments, purchase/settlement, bank review and supervision.
- PBOC Notice on Further Improving Cross-Border RMB Business and Promoting Trade and Investment Facilitation (Yin Fa [2018] No. 3): PBOC. Cross-border RMB settlement and trade/investment facilitation.
- Civil Code of the People's Republic of China: Supreme People's Court. Contract price, payment and breach.