Oracle JD Edwards and Stampli integration

What moves between them

Approved invoices move from Stampli into Oracle JD Edwards. On a schedule you define, ml-connector polls Stampli's outbound SFTP directory for new invoice CSV files, extracts invoice, vendor, and GL account records, maps Stampli vendor IDs and GL account codes to their JD Edwards equivalents (F0401 Vendor Master and F0901 Account Master), and posts approved invoices into the JD Edwards Accounts Payable Ledger (F0411) using the AIS Server batch voucher service (F0411Z1). Vendor and GL account reference data is pulled in both directions to ensure JD Edwards knows about any new Stampli vendors or cost centers before invoice posting. The poll frequency aligns with your AP close cycle, typically every 4 to 24 hours.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Oracle JD Edwards side, it accepts the full customer AIS Server URL provided at credential setup, refreshes the session token when it expires (every 30 to 60 minutes), and polls the AIS Server using POST to the dataservice endpoints for F0401, F0901, and F0411 with date filters on UPMJ (date updated). On the Stampli side, it connects via SFTP using the provided hostname, port, username, and password, downloads files from the outbound directory, and parses CSV records. Vendor records from Stampli are matched to JD Edwards vendors by name and ID; GL accounts from Stampli are matched to JD Edwards GL accounts by code. If a matching vendor or account does not exist in JD Edwards, the invoice record is queued for manual review rather than failing. Invoices are deduplicated by Stampli's internal invoice ID carried in the CSV file. Because both systems are polling-only, there are no webhooks or pushed events; the cadence is entirely controlled by your connector schedule. Every invoice post carries a full audit trail and can be replayed if a downstream validation fails.

A real-world example

A mid-sized manufacturing company runs Oracle JD Edwards EnterpriseOne on premises for accounting and procurement, and uses Stampli to automate invoice receipt, approval routing, and payment. Before the integration, AP staff reviewed approved invoices in Stampli and manually entered each one into JD Edwards, a process that took hours per close cycle and created transcription errors, duplicate entries, and reconciliation delays. With Stampli and JD Edwards connected through ml-connector, approved invoices from Stampli flow directly into the JD Edwards AP Ledger on a daily or weekly schedule, properly allocated to the cost center and GL account from Stampli's matching and approval workflows. The company eliminates manual invoice re-entry, reduces AP close cycle time by 2 to 3 days, and gains an audit trail linking each Stampli approval decision to the posted JD Edwards transaction.

What you can do

• •Pull approved invoices from Stampli and post them directly into Oracle JD Edwards Accounts Payable Ledger (F0411) on a schedule tied to your AP close cycle.
• •Map Stampli vendor IDs and GL account codes to Oracle JD Edwards Vendor Master (F0401) and Account Master (F0901) to ensure every invoice posts to a valid account and cost center.
• •Authenticate Oracle JD Edwards with session tokens on a customer-hosted AIS Server URL, and Stampli with SFTP credentials, handling token refresh and connection management.
• •Deduplicate invoices using Stampli's internal invoice ID and audit every record posted into Oracle JD Edwards with full traceability and replay capability.
• •Synchronize vendor and GL account reference data in both directions to keep Stampli's cost centers and account codes aligned with Oracle JD Edwards before invoice posting begins.

Questions

How do invoices move from Stampli into Oracle JD Edwards?

ml-connector polls Stampli's outbound SFTP directory for new approved invoice CSV files on your defined schedule, extracts the invoice, vendor, and account records, maps them to Oracle JD Edwards identifiers, and posts them into the Accounts Payable Ledger (F0411) using the AIS Server batch voucher service. Vendor and GL account references are synchronized first to ensure every invoice posts to a valid account.

Does the integration require a public AIS Server or special network configuration?

The AIS Server runs at your customer infrastructure on a customer-provided hostname and port. If your AIS Server is behind an IP allowlist, you must whitelist the connector egress IPs at the beginning of integration setup. The connector stores the full AIS Server URL as a credential and authenticates via session token with the username and password you provide.

What happens if Stampli exports an invoice for a vendor that does not exist in Oracle JD Edwards?

The invoice record is queued for manual review and inspection rather than failing the entire sync. Meanwhile, ml-connector pulls reference data from both Stampli and Oracle JD Edwards to identify new vendors and GL accounts that need to be synchronized. Once the missing vendor is created in Oracle JD Edwards (either manually or via the next reference-data sync), the queued invoice can be replayed and posted without re-downloading from Stampli.