How MarkView for Accounts Payable connects to Oracle E-Business Suite
Embedded or certified Oracle EBS integration
The vendor positions MarkView as integrated with Oracle EBS Payables, with invoice images and workflow tied to EBS transactions in real time. The listing does not spell out interfaces, but EBS integrations of this kind normally rely on the Payables open interface tables and EBS APIs. Confirm the specifics for your release.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Supplier invoice (paper, PDF, email) | MarkView | Invoice image and extracted header and line data | Invoice arrives and capture runs |
| Oracle EBS | MarkView | Suppliers, purchase orders, receipts and approval hierarchy for matching | Invoice validation and matching |
| MarkView | Oracle EBS Payables | Approved invoice for creation in Payables | Workflow approval complete |
| Oracle EBS | MarkView | Invoice status, hold and payment information | Payables validation or payment run |
Setting it up
- 1Confirm EBS release and supported versionsCheck the MarkView version against your EBS release and database before planning the project.
- 2Map invoice types and codingDefine which invoices are PO-backed versus non-PO, and how GL coding and approval limits work in each case.
- 3Configure supplier and PO data accessDecide how supplier sites, PO lines and receipts are exposed for two-way and three-way matching.
- 4Set tolerances and discrepancy routingDefine price and quantity tolerances and who resolves each type of discrepancy, such as buyer or receiving.
- 5Build approval hierarchyAlign approvers with EBS employee hierarchy or the roles you plan to use for approval.
- 6Run parallel testingProcess a month of historical invoices in test and compare results to what AP actually posted.
What usually breaks
- !Supplier and site mismatches between the extracted invoice and EBS cause invoices to stall in exception queues.
- !Matching tolerances set too tight flood buyers with discrepancies; too loose lets overbilling through.
- !Tax and freight lines not coded consistently produce Payables validation holds.
- !Approver hierarchy changes in EBS that are not mirrored in the workflow leave invoices with absent approvers.
- !EBS patches or upgrades can change interface tables or APIs; retest the integration after each.
A private AI layer across both systems
Discrepancy explanation
Read the invoice, the PO and the receipt and explain in plain terms why a three-way match failed, citing the specific lines.
Duplicate and anomaly screening
Flag possible duplicate invoices or unusual amounts against supplier history, for human review.
Aging and bottleneck questions
Answer questions such as which invoices are stuck with which approver, from read-only EBS and workflow data.
Draft supplier queries
Draft an email to a supplier about a pricing difference, sent only after an AP clerk approves.
Try it here, free
Oracle EBS AP Invoice Interface Template
Fill in header and line values to get insert statements for the Payables open interface tables, ready to adapt for your conversion or integration.
When something else fits better
- Oracle's own Payables invoice imaging and approval features may be sufficient for low invoice volumes.
- Other AP automation vendors with EBS connectors cover the same ground; compare on matching and exception handling.
- Improving PO discipline and EDI for top suppliers often removes more manual work than adding capture.
Frequently asked questions
Is MarkView still sold under the Kofax name?
The vendor page lists MarkView under Tungsten Automation, formerly Kofax. Product naming may still show Kofax in older materials, so check current documentation when evaluating.
Does MarkView run inside Oracle EBS?
The vendor describes it as an embedded and certified Oracle EBS integration with real-time connectivity. Ask for the deployment architecture for your release, since components may run alongside rather than inside the EBS tier.
Can AI replace MarkView?
No. MarkView handles capture and governed workflow. A private AI layer complements it by explaining exceptions and answering questions, with write-backs only after human approval.
Pairing documented at www.kofax.com/products/markview . MarkView for Accounts Payable is a product of Tungsten Automation (formerly Kofax); Netray is independent and not affiliated with either vendor.