The benefits of implementing supplier invoice management with an agile | cullen4congress

The benefits of implementing supplier invoice management with an agile approach

Supplier Invoice Management OpenText™ for SAP® Solutions (VIM) is a leading invoice processing and management solution that fully integrates with SAP. The solution streamlines and automates end-to-end processing from receipt to delivery through intelligent data enrichment, rules, functions, and pre-configured actions. The product includes solutions for the Purchase to Pay and Order to Collect processes, as well as to support any custom document processes.

Project methodologies have moved from the classic waterfall model to a more agile project approach in recent years. In the context of VIM, this enables earlier and deeper engagement of IT and business users in your future document processing solutions. The benefit of increased involvement during implementation is an invoice processing setup perfectly tailored to customer requirements and better change management and adoption.

OpenText Professional Services project managers and consultants implementing invoice management projects have been able to use an agile approach methodology for years: the VIM for FasTrak invoice processing package it provides a useful framework to stay focused while remaining completely flexible and efficiently achieve the common goal using the agile methodology at the same time.

Let’s look at how an agile project approach benefits supplier invoice management projects, using the Scrum framework as an example.

A quick introduction to Scrum

Scrum is a lightweight framework for creating solutions to complex problems. In increments, also known as sprints, which typically last two weeks, the project team moves toward a common goal. Brief daily meetings with all team members ensure that everyone is on the same page and that blockages can be removed efficiently. [1]

Sprint Planning

Sprint Planning is a collaborative meeting in Scrum where the team works together to determine what can be delivered in the next sprint. The team chooses items from the product backlog, breaks them down into actionable tasks, estimates effort, and commits to delivering a product increment at the end of the sprint. [2] This allows the entire team, including business users and consultants, to focus on individual functions with their full attention instead of gradually processing many tasks in parallel. In a complex process like invoice processing, it is essential that both the company have a comprehensive understanding of the solution and that the consultants have a comprehensive understanding of the business objectives.

Separating individual features into user stories, prioritizing them, and discussing them at the appropriate time allows both parties to have the necessary understanding. The result is a solution that is more tailored to the needs and ensures that business users have a deeper understanding of what is configured for them.

stand up meetings

Holding daily meetings, also known as stand-ups, with all team members helps ensure that everyone is aligned and working toward the product goal. [3] In addition to sharing status with everyone, this also helps identify and resolve impediments to progress early and quickly. This benefits the project from installation to commissioning, as all issues, including marginal ones, are not forgotten, but can be efficiently discussed and resolved when each project member has the latest information.

Sprint Review

Presenting sprint results after each sprint invites early feedback from project stakeholders. This ensures that the project team is headed in the right direction and that a clear focus on the product goal is always present. [4]

In an example of one of the Professional Services day-to-day projects at a large retail company, stakeholders were very pleased when the bill reduction feature was introduced during a sprint review, but noted that the following should be adopted. texts and design. Therefore, the requirement was identified right after implementation and at an early stage of the project and was directly realized in the next sprint.

Sprint Retrospective

Retrospective meetings give the project team time to reflect at the end of each sprint. [5] At the meeting, each team member can share what worked well in the sprint and where there is still potential for improvement. Optimal collaboration is a key factor for project success.

He Professional services The OpenText team has mastered the technology behind VIM to perfection and our business consulting is always at the forefront to make the most of the powerful technology behind VIM. We support clients in decision-making by finding out together if the product standard is suitable for their company’s processes or if additional adjustments are needed in the project to achieve a tailor-made solution.

While Vendor Invoice Management Projects were classically implemented using the waterfall project approach, the OpenText Professional Services product and methodology are 100 percent compatible with using an agile approach that takes full advantage of its benefits.

Are you interested in starting an agile supplier invoice management project? Contact us!


[1] Schwaber, K. & Sutherland, J. (2020, November). The Scrum guide. scrumguides.org. Retrieved May 4, 2023 from https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

[2] Schwaber, K. & Sutherland, J. (2020, November). The Scrum guide. scrumguides.org. Retrieved May 4, 2023 from https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

[3] Schwaber, K. & Sutherland, J. (2020, November). The Scrum guide. scrumguides.org. Retrieved May 4, 2023 from https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

[4] Schwaber, K. & Sutherland, J. (2020, November). The Scrum guide. scrumguides.org. Retrieved May 4, 2023 from https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

[5] Schwaber, K. & Sutherland, J. (2020, November). The Scrum guide. scrumguides.org. Retrieved May 4, 2023 from https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf