This solution provides supplier invoice management and posting within JD Edwards EnterpriseOne, OneWorld XE or ERP8. By capturing inbound invoice document images as they come into the organization and streamline the method in which customers work with these documents by removing the manual paper-based process and managing electronically.

This interface contains JDE UBE’s procedures and tables. It is supplied as an ASU. There are no changes to the standard JDE code.

The base framework is modeled to cover the following areas:

• Document Capture: There are various methods in which invoice documents can be captured: scanner/MFD, fax, and e-mail.
  
  
• Data Capture (OCR): There are two methods in which invoice data can be captured automatically from the imaged documents:
  
  
  
  
• Invoice Types: By default, there are 4 invoice types the solution is configured to manage and identified below:
  
  • Invoice with Purchase Order
  • Invoice without Purchase Order
  • Pre-Authorized Invoice
  • Unknown
  
  
  
  
• Intergrated JDE Split Screen Index Verification:
  • Queuing of inbound invoices for AP personnel to perform index verification utilizing
  the split screen data entry based on invoice type mentioned above
  
  • Documents will automatically be assigned an Invoice Type code based on the
  information gathered during data capture, but can be changed accordingly during review
  
  • All header index data captured automatically populated
  
  • Requests for additional fields and/or modifi cations to the layout of the split screen
  view will require additional services; price TBD based on requirements
  
  • Intergrated JDE-split screen manual 2- way/3- way matching: Integrated split screen that allows users to manually perform a 2- way (Orders-to- Match) or 3- way (Receipts-to-Match) operation on invoices with corresponding purchase orders.
  
  
  
  
  
• Coding/Routing/Approval: The base framework includes a facility for managing non-PO invoices that require further processing outside of JDE environment via Presenter and includes the following:
  
  • Routing Rules that allow customers to specify how invoices are routed based on
  user, dollar limits, and vendor settings. This will comprise of the baseline database
  architecture
  
  • Two split screen Responder views which are displayed based on user permissions:
  Coder or Approver
  
  • Integration with JDE Address Book to allow for Vendor Number/Name lookup and
  Validation
  
  • Ability to bill against multiple GL account codes (up to 3)
  
  • Data validation of various fi elds (e.g. – date, amount, number fields)
  
  • Error messages for data entry fields
  
  • Ability to manually forward documents queued in JDE for external approval
  
  • Daily transaction report detailing invoices pending approval
  
  • Audit log file which captures transactions within FormScape during the coding and
  approval process
  
  • Customers requiring more extensive routing rules will be incorporated on a time and
  material basis
  
  • Filtering of GL codes by user requires additional services on a time and material
  basis