Heard at SAP Sapphire

I recently attended and presented at the annual SAP Sapphire conference in Orlando. I expected to see strong interest in optimization of back office functions but after years of attending this event, I was amazed to see the high level of interest specifically around invoice process optimization. One personal example…I conducted a micro forum related to SAP Invoice Management where we expected 10 -15 people…the final attendance was 60 people.
In discussions with many of the attendees, I found a significant growth interest related to vendor networks such as provided by Crossgate and dynamic discounting (DD). The adoption of DD will drive corporations to invest in solutions such as SAP Invoice Management to ensure they achieve a high rate of straight through processing. DD will also require invoice exception processing to occur in very few days as opposed to weeks.
I also see the increased adoption of vendor networks driving standardization of invoice meta data content and format; not unlike what edi has driven in the past. This will be slow to evolve but I think will eventually happen.
One topic that caught my attention…Shared Service. While not a new topic, I feel a combination of searching for efficiency gains and control combined with merger and acquisitions has created renewed interest in shared services. The major difference this time around is focus is on utilizing technology and out of the box solutions such as SAP Shared Services Framework & SAP Invoice Management as opposed to prior efforts that focused on moving to less expensive labor pools.

Accounts Payable and Social Networks

I recently attended a presentation related to how Accounts Payable Departments might utilize social networks. This really got my attention since we at OpenText have long considered social networks as a means to enhance sharing of information ranging from individual contributions through departmental actions to corporate messaging. Open Text provides a tool “Pulse” as part of our ECM solution to assist with information sharing.
By using Pulse, organizations can take advantage of a Facebook-like social media environment within their existing Open Text ECM Suite deployments and move informal communications out of email, thus dramatically reducing dependence on inefficient and slow email chains. Additionally, it offers a way for people to collaborate rapidly in real time, while creating a secure knowledge base for new employees and team members. Pulse is a major step toward enabling customers to capture their organizational memory through the archival of formal and informal user conversations.
So…how can those in the business process around Invoice Processing utilize social networks? While I believe the use is unlimited, I will focus on a few examples.
Individual Information Sharing or what would an Accounts Payable Professional want others to know. By using tools like Facebook, Twitter, Pulse, etc an individual can inform others when they will be out of the office or they may want to share recently achieved Professional certifications. They may want to inform a group such as selected suppliers of upcoming requirement changes. Information might be shared with internal clients on payment activities.
Departmental Information Sharing – The department may want to share internal statistics such as on time payments and discounts earned. They can recognize those process participants that helped to achieve new success with invoice processing. The department may want to announce staffing changes such as retirement, promotions or transfers. They may want to create groups for selected participants such as procurement so they can immediately address resolutions being handled with SAP Invoice Management. For me, I am now able to know if one of my colleagues is traveling to the same event that I may be attending. I can also see when colleagues are on vacation…live vicariously through their adventures…makes my work day a little more pleasant.
Corporate Information Sharing – Your shared service center may want to utilize social networks to introduce policy changes to both internal and external clients. As with the Department, they may want to announce staffing changes. They may desire to communicate real time with internal Accounting Departments related to closing activities such as accruals. The use of the OpenText Pulse would be a great tool to increase the visibility of current policies and regulations. I for one monitor real time changes to travel budgets as well as new presentations that others may have saved to the content server. I don’t have to wait and hope I receive an email telling me about new presentations.
Let me know…how are you using social networks to improve your corporate contribution?
For more information on SAP Invoice Management http://ecohub.sdn.sap.com/irj/ecohub/solutions/SAPVIM
For more information on OpenText Pulsehttp://www.opentext.com/2/global/products/products-collaboration/products-opentext-extended-collaboration.htm

Electronic Invoicing…A Dog Chasing the Car

What is Electronic Invoicing? Just a simple search of the internet provides several answers. What is the correct way to write the term…spell it out or abbreviate with big E or little e? Does this relate to outbound invoices or inbound invoices? Is this just EDI? I ask for your comments based on my observation below…when you hear e-invoice…what comes to mind?
For my comments, I will use e-invoice and assume it relates to inbound invoices and I will assume that SAP is the backend solution. Invoices can be received electronically through several methods. EDI has been around for many years and seemed to have reached its peak. Most major trading partners were EDI enabled. EDI also requires a specific internal skill set to maintain. The maturity of EDI provides a proven electronic methodology but somewhat relegated to large corporations. Both large companies and small to mid size receive invoices through direct loads from vendor website and upload of files sent from Vendors. The direct link to Vendors is common with purchasing cards while files uploads are common with utilities. All of these electronic methods have in common the elimination of mail room activity and manual data entry. Another commonality is that all may still contain errors in the invoice meta data. Some consider fax or email attachment as electronic but both of these typically require first capture of the image and from that point they are handled the same as paper invoices.
There is a current trend to consider electronic invoice presentment and payment (EIPP) to be e-invoicing as provided by vendor networks. These networks accumulate invoices (typically those invoices still received by paper) from multiple Vendors and then submit them to the respective multiple clients…a many to many relationship. While these networks continue to be unique to specific providers, it is assumed they will eventually provide the ability to “roam” similar to cell phone networks.
Regardless of how a corporation receives e-invoices, it is how you process the header and line item meta data that creates significant additional value to e-invoicing. Moving from paper to e-invoice does not eliminate the vendor from providing incorrect meta data. It does not remove the labor required to correct invoice meta data, to route for approval or to report on the overall end to end processing. It does not provide the necessary process control or audit trails. SAP not only provides the vendor network capabilities through their Crossgate solution, they also provide SAP Invoice Management which is designed to work with all forms of e-invoice.
So not unlike the dog chasing the car…it is what you do with it when you catch it that makes the story most interesting.

See SAP EcoHub for more information on SAP Invoice Managment

Paper Invoices Can Be Best Practice

I am often ask by corporations “what is best practice for invoice receipt…paper, vendor networks, EDI, direct uploads, vendor portal ?”…and the answer is YES. Most corporations rely on multiple invoice input channels. That often prompts the reply…”you included paper as best practice…are you sure?”
While electronic communication has long been best practice for almost every aspect of our businesses, invoices continue to be generated primarily as paper. The obvious negatives related to filing and retrieval of paper is compounded by the variability of the paper. This variability includes where the data is located on the invoice such as purchase order number, the quality of the paper, the quality of the printer, handling during transmittal (folding, staples, getting wet), handling after transmittal (tears, coffee cup rings, more staples) and the addition of meta data such as a time stamp showing date received or hand written notes. But on a good note I am sure that ALL your invoices are in one language and one currency? Add to this the simple task of routing the paper with in a business process (isn’t land mail great!) and you have all the necessary ingredients for making a bad process.
It might be ask that how can this be considered a bad process since paper invoices are currently used by most successful corporations.
It is not how you receive invoices but how you work with them. How you capture and use this business content is what takes you down the path of best practice or bad practice. It is the header and line item meta data that is important in the Accounts Payable processing and not the document itself. The paper is obviously just a mechanism to convey the meta data. Best practice requires that you immediately scan and store the image while linking to the accounts payable posting within the accounting system. The content will be electronically extracted from image, tested and corrected to ensure accuracy and completeness and then automatically posted. The invoice is the result of procurement, which is the component of a larger business transaction that required the purchase. It is necessary to also link the structured AP document to additional structured documents such a purchase order and unstructured information such as contained in emails related to the purchase. It is also a requirement that the AP information be addressed by corporate record retention.
Since best practice in Accounts Payable is more about the content and use of the content than the paper itself; receiving paper invoices can still be a best practice! Many corporations have already taken the best practice initiative of moving to an ERP such as SAP. When the invoice receipt is paper based, SAP provides the best practice solution by offering all the necessary components including Document Archive for scan and storage, Invoice Management for OCR and exception processing and ECM to manage invoices as one component of the enterprise picture.
If you handle the content properly most certainly, those paper invoices can become a best practice.

How To Communicate Without Saying a Word

How to Communicate Without Saying a Word
This can be a difficult challenge in the world of Accounts Payable when working to post invoices accurately and quickly. Just accurately and quickly alone is a major task but when you add “quietly”…is it really possible?
Think of all the people involved…Accounts Payable Professionals, Approvers, Corporate Procurement, Field Procurement, Receiving, Contract Management, Master Data Management, Tax Professionals…just to name a few. There are a number of Vendors offering solutions to address the accurate and quick...although in many cases you have to decide…do you want it accurate or quick…one or the other but not both. Yet very few address the quietly issue. Why is this important? For invoices that are received and immediately posted without any human intervention due to issues such as problem resolution or approval, communication is not a critical factor. Yet when that 80/20 rule kicks in where 20% of your invoices result in 80% of the problems, the Accounts Payable Professional must reach out and communicate. They need to communicate with the individuals that have both the knowledge and security authorization to resolve / approve invoices as required by best practice separation of duties. As an example, in an ERP such as SAP this communication is often started by running a report such as MRBR to find invoices blocked for payment. Without a solution that includes “quietly” as a building block, the first communication triggers a barrage of activity including but not limited to emails, phone calls, entries into spreadsheets for follow up, follow up calls, making copies of invoices and pulling contracts.
So how do you add “quietly” to the process flow? You must examine the entire process flow from how you receive the invoice, how you capture the meta data at the header and line item level, how you determine if there is a problem and then who must be involved to resolve / approve. Equally important is anticipate what that person requires to complete the task…such as…access to invoice and related document images, history of others that have worked on the process including their comments, transactional data such as purchase order, goods receipt, prior postings to purchase order and options to resolution / approval.
One excellent example of a “quite” solution is provided by SAP with their SAP Invoice Management and optional OCR.
One last thought…quiet extends to reporting also…you need to anticipate the need for information related to the invoice. While invoice payment status is certainly important you must also anticipate others will want to know trends such as invoices paid without problem and if a problem…what type of problem is most common. Yet a truly quiet process goes beyond the expected reporting…the invoice occurred because of a purchase…the purchase occurred due to a larger business process such as a building project and so on. You must anticipate that others must be able to see the invoice as part of the bigger picture. This bigger picture is ECM. You would expect that a large ERP would anticipate this more holistic requirement and SAP has also done that by providing an ECM solution through it partnership with Open Text that takes the invoice and quietly makes it available as part of the ECM big picture. This allows you to see for example all the invoices from one vendor on one project in one virtual view or to see all the invoices related to the project regardless of vendor. No longer is it required to communicate and ask the Accounts Payable Professional to accumulate all the related information and wait for a response…it is already waiting for you to access immediate and quietly.
So…Accurate…Quick…Quiet…yes it is possible!
See SAP EcoHub for More on AP Optimization

Accounts Payable Shared Service - Round 2

Accounts Payable Shared Service - Round 2
In past years, the never ending search to increase corporate productivity led down a path to shared services. It quickly became apparent that one quick win was Accounts Payable. In round 1 many corporations equated shared services with moving the same functions to a less expensive labor pool. Obviously direct labor cost was reduced so this was deemed a success and others joined the movement. As the demand grew, basic economics kicked in…the law of supply and demand. The demand grew for skilled workers. In some areas once thought of as the place to move the tasks, the workers now move every few months due to double digit wage increases. The net result is the people processing your invoices are entry level and about the time they are trained; they are off to another company. When you compound this with the issues around time zones, language and scalability; the winner of round one may not be so clear.
As corporations reexamine their shared service concept, they are often finding that moving the transactional functions back within the corporate walls makes more sense. This is especially true when they take advantage of the process optimization and automation provided by ERP such as SAP Invoice Management by Open Text. The new solutions provide the ability remove non value touch points while replacing critical manual touch points with immediate electronic touch points. This is not to say human logic is eliminated, rather it ensures when required, the right person has the right information at the right time. In addition, AP processes now have a single point of contact. Standard process is the rule rather than the exception.
The winner of round 2 is definitely the corporation that utilizes the strength of an ERP combined with process optimization and automation. Best of class invoices are received and posted immediately without human interaction and those invoices that have an issue are resolved and posted in 1 – 3 days. Cash management is optimal, balance sheets are correct and timely and reporting promotes continual process improvement.
What will determine the winner of round 3…mobile AP functionality, dynamic discounting, ERS, standard invoice format, vendor networks, ?


See SAP EcoHub for More on SAP Invoice Management

PO Based Invoice are a Best Practice but are they Most Practical

Many in the P2P world agree that best practice is to create a purchase order before procuring goods and services…but…is that always the most practical?

If purchase orders are a best practice why do so many corporations pay invoices without purchase orders? It is not uncommon for major international corporations utilizing a strong ERP like SAP to have 50% or more non PO invoices. SAP provides an excellent tool set for the creation and approval of purchase orders. All of the benefits you would expect from a world class solution are there for the taking. So why not demand all invoices be PO based?

From a practical view, there is a point of diminishing return where the cost to create, approve and issue a purchase order is more than the cost of the goods being purchased. You may not want to create a PO to purchase a $5 book but at the same time, why would you purchase $5,000 in services without a purchase order?

In some companies, the purchase order is created only after the services have been rendered and the invoice received. The reason often given is that they don’t know the actual hours until the invoice is received. This scenario seems to only capture the budget reporting benefit of purchase orders. It is not considered practical to create the purchase order up front.

While processing 50% non po invoices is uncommon, I have worked with some companies where there is a corporate mandate that only selected invoices will be paid without a purchase. Tax payment, contributions and legal invoices are some that fit within the non po realm. In some companies as few as 5% of invoices are paid without a purchase order.

Is the acceptance of invoices without a purchase order always more practical or just easier? Most of us have “hated” filling out a purchase request at some point in our jobs. If ordering the $5 book without a purchase order is quick and easy, we tend to make larger purchases without a PO also. This can quickly become the norm. As companies tighten their budgets there seems to be a new commitment in P2P world to fully embrace the best practice of utilizing purchase orders. Is your company demanding the use of purchase orders…if not…should they?

For more on Accounts Payable Automation and Optimization see the SAP EcoHub for SAP Invoice Management by Open Text.