<\/b><\/p>\n
This question is described below with reference to SAP\u00ae content, but can be transferred and applied to any ERP system.<\/p>\n
The ultimate risk of this process deviation is that the actual release process of purchasing happens in the purchase order (or requisition). Thus, orders with reviewable volume and its release can be circumvented.<\/p>\n
First of all I want to point out that SAP is technically not able to later register the reference of an incoming invoice to an order. Entering an invoice with reference to a purchase order is not possible in an SAP system before entering the actual purchase order.<\/p>\n
So why does this case oftentimes occur in businesses and how can documents with this process weakness be identified?<\/b><\/p>\n
![\"SAP](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/2024\/04\/20140120_ANQ_SAP_InvDate_PODate_D_01.jpg\")
<\/p>\n
The steps of a process<\/h2>\n
The steps of a process usually run one after another, which makes it easy to order them by date. These key date fields are described below in their characteristics and handling.<\/p>\n
When creating a purchase order, the system automatically assigns the creation date (AEDAT)<\/strong>. This makes it possible to clearly determine the posting\/entry of a purchase order. In the area of invoice receipt, processes intersect with financial accounting, which is why particular attention should be paid to the following three key date fields:<\/p>\n The question is now, on what date the generating of the order is to be compared.<\/strong><\/p>\n From a technical point of view, the system date (CPUDT)<\/strong> makes no sense, as the invoice receipt can also be entered with an order reference only after generating the order. Thus, the difference calculation would not provide results.<\/p>\n The comparison with the posting date (BUDAT)<\/strong> is only of limited significance, as this date is used for valuation purposes in accounting. It is very likely that within a given period (e.g., a month), the exact date of invoice receipt is not recorded. Instead, the last day of the relevant period is often entered, if retrospective posting is even required at all.<\/p>\n In the end, only the comparison on document date (BLDAT)<\/strong> leads to a result. The date on the original invoice document proves the actual date of the invoice. When the document date is older than the related purchase order (AEDAT<\/strong>), this is the indication that the invoice was received before the purchase order was entered. However, there is a restriction with this date. It can be manually entered and editing is also possible.<\/p>\n In summary, the difference between the invoice document date and the creation date of the purchase order is the most reasonable to be looked at<\/strong>. The fact of the possibility to edit this field looses impact, when clear findings prove this approach right.<\/p>\n\n\n\n
This is the date of the receipt of invoice entered to the system, is assigned by the system and cannot be changed.<\/li>\n
This date determines in which period the stated amount has to be posted to. So it corresponds to the assignment of costs to a certain posting day and can be freely chosen within on open posting period by the agent.<\/li>\n
Provides the date on the invoice paper of the vendor. Depending on the use of automatic detection mechanisms (invoice scan) a date is proposed, which can be changed at any time by the user.<\/li>\n<\/ul>\n