If you experience an issue with bookings for an invoice in MediusFlow please contact the Medius support. Examples of booking issues:
- One or more preliminary or final booking(s) is not sent to the ERP.
- One or more preliminary or final booking(s) has been sent to the ERP, but the invoice(s) is still waiting for a voucher response in MediusFlow.
- You are receiving an error message when a booking is sent to the ERP.
- The invoice does not look the same in terms of amounts, coding or other information in the ERP compared to MediusFlow.
Please note that there are several solutions available in our success portals FAQ section. Searching the FAQ section is a good way to start troubleshooting the issue.
Please make sure to provide a detailed description of the problem. We recommend summarizing any internal e-mail conversations for us to get a better understanding of the problem. This will facilitate the Medius support to better help you.
Submit the following information:
- Which invoice(s) are having the problem. Provide invoice number and document ID. If it is a large amount of invoices, a few examples are enough.
- What activity or step were you performing when you experienced the problem?
- When did the problem occur? Provide date and time. Please include time zone, this makes it easier for Medius support to navigate logs.
- Did any error messages appear? If so, please include the error message, if still available.
- What is the status of the invoice in your ERP?
- Is there an error message in MediusFlow where the text is “Error message from ERP”? This indicates that the error message can come from your ERP. If this is plausible, please discuss this error message with your ERP resources and provide their feedback as well.
Please include screenshots if it helps describing the issues you are experiencing.
Examples of integration booking related FAQ items:
What to do with an invoice that is stuck in the integration step?
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article