¿Qué cargo es ese en el estado de cuenta de tu tarjeta empresarial?

The best prevention is real-time visibility. With Clara, every transaction on your corporate card shows the full merchant name, tax ID, category, and location at the moment of purchase.

You set limits per card, per spending category, and per period, and receive automatic alerts for out-of-policy charges — including duplicate patterns. The result is zero surprises on your statement and full control over recurring SaaS expenses.

The legal window varies by country:

• Mexico: 90 calendar days from the statement date (CONDUSEF)
• Colombia: 3 calendar months from the statement (Superintendencia Financiera)
• Brazil: 60 calendar days from the statement close date (Banco Central do Brasil)

After this window, the bank is not obligated to process the dispute. On corporate cards with multiple holders, the CFO should centralize disputes to avoid missing the deadline.

Look for two identical entries in your statement: same merchant name, same amount, with an interval of seconds to two days. This happens because of the gateway's automatic retry when a first payment fails or takes too long to confirm.

If you confirm the duplicate:

1. Save a screenshot of the statement showing both charges.
2. Contact your bank within the dispute window.
3. Request the chargeback providing the authorization codes of both transactions.

Clara detects this pattern automatically and alerts the CFO before the billing cycle closes.

Foreign-currency charges on a corporate card are converted at the exchange rate on the processing date, plus a bank FX spread. In Mexico, the spread is typically 2–4% over the USD value. In Colombia, a GMF (financial transaction tax) of 4×1000 also applies. In Brazil, IOF of 4.38% is added. This is why the statement total is always slightly higher than the original USD price.

• The conversion uses the exchange rate on the processing date, not the purchase date.
• For subscriptions like AWS, OpenAI, GitHub, and Adobe, budget 5–8% above the dollar amount.

The asterisk separates the payment processor (gateway) code from the merchant name. For example: PEX*ADOBE is an Adobe purchase processed via PEX; GOOGLE*ADS is Google Ads; AMZN*AWS is Amazon Web Services.

The code before the asterisk identifies the gateway or payment platform; the code after identifies the vendor. These are legitimate transactions with the technical naming conventions of payment processing systems — they do not indicate fraud.

Follow these steps before disputing:

1. Search the exact name in the tool above — many statement codes are technical processor names, not brand names.
2. Check with other card holders at your company to see if anyone recognizes the expense.
3. Review active subscriptions under your company's tax ID — automatic SaaS renewals are the most common culprit.
4. If you still don't recognize it, contact your bank within the legal dispute window (90 days in MX · 3 months in CO · 60 days in BR).

With Clara, you see the full merchant name, tax ID, and category for every transaction in real time.

PEX* on your statement indicates a transaction processed via PEX Card, a US corporate prepaid card platform used to control team spending. It commonly appears on B2B software purchases, SaaS subscriptions, or international services. If your company uses PEX cards for expense management, this code identifies the charge origin. It is not a fraudulent charge.