web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Inventory Transaction was split

(0) ShareShare
ReportReport
Posted on by 10

Hi ,

How is this inventory transaction was split on the same purchase order? both inventory transaction have the same purchase order number but in the purchase order line there is only one item inside and that is item that has 417 quantity. Where did the other item that has 0.00 quantity and 0.01 Cost amount go? I can't find that item.

pastedimage1636365441143v1.png

Can someone help me solve this problem? I would really appreciate it.

I have the same question (0)
  • Suggested answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hi Dan,

    The first line looks like a line related to a rounding issue.

    What the transaction / posting type of the line with the 0.01 amount?

    Best regards,

    Ludwig

  • Dan_213 Profile Picture
    10 on at

    It's a Purchase order / Purchase expenditure, un-invoiced.

  • Dan_213 Profile Picture
    10 on at

    It should have only one product receipt, I don't know why the inventory transaction is split into two lines.

  • Verified answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hi Dan 213,

    It looks like a rounding issue.

    You purchased 417 pcs and the cost price that I see is 1658.50, which gives a price/pcs of 3.97722.

    That seems to be the underlying issue for the additional line with the 0.01 rounding

    Best regards,

    Ludwig

  • Dan_213 Profile Picture
    10 on at

    So that remaining 0.01 came from the price of 3.97722 per pcs?

  • Dan_213 Profile Picture
    10 on at

    Can we avoid that from happening again?

  • Verified answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hi Dan 213,

    There is nothing that you can configure directly to avoid that from happening again.

    A good 'workaround' is setting up prices that do not result in rounding differences. That is, try to avoid prices that end with .33 / .67 or something alike that regularly cause rounding issues.

    Best regards,

    Ludwig

  • Dan_213 Profile Picture
    10 on at

    I see.

    Thanks for your help though, I really appreciate it.

  • Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    If there is nothing else left open / unanswered then lets please confirm the answers to get this thread completed.

    Cheers,

    Ludwig

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 584 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 499 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 254 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans