Unit 6: Invoice Verification – Further Customizing
Beyond tolerances and blocks, a number of Customizing settings shape everyday LIV work: message control, automatic account determination, number ranges for MM and FI documents, PO text notification, bar-code entry, the duplicate-invoice check, output determination and user authorizations/tolerance groups.
Lesson 1 · Adjusting Further Customizing Settings in Invoice Verification
After this lesson you can
- Change attributes of system messages
- Explain account determination and number assignment for LIV documents
- Configure PO text notification, bar-code entry and duplicate check
- Describe output (message) determination and user authorizations
1. System messages (OMRM)
For selected LIV messages you can choose the message category – information, warning, error, or suppressed – either for all users or for individual users ("Message control by user"). SAP predefines which messages are changeable and which categories are allowed for each.
SPRO › Materials Management › Logistics Invoice Verification › Define Attributes of System Messages (OMRM)
2. Automatic postings (OMR0 / OBYC)
At posting, the system determines the business transactions (transaction keys) involved and finds the G/L accounts per chart of accounts (assigned to the company code). For some keys the account can further depend on the valuation grouping code / valuation class (valuation area) and the debit/credit indicator. Keys relevant for LIV include:
| Key | Meaning |
|---|---|
WRX | GR/IR clearing |
BSX | Inventory posting |
PRD | Price differences |
KDM | Exchange rate differences (materials) |
DIF | Small differences, Materials Management |
RKA | Invoice reduction (clearing) |
UPF | Unplanned delivery costs |
FR1/FR3 | Freight / customs clearing (planned delivery costs) |
KON | Consignment payables |
PPX | Prepayment clearing |
SPRO › Materials Management › Logistics Invoice Verification › Configure Automatic Postings (OMR0)
SPRO › Materials Management › Valuation and Account Assignment › Account Determination
3. Number assignment
| Document | Controlled by | Customizing |
|---|---|---|
| MM invoice document | Transaction RD (manual entry) or RS (system-generated: reversal, ERS, EDI, invoicing plan, revaluation) → number range; intervals defined per "to year" | Maintain Number Assignment for Logistics Documents › Transaction – Assign Number Range; Maintain Number Range Intervals (OMRJ) |
| FI document | Document type proposed per LIV transaction (separately for secondary documents such as the invoice reduction credit memo). The document type carries the number range (per company code and year) and controls net vs. gross posting, allowed account types and whether a reference is required. Standard: RE gross, RN net. | Maintain Number Assignments for Accounting Documents (OMR4) |
| Account maintenance (MR11) | Same logic; FI document type KP; logistics transactions KP (account maintenance) and KS (cancel account maintenance) | Clearing Account Maintenance › number assignment activities |
SPRO › Materials Management › Logistics Invoice Verification › Incoming Invoice › Number Assignment › Maintain Number Assignment for Logistics Documents › Maintain Number Range Intervals for Invoice Documents (OMRJ)
SPRO › Materials Management › Logistics Invoice Verification › Incoming Invoice › Number Assignment › Maintain Number Assignments for Accounting Documents (OMR4)
4. Notification of PO texts (OMR8)
Decide whether the invoice clerk gets a message that the PO contains header texts, and for which text types – only texts relevant to invoice checking (e.g. special payment agreements) should trigger it.
SPRO › Materials Management › Logistics Invoice Verification › Incoming Invoice › Edit PO Supplement Text in Invoice Verification (OMR8)
5. Bar-code entry
When paper invoices are scanned into an archive, a bar code links the archived image to the invoice document. In LIV Customizing assign an SAP ArchiveLink document type to the FI document type (company-code dependent); in FI Customizing activate bar-code entry and its check per document type and user.
SPRO › Materials Management › Logistics Invoice Verification › Incoming Invoice › Maintain Bar Code Entry
SPRO › Financial Accounting › Document › Bar Code Entry › Specify Control Parameters for Bar Code Entry (OAC5)
6. Duplicate invoice check (OMRDC)
If the supplier master has Check double invoice set (company code data) and a reference is entered, the system looks for an existing invoice with the same company code, supplier, reference, invoice date, amount and currency. Supplier, amount and currency are always compared; whether company code, reference and invoice date are included is configurable. A full match raises message M8 108 (information or error, depending on settings). Example: reference a2b3c4 already exists; a new invoice with ab23c4 is flagged as possible duplicate only if reference is not a check criterion – which catches typing errors in the reference.
SPRO › Materials Management › Logistics Invoice Verification › Incoming Invoice › Set Check for Duplicate Invoices (OMRDC)
7. Message (output) determination
LIV uses condition technique like Purchasing and Inventory Management. Typical output types:
| Output type | Purpose |
|---|---|
MLPP | Mail to the purchaser when a price variance occurs (Define Mail to Purchasing When Price Variances Occur, OMRK) |
KONS / KONS6 (EDI) | Consignment settlement statement |
ERS / ERS6 (EDI) | ERS and invoicing plan settlement statement |
INS | Invoicing plan: statement of due payments |
REKL | Invoice reduction (complaint letter) |
SPRO › Materials Management › Logistics Invoice Verification › Message Determination
SAP S/4HANA Output Management (BRF+-based output determination, Fiori integration, flexible e-mail templates, Adobe forms via SAP Forms service) is available alongside the classic condition-technique message control. It is optional for LIV in on-premise; existing NAST-based output keeps working. In purchasing, new implementations increasingly use the new framework.
8. Authorizations and user tolerance groups
Authorization objects/profiles restrict per user: company codes and plants for which invoices may be posted, blocking reasons the user may delete (M_RECH_SPG), and whether variances without item reference may be accepted manually (M_RECH_AKZ). In addition, each user can be assigned an LIV tolerance group that defines the maximum invoice amount and the maximum cash discount percentage the user may post.
SPRO › Materials Management › Logistics Invoice Verification › Authorization Management › Define Tolerance Groups (OMRB)
SPRO › Materials Management › Logistics Invoice Verification › Authorization Management › Assign User Tolerance Group (OMRC)
- Duplicate check criteria: company code, supplier, reference, invoice date, amount, currency – not purchasing organization or account assignment. Indicator in the supplier master; optional criteria in OMRDC.
- User tolerance group: maximum amount and maximum cash discount rate (OMRB/OMRC) – not supplier groups.
- MM number range via transactions
RD/RS; FI numbering via document type (REgross,RNnet) in OMR4. - Account determination is per chart of accounts; OMR0 is the LIV entry to the same settings as OBYC.
Unit summary & exam focus
T-codes in this unit
| T-code | Purpose |
|---|---|
| OMRM | Attributes of system messages |
| OMR0 | Configure automatic postings (LIV) |
| OBYC | Automatic account determination |
| OMRJ | Number ranges for invoice documents |
| OMR4 | FI document types / number assignment |
| MR11 | GR/IR account maintenance (number assignment KP/KS) |
| OMR8 | PO text notification in LIV |
| OAC5 | Bar-code entry control (FI) |
| OMRDC | Duplicate invoice check criteria |
| OMRK | Mail to purchasing for price variances |
| OMRB | Define user tolerance groups |
| OMRC | Assign user tolerance groups |
Self-check questions
- Which fields does the duplicate invoice check compare?
Answer
Company code, supplier, reference, invoice date, amount and currency (company code, reference and date can be excluded in Customizing). - What controls the number range of the FI document created by LIV?
Answer
The FI document type proposed per transaction in OMR4; the document type holds the number range. - What is the difference between transactions RD and RS for MM invoice numbering?
Answer
RD = manually entered invoices; RS = system-generated documents (reversal, ERS, EDI, invoicing plan, revaluation). - What can a user tolerance group in LIV restrict?
Answer
The maximum invoice amount and the maximum cash discount percentage a user may post. - Which output type informs the buyer about price variances?
Answer
MLPP, configured via OMRK. - Can you make a warning in MIRO an error for one user only?
Answer
Yes, for messages SAP marks as changeable, via user-specific message control in OMRM.