• Home
  • About
  • Contact
  • German

Dynamics 365FO/AX Finance & Controlling

Dynamics 365FO/AX Finance & Controlling

Tag Archives: invoice

Vendor invoice recording (Part 3)

17 Wednesday May 2017

Posted by Ludwig Reinhard in Accounts Payable

≈ 1 Comment

Tags

invoice, invoice recording, project expense invoice, workflow

This post extends the previous one in a way that this time a project related expense invoice is recorded and posted. The major difference to the example shown in the previous post is related to the expenditure reviewer setup that needs to be made in a separate project distribution tab, which is illustrated in the next screen print.

205_p3_0005

Please note that the setup of the ‘orderer’ expenditure reviewer group is made in the same way that has been shown for ordinary expense related invoices in the organization distributions tab.

The setup of the ‘approver’ expenditure group differs from what has been shown in the previous post because the project manager is now defined as the responsible person for approving the vendor invoice. For details, please see the following screen print.

205_p3_0010

Please note that the sample invoice recorded below is for project no. 000188, which has Kevin Cook assigned as the project manager.

205_p3_0015

Also note that Kevin Cook is not a line level manager of Nicole Holiday who once again ordered the goods. This can be identified from the next organizational chart.

205_p3_0020

Against the background of all this information, another expense invoice for advertising materials is recorded in the pending vendor invoice form.

205_p3_0025

This time, with a project is specified in the project invoice line details tab.

205_p3_0030

The financial dimensions invoice line tab is filled with the same financial dimension values that have been used in the prior post. That is, Nicole Holiday – the worker who ordered the goods – is recorded in the financial worker dimension field and cost center 008 – that has Benjamin Martin assigned as the cost center owner – is recorded in the financial cost center dimension field.

205_p3_0035

Because of the project relationship, the respective project manager (Kevin Cook) and not the cost center owner is identified as the one who has to approve the vendor invoice before it can be posted. The next screen print illustrates this.

205_p3_0040

As the remaining process steps are identical to what has been shown in the previous post, they are skipped here for reasons of brevity.

The next post will build upon this one and illustrate how different signing limits can be incorporated into the vendor invoice workflow. Till then.

Vendor invoice recording (Part 2)

09 Tuesday May 2017

Posted by Ludwig Reinhard in Accounts Payable

≈ 1 Comment

Tags

invoice, invoice recording, workflow

Within this second part of the series on vendor invoice recording, we start with a process where a marketing employee (Nicole Holiday) orders some marketing materials via Email.

After the materials have been received by Nicole Holiday, the vendor invoice arrives and is manually entered in the pending vendor invoice form. After recording all invoice related data, the AP clerk initiates the invoice workflow.

Within the first workflow step, the one who ordered the materials (Nicole Holiday) needs to review the invoice and confirm that all ordered materials arrived in good condition.

Thereafter, the cost center manager (Benjamin Martin) needs to approve the expense amount before it can be posted and paid later on.

The next flowchart summarizes the different process steps that will be investigated in more detail from a Dynamics AX/365 for Operations perspective.

205_p2_0005

The following organizational chart highlights the employees/positions involved in the process in light brown color. Note that this chart will also be used for the subsequent posts on vendor invoice recording.

205_p2_0010

Based on findings that have been made by other Dynamics AX/365 for Operations experts – please see the following post / video – the invoice approval workflow has been set up in a way that makes use of two different expenditure reviewer groups.

The first expenditure reviewer group – denominated as orderer – thereby makes reference to the financial dimension worker and automatically assigns the workflow work-item task to the worker specified in the financial dimension worker field. For details, please see the following setup.

205_p2_0015

warningsignganzklein Getting the invoices correctly assigned to the person who ordered it, requires setting up all employees with their own financial dimension. In addition, each employee must be specified as the owner of this financial dimension because the financial dimension owner defines the person who has to review the vendor invoice. The next screen print shows this setup for Nicole Holiday who ordered the marketing materials.

205_p2_0020

The second expenditure reviewer group – denominated as approver – references the cost center financial dimension.

205_p2_0025

The person responsible for approving the invoice is consequently the one that is setup as the owner of the respective cost center. In the example illustrated, this is Benjamin Martin as the head of cost center 008.

205_p2_0030

warningsignganzklein It is the financial dimension owner and not the manager of the corresponding operating unit that is referenced through the expenditure reviewer group.

warningsignganzklein The way how the setup is made requires that the expense invoice is entered with the financial dimension worker, which defines the orderer who is responsible for verifying that the ordered materials arrived. In addition, the respective cost center needs to be entered because it determines the manager that is responsible for approving the invoice.

 

After describing the elements required for the invoice workflow, let’s have a look at the different workflow steps and the overall setup of the sample workflow used in this post, which is illustrated below.

205_p2_0035

The following two screen prints show the setup of the first workflow step (review invoice) that requires Nicole Holiday reviewing whether all materials have been delivered by the vendor. Please note that Nicole holiday is not directly addressed in the first workflow step but rather the workflow participant ‘orderer’. As the expenditure reviewer group ‘orderer’ links to the financial dimension ‘worker’, the person who ordered the materials needs consequently be entered in the financial dimension worker field at the time the invoice is entered. This will be shown further below.

205_p2_0040 205_p2_0045

The second workflow step – the invoice approval step – is also assigned to a workflow participant. This time, the approver, as illustrated in the next screen prints.

205_p2_0050 205_p2_0055

With this setup in place, let’s record the expense invoice for the marketing materials. The next illustration shows the vendor invoice recording, which makes use of the ‘advertising’ procurement category that defines the ledger account that will be used for posting the invoice.

205_p2_0060

warningsignganzklein Please note that the orderer (Nicole Holiday) is entered in the financial dimension worker field. The person that needs to approve the invoice is determined by the owner of the cost center entered in the cost center financial dimension.

205_p2_0065

After all invoice details are entered, the workflow process is started by the accountant Phyllis Harris. Based on the workflow setup, Nicole Holiday is the first one that gets a workflow item-task assigned. Please see the next screen print.

205_p2_0070

If Nicole opens the assigned work item, she can inspect the invoice recorded by the AP clerk. Provided that everything is ok, she can then complete her review task.

205_p2_0075

warningsignganzklein If Nicole Holiday rejects the review, the invoice will be returned to the AP clerk who can then clarify with the vendor how to deal with the invoice received. Provided that the invoice is unjustified, the AP clerk has the option to recall the workflow and delete the record from the pending vendor invoice form until a new or corrected invoice from the vendor arrives. Another available workflow action for Nicole is to delegate the workflow task to another user who will then become responsible for finalizing the invoice review workflow step.

Once Nicole has completed her review task, the workflow assigns another work-item to Benjamin who has to approve the amount to be spend.

205_p2_0080

Benjamin can similarly choose among different workflow actions, such as approve, reject, etc.

205_p2_0085

warningsignganzklein In addition to approving the invoice Benjamin Martin has the option to reject the invoice, which returns it to the AP clerk – the workflow originator – who can then decide how to proceed. Delegating the approval step assigns the invoice approval to another user. The same applies to the request change workflow action, which allows specifying a user that has to make some changes – for example to the sales tax – before the invoice workflow can continue.

Once Benjamin Martin approved the expense invoice, all workflow steps are completed …
205_p2_0090

… and the invoice becomes available for posting.

205_p2_0095

warningsignganzklein Provided that all invoice details have already been entered in the first place and against the background that the invoice has been reviewed and approved by two different people, it can be posted automatically from the author’s perspective, which can be realized by including an automatic posting step in the workflow. The next screen print illustrates this.

205_p2_0100

Posting the vendor invoice ends this second post on vendor invoice recording. The next posts will successively extend the sample invoice workflow process illustrated here. Till then.

Vendor invoice recording (Part 1)

04 Thursday May 2017

Posted by Ludwig Reinhard in Accounts Payable

≈ 1 Comment

Tags

invoice, invoice recording, workflow

Over the last couple of years, I have seen a lot of different ways how companies record and process their vendor invoices. Some people I talked to about vendor invoice processing mentioned that the standard invoice recording tools would not be sufficient, others stated that they are too complex and even one time I was confronted with the statement that the standard tools cannot be used because ‘everybody’ says that they are not mature enough. Many of those people resp. companies ended up implementing expensive software add-on’s that often had their own problems and required some customizations in the form of interfaces and alike. Against the background of those statements, I will illustrate within this and the following posts how expense and purchase order related vendor invoices can be processed in the standard Dynamics AX/365 for Operations application.

warningsignganzklein Expense related vendor invoices are those for which no purchase order has been created and that are consequently not matched against product receipts.

The aim of this series is not to backfire on those previous – sometimes quite offensive – statements I was confronted with but rather to carve out the advantages and disadvantages, strength and weaknesses of the standard invoice recording tools in order to allow you making your own assessment.

Before we dig into the details, I would like to mention that all of the following illustrations and explanations will make use of what I call the vendor invoice ‘workbench’, that is, the ‘pending vendor invoice form’. Vendor invoice journals, vendor invoice register journals and invoice approval journals won’t be used at all because of the following reasons:

  1. The invoice workbench provides a single point of entry for entering expense related and purchase order related invoices.
  2. Entering vendor invoices through journals does not make use of the subledger accounting framework. As a result, important invoice audit functionalities are simply not available. For details, please have a look at this prior post
  3. Project related expense invoices that are recorded through journals are not considered as committed project cost. As a result, project costs might be observed too late, resulting in wrong decision makings and project analysis. For details, please have a look at the following post.
  4. The vendor invoice workbench allows recording project related intercompany expenses that cannot be recorded through the different invoice journals. What is more, intercompany projects automatically create intercompany invoices in the vendor invoice workbench. Using journals for recording vendor invoices consequently result in a situation where companies have to differentiate between (a) ordinary expense related invoices, (b) purchase order related invoices and (c) project related intercompany invoices and record them in different forms in Dynamics AX/365 for Operations.

Recording vendor invoices through the invoice workbench does also have some disadvantages, such as:

  1. That fact the value added tax included in the invoice amount will be posted later compared to posting it at the time the invoice is registered in the invoice register journal. This timing difference can result in cash flow related opportunity costs if the tax is deduced in future financial periods. Even though this statement is true, I have not seen many companies posting the value added tax at the time vendor invoices are registered. In addition, if the vendor invoice throughput time is short, the time difference argument falls short.
  2. That accountants who are used to recording expenses directly on ledger accounts have to relearn how they record vendor invoices. That is because the vendor invoice workbench does not allow entering ledger accounts directly but rather makes use of so-called procurement categories. The following figure illustrates an expense invoice for advertising expenses, where the ledger account that is assigned to the procurement category can be observed only indirectly through the accounting distribution form.
    205_p1_0005
    I made the experience that this last point is often the biggest hurdle that prevents people from using the vendor invoice workbench. From the authors perspective this second point is regularly used only as an excuse that is brought forward in order to prevent changes to familiar business processes. As an example, the argument that procurement categories do not provide users with an indication of the ledger account that will be used for posting can be overcome by including or adding the account number in the procurement category name.

The next posts will focus on expense related vendor invoices and how they can be entered and processed through the invoice workbench in Dynamics AX/365 for Operations. Thereafter, entering and processing purchase order related invoices will be illustrated before this series will conclude with a summary of the advantages/disadvantages, strength and weaknesses of the standard vendor invoice processing functionalities.

← Older posts
Newer posts →

Microsoft BizApps Deutschland Podcast

Dynamics UserGroup Deutschland

Project Accounting Book – Part 2

Project accounting book

Categories

  • Accounts Payable
  • Accounts Receivable
  • Bank Management
  • Book reviews
  • Budgeting
  • Cost accounting
  • Fixed Assets
  • General Ledger
  • Inventory
  • Management Reporter
  • Miscellaneous
  • Podcast
  • Project
  • Sustainability
  • Uncategorized

Tags

Advanced bank reconciliation Allocations Artificial Intelligence Bank reconciliation Budgeting Controlling Cost accounting Cost accounting module Cost center accounting customer D365 D365FO Dynamics 365 Dynamics AX Dynamics AX 2012 Electronic reporting Email Environment Fixed asset statement General Ledger journal Global Warming intercompany Inventory Inventory reconciliation invoice invoice recording IOT Management Accounting Management Reporter Modern Finance MS Flow MT940 PowerApps PowerAutomate PowerPlatform Project Project module Resource scheduling Sensor settlement SharePoint Sustainability Sustainability Accounting Tax time recording timesheet Vendor invoice recording Vendor payments WBS workflow

Important Websites

  • Dynamics AX/365FO Links

Legal

  • Disclaimer

Subcribe

  • RSS - Posts
  • RSS - Comments

Enter your email address to follow this blog and receive notifications of new posts by email.

Archives

  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015

Blog at WordPress.com.

  • Follow Following
    • Dynamics 365FO/AX Finance & Controlling
    • Join 583 other followers
    • Already have a WordPress.com account? Log in now.
    • Dynamics 365FO/AX Finance & Controlling
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar
 

Loading Comments...