Duplicate invoice check

[former_member193587]

Hi experts,

Presently i configured duplicate invoice check for miro .Now system checks these parameters.

Vendor

Currency

Company code

Gross invoice amount

Reference document number

Invoice date.

& if repeat same reference number it create error massage. But suppose i put reference number 1212 with document date 31-07-2013

& for second document suppose i enter reference number 1212 with the date 01-08-2013 system allow to post invoice. So query is suppose date is different but reference number is same ,system should restrict to post invoice.Please help to achieve this.

Regards

ragini

[BijayKumarBarik · Accepted solution]

Hi,

Use t.code: OBA7  and keep "Reference number" mandatory in 'Required during document entry segment' for "RE" document type.

AND

Use t.code: OMRM,Set Error message for  message number M8 -108 & M8 - 462 and save.

Regards,

Biju K

[former_member193587 · Accepted solution]

hi

i already do this configuration, but vendor send double invoices with same reference number on two different date, so we have to avoid duplicate vendor payment.

Regards

Ragini

[BijayKumarBarik · Accepted solution]

Hi,

The above message numbers will work for duplicate invoice for vendor and also check – you set above message numbers as Error in t.code:OBMSG.

The above message numbers works for restriction in reference number field - You can save to create 1st invoice by entering 1212 in reference number field and later you cannot save any invoice by entering 1212 in reference number field.

In your case, if you got two invoices for goods receipt quantities for a purchase order, then receive 1st invoice by entering 1212- I in reference number field and later receive 2nd  invoice by entering 1212-II in reference number field.

Regards,

Biju K

[JL23 · Accepted solution]

Wouldn't this desired fake entries open the door for the user to get around any error message that comes up? This turns the control useless, instead of start thinking most users would just use the way of the least resistance and just change the number like that.

[BijayKumarBarik · Accepted solution]

The above messages setting are available to triggers error message for duplicate invoice if users enter again same text in reference number field.

Fair enough, this process may result fake entries but sometimes, business situation* arises for business to do so!

* Business situation where vendor sends two time goods and send invoice by courier with one invoice number for two times goods supply. In this case business done one goods receipt (MIGO) and one invoice receipt but forgot to enter 2nd goods receipt (MIGO).In this case business can go for quickly goods receipt for 2nd supply  and can go for invoicing process as explained my above reply.

Depends on business how they handled the above process  for  fake entries OR go for restriction - In general, the MIRO transaction handled by finance department. With addition, if business wants can set message M8 -087 & M8 -081 for restricting MIRO to post greater than PO values and quantities

[former_member187965]

Hi,

System behavior seems correct to me. Let's assume, vendor resets invoice number range after fiscal year change and you receive same invoice number but date is different then as per your logic system will restrict invoice posting, then how will you post invoice ? So, from business point of view, it's logical to allow invoice posting, if invoice date is different.