Parameters
Challenge
Our Fix
Invoices Submitted to DIAN One at a Time
Manually submitting each invoice for DIAN validation doesn't scale once shipment and billing volume grows.
CargoWise invoices submit to DIAN for validation automatically, with confirmation matched back to the originating job before issuance.
Multiple Document Types With Separate Requirements
Supporting documents and electronic payroll each carry their own validation rules, on top of standard invoices.
Supporting documents are mapped and submitted under the same automated framework as standard invoices.
An Invoice Is Not Valid Until DIAN Confirms It
Validation happens before legal issuance, not as a follow-up step, which makes reliable real-time submission essential.
Real-time submission keeps the invoice validation step from becoming a bottleneck in your billing process.
Invoice Formats Not Matching Between Systems
The invoice format CargoWise generates and the UBL XML structure DIAN expects are not automatically the same.
Field mapping keeps your CargoWise invoice and the submitted UBL version in sync, with a clear audit trail between the two.
Data Errors Reaching DIAN
Incorrect NIT, tax codes, or line-item details submitted in UBL format get rejected, or worse, accepted incorrectly.
Invoice data is validated against CargoWise records before submission, catching mismatches before they ever reach DIAN.