How do I dispute charges with UPS?

Learn how to dispute UPS charges.

The steps below outline how to dispute charges with UPS:

  1. Log in to ups.com
  2. On the Quick Start menu, select View & Pay Bill.
  3. Select UPS Billing Center.
  4. Click Reporting → Search.
  5. Select the Tracking Number Detail option.
  6. Click on the invoice number.
  7. Click Download Documents.
  8. Paste the tracking number in the Supporting Documents section in the search field.
  9. Click on the appropriate tracking number hyperlink, which will open the details of that import shipment.
  10. Select Brokerage Forms at the bottom of the screen.
  11. Select Dispute at the bottom right of the screen to open a new window where you can enter the details of the dispute.
  12. Enter an appropriate description of the dispute and hit Continue. (WARNING: The description only allows for 80 characters).
  13. On the following screen, enter the dollar amount of your dispute (the amount that you believe was in error).
  14. Hit Continue and verify all the applicable pop-ups alerts to submit the dispute.

FAQ

How long do dispute refunds take?

The process will typically take months depending on the country and carrier. Learn how to avoid this headache with Zonos Landed Cost Guarantee!

Why would I need Landed Cost Guarantee of Zonos is so accurate?

Once the package is shipped off, there are a lot of uncontrollable variables:

  • A customs agent may decide to reassign your package’s description or HS code because they don’t agree with what was originally there, which could change the total landed cost.
  • Additional and unexpected fees or events could take place i.e. supply chain issues, storage, or government fees. 
  • Humans aren’t perfect, so it could be due to human error.
  • Incomplete or incorrect HS codes could have been assigned to your products.

Still have questions?

View our additional documentation on how to dispute UPS charges.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.