Managing the distribution of goods.
After three cups of coffee and a highlighter, I reconstructed the actual workflow from the scattered data in the PDF. Here is the "Reader's Digest" version of Manual de Uso do COLOGA: Manual de Uso do COLOGA.pdf
Reading the PDF is like using a map where the legend is in the back, upside down. Here are the three things the manual implies but never states clearly: Managing the distribution of goods
1. The XML is the King, the PDF is the Witness
The manual obsesses over generating the PDF of the COLOGA, but the real action is in the XML. If your XML schema doesn’t match the SEFAZ standard (a specific tag in the transporte block), the manual won't help you; the system will just reject your file with a vague "Erro crítico." Picking List (Separação):
2. "Evento" vs. "Documento" This is the chapter everyone misreads. The manual explains that you send an Evento (a correction, a cancellation) and a Documento (the original freight note). But in practice, you must wait 24 hours between the two. The PDF buries this latency requirement in a footnote on page 112. If you try to cancel a note too fast, the system ghosts you.
3. The 'Weight Paradox' There is a beautiful flow chart on page 78 showing how to input vehicle tare weight. What the manual doesn't say is that if your tare weight varies by more than 5% from the previous registration, the system will block your CNPJ. You need a scale ticket dated that day. This is not in the main text; it is in the "Erros Comuns" appendix.