© SAP AG TAMM30 4.

0B 15-1
© SAP AG TAMM30 4.0B 15-2
 In the standard system, there is a document type for gross posting and a document type for net posting
in Invoice Verification. For each transaction, you configure the document type that should be used to
post documents. For the transactions in Logistics Invoice Verification, you should also configure
separate document types for other documents (revaluation document, invoice reduction document).
 You can define number intervals specific to a certain year.
 In Logistics Invoice Verification, you can define two number intervals, one for posting invoices, the
other for reversing invoices, ERS and EDI.
 In Logistics Invoice Verification, you use the entry profile to control which view of the item list is
displayed, how the item list is sorted and how messages are issued.
 In Logistics Invoice Verification, you use the field selection function to control which fields are
displayed on the initial screen and header data screen and which fields are ready for input.
 You use the tax version to define whether 1, 2 or 4 lines of tax information can be entered on the
vendor screen (in conventional Invoice Verification) or on the initial screen (in Logistics Invoice
Verification) and which tax codes should be suggested. The tax code for unplanned delivery costs is
also suggested, in case unplanned delivery costs are to be posted to a separate account in Logistics
Invoice Verification.

© SAP AG TAMM30 4.0B 15-3

 If the exchange rate at the time of receipt differs from the exchange rate at the time of invoice receipt,
the system can handle the resulting differences in various ways.
 In Logistics Invoice Verification, you configure the system to apportion unplanned delivery costs
among the invoice items or to post them to a separate G/L account.
 You can define various subsequent debit/credit indicators, so that you can distinguish subsequent
debits/credits in the purchase order history. For each subsequent debit/credit you define whether the
system should carry out a price check when you enter a subsequent debit/credit.
 The buyer can add various texts to a purchase order. In Customizing for Invoice Verification, you can
configure the system to send the accounts payable clerk a message if certain texts are entered in a
purchase order.

© SAP AG TAMM30 4.0B 15-4

 In the case of a price variance, you have the option of directly informing the buyer of a posted price
difference by mail. In addition to activating the automatic mail function, you must also configure
output determination to do this.
 In Logistics Invoice Verification, you can configure the system to automatically reduce or accept
invoices that contain variances without reference to an item. To do this, you define tolerance groups in
Customizing for Invoice Verification. In the vendor master record, you can assign each vendor to a
tolerance group.

© SAP AG TAMM30 4.0B 15-5

 You can only process invoices with the payment block “R” using the Invoice Verification function
Release invoices. You delete the other payments blocks using the Financial Accounting function
Change document.
 There is a tolerance key for each variance type (for example, quantity variance, price variance, see
unit 5), for which you must configure tolerance limits. In addition, there are tolerance keys for the
amount check (see point 3 above), small differences (see unit 7) and for the maximum price change.

© SAP AG TAMM30 4.0B 15-6

 When you release blocked invoices, you can choose between the list variants for item display and
totals display. Within the list of invoices to be released, you can switch between the different list
variants.
 In addition to the standard list variants, you can also define other list variants.
 You can release blocked invoices only from a standard totals variant. You can define your own totals
variants, but you can only use them for information purposes.

© SAP AG TAMM30 4.0B 15-7

 In order to maintain the GR/IR clearing account, you must configure the document type that should be
used to post the accounting document.
 For Invoice Verification in the background, you can configure whether invoices posted in the
background are given the status “verified as complete” or “completed”.
 For invoice receipt via EDI, you must configure how the tax code is determined and whether the
invoice should first be parked.

© SAP AG TAMM30 4.0B 15-8

 In the case of a price variance, the system can inform the buyer by mail.
 With consignment settlement, you must send the vendor a statement of settlement, so that the vendor
can check the payment and has an overview of the quantity of the consignment stock.
 With Evaluated Receipt Settlement (ERS), you must send the vendor a statement of the invoices
generated, so that the vendor can compare the payments made with the purchase orders and deliveries.
 When you have reduced an invoice, you must inform the vendor so that differences between the
payments and the receivables can be accounted for.

© SAP AG TAMM30 4.0B 15-9

 You can configure the following authorizations and profiles individually for each user:
 The company code for which the user can post documents
 The plants for which the user can post invoices
 The blocking reasons which the user can delete
 Whether the user can manually accept variances without item reference
 You can assign each user to a tolerance group. You set the maximum amount and the maximum cash
discount that the tolerance group is allowed to post.

© SAP AG TAMM30 4.0B 15-10

© SAP AG TAMM30 4.0B 15-11