Skip to main content
Solved

Charged quantity is higher than the invoiced quantity

  • September 2, 2024
  • 3 replies
  • 47 views

Forum|alt.badge.img+3

Hi All,

Getting the below error when matching the receipts in a manual supplier invoice.

 

Checked the following windows.

Purchase order part lines tab.

 

Purchase Order Charges tab.

 

Purchase Order matching window.

 

The receipt quantity is shown as 2 for the charges.

Is there any reason for that to happen?

 

Thank you.

Kind regards,

NishaniF

Best answer by Chanu_Yazi

NishaniF wrote:

Hi @Chanu_Yazi 

Thank you very much for your reply.

I have not been able to reproduce this in the test environment. However, there are 3 POs with this same error.

Kind regards,

NishaniF

 

Hi @NishaniF 

I believe solving this may require a data repair.

 

I'm happy to share my advice on this. If you found the answer helpful, please mark it as the correct answer. This will allow us to close the thread and make it easier for other community users to find and benefit from in the future.
 

BR.

Chanuka

View original
Did this topic help you find an answer to your question?

3 replies

Chanu_Yazi
Hero (Partner)
Forum|alt.badge.img+11
  • Hero (Partner)
  • 146 replies
  • September 7, 2024

Hi @NishaniF 

 

I find this issue quite unusual.

Have you tried to recreate this error in a test environment? Were you able to reproduce it?

I believe solving this may require a data repair. From what I see, the charge amounts are the same even though the quantities differ.

Regards,

Chanuka


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Partner)
  • 5 replies
  • September 10, 2024

Hi @Chanu_Yazi 

Thank you very much for your reply.

I have not been able to reproduce this in the test environment. However, there are 3 POs with this same error.

Kind regards,

NishaniF

 


Chanu_Yazi
Hero (Partner)
Forum|alt.badge.img+11
  • Hero (Partner)
  • 146 replies
  • Answer
  • September 10, 2024
NishaniF wrote:

Hi @Chanu_Yazi 

Thank you very much for your reply.

I have not been able to reproduce this in the test environment. However, there are 3 POs with this same error.

Kind regards,

NishaniF

 

Hi @NishaniF 

I believe solving this may require a data repair.

 

I'm happy to share my advice on this. If you found the answer helpful, please mark it as the correct answer. This will allow us to close the thread and make it easier for other community users to find and benefit from in the future.
 

BR.

Chanuka


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings