Cross-Border Payment Compliance for Exporters Selling into the Philippines (2026)

2026-10-18 12:00:00

I run payments and finance for a Singapore-registered company that sells industrial consumables and a subscription software product to customers in the Philippines. For the first year we collected in pesos through a local reseller and received whatever was left after the reseller took a cut, converted at a rate we never saw. When we moved to collecting directly, the hard part was not the integration. It was understanding which rules apply when money is collected inside the Philippines by a company that is not Philippine, and how that money legally leaves the country. This article is the compliance map I wish I had: who may hold the pesos, what the bank will ask for when you convert and remit, where tax attaches, what anti-money-laundering and data rules reach your business, and how to build the paper trail into your payment integration from day one. The entity and API side of the same journey is covered in Payment Gateway Integration for Global Merchants; this piece stays on compliance.

Two Directions, Two Rulebooks

"Cross-border payment compliance for exporters" means different things depending on which way the goods travel. Both directions matter, and they are regulated differently:

Foreign exporter selling into the Philippines. You ship goods or deliver digital services to Philippine buyers, collect in pesos, and need to move the proceeds out. The questions are about who may collect on your behalf, how pesos are converted to foreign currency, what documents a bank needs to remit them, and whether Philippine tax attaches to the sale.
Philippine exporter selling abroad. A Philippine-registered company receives foreign currency from overseas buyers. The questions are about how export proceeds may be received and held, whether they must be converted, and how the receipt is documented for tax and customs.

Most of this article is written for the first direction because that is where foreign businesses get stuck. The second direction gets its own section further down. In both cases the central reference is the Bangko Sentral ng Pilipinas (BSP) Manual of Regulations on Foreign Exchange Transactions, usually called the FX Manual, which sets the documentary requirements for banks that sell foreign currency or receive it on a client's behalf.

Who Can Legally Collect and Move the Money

The Philippines regulates payments by entity type, and a foreign company has to work through entities that hold the right authorisation at each step:

Collection inside the Philippines from wallets, QR Ph and bank transfers must run through a BSP-supervised participant: a bank, an Electronic Money Issuer (EMI) or a registered Operator of Payment System (OPS). An unregistered intermediary that "collects for you" into a personal account is not a shortcut; it is a compliance failure for both of you.
Conversion of pesos to foreign currency is done by BSP-authorised agent banks and, for smaller amounts and specific purposes, by registered money service businesses. Banks are the only path for trade-related outward remittance at any meaningful scale.
Outward remittance goes through the banking system under the FX Manual. The bank, not you, is the regulated party, which is exactly why it will ask you for documents: it must be able to show the regulator why it sold you foreign currency.

Practically, a foreign exporter has three ways to structure the chain. Each puts the pesos in different hands and carries a different compliance load:

Path	Who holds the pesos	Documents the chain needs	Compliance burden on you	Best for
Local subsidiary or branch with its own bank account	Your Philippine entity	SEC registration, BIR registration, invoices, contracts, board approvals for remittance, tax clearance where applicable	Highest: full Philippine entity obligations	Exporters with local staff, inventory or long-term presence
Licensed payment gateway collecting on your behalf with cross-border settlement	The licensed EMI or OPS, in segregated client funds	Your corporate KYB documents, product descriptions, invoice and order data per transaction, settlement instructions to your foreign account	Medium: you supply documentation, the licensed entity handles conversion and reporting	Most exporters without a local entity
Marketplace or merchant-of-record	The platform, which is the legal seller	Platform onboarding only; the platform invoices the buyer	Lowest, but you lose pricing control and pay the platform's margin	Testing the market or low volumes

SMARTPAY holds both OPS and EMI authorisations from the BSP. For foreign exporters that means peso collection happens inside a licensed, supervised entity, and cross-border settlement to your overseas account is executed through authorised banking channels with the transaction-level documentation the FX Manual requires. The compliance obligations do not disappear, but they are carried by the party licensed to carry them.

What the Bank Will Ask For Before Remitting

Whether the remitting party is your own subsidiary or the licensed gateway settling to you, a bank selling foreign currency for a trade purpose will want to see a coherent story linking the pesos to a legitimate sale. In our experience the file needs to contain:

Proof of the underlying transaction: commercial invoices, order confirmations or subscription agreements, and for goods the shipping documents or customs entries. For digital services, a service agreement plus usage or delivery logs.
Proof of the payer: the buyer's name and, for business buyers, registration details. Wallet and QR payments give you a reference number and a masked payer identity; your order system has to tie that reference to a buyer record.
Proof of the beneficiary: your foreign company's registration, bank account ownership and, increasingly, beneficial ownership information. Banks screen the beneficiary against sanctions lists.
Purpose declaration: outward remittances carry a purpose classification. Payment for imported goods, payment for services, and repatriation of a subsidiary's earnings are different purposes with different supporting documents.
Tax evidence where the purpose requires it: for some purposes banks ask for proof that applicable Philippine taxes were withheld or paid before foreign currency is released.

The FX Manual sets documentary thresholds that change over time, so do not hard-code them. Design your process so that every transaction already carries the data needed for the strictest case, and let the licensed party decide what to present.

Where Philippine Tax Touches a Foreign Exporter

Payments compliance and tax compliance are different departments, but the bank and the regulator treat them as one story. The touchpoints that affect a foreign exporter:

VAT on digital services. Philippine law now requires non-resident digital service providers selling to Philippine consumers to register with the Bureau of Internal Revenue (BIR) and account for VAT on those sales. Whether you sell software subscriptions, streaming, online courses or marketplace services, check whether you fall within scope and whether business buyers self-account under a reverse-charge style mechanism instead.
Withholding on payments to non-residents. When a Philippine business pays a foreign company for services, the payer may be required to withhold tax at source and remit it to the BIR. Your invoices and your B2B customers' finance teams need to agree on this before the first payment, or your settlement will arrive short and nobody will know why.
Import duties and VAT on goods. Collected by customs from the importer of record. If you sell delivered-duty-paid, the duty becomes your cost and your customs broker's paperwork becomes part of your payment file.
Permanent establishment risk. A local warehouse, dependent sales staff or a reseller acting as your agent can create a taxable presence. This is a question for tax counsel, but your payment structure is evidence either way.
Invoicing and e-invoicing. Philippine buyers, especially businesses, will ask for a document they can book. If you have a local entity, BIR invoicing and the electronic invoicing rollout apply to you. The record-keeping side is covered in Payment Records and Tax Reporting for Philippines E-commerce Merchants.

None of these taxes are collected by your payment provider on your behalf unless your contract says so. What the provider can do is give you settlement reports with transaction-level data that make the tax filings possible.

Anti-Money-Laundering, Sanctions and Data Protection

The Anti-Money Laundering Act (AMLA) makes banks, EMIs and OPS "covered persons" with obligations to know their customers, monitor transactions and report suspicious activity. You, the exporter, are the customer being known. Expect to provide and periodically refresh:

Corporate registration, directors and beneficial owners, with identity documents;
A description of what you sell, to whom, in what volumes, and through which channels, so that the provider can set a transaction profile and detect deviations;
Explanations for unusual patterns: a spike in refunds, a cluster of payers in one location, large round-number transactions.

Sanctions screening runs in both directions: the licensed provider screens you and your settlement bank, and the remitting bank screens the beneficiary account. Keep your corporate structure transparent; opaque ownership is the most common reason onboarding stalls.

Data protection is the third leg. The Data Privacy Act applies to personal data of Philippine buyers that you process, including when it leaves the country. Collect only what the transaction needs, document the lawful basis, protect it in transit and at rest, and be prepared to honour access and deletion requests. Payment references, masked wallet numbers and delivery addresses are all personal data.

Building the Compliance Trail into the Integration

The cheapest compliance is the kind that is captured automatically at the moment of sale. We treat every payment request as the first page of the remittance file. Concretely, each payment carries structured metadata that later becomes evidence, and each settlement report is stored unaltered alongside our own ledger.

// Create a payment with the metadata that the remittance file will later need.
// Field names follow the gateway's documentation; the point is what you capture, not the exact keys.
const payload = {
  merchant_order_id: 'INV-2026-004731',
  amount: invoice.totalMinorUnits,          // integer in minor units, per gateway docs
  currency: 'PHP',
  channel: 'qrph',                          // or 'gcash', 'maya', 'instapay'
  metadata: {
    invoice_number: 'INV-2026-004731',
    invoice_date: '2026-10-18',
    goods_or_services: 'services',          // drives purpose classification later
    hs_code_or_service_desc: 'SaaS subscription, annual, 10 seats',
    buyer_type: 'business',                 // 'business' or 'consumer' matters for VAT treatment
    buyer_tin_provided: true,
    contract_ref: 'MSA-2025-PH-017',
    delivery_evidence_uri: 's3://exports/INV-2026-004731/delivery.json',
  },
  callback_url: 'https://api.example.com/payments/webhook',
};

const res = await fetch('https://api.example-gateway.com/v1/payments', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Bearer ${process.env.GW_TOKEN}`,
    'Idempotency-Key': `pay-${payload.merchant_order_id}`,
  },
  body: JSON.stringify(payload),
});
const payment = await res.json();
await db.payments.insert({ ...payment, metadata: payload.metadata, raw_response: payment });

When funds are settled cross-border, the settlement instruction carries the purpose and a pointer to the documents. Keeping the pointer, not the documents, in the API call keeps personal data out of logs:

curl -X POST https://api.example-gateway.com/v1/settlements/cross-border \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $GW_TOKEN" \
  -H "Idempotency-Key: settle-2026-10-W42" \
  -d '{
        "period": { "from": "2026-10-12", "to": "2026-10-18" },
        "beneficiary_account_id": "BENE-SG-0001",
        "purpose": "payment_for_services",
        "supporting_documents": [
          { "type": "invoice_batch", "uri": "s3://exports/settlements/2026-W42/invoices.csv" },
          { "type": "service_delivery_log", "uri": "s3://exports/settlements/2026-W42/delivery.csv" }
        ],
        "notes": "Weekly settlement of SaaS subscription receipts, B2B and B2C split in invoice batch"
      }'

The data model that makes this work is small but has to be enforced at the point of sale:

Field	Why compliance needs it	Where it comes from
Invoice number and date	Links the peso receipt to a documented sale for FX and tax purposes	Your billing system, before payment is created
Goods vs services, with description	Determines remittance purpose and tax treatment	Product catalogue
Buyer type and tax identifier	Separates consumer VAT from business reverse-charge or withholding	Checkout or account profile
Payment channel reference	Ties the settlement line to the buyer's payment for reconciliation and disputes	Gateway response and webhook
Delivery or usage evidence	Proves performance of the sale if the bank or regulator asks	Logistics or service platform
Settlement report, unaltered	Primary evidence of amounts, fees and FX applied	Gateway settlement API

Settlement timing choices, including same-day settlement into a Philippine account before cross-border transfer, are discussed in D0 Same-Day Settlement in the Philippines. If you also pay Philippine suppliers or contractors from your collections, the disbursement side has its own documentation rules; see Batch Payout in the Philippines and GCash Payout for Overseas Companies Without a Local Bank Account.

The Other Direction: Philippine Exporters Receiving Foreign Currency

If you are a Philippine-registered exporter, the FX Manual is on your side in most respects. Export proceeds may be received in foreign currency and held in foreign currency deposit accounts with Philippine banks; conversion to pesos is your choice, not an obligation, within the rules your bank applies. What you must keep straight:

Export documents (invoices, bills of lading, customs export declarations) matched to inward remittances, because your bank reports and may ask;
VAT treatment of export sales, which generally differs from domestic sales and requires documentary support to claim;
Receiving through overseas platforms or foreign payment providers, which is lawful but still has to be booked and documented as export revenue when it lands.

Philippine exporters who also sell domestically often run both flows through one licensed provider so that peso collection and foreign currency receipt land in one set of reports.

Mistakes That Cost Exporters Months

Collecting into an individual's wallet or bank account "temporarily". It breaks the documentary chain, creates tax exposure for the individual and is the fastest way to get an account frozen.
Using an unlicensed agent to collect and remit. The agent cannot lawfully hold client funds and cannot give a bank the documents it needs; when the agent's account is frozen your money is inside it.
Treating marketplace or platform payouts as already compliant. The platform's compliance covers the platform. Your income still has to be declared where you are tax resident, and possibly in the Philippines.
Missing or generic invoices. A receipt that says "payment" with no description cannot support an FX purpose or a VAT position.
Mixing B2B and B2C without a flag. They have different VAT and withholding treatment; if your data cannot separate them, your tax position is guesswork.
Converting through informal channels to get a better rate. Beyond the legal exposure, the resulting funds have no documented origin when they reach your home bank.

Frequently Asked Questions

Do I need a Philippine company to collect pesos from Philippine customers?

No. A licensed payment provider can collect on behalf of a foreign company and settle cross-border, provided your company passes KYB and your products are permitted. A local entity becomes advisable when you hold inventory, employ staff or want to invoice locally.

Can the provider convert pesos and send me foreign currency directly?

A licensed EMI or OPS arranges conversion and remittance through authorised banks; it does not act as the foreign exchange dealer itself. Your contract should state the settlement currency, the rate reference and the documents you must supply.

Is VAT on digital services my problem if I sell only to businesses?

Business buyers may self-account under the rules for non-resident providers, but you still need to identify them as businesses and keep evidence. Confirm the mechanism with Philippine tax counsel; the rules distinguish consumers from VAT-registered businesses.

What happens if a Philippine customer withholds tax from my invoice?

You receive less than invoiced, and the customer should give you a withholding certificate. Depending on a tax treaty between the Philippines and your country, you may be able to claim relief or a credit at home. Build this into your B2B pricing and contracts.

How long should I keep payment and remittance records?

Keep them for the longest period required by any of the applicable regimes: Philippine tax rules, your home jurisdiction's tax and company law, and your provider's AML retention requirements. In practice that means years, not months, and in a form that can be produced on request.

Does cryptocurrency or stablecoin settlement avoid these rules?

No. Virtual asset service providers in the Philippines are BSP-regulated, and converting pesos to a stablecoin for the purpose of moving value abroad is still a cross-border transfer in the eyes of the AML and tax rules. It also complicates your documentary trail rather than simplifying it.

What is the single most useful thing to prepare before onboarding?

A one-page description of your business: what you sell, to whom, expected volumes, channels, your corporate structure with beneficial owners, and your settlement account. Every licensed provider and every bank in the chain will ask for the same thing.

Where to Start

Treat compliance as a data problem with a legal wrapper. Decide which of the three structures fits your presence in the Philippines, pick a licensed partner whose authorisations you can verify (the licensing landscape is explained in BSP Licensing Requirements for Payment Service Providers), and build invoice, buyer-type and delivery evidence into every payment from the first transaction. If you are planning to sell into the Philippines or want to regularise an existing flow, reach out on Telegram at @LouisSMARTPAY or by email at [email protected].