Skip to main content

Troubleshooting tax discrepancies

If a shipment sent as DDP (Delivered Duty Paid) still results in taxes or duties being charged to the recipient, there are several common causes to investigate. This article walks through how to identify and resolve them.

J
Written by Jemma O'Leary

1. Incorrect commercial invoice

The export/import terms on the commercial invoice must be set to DDP, not DAP. If the invoice shows DAP, carriers will treat the shipment as such and bill the recipient.

Fix: Check the commercial invoice and ensure the Incoterm is explicitly set to DDP.


2. Misconfigured connected platform

If you use a connected warehouse management system (WMS) or shipping platform (such as Dispatch Cloud), service mapping and export settings may not be applying DDP correctly on carrier documentation.

Fix: Confirm that your connected platform is configured to apply DDP on all outbound carrier documentation.


3. Carrier records not updated

The carrier's own system may not reflect the shipment as DDP — even if the invoice is correct. For example, FedEx records should show that duties and taxes are covered by the sender.

Fix: Verify the carrier record directly. Contact carrier support if there is a discrepancy.


Further verification

Use the Swap Global Dashboard to verify the breakdown of duties by product, country of origin, and HS code to check for any compliance issues.

Did this answer your question?