Auto PO Matching for Oracle EBS

DocuSphere includes a sophisticated Auto PO Matching agent that manages the process of automatically matching invoices with purchase order (2-way match) or purchase order and receiving data (3-way match) from within the Oracle E-Business Suite respectively. The Auto PO Matching agent also leverages associated matching tolerance rules which have been established within Oracle E-Business Suite. For example, if a tolerance rule was set within Oracle E-Business Suite to allow matching to occur as long as invoice data was within 5% of the purchase order value, DocuSphere Auto PO Matching would take this into account.

At a more detailed level, depending upon the specific circumstances of typical relationships between purchase orders, receipts, and invoices within a given enterprise, one can elect to Auto PO Match at an extracted invoice subtotal level – primarily in situations where there tends to be a one-to-one ratio between purchase orders and invoices when purchase orders tend to be received in full; alternatively, if the ratio of purchase orders to associated receipts and invoices, then matching at a detail line item-level would likely make better sense. Once invoices are successfully Auto PO Matched within DocuSphere, they are passed along to the Auto AP Invoicing agent for the creation of invoices for payment within Oracle E-Business Suite via standard processes.

If it is common that the receipt of invoices precedes either the physical receipt of goods, or at least precedes the recognition of those receipts within Oracle E-Business data, the process may be established to automatically forward that work item to a “Wait” process for a specified period of days, after which the system would once again attempt to Auto PO Match that invoice. Alternatively, work items with Auto PO Match matching exceptions can be routed to appropriate exception processing queues based on the specific exception result for that task.