Skip to main content
Answer

Carrier Integration - Bill to Recipient Incorrectly Bills to 3rd Party

  • June 5, 2024
  • 10 replies
  • 205 views

When we bill a customer account, for some reason its showing as Bill 3rd Party on the label and a vendor just reached out letting us know they are getting hit with fees.

We've talked with Fedex multiple times. Fedex said it's some type of configuration in the back end of Acumatica causing this issue. We are sending to the responsible party. FedEx Support said it's being sent over as 3rd Party. 

FedEx support is unable to change it, said it has to be changed on the backend of the system: 


"The payment type is coming in the transaction and Acumatica needs to work with the Web Service hotline – 8773392774.   Thank you.

 

We've also had one of our devs look at it. His analysis:

From review of Acumatica source code, it looks like when the shipment Use Customer Account endorsement is set and the carrier billing type for the customer is Receiver, then the integration adds 'RECEIVER' as an attribute.  I don't have view into the Acumatica FedEX api, so I can't see exactly how everything is fed into the specific carrier service.

 

I can verify that the labels are being generated by the carrier marked as BILL THIRD PARTY, seemingly whenever the Use Customer Account endorsement is checked.  I also see BILL SENDER when this is not checked.  Keep in mind that I am spot-checking shipments, but I have not seen any FedEx labels marked as BILL RECIPIENT in the our system. 

We're wondering if this is a known issue with your Fedex API, and what are the steps we need to take to make sure that Fedex recognizes the Billing Type Receiver instead of incorrectly assigning Bill 3rd party.

We’ve also confirmed that this is also happening with UPS. This isn’t just a Fedex API issue.

Any thoughts or ideas?

Best answer by KellenReimers95

We passed this along to ACU Support, and they said that the fix for this was applied in 23R2. Because 22R2 is now sunsetted, we have been forced to upgrade mainly because of this issue.

10 replies

Forum|alt.badge.img
  • Freshman I
  • July 11, 2024

Were you able to find a solution ?


  • Author
  • Freshman II
  • Answer
  • July 16, 2024

We passed this along to ACU Support, and they said that the fix for this was applied in 23R2. Because 22R2 is now sunsetted, we have been forced to upgrade mainly because of this issue.


Forum|alt.badge.img+1
  • Semi-Pro II
  • September 15, 2025

We changed our UPS integration to UPSRest in 2024 R2 last week and are now having this issue. (We were previously using the EasyPost integration and Receiver and Third Party shipping was working correctly. Has anyone else seen this issue return?


Dana Moffat
Community Manager
Forum|alt.badge.img+2
  • Community Manager
  • September 18, 2025

Hi ​@alicezyks51,

Thank you for your post and for logging a support case with Acumatica.

I am reviewing your support case.

-Dana


Dana Moffat
Community Manager
Forum|alt.badge.img+2
  • Community Manager
  • September 30, 2025

Update: This issue is being resolved and is targeted to the next 24R2 update.


Forum|alt.badge.img+1
  • Semi-Pro II
  • October 3, 2025

@Dana Moffat While waiting for the UPS Rest issues to be resolved, we attempted to revert back to the EasyPost integration but selecting the EasyPost Carrier fails. We’ve had a case open for over two weeks but support has been unable to get us back on EasyPost. Has anyone else had this issue and more importantly were they able to resolve it? The case is:

[Case #468997] EasyPost Integration Error - Error: Unhandled exception has occurred, your changes have been rolled back: Method not found: 'System.Collections.Generic.List`1<PX.CarrierService.CarrierMethod> PX.EasyPostCarrier.EasyPostCarrier.G…

A couple additional notes:

  • Our test instance was never changed from EasyPost to UPS Rest and that integration is still working.
  • We’ve tried unpublishing all customizations and establishing the integration but it still fails.
  • Updating the existing UPS carrier and adding a new UPS carrier both fail.

Any suggestions would be appreciated. Thanks!


Dana Moffat
Community Manager
Forum|alt.badge.img+2
  • Community Manager
  • October 3, 2025

Hi ​@alicezyks51 thank you for your post.  I will review the Support Case.


Dana Moffat
Community Manager
Forum|alt.badge.img+2
  • Community Manager
  • October 3, 2025

Hi ​@alicezyks51 support will be reaching out to you quite soon with a resolution.  I have escalated this case.

-Dana


Forum|alt.badge.img+1
  • Semi-Pro II
  • October 3, 2025

@Dana Moffat This issue is resolved.

Per support the issue was from a published hotfix customization (needed to fix AC-308380) related to Known issue: In some cases, if EasyPost was selected as the carrier provider, the system displayed the "Carrier service returned error: UPS: Error converting value {null} to type 'System.Boolean'" error upon shipment confirmation. Needed to unpublish since no longer needed on our current version. Once that was done, support did DLL restoration and we republished our other customizations. Connected to EasyPost with no further issues.

Thanks for your help on this.


Dana Moffat
Community Manager
Forum|alt.badge.img+2
  • Community Manager
  • October 3, 2025

You’re welcome ​@alicezyks51.  Thanks for letting me know.