Goal
Validate many transfers at once: you upload a file with their data — or photos of the receipts —, the platform reads every row and tells you which group it landed in, you fix what can be fixed, and you confirm the batch. From there the validations run in the background against Banxico's CEP, exactly as if you had submitted them one by one.
Prerequisites
- A signed-in session in the Veriko console.
- The transfer data, in one of two shapes:
- Text file — CSV, XLSX, XLS, TXT or JSON.
- Images — PNG, JPG or WEBP, loose or inside a ZIP.
- One batch at a time. If an import is already running, the next upload answers
422 import_already_in_flight: finish or cancel it first. - Enough monthly quota for every row in the batch. It is not checked on upload but on confirmation — see Quotas and plans.
Steps
1. Download the template (optional, recommended)
The template carries the canonical headers and three sample rows, and can be requested as csv, xlsx, xls, txt or json. The headers come out in your language, but that is only a convenience for whoever fills it in: the reader accepts Spanish and English headers interchangeably.
Using it saves you the free mode, which is less precise.
2. Upload the file
On upload you choose between two modes, and within the first, between two reads:
| Mode | What it does |
|---|---|
Text · template | Reads the file by its canonical headers. This is the precise path. |
Text · free | Line-by-line regular-expression sweep, with no escalation to AI. Useful for files that follow no structure, at the cost of precision. |
| Images | Every image goes through the same OCR and normalisation as a single receipt validation. If you select several, the server merges them into one batch. |
3. Wait for the read
The batch starts at pending, moves to parsing while the file is read, and reaches preview_ready once there is something to review. The console shows this as Analizando archivo… and advances on its own.
4. Review the four groups
Every row that was read lands in a group, and the preview lets you filter by them:
| Group | What it means |
|---|---|
| Valid | The row is complete and passes the local checks. It goes into the confirmation as is. |
| Correctable | A field is wrong, but you can fix it right here. |
| Fatal | Something is missing that the preview cannot supply. |
| Duplicate | The row clashes with another one in the same batch. |
5. Fix or drop rows
Editing a row runs the local checks again — CLABE checksum, valid date, amount greater than zero — and reassigns its group on its own: a correctable row that is properly fixed becomes valid without any further action. You can also delete a row from the batch; the counters update immediately.
Both are only allowed while the batch sits at preview_ready. Once confirmed, no longer.
6. Confirm the batch
Confirming dispatches every committable row. Before dispatching any of them, the platform adds the rows up and compares them against your available quota: if it falls short, not a single row is dispatched and the answer is 422 quota_insufficient. There are no half-run batches for quota reasons.
7. Follow the progress
Once confirmed, the batch moves to committing and then to completed. The execution counters add to the preview ones: dispatched, valid, not found, invalid, CEP unavailable, error and skipped. You can tick Avísame cuando termine and leave the tab.
8. Cancel, if you need to
Cancelling discards the rows that have not gone out yet. Those already in flight finish on their own, and the Banxico quota already spent is not refunded.
Next steps
- Review the results one by one: Inspect your validation history.
- Understand how rows are classified and what the two import domains share: Bulk imports.
- If you are loading beneficiary accounts rather than transfers: Bulk beneficiary import.