Do you have any question about this error?
Message type: E = Error
Message class: M8 - Invoice Verification/Valuation
Message number: 698
Message text: Invoice document & was posted and blocked for payment ( & & )
Error message extract from SAP system. Copyright SAP SE.
The SAP error message M8698 indicates that an invoice document has been posted but is blocked for payment. This can occur for various reasons, and understanding the cause is essential for resolving the issue. Here’s a breakdown of potential causes, solutions, and related information:
Causes:
Blocking Reasons: The invoice may be blocked for payment due to specific reasons set in the system, such as:
- Missing or incorrect purchase order (PO) reference.
- Invoice verification issues.
- Discrepancies between the invoice and the PO (e.g., price or quantity differences).
- Manual blocking by a user or due to a workflow process.
Account Issues: The vendor account may have issues, such as:
- The vendor is blocked for payment.
- The vendor has exceeded credit limits.
Configuration Settings: Certain configuration settings in the SAP system may lead to automatic blocking of invoices based on specific criteria.
Incomplete Data: Required fields or data may be missing in the invoice document.
Solutions:
Check Blocking Reasons:
- Use transaction code MRBR to analyze and release blocked invoices. This transaction allows you to see the reasons for blocking and take necessary actions.
Review Invoice and PO:
- Verify the invoice against the corresponding purchase order. Ensure that the quantities, prices, and other details match.
- If discrepancies exist, correct them in the invoice or PO as necessary.
Vendor Account Review:
- Check the vendor account status using transaction code XK03 or MK03. Ensure that the vendor is not blocked for payment and that all necessary data is complete.
Consult with Finance Team:
- If the issue is related to financial settings or configurations, consult with your finance or accounting team to ensure that all settings are correct.
Release Block:
- If the invoice is blocked due to manual intervention, you may need to release the block manually if you have the necessary permissions.
Check Configuration:
- If the issue persists, review the configuration settings related to invoice verification and payment blocking in the SAP system.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed information on invoice verification and payment processes.
User Roles: Ensure that the user attempting to release the block has the necessary authorizations to do so.
By following these steps, you should be able to identify the cause of the M8698 error and take appropriate action to resolve it. If the problem persists, consider reaching out to your SAP support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
M8697 Invoice document & was posted ( & & )
Self-Explanatory Message Since SAP believes that this specific error message is ...
M8696 Enter an invoicing party
Self-Explanatory Message Since SAP believes that this specific error message is ...
M8699 Document canceled under number &. Clear FI documents manually ( & & )
What causes this issue? The invoice was successfully cancelled. However, the FI...
M8700 ************************ Messages from reports ***************
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.