# MarkView for Accounts Payable and Oracle E-Business Suite

> Source: https://netray.co/stack/markview-accounts-payable-oracle-ebs
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

MarkView combines document capture, discrepancy workflow and real-time ERP integration to automate AP invoice processing inside Oracle EBS. The vendor describes it as an embedded, certified Oracle EBS integration, so approvers and AP clerks work with invoices linked to Payables and Purchasing records. A private AI layer can help explain discrepancies without sending invoices outside your network.

## Erp

Oracle E-Business Suite

## Erp Key

oracle-ebs

## On Prem

true

## Product

MarkView for Accounts Payable

## Vendor

Tungsten Automation (formerly Kofax)

## Category

AP automation

## Integration

**Method:** Embedded or certified Oracle EBS integration

**Detail:** 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.

## Data Flows

**From:** Supplier invoice (paper, PDF, email)

**To:** MarkView

**Data:** Invoice image and extracted header and line data

**Trigger:** Invoice arrives and capture runs

**From:** Oracle EBS

**To:** MarkView

**Data:** Suppliers, purchase orders, receipts and approval hierarchy for matching

**Trigger:** Invoice validation and matching

**From:** MarkView

**To:** Oracle EBS Payables

**Data:** Approved invoice for creation in Payables

**Trigger:** Workflow approval complete

**From:** Oracle EBS

**To:** MarkView

**Data:** Invoice status, hold and payment information

**Trigger:** Payables validation or payment run

## Setup

### Confirm EBS release and supported versions

**Detail:** Check the MarkView version against your EBS release and database before planning the project.

### Map invoice types and coding

**Detail:** Define which invoices are PO-backed versus non-PO, and how GL coding and approval limits work in each case.

### Configure supplier and PO data access

**Detail:** Decide how supplier sites, PO lines and receipts are exposed for two-way and three-way matching.

### Set tolerances and discrepancy routing

**Detail:** Define price and quantity tolerances and who resolves each type of discrepancy, such as buyer or receiving.

### Build approval hierarchy

**Detail:** Align approvers with EBS employee hierarchy or the roles you plan to use for approval.

### Run parallel testing

**Detail:** Process a month of historical invoices in test and compare results to what AP actually posted.

## Pitfalls

- 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.

## Ai Layer

### Discrepancy explanation

**Description:** 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

**Description:** Flag possible duplicate invoices or unusual amounts against supplier history, for human review.

### Aging and bottleneck questions

**Description:** Answer questions such as which invoices are stuck with which approver, from read-only EBS and workflow data.

### Draft supplier queries

**Description:** Draft an email to a supplier about a pricing difference, sent only after an AP clerk approves.

## Alternatives

- 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.

## Faq

### Is MarkView still sold under the Kofax name?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Source

https://www.kofax.com/products/markview

## Search terms

kofax markview oracle ebs, markview accounts payable, oracle ebs invoice automation, tungsten markview oracle, oracle ebs ap invoice imaging

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json