Why might a manual (high security) approval lead to an unmatched transaction in EMIS Web, and how can I prevent this scenario?

Manual (high security) approval in EMIS Web is used in circumstances where an error needs immediate resolution without the automatic transmission to external trading partners. This can lead to unmatched transactions when, for example, the Health Authority approves the transaction differently, which EMIS Web does not automatically reconcile.

Why Does This Happen?

The most common cause of an unmatched transaction occurs when the Health Authority has processed an approval or deduction ahead of EMIS Web manually and subsequently sends an acknowledgment that does not match the record in EMIS Web.

Did you know? Manual high-security functions are essential for resolving registration errors internally without affecting external records immediately. They ensure that any errors identified can be rectified swiftly, maintaining accurate records and preventing a backlog.

Preventing Unmatched Transactions

• Check Trading Partner Acknowledgments: Always check for acknowledgments from your trading partners before performing manual operations to ensure no conflicts occur.
• Update Records Promptly: Make sure that manual changes are updated both locally and acknowledged by trading partners where applicable.
• Communicate With Health Authorities: If unmatched transactions occur, contact your Health Authority with the transaction details to reconcile any discrepancies.