Parameters
Challenge
Our Fix
Authorisation Required Before Goods Can Move
Without a valid SEFAZ authorisation protocol on the NF-e, the shipment legally can't proceed.
CargoWise NF-e submissions authorise with SEFAZ automatically, with the protocol matched back to the originating job before dispatch.
Real-Time Authorisation Adds a Dependency
If SEFAZ integration isn't handled reliably, a failed or delayed authorisation response can hold up dispatch entirely.
Invoice data is validated against CargoWise records before submission, catching mismatches before they ever reach SEFAZ.
State-by-State Variation in SEFAZ Rules
Each state administers its own SEFAZ, and rules can differ enough to trip up a generic national approach.
Configuration accounts for the specific state SEFAZ rules relevant to your operations, not a one-size-fits-all national template.
Invoice Formats Not Matching Between Systems
The invoice format CargoWise generates and the XML structure SEFAZ requires are not automatically the same.
Field mapping keeps your CargoWise invoice and the submitted NF-e in sync, with a clear audit trail between the two.
CT-e Has to Reference the Underlying NF-e Correctly
A mismatch between the transport document and the goods invoice creates compliance and operational problems.
CT-e transport documents reference the correct underlying NF-e automatically, keeping goods and transport records aligned.