Double invoice entry at the FI Level

Question

Where do I go in the FI level not to allow double invcoice entry.
Thanks
AG

Answer 1

> Csaba Soltesz,
> Could you explain both:
> How do I set up the FI_DUPLICATE_INVOICE_CHECK
> validation and also how to do it for MIRO
> transactions.
> I would appreciate feedback.
> Thanks
> AG
Hi Ana,
sorry for the late reply.
For the FI check, there is no specific setup. Only thing you need is to set the corresponding flag in the vendor master (company code view). Then, if the prerequsites are met (see below), a warning message will appear.
How the check is working in FI? (ie., FB01, FB60 or similar, NOT logistics invoice verification, for LIV, see below):
1. Is this a vendor line (account type K)?
2. Is the flag set in the vendor master?
3. Is the line item sales relevant (based on the posting key, e.g., 31 is sales relevant, 25 is not)
4. Is this a normal document? (not recurring, parked, clearing, sample doc)
5. Do we know the document currency?
6. Do we know the document date?
7. Is the amount in document currency <> 0?
If the answer to all of the above was YES, then the check is carried out. What is actually checked, is table BSIP. Every time when you post a document meeting the above criteria, BSIP will be updated. Next time the BSIP entries are checked.
And here the checking rules:
IF the reference field (BKPF-XBLNR) is filled in, then the message is issued when there is a BSIP record already with the same:
- company code
- vendor number
- document date
- reference
- document date
- D/C indicator
IF the reference field is NOT filled in, in addition to the above, the amount in document currency is also checked in BSIP, so that field must match too in order to get the message.
The message is F5 117 and the type can be changed in customizing (view V_T100C) as usual for customizable messages.
The above list also answers another question in this thread: NO, it is not possible to check it cross company code. I.e. if you have entered an invoice for company code A, then you can enter the very same invoice for company code B, there will be no message at all. You need to create some validations (transaction OB28) to achieve this. The standard check is working within the same company code only, see the list above.
Now,  that was the pure FI thing, how about Logistics Invoice verification (MIRO, etc.). Here, you have some more configuration options. The function module called here is MRM_FI_DOCUMENT_CHECK.
The check in Logistics Invoice Verification is carried out only if the below criteria are met:
1. Reference field is filled in (!!!!! extremely important!!!!)
2. This is an invoice (and not a credit memo... see RBKP-XRECH must be X)
3. The vendor number is known
4. The flag is set in the vendor master (company code view).
The check is made against BSIP again, but WHAT exactly is checked, i.e., which fields must match, is customizable. In table T169P, you can tell the system which fields you want to consider as indicators for a double invoice entry. You can choose from: Reference, Company code, Document date.
Here is part 2 of the answer to the previous question: YES, Logistics Invoice Verification can be set up in a way that invioces are checked cross-company code. If you do NOT mark the field company code, than this field is not checked, and the same invoice cannot be entered for 2 different company codes.
First, the system tries to find a BSIP record with the same values in the fields below:
- Vendor number
- Document currency
- Amount in document currency (this only if Reference is NOT ticked in table T169P)
- Company code (only if ticked in T169P)
- Document date (only if ticked in T169P)
- Reference (only if ticked in T169P)
If there was a BSIP entry found, message M8 108 will appear as a warning. Again, you can change the msg type to error if you like (user-specific).
Also, Logistics Invocie Verification can be a 2-step procedure: first, the invoice creation (entry in table RBKP) and second, the posting of this invoice to Accounting (entry in table BKPF). In most cases, this happens in the very same moment when you press Save in MIRO, but it could be also set up in your company that you do these 2 steps separately.
That's why after the posted invoices (BSIP) were checked, the system tries to check the invoices not yet posted to Accounting (invoice document status is "Not yet posted"). This is to make sure an entered but not yet posted invoice is also checked early enough. Basically the same fields as above are checked, but the message is a different one: M8 642. Default type is warning, changeable to Error if you like.
Hope that helps, points welcome
Csaba