Historical CEP and batch-check progress
A history import is an index, not downloaded or validated evidence. New batch checks may transfer money.
Instructions reviewed
Current workspace availability, quotes and permissions apply. The review date is not a live provider status. Reading help makes no checks or payments.
Before you start
- Use authorized internal MFA access and approved files. Inspect an existing queue without reimporting, resetting or replaying it.
Follow these steps
Open Products → Mexico account-name testing → Historical CEP. Read rows, unique accounts, originals, signatures and exact bindings separately.
You should see： Definitions and latest success are visible. All CSV rows imported is not backfill complete.
Inspect stage, access holds, next action and remaining accounts. Preserve uncertain submissions; do not increase concurrency or change IPs to evade holds.
You should see： Working, cooldown, reconciliation and authorization waits are distinct; no invented ETA.
Inspect user/account analysis. For a new Excel batch, use the separate batch page and preflight duplicates, supported accounts and costs; real execution needs authorization.
You should see： Analysis subjects are not automatically verified unique people; history reads and new transfers stay separate.
Completion check
You can explain remaining work and metrics without interrupting backfill.
If you get stuck
- Review/inconclusive: preserve evidence and inspect the reason; do not infer invalidity or replay permanently claimed XML.
Next steps and related guides
Unclear step? Report its location
Include the guide, step, visible message and expected outcome. Redact screenshots. Do not include codes, keys, identity documents, full accounts or customer records.
open@gridzen.ai