![](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/2024\/04\/20141002_invoice-receipt-vs-purchase-order_D_01.jpg\")
<\/p>\nIn today’s blog post I will show the necessary SAP\u00ae data and analysis steps to compare the purchase order value with the total invoice receipt amount. <\/p>\n
Usually the invoice receipt amount should match the purchase order amount \u2013or at least, those amounts should not differ too much. For example, if one laptop has been ordered with a net value of 1,000.00 \u20ac, an invoice with an amount of 1,000.00 \u20ac is expected accordingly (if the same article which has been ordered got delivered). <\/p>\n
However, there may be reasons for discrepancies: There could be unplanned additional delivery costs which have not been entered when the PO was created, but now are stated on the vendors\u2019 invoice. Another reason may be the simple fact that the invoice has been entered incorrectly when booking the invoice receipt (a typo for example) or the vendor created the invoice wrongly. <\/p>\n
In SAP\u00ae, tolerance limits on PO line item level can be set up (percentages for example which will be accepted by the system automatically). However, if those limits are exceeded, they sometimes can just be accepted by the users if he is able to override them, or even the \u201cunlimited overdelivery\u201d flag could be in place. <\/p>\n
Because of such scenarios it can be very interesting to compare the total invoice receipt value with the original purchase order value, like shown in this blog post. <\/p>\n
Purchase orders in SAP\u00ae can be displayed via the transaction "ME23N". It provides all details of the PO items. The tab "Order History" in the item details allows an insight into the corresponding goods receipts and invoice receipts which already have been entered in context of this PO line item. Looking at these values, the total invoice receipt amount can easily be compared with the PO item value for one specific PO by simply using the SAP\u00ae transaction ME23n.<\/p>\n
<\/p>\n
However, this only allows to look at the data case by case, PO by PO. It is not a structured approach in terms of data analytics or analyzing \u201cbig data\u201d, e.g. checking all purchase orders of the last two fiscal years regarding invoice receipt exceeding\u2019s. To achieve this, you should consider looking at the SAP\u00a9 tables containing the raw data: <\/p>\n
The table "EKPO" contains the purchase order line items, e.g. material number, item text, quantity, price and total value. The table "EKBE" (\u201cPurchase order history\u201d) is interesting as well, as it contains – amongst other information – all invoice receipts which have been posted with reference to a PO. In addition to invoice receipts are several more event types in table EKBE that can happen in context of a purchase order line item. The most common SAP\u00a9 event types are listed below: <\/p>\n
![](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/Publ\/cD\/20141002_invoice-receipt-vs-purchase-order_D_02.jpg\")
<\/p>\n
1. Processing the invoice receipts (table EKBE) <\/b>
\na) Isolating the invoice receipts <\/p>\n
As described above, this table contains a variety of different event types. For our task only the invoice receipts are essential. The necessary transactions can be filtered and isolated by putting them in a new table. <\/p>\n
b) Applying the Debit \/Credit indicator to use the correct amount <\/p>\n
In most SAP\u00ae financial tables you will find only absolute amounts. Those have to be looked at in context of the associated debit\/credit indicator (\u201cS\u201d for Debit, \u201cH\u201d for credit). In order to answer the audit question currently, each invoice receipt amount must be transferred into a positive or negative amount depending on the debit \/ credit indicator. It should be negative, if the indicator is \u201cH" (Credit), and positive if the indicator is \u201cS\u201d (Debit). As the following example shows, this is important because of credit notes or reversed invoices, which will also be listed in the purchase order history as \u201cInvoice received\u201d event: <\/p>\n
![](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/Publ\/cD\/20141002_invoice-receipt-vs-purchase-order_D_03.jpg\")
<\/p>\n
In this example, three invoice receipts listed for the purchase order item. Having a closer look we can see, there are two debit ("S") lines and one credit "H" line. This means that two invoices have been entered, but one invoice was cancelled (or a credit note was entered). This means, only a total invoice receipt amount of 600 \u20ac is relevant (600-600+600). <\/p>\n
c) Summarizing all invoice receipts <\/p>\n
The possibility of multiple invoice receipts (or credit notes \/ cancellations) can be taken into account by summarizing the data on PO line item level, using the purchase order number and item number plus cumulating the positive and negative amounts as explained above allows us to identify the total (cumulated) invoice receipt amount for each PO line item. <\/p>\n
<\/p>\n
2. Combining purchase order items (EKPO) versus summarized invoice receipts (EKBE)<\/b><\/p>\n
The purchase order items and the summed up invoice receipts can now be combined by using purchase order number and line item number. Once you have the purchase order and invoice receipt values next to each other, the difference between the net order value and the total invoice receipt value can be calculated. The following figure shows an example of the result: <\/p>\n
![](\"https:\/\/www.dab-europe.com\/\/wp-content\/uploads\/Publ\/cD\/20141002_invoice-receipt-vs-purchase-order_D_04.jpg\")
<\/p>\n
In the same way you could include the goods receipts values to compare all three process steps in one single table. <\/p>\n
A very quick but important analysis to identify too high invoice receipts from vendors. The main trick is to consider the fact of multiple invoice receipts (including credit notes or reversed invoices, which have to be deducted). A final tip – not only for this analysis – keep the currency of the amounts in mind, and be careful not to compare values of different currencies without adjusting them first. <\/p>\n
Best Regards
Florian Popan <\/p>\n