How Many Times Should AP Make the Same Decision?

<span id="hs_cos_wrapper_name" class="hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_text" style="" data-hs-cos-general-type="meta_field" data-hs-cos-type="text" >How Many Times Should AP Make the Same Decision?</span>

An invoice arrives from a vendor your company uses every month. The details have been captured, but someone still needs to choose the account, assign the department, and check whether any costs belong to a project.

So they open last month’s invoice to see how it was handled.

It’s a small task. Repeat it across dozens of invoices, and it becomes a regular part of someone’s day.

For AP teams, this is one reason invoice processing still takes time, even after reducing paper and manual data entry. Getting the information into the system is only part of the work. Someone still has to decide where the expense belongs.

The invoice is captured. Now what?

Capturing an invoice means reading information such as the vendor, invoice number, date, and amount. Coding it means deciding how to record the...

Log in to continue reading

This article is available for FREE to registered readers of The ERP Update.

About the Contributor

Amiee Keenan

Contributor to The ERP Update.

Blog Post CTA

Stay Updated on ERP & Business Software

Get the latest insights, comparisons, and resources delivered straight to your inbox.

Join the Conversation

Share your thoughts and comments on this article.