The Problem: Concur allows users to charge transactions to projects. The field used to enter projects is free form text. The entity required project entries to follow a specific nomenclature for automated loading into the Oracle Projects module. The free form text format presented a challenge. Without correct input, the project field would fail validation resulting in costly rework and/or manual intervention.
The Approach: The free form text field was the main item to address. Since the field was going to be loaded directly into Oracle, we needed to create a standard entry format to pass validation. Working with key users and the local accounting team, we identified a nomenclature that would split projects off from tasks. Using unique identifiers throughout the string, the process that extracted information from Concur correctly populated the Project and Task fields in Oracle Projects. We conducted training classes and provided print screen work instructions.
The Result: Most users adapted quickly to the new format. Accounting Review identified any reports with incorrect Project-Task strings. Accounting review returned incorrect reports. Rework and payment delays were the impetus to users embracing the new format. Soon after go live we achieved virtually 100% first time, zero defect compliance. Covering three years and hundreds of expense reports the process is an unqualified success.
The Approach: The free form text field was the main item to address. Since the field was going to be loaded directly into Oracle, we needed to create a standard entry format to pass validation. Working with key users and the local accounting team, we identified a nomenclature that would split projects off from tasks. Using unique identifiers throughout the string, the process that extracted information from Concur correctly populated the Project and Task fields in Oracle Projects. We conducted training classes and provided print screen work instructions.
The Result: Most users adapted quickly to the new format. Accounting Review identified any reports with incorrect Project-Task strings. Accounting review returned incorrect reports. Rework and payment delays were the impetus to users embracing the new format. Soon after go live we achieved virtually 100% first time, zero defect compliance. Covering three years and hundreds of expense reports the process is an unqualified success.
RSS Feed