Double Invoice Verification

We have a process in which we book multiple invoices of single vendor in single FI document. The issue is, double invoice verification feature works with Header Text Assignment field. If vendor sends twice the same invoice, bundled into many invoices, Document Header Assignment filed cannot be used for verification of double invoice.
Can double invoice verification work at Line Item level rather document header level?
Thanks

Hi,
you can set the flage of check double invoice verification in vendor master - Payment Transaction Accounting you can find the field.
In checking for duplicate invoices, the system compares the follow
characteristics by default:
Vendor
Currency
Company code
Gross amount of the invoice
Reference document number
Invoice document date
If all of these characteristics are the same, then system will throw a warning message.
Regards,
SAP User

Similar Messages

Same nr range in Invoice Verification (MIRO) and FI document

Dear all can you please help to solve this issue?
We would like to have the same number range for invoice verification and for financial document, what we have to do?
Regards
Marco

Please follow the steps as below
Step 1. Maintain FI document number range. Use transaction OMR4 and go to Number range for document types in FI. Select the company code for which you want to create the new number range interval and click on the change interval button. Insert a new document number range by clicking on the insert interval button on top of the screen.for example, I created number range interval 52 with the document numbers 5200000000 5299999999. Don't forget to set the external number range check box (Ext).
Step 2. Assign FI number range to FI document types. The second step is to assign the number range created in step 1 to the FI document type for invoices. Again use transaction OMR4 and go to Document type. Double-click on the document type, which you are using for LIV invoices. In my example, I used the SAP standard document type RE. In the number range field, assign the new number range interval 52
Step 3. Maintain MM document number ranges. Use transaction OMRJ and click on change interval button. Insert a new document number range by clicking on the insert button at the top of the screen. For MM documents, I created number range interval 52 with the document numbers 5200000000 5299999999. For the internal number range assignment, do not set the external number range check box (Ext).
Step 4. Update MM number range assignment. The last step is to assign the MM number range to your MM transaction via IMG menu path Materials Management>Logistics Invoice Verification>Incoming Invoice>Number Assignment>Maintain Number Assignments for Logistic Documents>Transaction Assign Number ranges. Two transactions are available. LIV contains the following two internal transactions that are used for the MM document number determination:
RD: manual invoice entry (MIRO)
RS: cancel, reverse invoice (MR8M), evaluated receipt settlement (MRRL), EDI invoice receipt, invoicing plan (MRIS), and revaluation (MRNB).
You need to update the number range interval for transaction RD.
hope now that things r clear
reward accordingly

Configuring double invoice check for vendor invoices posted through FB60

Dear all
Can anyone tell me how to configure double invoice check for vendor invoices posted through FB60.
for miro documents..we can use Tcode OMRDC
Is there any such tcode which can be used for configuring fi invoices for double checking..
regards
Expertia

Dear Expertia,
In FI,when checking for duplicated invoices, the system compares the
following :Vendor, currency, company code, gross amount of the invoice,
reference document number and Invoice document date.
SAP Note 305201 clarifies this in a more details; please read it.
The following fields must be identical for Duplicate invoice check
     Company code                              (BUKRS)
     Vendor number                             (LIFNR)
     Currency                                  (WAERS)
     Reference number                          (XBLNR)
     Amount in document currency               (WRBTR)
     Document date                             (BLDAT)
If the document is having any one of the above filed different then the
system does not consider it as a duplicate invoice.
Also It will check duplicate invoice check in vendor master data and
in posting key is there check box selected for sales related
The setting you making in OMRDC i.e Materials management->Logistics
Invoice Verification->Incoming Invoice ->Set Check for Duplicate
Invoices is only valid for MM and not FI invoices posted via FB60/FB65
You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
in the relevant vendor master record (transaction FK03).
Please also check, that message F5 117 has been set correctly in the
IMG using this path:
Financial Accounting -> Financial Accounting Global Settings ->
Document -> Default Values for Document Processing -> Change Message
Control for Document Control For Document Processing
Finally & mainly, go to the relevant posting key is defined as sales
related in transaction OB41. You have to flag this field if the
duplicate invoice check should work.
I hope this helps You.
mauri

MM-Check Double Invoice functionality for Vendor Invoices

Dear All,
How Check Double Invoice functionality for Vendor Invoices can be implemented in SAP?
We have implemented Check double invoice with the standara sttings for it however if i give my referenece text differently it will aloow me to post double invoices and against vendor open items are shown for payment?
Is there any other efficient way to do it?
Thanks and Regards
Shrinivas

dear SAPian friend,
go through the below link and you will find the solution with the screenshots.
http://sapfunctional.com/MM/Duplicate/Invoices.htm
U can also do the setting using the SPRO t-code:-
path is
>>SPRO
>>SAP Reference IMG
>>Materials Management
>>Logistics Invoice Verification
>>Incoming Invoice
>>Set check for duplicate invoices

Check for double invoices

Hi,
1) Can someone explain me what is meant by "Check for double invoices " field in vendor master and its importance?
2) I am also confused between "Check for double invoices " filed in vendor master, and set check for Invoce duplication in "SPRO -> SAP Reference IMG -> Materials Management -> Logistics Invoice Verification -> Incoming Invoice -> Set check for duplicate invoices". Can some one exaplin that too?

Hi,
1) Can someone explain me what is meant by "Check for double invoices " field in vendor master and its importance?
This field for vendor reference while doing MIRO
2) I am also confused between "Check for double invoices " filed in vendor master, and set check for Invoce duplication in "SPRO -> SAP Reference IMG -> Materials Management -> Logistics Invoice Verification -> Incoming Invoice -> Set check for duplicate invoices". Can some one explain that too?
here you can define criteria for duplicate invoice including reference field also
In vendor master press F1 for duplicate invoice indicator ,you will get good info with Example.
how it work
check following link also
[http://help.sap.com/saphelp_470/helpdata/en/ce/4f3e39ea3aee02e10000000a114084/content.htm]
Regards
kailas Ugale
Edited by: kailasugale on Jan 16, 2012 2:43 PM

Check double invoice with GL account and Reference field

Dear SAP GURU's,
I am very new to SDN. I have one query.
I know we have the option of control double invoice against Vendor/Customer by using reference field. But here my client is asking that control has to be from GL account and reference field, becoz some times he will receive the shipping bills 3 or 4 times agianst one billing document ( i am booking Transporter Vendor invoice by using FB60) with same bill number but expense GL's will be different most of the times. Some times knowingly or unknowingly same GL Expenditure account will be repeated with the same shipping bill number. This was happend most of the times.
So can i know how can i get the GL account and Reference field checking and error message for the same.
Thanks & Regards,
Shobha.

Dear Shobha,
I feel that having a check on GL is not a good idea. If your client insists you can go for an exit or BTE.
We used BTE to have the same functionality of Logistics for FI documents also in our office.
Duplicate Invoice check process documentation is given below for your ready reference --
with Regards
Check Flag for Double Invoices or Credit Memos
Indicator which means that incoming invoices and credit memos are checked for double entries at the time of entry.
Use
Checking Logistics documents
Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
Checking FI documents
The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
Checking Logistics documents
In checking for duplicate invoices, the system compares the following characteristics by default:
Vendor
Currency
Company code
Gross amount of the invoice
Reference document number
Invoice document date
If all of these characteristics are the same, the system issues a message that you can customize.
When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
No message is issued if you enter a document that has previously been reversed.
Dependencies
The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
Reference document number
Invoice document date
Company code
This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
Example
The following document has already been entered and posted:
Reference document number: 333
Invoice date: 04/28/00
Gross invoice amount: 100.00
Currency: EUR
Vendor: Spencer
Company code: Munich
You have made the following settings in Customizing:
The field "Reference document number" and "Company code" are deselected, which means that these characteristics will not be checked.
Now you enter the following document:
Reference document number: 334
Invoice date: 04/28/00
Gross invoice amount: 100.00
Currency: EUR
Vendor: Spencer
Company code: Berlin
Result
Because you entered a reference document when you entered the invoice, the system checks for duplicate invoices.
The reference document number and the company code are different from the invoice entered earlier, but these characteristics are not checked due to the settings you have made in Customizing.
All other characteristics are the same. As a result, the system issues a message that a duplicate entry has been made.
If the "Reference document number" had been selected in Customizing, the system would have checked the document and discovered that it was different from the invoice entered earlier, so it would not have issued a message.
Checking FI documents
Depending on the entry in the field "Reference", one of the following checks is carried out:
1. If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
Company code
Vendor
Currency
Document date
Reference number
2. If no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
Company code
Vendor
Currency
Document date
Amount in document currency

Invoice verification - vendor

Hello Sap Guys!
Is there some configuration in SAP that carries through the verification of the Vendor of the PO and the Vendor of the invoice (MIRO). At the moment of emission of MIRO?
Thanks,
Gustavo

Hi Gustavo,
Yes, there is a configuration is required to verify the Invoices from Vendor is mentioned in below:
Use the path:
      IMG Display--> MM --> Logistic Invoice Verification --> Incoming Invoice -->
      Set Check for Duplicate Invoice (Screen appears as mentioned in below combination, you need to flag the checkboxes):
   Co.Code: Check Co.Code Check Reference Check Invoice Date
then
     you can stop the invoice entering double time.
Or
     If you want to check for duble /duplicate invoice, only for the perticular vendor:
then
you have to set the flag/indicator for Check duble Invoice (which is in payment data in the screen of Payment transactions of Company code data of Vendor master, this is specific to vendor)
hope it will clarify your query,
reward, if it solves,
Regards,
Srinu.K

Create a validation for check double invoice

Hi,
I have read here on SDN for check double invoice on reference number. We want to create an warning message if same reference number is posted twice, not depending on invoice date. So if I, on 1st of October have posted an invoice with reference number 123 and then want to post with same reference number on 2nd of October I want to have an warning message. If I had understand right I need to make a validation for that. Is it true that I need to have a programmer to do that or how am I doing (one thread said that this was the solution, see; )?
I suppose that my prerequisite will look as follows:
BKPF-BLART = 'KR' OR BKPF-BLART = 'RE' (I want the check when entering both an invoice in FB60 and MIRO)
How will my "check step" look like when I want to check if this reference has been entered before? Please describe in technical name.
Is it possible to do a validation for getting a warning, or is it just possible with error message?
I have also tried to change in IMG, in Material management > Logistics Invoice Verification > Incoming invoice > Set check for Duplicate invoices. Here we have all fields selected (check co. code, check reference, check inv. date). I changed to just select check reference, but this doesn´t solved my problem.
Best regards Lisa

Hello Lisa,
Your first question,
Yes system does not check MIRO invoice while posting FB60 invoice. Because when you post invoice with using FB60 transaction, system check BSIP table for duplication. But when you post MIRO invoice system doesn't fill BSIP table.
So that your question answer is YES, you can register an invoice in MIRO with same reference without a warning.
Your second question,
BTE means Business Transaction Event. Those events are known as FI user-exit.
So that when you posting an invoice with using FB60, system triggered on BTE 00001110 as i said on my previous message.
I try to explain step by step how can you activate this BTE. But you need to ABAPer for giving warning message on this exit.
Call FIBF transaction -> Settings -> Products -> ...of a customer
Create a new line,
Product : ZXX
Text : BTE Products for FI Exit
Product active : tick checkbox.
Call SE37 for exit function and copy from FM SAMPLE_PROCESS_00001110 to ZFI_PROCESS_00001110. Then active your FM and go to FIBF transaction again.
FIBF -> Settings -> Process Modules -> ...of a customer
Define a new line.
Process : 00001120
Function Module : ZFI_PROCESS_00001110
Product : ZFI
And then you can some write ABAP code for validation and give warning message.
In this FM, If you don't want to check duplicate invoice for your cases you can set export parameter e_nostd = 'X'.
I hope it helps to you,
Regards,
Burak

Check when saving Logistics Invoice Verification (MRMBADI_INVOICE_SAVE)

Hi everybody, we have an ECC 6.0. with IS-Retail platform, and we have noticed that during Logistics Invoice Verification process (Tx MIRO), it´s possible to make mistakes by choosing a vendor, then picking an invoice from another vendor, with the particularity that both invoices have the same delivery note number as PO reference (same vendor´s delivery note number / GOHEAD-LFSNR). The system doesn´t check if PO reference corresponds with correct vendor while saving the document.
Our question for you is if there is a Customizing way to activate a validation which allow us to solve mistakes describe before???
We found BAdI method IF_EX_MRM_INVOICE_UPDATE PROCESS_AT_SAVE which is processed when saving an invoice, the method calls are encapsulated in the function module MRMBADI_INVOICE_SAVE which is responsible for saving invoices.
If there isn´t a Customizing way to activate a check like that, the second question we have for you is if you have experience with this BAdI??? Does it work with this kind of validation??? We need to ensure that PO reference corresponds to correct vendor (GOHEAD-LIFNR / RF02K-LIFNR).
Thanks in advanced for your help,
Regards,
Miyuki Quiroz.

Hi,
Duplicate invoice check will fulfill your requirement. System will check is the invoice exists with same invoice date, reference and company code.
Follow the path SPRO -- IMG -- MM -- LIV -- Incoming Invoice -- Set Check for Duplicate Invoices
Also tick check box for "check double invoice" in vendor master accounting data.
In case you want amount also as one of the checking parameters, then you need to go for validation. No standard setting is allowed for that.
Nikhil

Set up tolerance key (invoice verification)

Hi Experts,
I would like to set up tolerance key and to control invoice item in reference to a PO item and I also need to set up a global tolerance.
What I need to maintain in order to have a double check: at item level and the total amount of the invoice?
(I have already set up PP tolerance key in order to have a check at item level and I need one other control for the global amount of the invoice but which one?)
Many thanks for your help.
BR,
Cesar
Edited by: Cesar on Sep 2, 2009 6:18 PM

Hello Cesar,
You can block the invoice for payment.
You have to set up the tolerance limits at company code level.
Path: IMG -> Material Management -> Logistic Invoice Verification -> Invoice Block -> Set Tolerance Limits ->
Here you need to maitain the respected " Tolerance Key" and Lower limits and Upper limits %.
This will solve your issue.
BR
Suneel Kumar

Freight payment invoice verification two times

Hi
During freight payment with invoice verification for condition type FRE1(Fixed amount)
The attributes of the condition type is fixed amount
For the given purchase order
QTY-10NOS,freight value-Rs100)
Invoice verification done with value 100nos then again system allows to do invoice verfication for the same condtion type.How to block the condtion type to prevent invoice verification again.
Both the time i have used the transaction- Invoice only.
Regards
Umapathy.M

Hi first of all at the vendor master the field 'Chk double inv.' should be checked then system checks whether its duplicate or not according to the following items
Company code (BUKRS)
Vendor number (LIFNR)
Currency (WAERS)
Reference number (XBLNR)
Amount in document currency (WRBTR)
Document date (BLDAT)
Duplicate Invoice Check customization should be done also via
Logistics Invoice Verification > Incoming Invoice > Set Check for Duplicate Invoices
check the following link is helpful for your case:
http://help.sap.com/saphelp_47x200/helpdata/en/ce/4f3e39ea3aee02e10000000a114084/frameset.htm
Regards
Hope it helps
Volkan

Posting double invoice - where is the control?

Hello Gurus,
Need your help.
Can anyone advice me on where in SPRO I can change so that the system will check the document reference number to determine whether the invoice has been posted before or not? The invoices are being posted in FICO-AP (transaction FB60) I want to avoid having two same invoices being posted.
In vendor master, the check for double invoice is checked. I've already setup the following steps for Logistic Invoice Verification Check:SPRO --> Logistics Invoice Verification --> Incoming Invoice -->Set Check for Duplicate Invoice.
But since we are talking about the invoices posted in FICO, I don't think the above step applies.
Any advice is wlecome.
Thank you in advance.
Anisah

Hi
Sorry. After so many days, I logged in today only.
I will give a gist of whats in my mind. You may need to talk to your abaper.
As you are aware of, user exist is kind of a small program which triggers at the time of posting a document.
Here the logic should check for the existing entries of XBLNR field values in BKPF and comapre with the value entered by the end user and then if its no duplication, allow otherwise, say entry exists.
But, pls note that XBLNR allows both alpha and numerical. So, slight mismatch also will be treated as new entry.
But, note that this will reduce system performance over a period of time. So, may be you need to come up with such a logic like BELNR+GJHER should be the value in XBLNR.
So, that it will be easy for the sytem to check for duplicate entries. As I said earlier, better not to enter alphabets in the xblnr.
Hope this helps
regards
Sridevi

Double invoice issue

Hi,
We have an internal vendor and so automatic invoice verification is implemented against the said internal vendor. However, the issue is there is a double invoice for some of the invoice refrence numbers. Check box for checking double inovice is already in place in the vendor master. Inspite of that there are double invoices for some of the invoice reference numbers.
I checked the settings in OMRDC and there are 3 fields checked - company code, document date and invoice reference number.
Point to be noted is the document date of the duplicated invoice reference numbers are different. I suspect that the invoices have been interfaced twice from the legacy. However, I need to check with the legacy team for the same.
Say for example:
Invoice 5555 is posted against invoice reference number 1234 for vendor XYZ on document date 28.12.2011.
Invoice 6666 is posted against invoice reference number 1234 for vendor XYZ on document date 11.01.2012.
In the above scenario - does it mean that the double invoice could go thorugh as the system checks the settings based on the combination of invoice refernce number and document date (for vendor vendor XYZ).
In other words - is it because the system found IV reference number 1234 on different dates that double invoicing could go though.
Please suggest.
Regards,
Soujanya.

Hi,
Ok...inspite of having same invoice refrence number - as they were interfaced on different dates, it has not checked for double invoice. In that case, to avoid such things to happen - I hope I should uncheck the document date in OMRDC and just retain invoice reference numbers and company code.
As far as the account key is concerned - ERL postings do not happen here as this is a case of purchases. However, could you suggest what is MRRL and where can I find it. And what is the siginificance of MRRL in GR.
Regards,
Soujanya.

Double Invoice Check

Hi
How do we set the double invoice check in SPRO for Invoice Number and Reference field for Vendor Incoming Invoices
Regards
Sanil Bhandari

Hi,
Please go to vendor master > Payment Transaction Tab
Check the Double Invoice option...
System will carry out checking as mentioned below:
Checking Logistics documents
Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
Checking FI documents
The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
Checking Logistics documents
In checking for duplicate invoices, the system compares the following characteristics by default:
Vendor
Currency
Company code
Gross amount of the invoice
Reference document number
Invoice document date
If all of these characteristics are the same, the system issues a message that you can customize.
When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
No message is issued if you enter a document that has previously been reversed.
Dependencies
The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
Reference document number
Invoice document date
Company code
This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
I Hope u found useful
Please Reward Points if Found Useful
Regards,
Jigar

Double invoice entry at the FI Level

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

> 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

Double Invoice Verification

Similar Messages

Maybe you are looking for