Active modules
Stamping
CargoWise accounting documents → fiscal checks → Facturapi CFDI → artifacts back to CargoWise.
Analytics
Org-scoped reporting Postgres for SQL, Power BI, and curated views.
Stamping
The core product. Income invoices, payment complements (REPs), credits, and cancellations enter through Lambda ingress, reconcile against SAT rules, stamp when eligible, and return XML/PDF to CargoWise when outbound is configured. You work this module from the invoice workspace: statuses, notes, timelines, and the next safe action when Lambda offers one. Retry and recovery live inside stamping — they are not a separate module. Start with Stamping overview and How stamping works.Analytics
Long-term reporting storage for your organization. You get a dedicated Postgres database with a stablereporting schema, curated business tables, and credentials you create in Lambda.
Analytics does not store invoices, Facturapi responses, or SAT artifacts. Stamping owns fiscal evidence; Analytics owns reporting visibility.
Start with Analytics overview and Connect.
Shared platform services
These surfaces are always part of Lambda. They support the modules above rather than replacing them.Ingress is acceptance, not completion
When CargoWise pushes a document, Lambda ingress returns acceptance after the capture is saved and work is queued. CargoWise treats that as delivered. The stamp may still be Received or Processing in the invoice workspace — check there if a document seems stuck.Outbound is separate from stamped
A CFDI can be issued while CargoWise delivery is still retrying. Stamp success and outbound delivery are different outcomes.Workspace map
Settings → CargoWise configures enterprise/server IDs, ingress auth, and outbound. Settings → Stamping / Analytics hold each module’s credentials and options.
Next
- AI-native — how assistants participate inside these modules
- Stamping overview — CFDI path and workspace statuses
- Analytics overview — reporting Postgres