SPEI payments explained: receiving MXN from Mexican clients

A Mexican client wants to pay your business in pesos and asks for a CLABE. Later, its finance team sends a tracking key and says the payment is complete.

What do those identifiers tell you? And how does a local peso payment become money your international business can use?

SPEI is Mexican interbank payment infrastructure. A supported collection arrangement can use it for the local MXN stage of a wider payment journey. The receiving account, allocation rules, conversion, and final payout remain separate parts of that journey.

This guide explains the payment terminology and shows how to keep the commercial invoice, local transfer, and eventual payout connected.

What is SPEI?

SPEI is the Interbank Electronic Payments System operated by Banco de México. It enables transfers between participating financial institutions. Customers access the service through their institution’s banking or payment channels. Banco de México: SPEI information.

For a business receiving payments, the relevant unit is MXN, the Mexican peso. If you invoice in USD but a customer pays locally in MXN, a conversion decision must happen somewhere in the commercial or financial process.

Do not describe that as “SPEI converts the invoice.” Identify the provider or agreement that determines the exchange rate and the peso amount. The payment system moves the resulting local payment; it does not settle every pricing question around the sale.

Understand CLABE, reference, and tracking key

The most useful first distinction is between the destination and the transaction.

Identifier	What it is used for
CLABE	An 18-digit standardised account identifier used for Mexican transfers
Beneficiary name	The intended account holder specified by the receiving instructions
Payment concept or reference	Commercial or allocation information accompanying the transfer
Clave de rastreo	A tracking key used to identify a SPEI transaction
Invoice number	The seller’s commercial record of the amount owed
CEP	Electronic payment confirmation associated with the completed transfer information

Banco de México explains CLABE and the available transfer identifiers in its public SPEI guidance. Its payment-information service also describes the tracking key provided by the sending institution. SPEI information module.

An invoice number is not a substitute for a CLABE, and the CLABE does not uniquely identify a particular invoice payment. Keeping the fields separate prevents a finance conversation from collapsing everything into “the reference.”

What a CLABE does not prove

A correctly formatted CLABE identifies an account destination under the relevant system. It does not establish that your service permits every payer or commercial purpose, that a business has completed onboarding, or that the account supports every other banking feature.

Use the exact CLABE issued by the bank or receiving service. Do not construct one from partial account data or replace it with a card number because another banking interface supports card-based lookup.

Check the beneficiary name and any required information alongside it. Where a provider uses account identifiers for payment allocation, follow its explanation of the underlying arrangement rather than presenting the account as something it is not.

If the client cannot enter the details in its chosen interface, resolve the mismatch with the institutions before sending. A workaround that merely passes the app’s validation can still be the wrong financial route.

Plan a local MXN collection flow

An international business needs to confirm the entire arrangement: who can pay, where the business is established, which provider can collect MXN for it, and which final payout destinations are available.

A fictional software agency might serve a company in Mexico that budgets in pesos. The client sends a permitted local SPEI payment using the issued instructions. The agency’s provider then identifies the receipt, applies the relevant checks, and offers the available conversion or payout options.

That example does not mean every international company can obtain Mexican receiving details. Eligibility and the legal structure of the service matter.

Before agreeing to the method, ask the provider to confirm whether registered-business payments, marketplace payments, and self-funding are treated differently. A route approved for your own funding should not automatically be advertised as a collection method for all customers.

Make the peso amount unambiguous

If the invoice is in MXN, state the amount clearly and check that the payment request matches it. Avoid a document that uses only a dollar sign without identifying the currency; that can be ambiguous in an international relationship.

If the invoice is in another currency, establish how the MXN amount will be calculated. Decide who obtains the quote, when it is fixed, how long it remains valid, and what happens if the customer pays a different amount.

A customer should not have to choose between the amount in an email, the amount in a converted PDF, and the amount on a payment page. Give them one current instruction tied to the commercial agreement.

Use explicit currency codes in cross-border communications: MXN 25,000 is clearer than an unexplained “$25,000.” Keep the original invoice currency and the actual payment currency separately in your records.

Prepare the instructions for the finance team

A useful MXN handover identifies the invoice, peso amount, permitted method, beneficiary, CLABE or other explicitly issued identifier, and required reference.

Do not append unrelated project text to a mandatory allocation code. If the service requires an exact value, preserve it and identify the invoice through separate remittance advice when necessary.

Ask the payer to confirm that its supplier record has been updated. Many business payments are generated from saved beneficiaries, so a correct email alone does not ensure the correct destination is selected.

If an account name or destination changes unexpectedly, verify the change through an established independent contact. The fuller payment handover guide explains how to control those updates.

Use CEP and tracking information appropriately

Banco de México provides tools to investigate SPEI payments and obtain a Comprobante Electrónico de Pago, or CEP, when the relevant confirmation information is available. Its guidance distinguishes payment status from the information needed to generate the CEP. Banco de México: Mi SPEI.

For your own workflow, a bank-generated confirmation is more useful than a cropped image saying “sent.” Keep the date, amount, sending and receiving institutions, destination, and tracking key.

A local payment confirmation does not necessarily answer what happened later inside an international provider’s review, conversion, or payout process. Identify the stage you are investigating before asking for more evidence.

Also protect the information. Use official banking and central-bank channels, and avoid entering transaction details into an unverified tracking website. A support enquiry should not require your online-banking password or one-time authentication code.

Reconcile a payment made in a different currency from the invoice

Cross-currency payment records need more than one amount.

Suppose a fictional invoice is USD 1,200. Under an agreed illustrative quote, the client pays MXN 21,600. The collection service deducts MXN 60, then converts the remainder at a fictional rate of 18 MXN per USD.

Record	Amount
Commercial invoice	USD 1,200
MXN payment sent	MXN 21,600
MXN after collection charge	MXN 21,540
Converted amount before any later fee	USD 1,196.67, rounded

The calculation explains the net result; it does not decide who owes the USD 3.33 difference. That depends on the agreement about fees and the supported quote.

Do not edit the original invoice amount simply to make it equal the net bank receipt. Preserve the commercial record and explain charges, conversion, and any outstanding balance separately. The reconciliation guide develops this approach for larger payment volumes.

MXN payouts are a separate capability

A provider may support paying pesos to eligible Mexican accounts even when it does not offer local MXN receiving details to every customer.

For an outgoing payout, verify the beneficiary, destination identifier, ownership or recipient requirements, and supported route. Do not assume that successfully collecting one SPEI payment automatically approves every future recipient.

If your provider offers both collection and payouts, maintain separate records for them. A customer paying your invoice and your business later withdrawing the proceeds are different events, not two independent sales.

When comparing routes, use the final amount received by the intended beneficiary and the total amount funded. Include conversion where needed and any known destination charges.

Troubleshoot the local leg before changing the wider route

Situation	Useful next question
Client cannot enter the destination	Is it using the supported payment method and exact identifier?
Payer has a tracking key but no receipt is visible	What status do the bank and official investigation tools show?
Required reference was omitted	Can the receiving service locate and allocate the existing transfer?
Local receipt is confirmed but payout is pending	What is the separate conversion or payout status?
The client paid a different MXN amount	Was the quote current, and what commercial balance remains?

Do not treat every delay as a failure of SPEI. The payment may not yet have been submitted, may require identification, or may have completed locally while another stage is pending.

Preserve the original transaction and investigate it before sending a replacement. If the destination may be wrong, contact the institutions promptly and ask about available recovery procedures without assuming success.

A practical setup checklist

Before using the flow with clients, confirm:

1. Your eligibility for local MXN collection or payout.
2. The accepted payer and transaction types.
3. The exact destination, beneficiary, and required reference.
4. The invoice currency and method for setting the MXN amount.
5. How to obtain and retain payment evidence.
6. How collection fees and conversion will be recorded.
7. Who handles an unmatched receipt, return, or delayed payout.

Test the internal recordkeeping process with a permitted transaction when appropriate. A technical success is useful only if you can also explain it in your invoice and payout records.

MXN through Ostro

Ostro’s available MXN receiving and payout options depend on activation, eligibility, jurisdiction, compliance review, supported routes, and licensed financial partner availability. Use the specific instructions shown in your workspace. This guide does not promise CLABE issuance or every SPEI use case to every customer. Receiving details and payout options explain the product context.

Frequently asked questions

Is SPEI the same as a CLABE?

No. SPEI is the payment system; CLABE is an account identifier that can be used for a transfer. A payment also has its own tracking information.

Can a foreign business collect payments in pesos?

Some providers support eligible arrangements. Verify the business jurisdiction, customer type, local collection route, and final destination before offering it.

Does a CEP prove my overseas payout is complete?

It relates to the local payment information. A separate international conversion or payout may have its own status and evidence.

Can I use MXN receiving details for another currency?

Only if the issuing provider explicitly supports that route. Do not assume that a valid account identifier permits unsupported currency transfers.

What should I ask a client when a payment is missing?

Request the actual date, MXN amount, destination, reference, method, and tracking key. Then compare those facts with the receiving instructions and provider status.

A clear Mexican-peso workflow keeps the local transfer evidence connected to the commercial agreement and the final destination. That is what makes a fast local payment useful in an international business.