The Blog Master posted a link to an AP process success story yesterday, did you get it?
https://faoblog.com/ap-success-story/
And the post before that had a free white paper from Aberdeen Group.
https://faoblog.com/receivables-management-reduce-manual-interventions/
Coming back to AP, now, you are working at migrating the process. How will you add value by applying your best practices? One way is to bring better transparency by defining the stage your invoice / transaction is in.
Stage Definition
At the system level, we need to define the stages where the WIP items shall reside. This module shall provide for the enhancement of the WIP Queue types. Each Queue type shall be identified by a Queue code, which shall be unique to the system, and its description.
Some standard queues used are :
- Non-Prep Initial receipt
- Prep Invoices Prepared
- Prep – Hold Invoices Prepared – kept on hold
- Vendor Maintenance Requiring Vendor updated
- Approval Requiring Approval
- Approval – Client Requiring Client Approval
- Hold – Clarifications On hold for clarifications
- Rejects Rejected for processing
- Park Invoices Parked
- Posted Invoices Posted
- Response Awaiting response
- Rejection Feedback Recd. after clarification
- Trash Finally rejected and deleted
- Released Released for payment
We have enabled a button on the top of the first page, which will enable you share your posts. If you wish to write about any of the current streams, you can do it at https://faoblog.com/guest-post/. We will review your post and release it within 48 hours of your posting.
Trackbacks/Pingbacks