MIGO is for Goods Movements. for detail explanation, please check this link. MIRO is for Logistics invoice verifications.
This transaction is for Invoice verification step in a typical Procurement scenario for your vendors. This generally follows goods movement step when you receive the goods from your vendor and post via MIGO. MIRO is used for posting vendor invoice.
MIRO is a transaction code used for Enter Incoming Invoice in SAP. It comes under the package MRM. When we execute this transaction code, SAPLMR1M is the normal standard SAP program that is being executed in background.
MIGO and MIRO are part of procure to pay cycle where MIGO means a Goods Receipt, here your stock will be increased and an entry will be passed to intermediate GRIR account . Accounting entry. Stock Debit. GR/IR account Credit. And MIRO means an Invoice Receipt, here liability is created against the vendor.
Business process– Fb03 is used to display a document. It is one of the most commonly used transaction codes. FB03 is used to display finance documents only. Suggestion– Add this tcode to your favorites. Menu Path- Accounting-Financial Accounting-General Ledger-Document-Fb03 Document Display.
MIRO: How to Perform Invoice Verification in SAP
- Enter transaction code MIRO. Choose invoice as a transaction type. Enter the invoice date. Enter the purchase order number. Hit ENTER.
- On Payment tab choose R - invoice verification.
SAP Hold MIRO transaction and posting by another person after checking.
- Use TR "MIRO" for entering Invoice at first stage.
- Use TR "MIRO", Click on "Show Worklist".
- Select that held invoice document and double click on it and "Simulate" as regular after checking (e.g. other person).
- Then Post/save it.
Once goods are procured from a vendor and placed in company's premises through goods receipt, we need to pay to the vendor for the acquired goods and services. The amount to be paid along with the details of the material is provided by the vendor in the form of a document that is known as the invoice.
Creating Screen Variant
- First, run the transaction SHD0.
- Now please choose the transaction for which you want to create a variant, let say you choose FB50 (program SAPLFSKB) now go to the screen variant tab and choose a name for the screen variant to select the program and the screen.
When an invoice is blocked, Financial Accounting cannot pay the invoice. Invoices can be blocked either automatically or manually. When you enter an invoice, the system suggests the values that it expects an invoice to contain as a result of the purchase order or goods receipt.
You can
test a
release strategy used by the purchasing document by clicking the "
Release Strategy" button on the above screen.
Step 2) You will see the list of purchase documents available for release cancelation.
- Choose the appropriate document.
- Click on the Cancel release button.
- Save and you are done.
The use of the payment block “A” to automatically set Down Payments blocked for payment. When posting a down payment, SAP system define the block A for that sub-ledger line items to avoid Automatic Payment Process to clear this open item with other offsetting open items.
An “R” in the payment block field occurs when an invoice exceeds the agreed upon purchase order line item price by 10% or more requires verification of the invoice amount. The department should then determine whether the invoice amount is correct and have the excess amount approved prior to removing the payment block.
An invoice can be blocked for payment due to one of the following reasons: Variance in an Invoice Item. Amount of an Invoice Item. Stochastic Block.
MRBR is a transaction code used for Release Blocked Invoices in SAP. It comes under the package MRM. When we execute this transaction code, RM08RELEASE is the normal standard SAP program that is being executed in background.
Select the Payment transactions view in the Company code data section of the screen and choose Enter. The Change Vendor: Payment Transactions Accounting screen appears. Set the blocking key in the Payment block field in the Automatic payment transactions field group.
Open item is created by different postings, And when payment is received against the specific invoice then you use the tcode F-53, which clears the invoice line items .
Tcode – OMR4.Click on “Document types in Invoice Verification” tab. Select the “MIRO” transaction code line and display its details. The tab highlighted in yellow is where we maintain the document type for Retention process which will then flow while we are Invoicing the Purchase order.
A document type definition (DTD) is a set of markup declarations that define a document type for an SGML-family markup language (GML, SGML, XML, HTML). It defines the document structure with a list of validated elements and attributes. A DTD can be declared inline inside an XML document, or as an external reference.
SAP Document Types & Numbers
| Accounting Services Department (Grants) (x7361) |
|---|
| Doc. Type | Description | From Number |
|---|
| AB | Accounting Document | 100000000 |
| AF | Dep. Posting | 3000000000 |
| SA | G/L Account Document | 100000000 |
Document Types in the Standard System
| Document Type | Description |
|---|
| CO | CO posting |
| DG | Customer credit memo |
| DZ | Customer payment |
| DR | Customer invoice |
How to Define Document Type and Number Range in SAP FICO
- Enter a unique Document Type Key.
- Enter the Document Type description.
- Select a number range for the Document Type.
- In Account Type Allowed Section , select the Account type which you would like to do posting.
- Enter Appropriate Selection in the Control Data Section.
Enter the group table field for
number ranges here, if you want the application to support one
number range only (external or internal).
Change a Number Range Object
- Call the number range transaction ( SNUM or SNRO ).
- Enter an object name and choose Change.
- The following fields can be changed:
Create a New Document Type
- Click Menu.
- Click Document Types .
- Under Configuration:Document Types dashboard, click Add New Document Types .
- In the Create: Document Type, enter the Name of the document type, and select a color for the document from Document Type Color drop down menu.
- Click Document Schema tab.
A Number range is a Group of numbers to which the unique-Id created for an SAP Object belongs. There are 2 categories of number ranges: Internal numbers: These are purely numbers. System generates the number (within the range you've specified) next to the immediate previous allotted number.
Posting Keys :– Posting key in SAP is a two digits numerical key that determines the type of transaction entered in a line item. Posting keys in SAP controls the entries in a line item of document entries. It determines account type to post i.e. amount should be posted on debit side or credit side.
Maintaining a Number Range Object
- Call the number range transaction (SNUM or SNRO).
- Enter an object name and choose Create. An input window appears where you can enter the development class in which you want to save the number range object.
- Enter a development class and choose Save.
- To define the number object, make entries in the following fields: