SPEI, STP and collections: payment operations that do not pause recovery
If cash application lags, collectors sell the wrong balance. This is how Mexican payment rails should sit inside a collections and finance operating system.
Direct answer: Collections software without same-day cash application trains agents to argue with customers who already paid. In Mexico that argument happens on WhatsApp and becomes a CONDUSEF story.
Rails are not the product; posting is
SPEI, store networks and cards all fail the same way: money arrives, the reference is wrong or delayed, the screen still shows due. Fix posting, then brag about channels.
Operating rules:
- One live reference per account, rotated only with a documented reason
- Unapplied cash queue with an owner every morning
- Collector desktop shows as-of timestamp of last posting
Reconciliation as a factory
Bank files vs GL vs collections subledger. Auto-match on reference + amount + date; humans only see breaks. This is the same muscle as accounting close and fintech operations.
Do not pause recovery for a migration
When you change ERP or banks, dual-post for a window. The international books make this worse (two calendars, two rails). Plan the cutover like a plant shutdown, not an IT ticket.
Register for a rails-and-recon diagnostic.
Questions operators actually ask
What is a payment reference in collections?
A unique SPEI/CLABE or convenience-store reference that posts to one account. Shared references are how cash goes to unapplied hell.
How fast should cash hit the collector screen?
Same day for SPEI in a serious operation; next business morning is the outer SLA. Anything slower creates double-collect and complaints.
Do we need our own bank?
No. You need a treasury design: concentration accounts, named reconcilers, and exception queues. The bank is a rail, not the operating system.
Send an anonymised extract.
We return a recovery projection within five business days. No cost, no obligation to sign.
Register my company