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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Accruing purchase orders - posting profile dilemma

(0) ShareShare
ReportReport
Posted on by

I'm sure this has been brought up before. Wondering what the industry has done to resolve the dilemma I'm up against.

Accruing the purchase order (at time of product receipt posting), the voucher is driven by the item/group/procurement category in inventory posting profile.

How does one circumvent this if they want the accrual to go to the GL account that is setup on the PO line? Seems to be something missing here where theoretically there's only 1 accrual account available when a receipt is posted against the PO. If the PO is for expenses only (where items are really service items), I would like the accrual at time of product receipt posting to go to the GL account that is setup on the line item of that PO.

Yes I can have a different account to accrue to based on the item or item group or procurement category, but this still doesn't support my posting when I use this same item for project purchase orders or non project purchase orders (where non project purchase orders are used as expense PO's and project PO's are used for capital purchases).

There's no ability to drive the profile (product receiving) if the PO is project related or not.

Anyone has any opinions / comments?

Robert

*This post is locked for comments

I have the same question (0)
  • Brandon Wiese Profile Picture
    17,788 on at

    I can make some suggestions on where to look in the code to make this change.

    On the table PurchLine, the methods .accountReceipt() and .ledgerDimensionReceipt() reference the field .LedgerDimension as follows.

       if (this.LedgerDimension && InventMovement::construct(this).mustBeBookedBalanceSheet())

       {

           ledgerDimension = this.LedgerDimension;

           ledgerAccount   = DimensionStorage::ledgerDimension2AccountNum(this.LedgerDimension);

       }

       else

       {

    ..

    The idea here is that if the LedgerDimension field is used (not 0) and the Inventory movement must be booked to the balance sheet (code-speak for carries Inventory on-hand value or "must be booked physically/financially"), then use the Main account specified on the Purchase order line, otherwise fall back to the configuration according to the Inventory posting setup.

    I suspect what you want to do is similar but could be implemented in a different method on PurchLine.  Most of the Main account logic is found there in methods similar to what I've already referenced.

    Have you made any progress on this yet?

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans