In most organizations we commonly see a problem in gathering the accounting and other missing information for Non-PO invoices. Oracle Payables does not help us much in gathering this information within Oracle system itself. So, AP team has to gather this information outside of Oracle.
However, a workaround involves using the Invoice Approval Workflow to gather the missing information from the Invoice Approver. But, for this to work the invoice distribution lines have to be completed. SO, what i suggest is use a dummy invoice distribution lines which uses a particular CCID (can be a clearing account) which the AP clerk uses. Using Invoice Approval Workflow we can gather the correct invoice distribution details like tax details, accounting details, etc from the invoice approver and then the AP clerk goes back to the invoice and updates the lines with the correct values. To prevent payment of such invoices without the correct invoice details we can use different means like changing th payment due date to a much later date, putting the invoice on a custom hold, etc.
However, i am looking forward to Oracle to come forth with a more standard solution to this common problem for Non-PO invoices which almost all organizations who have implemented Payables face today.
However, a workaround involves using the Invoice Approval Workflow to gather the missing information from the Invoice Approver. But, for this to work the invoice distribution lines have to be completed. SO, what i suggest is use a dummy invoice distribution lines which uses a particular CCID (can be a clearing account) which the AP clerk uses. Using Invoice Approval Workflow we can gather the correct invoice distribution details like tax details, accounting details, etc from the invoice approver and then the AP clerk goes back to the invoice and updates the lines with the correct values. To prevent payment of such invoices without the correct invoice details we can use different means like changing th payment due date to a much later date, putting the invoice on a custom hold, etc.
However, i am looking forward to Oracle to come forth with a more standard solution to this common problem for Non-PO invoices which almost all organizations who have implemented Payables face today.
Posts
