Invoice OCR for JDE that posts straight to F0411.

JDE doesn't really do invoice OCR

JD Edwards has solid voucher workflow but no native OCR. Most shops either key bills by hand or stitch together a third-party imaging tool (Kofax, IntelliChief) with a custom F0411Z1 loader. That works, but it's a maintenance burden — every JDE tools release risks breaking the integration, and the OCR vendor charges per page.

Core Invoice extracts:

• Supplier identity → matched against your F0101 Address Book
• Voucher header data (number, date, due date, currency)
• Every line: account distribution, quantity, unit cost, extended amount
• Taxes (tax rate area, tax explanation code)
• PO reference for 3-way matching against F4301

Output maps cleanly onto F0411 (voucher header) + F0911 (G/L distribution) — no field translation gymnastics required.

AIS Orchestration setup (preferred path)

1. Verify AIS Server is running and reachable from your network. Typically https://<ais-host>:9300/jderest.
2. Create the Voucher Entry Orchestration in JDE Studio (or import the one we ship). It wraps P0411 (Standard Voucher Entry) with the field mappings Core Invoice expects.
3. Create a dedicated JDE user for the integration, assigned to a role with P0411 / P04012 access. Typically the *ALL role or a custom AP_INTEGRATION role.
4. Add the connection in Core Invoice: AIS base URL, environment (DV910 / PY910 / PD910), user, password, role, and the orchestration name.
5. Click Test — Core Invoice runs a tokenrequest and confirms the response.

Z-file path (R0411Z1S)

If AIS isn't an option, Core Invoice writes F0411Z1 records directly via JDBC to your JDE database. Your existing R0411Z1S UBE picks them up on its normal schedule. This path:

• Doesn't require AIS deployment
• Posts in batch — the next R0411Z1S run picks up the queued records
• Lets you keep R0411Z1S as the source of truth for posting
• Trades real-time error feedback for compatibility

Switching from Z-file to Orchestration later is a per-connection toggle — no data migration.

3-way matching with PO + Receipt

For PO-referenced vouchers, Core Invoice reconciles each line against the open F4301 / F4311 purchase order and matching F43121 receipt records:

• Quantity against the receipt — tolerance configurable per branch/plant
• Unit cost against the PO — tolerance configurable per supplier
• Branch/Plant mismatch is a hard fail

Tolerances default to your JDE Voucher Match (P4314) settings if we can read them, so the reconciliation rules match exactly what your existing P4314 process would apply.

Account distribution and G/L coding

For non-PO vouchers, Core Invoice maps the bill into account distributions on F0911. Three options per connection:

• Default from supplier: use the AAI-defined expense account from F0101 / F0911.
• Smart-suggest from history: Core Invoice recommends accounts based on the past 6 months of approved vouchers for that supplier.
• Mandatory review: every line requires AP approval of the suggested account before posting.

Multi-company JDE

Each JDE company (00001, 00100, custom) maps to its own ERP connection in Core Invoice — distinct credentials, default G/L offsets, business unit defaults, and pay-status overrides. Cross- company vouchers (intercompany settlements) are not in scope; those still go through your normal JDE process.

Security

JDE user passwords are Fernet-encrypted server-side and never logged or returned. We recommend pairing the integration user with JDE row-security on F0411 so the dedicated user can only see / modify vouchers they originated — minimising blast radius if credentials ever leak.

Try it on a JDE DV environment

Point Core Invoice at your JDE DEV environment, drop in a real supplier bill, and watch a PV voucher appear in P0411 — usually in under 15 seconds.

Start free with JDE How the OCR works