I have found it to be curious that Account Payable Automation projects can be hit or miss. A hit is a full adoption with no one person left out. A miss is having one process that is automated and a second process that is paper.

What?

That’s right, you may be surprised how many AP Automation projects are not fully adopted. At the risk of playing the blame game (client vs service provider) the blame is squarely placed on both. The client will go into automation with the mindset that there will be certain invoice types that need to be left out. They types in the client’s mind will be too difficult for automation. Then, on the other side, the service provider will approach the client with advice to leave certain invoice types out because their software is deficient (I have written many times that you should never let the service provider’s problems become your problems).

Adoption

Here is what I have found. You have to get as many invoice types into your AP Automation project to increase adoption. The key to getting as many invoice types into your project are options. There is a few areas where as many options as possible helps with adoption.

1. Invoice Receipt – the more options a service provider can receive invoices the higher the adoption. A few examples are, multiple scanning options, email, portals, EDI and API connection.
2. Workflow Triggers – Once an invoice is converted the technology should assign an approval process or workflow to that invoice. The more options the service provider has the higher the adoptions. Here are a few trigger examples, vendor, PO, attention to, project, location, business unit, property, cost center and department.
3. Approval Process Flexibility – Once the invoices has been assigned to an approval process the more flexible the approval process the higher adoption. Examples are dollar amount, contract, PO and budget escalation.
4. System Integration – Lastly when invoices are fully approved how the AP Automation system and the ERP or Accounting System communicate. The more options you have to either import, sync or integration the higher the adoption. Once size doesn’t fit all when it comes to integrations.

Want to know more? Buy My Books!

To buy the book – The Argument to Automate – How Innovation Can INSPIRE Not Fire – click here to buy

(Also) To get your copy of The 8 Pitfalls of Accounts Payable Automation – click here to buy

How about a children’s book? The Princess and the Paper – click here to buy