AutoMatch for JD Edwards

DocuSphere includes a sophisticated AutoMatching 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 JD Edwards respectively. The AutoMatch agent also leverages associated matching tolerance rules which have been established within JD Edwards. The AutoMatching agent takes into account any and all matching tolerance rules for each of the three categories of quantity, unit cost, and extended amount, based on percentages, units, or amounts. As long as items are within your JD Edwards tolerance rules, the voucher will be created within JD Edwards using standard EDI processes, which in turn will handle any associated variances.

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 AutoMatch 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 is either one-to-many or many-to-many, then matching at a detail line item-level would likely make better sense. Once invoices are successfully AutoMatched within DocuSphere, they are passed along to the AutoVoucher agent for the creation of vouchers for payment within JD Edwards via standard EDI 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 JD Edwards 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 AutoMatch that invoice. Alternatively, work items with AutoMatch matching exceptions can be routed to appropriate exception processing queues based on the specific exception result for that task.

Further, the DocuSphere AutoMatching agents allow for the configuration of account codes to be established for additional charges not appearing on the purchase order, such as freight and miscellaneous charges. The organization can elect to allow and limit the additional charges or not allow them at all.