How to add document OCR to Oracle E-Business Suite
Short answer
Capture documents from scanners, folders or email, run OCR and field extraction, validate against EBS data, and send clean results to the Payables, Receiving or Purchasing open interfaces while storing the image as an attachment. Fields below the confidence threshold go to a human review screen before anything is posted.
Oracle EBS has long supported document handling through attachments and, in the Payables world, invoice imaging options, but many plants still run on paper: supplier invoices delivered by post, packing slips signed at the dock, material certificates stapled to the receipt and drawings with revision marks.
The shift in the last few years is that OCR combined with layout-aware models is good enough for varied supplier formats without a template for each vendor. The work that matters is on the EBS side, mapping what was read onto valid suppliers, sites, POs and receipts, and handling the exceptions in a way that keeps auditors comfortable.
This page describes document capture for EBS 12.1.3 and 12.2.x using supported interfaces only, with attention to what has to stay on-prem for regulated manufacturers.
What teams use it for
Supplier invoice capture and 3-way match
Read invoice header and lines, find the PO and receipt, and stage the invoice for Payables import with variances flagged for AP.
Packing slip to receipt
Read dock paperwork, match to PO shipments and propose receiving lines through the Receiving Open Interface, so dock staff confirm rather than type.
Certificates of conformance and mill certs
Extract heat or lot numbers, specification and revision, then attach the document to the receipt and lot with a link for the inspector.
Drawing and revision verification
Read title block fields, compare revision to the item revision in Inventory or Engineering, and flag mismatches before production uses the drawing.
Expense and freight documents
Capture freight bills and receipts for accrual matching and expense reports.
Oracle E-Business Suite integration surface
- Payables Open Interface: AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE with the Payables Open Interface Import program, which reports rejections you can feed back to the reviewer.
- Receiving Open Interface: RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE processed by the Receiving Transaction Processor, with PO matching via PO_HEADER_ID and PO_LINE_LOCATION_ID.
- Attachments: FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS and FND_LOBS store files against entities such as invoices, PO lines and receipts; programmatic attachment uses supported FND attachment APIs.
- Invoice imaging or Oracle Document Capture style options in Payables, whose availability and licensing depend on your release and what you bought; verify before assuming.
- Quality results and lot data through the Quality and Inventory modules for linking certificates to MTL_LOT_NUMBERS.
- Supplier and site validation from AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL, used to confirm who sent the document.
How it works
- 1
Choose capture points
Scan at AP, at the receiving dock and at quality. Accept PDFs by email and folders from MFPs. Keep the original file and compute a hash to detect duplicates.
- 2
Pre-process images
Deskew, denoise and split multi-page batches. For drawings, keep resolution high enough to read title blocks and notes.
- 3
OCR and field extraction
Run OCR plus a layout-aware extraction model with a schema per document type. Record the confidence for each field and the page coordinates for review highlighting.
- 4
Validate against EBS
Check supplier and site, PO open status, line quantities and prices, tax, currency and duplicate invoice number for the supplier. Anything that fails is a flagged field, not a silent guess.
- 5
Set confidence thresholds
Define per field thresholds, for example stricter for amounts and PO numbers than for descriptions. Below the line, the document goes to review.
- 6
Review and correct
A side by side screen shows the image with highlighted fields. Reviewer corrections are saved and used to tune extraction for that supplier.
- 7
Post through interfaces and attach
Write to the open interface, run the import, capture rejections and attach the image to the new document with the FND attachment API.
Example flows
Paper invoice to Payables
Trigger: An invoice scan lands in the AP scan folder.
- OCR reads supplier, invoice number, date, total and lines.
- System matches the supplier site and PO number.
- A price variance on one line exceeds tolerance and the invoice goes to review.
- AP corrects or holds the line, the staged invoice imports, and the image attaches.
Result: AP keys fewer lines and sees variances before the invoice posts.
Mill cert to lot
Trigger: Receiving scans the material certificate with the packing slip.
- Extraction reads heat number, alloy, specification and revision.
- System compares to the PO specification and approved supplier list.
- Mismatches create a quality alert; matches attach the cert to the receipt lot.
Result: Traceability documents are linked at receiving rather than found later in a filing cabinet.
Keeping data on-prem
Scanned invoices and certificates are some of the most sensitive documents a manufacturer holds, and drawings can be export controlled. Run OCR and extraction models on your own servers, with open-weight vision or layout models or classic OCR engines on CPU or GPU, and keep images in a storage area inside the EBS network. The review UI and staging database live next to EBS, and only supported interface calls cross into the application. For air-gapped plants, model weights are loaded through an approved transfer, and updates follow your change control. No document, field value or review correction needs to leave the site.
Security checklist
- Store images in a controlled share or the EBS file store with role-based access, and encrypt at rest.
- Do not log full document text or amounts to application logs.
- Use a dedicated integration account limited to the interface tables and attachment API.
- Block duplicate invoice numbers per supplier before staging, and preserve the original hash.
- Segregate duties so the person approving corrections is not the sole poster of the invoice for high value items.
Ways to get it done
Vendor AP automation or invoice capture product
Effort: Weeks for configuration and supplier onboarding.
Fits sites that only need invoices and accept a hosted service or a licensed Oracle option.
Build with open OCR and extraction models
Effort: Two to four months for invoices plus one more document type.
Fits teams that need multiple document types and on-prem control.
Partner build with Netray
Effort: Pilot on one supplier group and one document type.
Fits regulated sites wanting private extraction, review UI and EBS interface mapping handled together.
Pitfalls
- !OCR accuracy on stamps, handwriting and fax-quality scans is lower; set expectations and thresholds per document type.
- !Invoice tax and withholding rules differ by country and ledger, so test with real multi-org data.
- !Matching on supplier name alone fails; use tax ID, remit-to or known sender addresses.
- !Attachments left as large files in FND_LOBS can inflate the database, so plan storage and retention.
- !Interface rows with the wrong org context never import and are easy to overlook without monitoring.
Frequently asked questions
Does Oracle EBS include OCR?
Not as a general capability. Some releases and licensed options offer invoice imaging or document capture add-ons, but coverage and licensing vary. Check what you own, then decide whether to extend it or build a pipeline that uses the open interfaces.
How are low confidence fields handled?
They are routed to a human review screen with the source image highlighted, and nothing is staged until the reviewer confirms. Corrections feed back into rules so the same supplier layout improves over time.
Can drawings be processed too?
Title block fields such as drawing number and revision can be read reliably when the layout is consistent. Treat the result as a check against EBS item revisions, not as a replacement for engineering release control.
Where do the images live?
Typically in a secured file store or in EBS attachments via the FND attachment APIs. Keeping originals linked to the posted document gives auditors a direct path from entry to source.
Can this run without sending documents to the cloud?
Yes. Open-weight OCR and layout models run on your own servers, and the review UI and staging sit inside the network. This is the usual design for aerospace and defense suppliers handling controlled documents.
Want Document OCR working on your Oracle E-Business Suite?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment