Argentina in River Plate Spanish; the rest in neutral Spanish; English for everyone else.
Each of your customers has their own personal account, in your company's name. When they transfer, the payment is detected instantly and attributed to that person —even if someone else pays—; whoever needs to know gets an alert and the reminders stop. If your management system is connected, the payment goes into your system on its own.
Nobody checks the bank or enters anything by hand. And in the afternoon, the report balances to the cent.
Payments received
Validated today
Laura Gómez · N° 4127
US$5.33 · validated · transaction 7F3A-91C2
Marcelo Ríos · N° 2210
US$10.27 · validated · paid by their son
Andrea Paz · N° 3381
US$4.13 · applied in your system
Ricardo Sosa · N° 1904
US$6.60 · validated · driver alerted
No clear owner
US$2.67 · administration reviews it
Nora Vidal · N° 2876
US$14.00 · validated · reminders stopped
Pablo Ledesma · N° 3015
US$5.00 · reported to your system
Five steps, in the order they happen. The money goes straight to your account: Cobratia detects the payment and attributes it, but the money doesn't pass through us.
One personal account per customer, in your company's name: in Argentina, their own CVU and alias. Their alias is shared with them by your team, your drivers, the assistant and their app.
They transfer to their personal account from whatever bank or wallet they use, at any hour.
The payment arrives with the customer already in it: no need to figure out whose it was. It's validated with its transaction code.
To the driver on that route, to administration, to whoever you choose. And nobody asks for money again from someone who already paid.
If your management system is connected, the payment is reported to it and confirmed once applied. The balance goes down where you've always kept it.
The moment the payment is validated, the alert reaches whoever needs to know: the driver on that route, administration, the supervisor. Each on their own channel —WhatsApp, Telegram or email—, and if your management system has a delivery app and it's connected, right there, in the app the driver already uses.
Each payment gets its own alert: if the same customer pays twice in a day, two go out. And if an alert didn't go out, it stays in view with the reason.
Your customer can also get a confirmation —"we received your transfer"—, and the assistant, if you have it, already knows they paid: it doesn't ask them for money again or send them the payment details, even if your system hasn't deducted it yet.
If your management system is connected —today, Gestión Aguas / AIRTECH—, Cobratia reports each payment as just another payment, with its payment method, and your system posts it. The balance goes down where you've always kept it: your system remains the source of truth.
Each payment goes through three statuses you see in the panel: pending, reported and applied. During the day, every half hour, Cobratia checks your system and confirms the ones already applied, without waiting for the night. And if you don't want to wait, the "Sync with your ERP" button does it on the spot.
The path goes the other way too: when a new customer comes in, their personal account is opened and their alias reaches their record in your system, so your team and your drivers have it at hand.
Use a different system? We review its API before promising anything. See integrations →
Payments received
Payments reported to your system
Laura Gómez · US$5.33
✓ Applied in your system · receipt 1532
Pablo Ledesma · US$5.00
Reported · waiting for your system to pick it up
Nora Vidal · US$14.00
✓ Applied in your system · receipt 1529
Marcelo Ríos · US$10.27
✓ Applied in your system · receipt 1527
Ricardo Sosa · US$6.60
Pending · goes out in the next send
Andrea Paz · US$4.13
✓ Applied in your system · receipt 1524
What Cobratia recorded and what your management system says are cross-checked on their own. These are the controls that make the number trustworthy.
A charge is marked as paid when the payment provider confirms it. A receipt photo isn't enough: the assistant reads it and leaves it ready for a person to validate.
If the bank's notice arrives twice, the payment is recorded once. And if the same customer pays twice on the same day, that's two alerts: each payment gets its own.
If the amount doesn't match or it's unclear whose it is, nobody marks it as paid: it goes to administration to decide.
Even if your system hasn't deducted it yet, the assistant knows they paid and doesn't send them the payment details again.
In Payments received, each payment with its number in your system and a box comparing it with your treasury. If one goes two business days without being applied, you get an email.
Every morning we cross-check payments with the payment provider and with your system. Whatever doesn't match, we look into it, with its reason, before you hear about it from a customer.
A payment shows as applied in your system only when it appears there with the exact mark Cobratia left, for the full amount sent.
Real numbers from the companies that use validation, added up and without naming any. They update themselves.
Each customer with their own CVU and alias, in your company's name.
Each customer with their CLABE, generated in your company's name.
Pago Móvil or bank transfer, confirmed against the bank.
What people ask us most before getting started. If something's missing, write to us and we'll answer it.
No. Your customers' personal accounts are opened in your company's name and the money goes straight to your account. Cobratia detects the payment, attributes it to the right customer and sends the alert: it never touches it.
It's still attributed to the right customer: the payment is recognized by the account it went into, not by the name of whoever transfers. If the husband, the son or the accountant pays, the payment belongs to that customer.
No. It works whatever system you have, or none. If we connect it, the payment goes into your system and your system keeps tracking the debt; if we don't, Cobratia keeps the account.
It doesn't touch it directly: it reports the payment to your system, as just another payment, and your system posts it. Cobratia then confirms it was applied. The balance is still kept by your system, which is the source of truth.
That payment isn't detected on its own, because there's no way to know whose it is. If they send the receipt, the assistant reads it —amount and date— and leaves it ready for someone on your team to validate.
An alert with the customer, their number, the route, how much they paid and the transaction code, through the channel they use: WhatsApp, Telegram, email or your management system's delivery app, if it's connected.
In Argentina, with each customer's own CVU and alias; in Mexico, with their CLABE; and in Venezuela, with Pago Móvil or bank transfer, which are confirmed against the bank.
Yes, it's one of the packages. The rest of Cobratia you see with a lock and add whenever you want: with collections, reminders stop on their own when the customer pays; with the assistant, it confirms the payment in the conversation.
Transfer, deposit, cash on the route: tell us how you collect and what system you use, and we'll show you how each payment would be validated on its own.
Validation is one of the eight modules. These are the ones most often added to it.