CVGo Daily Cycle
End-to-end walkthrough for processing one day of CVGo POS data — from receiving the ZIP files to a balanced, fully posted day.
Station accountants and collection clerks who run the daily CVGo workflow. Read this first; use the feature pages under Operations Reference for field-level detail.
When to run this
Once per business day, after the station has closed all shifts and CVGo has produced the day's XML export. Late files are handled the same way — the cycle is per-day, not per-clock.
Process map
Walkthrough
| # | Step | Where | You're done when... | Deep dive |
|---|---|---|---|---|
| 1 | Switch to the correct branch | Top-right company switcher | The active branch matches the station the ZIP came from | — |
| 2 | Upload the ZIP | Shell18 > CVGo > Upload XML Day Data | One CVGo POS Data record per file appears in the list | Upload |
| 3 | Validate | Open the CVGo POS Data record > Validate | Status moves to Validated; transactions, MOPs, and shift totals are visible on the record | Validate |
| 4 | Post | Same record > Post | Sales Orders, Invoices, Deliveries, and the auto-generated Payments exist and are linked back to the CVGo record | Post |
| 5 | Reconcile | Same record > Reconciliation tab | All MOP rows show a 0.00 variance against CVGo totals | Reconcile |
| 6 | Register manual payments (only for MOPs not auto-paid) | Customer invoice > Register Payment | Each non-auto MOP has a matching payment in Odoo | Register Payment |
| 7 | Close the day | CVGo POS Data record state | Record is Done and reconciliation variance is 0.00 | — |
Common exceptions
Duplicate file
Symptom: Upload fails with "File Hash already existing!". Why: The same ZIP was uploaded earlier — hashes are deduped on purpose. Fix: Search existing CVGo POS Data records by date and station; you almost certainly already have it. Do not rename the ZIP to bypass the check.
MOP mismatch at reconciliation
Symptom: Reconciliation tab shows a non-zero variance on one or more MOPs. Why: Most often a missing MOP-to-account mapping, or a manually voided transaction in Odoo that doesn't exist in CVGo. Fix:
- Confirm the MOP exists under MOP Accounts configuration.
- Check the linked Invoice/Payment hasn't been edited outside this workflow.
- If both look right, treat the variance as a station-side data issue and escalate before closing the day.
Missing product mapping
Symptom: Posting fails citing a product that can't be resolved. Why: A new SKU appeared in CVGo that hasn't been mapped in Odoo yet. Fix: Add the product under Partners and Products, then re-run Post on the record.
Re-run after a fix — what gets overwritten?
Re-running Validate is safe; re-running Post after a partial failure will create new SO/Invoice/Delivery records for the unprocessed transactions only — it does not duplicate already-posted ones. Never delete posted records manually to "retry"; use the cancel/reverse actions on the linked documents.
End-of-day checklist
- Every CVGo ZIP for the day is uploaded
- Every CVGo POS Data record is in Done state
- Reconciliation variance is 0.00 on every record
- Every non-auto MOP has a matching registered payment
- No "in progress" or "validated-but-not-posted" records left over
Related
- Reference: Upload, Validate, Post, Reconcile, Register Payment
- Configuration: MOP Accounts, Partners and Products
- Recovery: Troubleshooting