How to add document OCR to Oracle Fusion Cloud ERP
Short answer
Use Fusion's built-in invoice recognition where it is enough, and add an OCR and extraction service for packing slips, certificates and other documents it does not cover. Match extracted fields to Fusion records, attach the source file, and queue low-confidence fields for review.
Paper still crosses the dock. Packing slips, mill certifications, certificates of conformance, bills of lading and supplier invoices in every layout all end up as scans or PDFs. Fusion can hold them as attachments, but attachments are not data.
Oracle provides document recognition features for Payables invoices, and those should be the first thing you evaluate. The gaps are usually everything else: receiving documents, quality certificates, drawings revision checks and non-standard invoices.
A good OCR project is less about the OCR engine and more about matching and exceptions. Reading a part number is easy; knowing it is the supplier's variant of your item is the work.
What teams use it for
Packing slip to receipt
Extract PO number, lines and quantities from a supplier packing slip and prepare a receipt for the dock clerk to confirm.
Certificate of conformance capture
Read heat or lot numbers and spec references from certificates and attach them to the receipt or lot record for traceability.
Non-standard supplier invoices
Extract header and lines from invoices Fusion's recognition does not handle well, and create a draft Payables invoice.
Drawing revision check
Compare the revision on a supplier drawing or inspection report against the item revision in Fusion.
Customs and freight paperwork
Capture HS codes, weights and values from commercial invoices for landed cost or trade compliance review.
Oracle Fusion Cloud ERP integration surface
- Payables invoice recognition (Intelligent Document Recognition) as a configurable Fusion feature; availability and setup depend on your release.
- Attachments API on business objects, which lets you attach the source file to a PO, receipt, invoice or lot.
- REST resources and FBDI templates for creating receipts, invoices and inventory transactions after extraction.
- Lot and serial attributes and descriptive flexfields, where certificate data can be stored if your setup supports it.
- Object Storage or UCM locations for staging files, and Oracle Integration for orchestration.
How it works
- 1
Inventory your document types
Count volumes by type and supplier. A few suppliers usually produce most of the paper, so start there.
- 2
Try native recognition first
For invoices, test Fusion's own recognition and measure how many land without edits before adding anything custom.
- 3
Ingest and normalize scans
Deskew, convert to consistent resolution and keep the original untouched. Handle multi-page and mixed PDFs.
- 4
Run OCR and extraction
Use OCR for text and layout, then a model or template to map to a fixed schema with a confidence per field.
- 5
Match to ERP data
Resolve supplier, PO, item, UOM and lot to Fusion records through REST. Anything unresolved stays flagged.
- 6
Review and post
Show the image beside extracted fields; reviewers fix and approve. Then create the receipt or invoice draft and attach the original.
- 7
Tune from corrections
Track per-supplier field accuracy and promote reliable suppliers to a higher automation level.
Example flows
Packing slip to receipt draft
Trigger: A receiving clerk scans a packing slip at the dock.
- OCR extracts supplier, PO number, item numbers and quantities.
- The service pulls the open PO schedules and matches lines.
- Differences in quantity or missing lines are highlighted.
- The clerk confirms and the receipt is created; the scan is attached.
Result: Receipts follow physical arrival faster and mismatches surface at the dock.
Certificate attached to lot
Trigger: A certificate of conformance PDF arrives with a shipment.
- Extraction reads lot or heat number, material spec and supplier signature presence.
- The service finds the received lot in Fusion.
- The certificate is attached to the lot or receipt with extracted values stored if configured.
- Missing signature or spec mismatch routes to quality.
Result: Quality can retrieve evidence by lot during audits.
Keeping data on-prem
Certificates and drawings can be sensitive, particularly in aerospace and defense. Run OCR and the extraction model on your own servers, with GPUs if you use vision-language models, so documents never reach a shared API. Fusion receives structured results and an attachment through its API. If an external OCR service is used, confirm region, retention and training terms in writing first, and consider hybrid routing where only low-risk documents go to the cloud.
Security checklist
- Encrypt staged documents at rest and delete working copies on a schedule.
- Restrict reviewer access by business unit and document class.
- Never auto-post bank detail changes extracted from documents; require out-of-band verification.
- Keep the original file immutable and link it to every derived record.
- Log model and OCR versions so results can be reproduced during disputes.
Ways to get it done
Fusion native recognition plus attachments
Effort: Configuration and tuning.
Standard supplier invoices with decent layouts.
Cloud document AI service in your pipeline
Effort: Weeks, plus review UI.
Teams comfortable with a hyperscaler and non-sensitive documents.
Private OCR and extraction with a partner such as Netray
Effort: Phased by document class, starting with one supplier group.
Regulated documents, certificates, drawings and mixed languages.
Pitfalls
- !Trusting OCR on part numbers with O and 0, I and 1 confusion without validation against master data.
- !Skipping unit of measure conversion when packing slip units differ from PO units.
- !Posting receipts from partial shipments as complete.
- !Storing extracted values only in a side database where quality cannot find them.
- !Underestimating the review screen; it decides whether users adopt the system.
Frequently asked questions
Does Oracle Fusion include OCR?
Fusion offers invoice recognition features for Payables that read scanned or emailed invoices. Coverage for packing slips, certificates and other documents is not the same, so confirm what your release supports and fill gaps with an external service.
How do I attach the scan to the transaction?
Use the attachments capability exposed through REST on supported business objects, or the UI attachment features, and store a reference to the original in your own audit table too.
What confidence threshold should I use?
Choose it empirically. Run a few hundred real documents, record where errors occur per field, and set thresholds so the automated set has an error rate your finance and quality teams accept.
Can it read engineering drawings?
It can extract title block data such as part number and revision reasonably well. Reading dimensions and tolerances reliably is much harder; keep a person in the loop for anything that affects acceptance.
Is a vision-language model better than classic OCR?
Often for messy layouts, but it can be slower and may hallucinate. Many pipelines combine OCR text with a model constrained to a schema, then validate every field against Fusion data.
Want Document OCR working on your Oracle Fusion Cloud ERP?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment