← Back to blog
Payments

SPEI Reconciliation Without the Headache: Match Payments to Invoices

November 12, 20264 min readIng. Humberto González

Stop losing hours to ambiguous bank transfers. Learn how to match each SPEI payment to its exact order, handle partial payments and returned transfers, and why auto-applying mystery deposits is a trap.

The Problem Every Business Faces with SPEI

You receive a SPEI transfer. The reference line says 'Pago' or a customer's name. You have fifteen open invoices. Which one is it? You message the customer. They don't reply for three days. Meanwhile, your accounting is stuck, your cash flow report is incomplete, and you've lost time you didn't have.

This isn't a small annoyance—it's a reconciliation bottleneck that compounds. Every ambiguous transfer creates manual work, delays collection follow-ups, and risks double-payment errors. I've watched businesses with clean operations spiral into chaos because they treated SPEI matching as 'figure it out later.'

The Right Way to Match SPEI to Orders

Matching works best when each payment identifies itself. Here's the hierarchy:

  • Invoice number in the reference: Cleanest. Customer sends 'INV-2024-0156' or similar. You match in seconds.
  • Order ID or internal code: Works if your customers know it and use it consistently. Often they don't.
  • Amount + date + customer ID: When reference is vague, this combination usually solves it. One customer, one amount, one date—usually one invoice.
  • Everything else requires a phone call. Don't auto-apply it.

The key rule: if the match is not obvious, stop. Ambiguous payments should go to a 'pending reconciliation' bucket, not your cash account. I know it feels slower, but it prevents the chaos of reversals and corrections later.

Partial Payments: The Trickier Case

A customer owes 10,000 MXN across two invoices (6,000 and 4,000). They send 5,000. Now what?

You need a process:

  1. Confirm with the customer which invoice the partial payment covers, or if it's split.
  2. Apply it to the invoice they confirm, not to your guess.
  3. Document the partial application clearly—many accounting systems let you do this, but some don't. If yours doesn't, note it in a memo field.
  4. Follow up on the remaining balance immediately. Partial payments are often a sign the customer is short on cash.

Don't assume a 5,000 transfer means 'apply half to each invoice.' That's a recipe for reconciliation hell.

Identical Amounts and Returned Transfers

Two invoices for exactly 8,500 MXN arrive on the same day. A customer sends 8,500. Which one did they pay? You don't know. Ask before you apply. Yes, it adds a step. Yes, it's worth it.

Returned or rejected transfers are their own nightmare. A SPEI bounces (bad CLABE, insufficient funds on their end, whatever). Your bank reports it. Now you have a 'ghost' payment in your inbox. Make sure your accounting system flags returned transfers separately. Don't re-apply them to cash until you've confirmed the customer has actually sent new funds.

The Complemento de Pago and Later Invoicing

Here's a scenario: a customer receives goods on credit, sends a SPEI weeks later, and you need to invoice them retroactively (or they invoice you). The complemento de pago (payment receipt in SAT terms) ties the payment to the invoice.

In practice: if you're using a modern invoicing system, the payment receipt should reference the original invoice number. If you're not invoicing until after payment, create the invoice first, then attach the payment record. Don't leave a payment orphaned. It will confuse your auditor and your future self.

Building a System That Doesn't Fail

If you're collecting SPEI payments manually, you need three things:

  1. A clear customer instruction: 'Put your invoice number in the reference, or we'll need to confirm it.'
  2. A pending bucket for ambiguous transfers—review it daily, not 'sometime.'
  3. A rule: never auto-apply a payment you can't trace.

Many businesses solve this by giving each customer a unique identifier—a fixed reference code or account number they use for every payment. This eliminates the guessing game entirely. FinaxaPay does this automatically: each customer gets a unique CLABE, so the moment the SPEI lands, you know exactly who sent it and which account or customer record it belongs to. No ambiguity, no manual matching, no pending bucket. The payment reconciles itself.

Stop chasing receipts. Build the system so receipts find you.

Let every transfer tell you who paid

A unique CLABE per customer: each deposit identifies itself and reconciles against its order or invoice, no screenshots needed.

Meet FinaxaPay →

You might also like