Status Check in Admin Tool for Monitoringīelow are some of the statuses you can find in transaction code /n/OPT/VIM_7AX8 Admin Tool for Monitoring. You can read more about the 3-way match in the linked reference. In concept, the 3-way match prevents us from incorrect payments and (in a way) prevents transaction with fraudulent invoices. We also want to ensure that we do not double pay or have duplicate payments. At the end of the day, we need to pay the vendor accurately. When we talk about the Accounts Payable process, recall that this process involves payment. …Okay, so why do we have to do this 3-way match? …What is the purpose of the 3-way match anyway?
Invoices are sent to SAP electronically which can be viewed as IDocs. WE10 in this case, will help you search for a specific IDoc. You will notice a general transaction code for IDocs “WE10” in the process below because you are expecting an inbound IDoc. Overall, invoice details will be sent to SAP by EDI which will trigger the usual process of processing data, checking for duplicates, so on and so forth. One good example is through the use of IDocs or Intermediate Documents. Instead of dealing with scanning and OCR, invoices can be sent electronically to SAP (thus, the concept of e-invoicing) through EDI or Electronic Data Interchange. This means that all steps are within SAP. In comparison to the previous process flow, you will notice that the green dotted lines cover the whole e-invoicing process. Payment proper will be triggered utilizing the posted SAP document. n/OPT/VIM_WP (VIM Workplace) /n/OPT/VIM_ANALYTICS (VIM Analytics) FB03 (View FI Document) If fully approved, SAP document will be posted. n/OPT/AR_COA (Chart of Authority) /n/ORS/MAIN_SUBS (Substitution Maintenance) /n/OPT/VIM_WP (VIM Workplace)Īpproval Process. n/OPT/VIM_7AX8 (Admin Tool for Monitoring) /n/OPT/VIM_WP (VIM Workplace)
#OPEN TEXT WORKFLOW VERIFICATION#
Verification / duplicate checks happen for the invoices in SAP. Scanning proper using ICC tool to interpret the document image and convert it to system text. Invoices are prepared as a pre-requisite for scanning. Automated paper to post invoice management (with OCR) process # You can think of this as a separate server or environment where the scanning of invoices take place. The orange dotted lines indicate that this process happens outside of SAP – specifically in the ICC or the Invoice Capture Center. You will notice that in the process diagram below, the invoices need to be prepared and then scanned before it reaches SAP. This process involves the optical character recognition component of OpenText VIM. Integration of standard SAP functionalities such as invoice verification, financial processing, etc.Īutomated paper to post invoice management (with OCR) process.Take note that in this packaged solution, you can expect features such as: OpenTextĪs such, we can expect several vendor invoices in SAP managed through VIM for further processing. Stakeholders involved in any invoice problem can quickly and efficiently access invoice information, such as relevant PO number, status of invoice payments and more. OpenText™ Vendor Invoice Management for SAP® Solutions (VIM) optimizes and simplifies the process of receiving, managing, routing and monitoring invoices and related documentation. In case you need an overview on the accounts payable process, you may refer to “ SAP CHEAT SHEET: Basic Accounts Payable / Procure to Pay Process”.įrom the OpenText website, VIM for SAP is formally defined below. In this post, we will cover the basic end to end process of VIM for SAP and each of the transaction codes.įor now, let us focus on the keyword’s “vendor” and “invoice”. OpenText VIM or Vendor Invoice Management is associated with the accounts payable process.
0 kommentar(er)
