SoftCo
Book a demo
JD EDWARDS ERP INTEGRATION

AP automation that fits your JD Edwards environment

SoftCo works with your JD Edwards environment as it is today, adapts when that environment changes, and doesn’t ask you to wait for an ERP migration to finish before you automate AP.

Talk to us about your JD Edwards environment
WHERE SOFTCO FITS

JD Edwards stays your system of record. SoftCo handles the work around it.

JD Edwards holds your financials, procurement and general ledger, and it remains the system of record for posting, payment and GL. SoftCo automates what happens before an invoice reaches JD Edwards: capture, matching, approval and exception handling.

HOW IT CONNECTS

How SoftCo connects to JD Edwards

The way SoftCo connects depends on your JD Edwards setup and your team. See how each method works, what data moves, and how the connection is secured.

JD Edwards EnterpriseOne

WORKS WITHJD Edwards EnterpriseOne 9.2 or later.

01

How it connects

MethodHow it worksWho runs it
JDE Orchestrator (sFTP or Web Service API)

Orchestrator processes in JD Edwards EnterpriseOne deliver data to SoftCo as sFTP files or direct Web Service API calls. Approved invoices return and are posted through JD Edwards’ standard voucher interface.

Shared.

Your JDE team builds the Orchestrator processes. SoftCo runs the SoftCo side.

Boomi JDE EnterpriseOne integration via AIS REST

SoftCo runs the integration on its own platform and connects to JD Edwards through its Application Interface Services (AIS) REST interface, using token authentication.

SoftCo-managed.

Your JDE administrator publishes the required Orchestrations. No licence for the integration platform is needed from you.

SoftCo REST API / sFTP

Your ERP, or your own integration layer, pushes and pulls data to SoftCo through the SoftCo REST API or sFTP.

Customer-run.

Your team handles extraction and delivery. No licence for the integration platform is needed from you.

SoftCo can also push approved invoices to an endpoint that you provide in JD Edwards.

02

What moves

Diagram of four data transfers between JD Edwards and SoftCo AP automation through the SoftCo integration layer. Master data and transactions flow from JD Edwards to SoftCo as required. Approved invoices flow from SoftCo to JD Edwards on approval. Posting and payment confirmation flow back from JD Edwards to SoftCo where configured.

  1. Master data

    JD Edwards to SoftCo, as required. Suppliers, GL codes, cost centres, payment terms, currencies.

  2. Transactions

    JD Edwards to SoftCo, as required. Purchase orders and goods receipts, for three-way matching.

  3. Invoices

    SoftCo to JD Edwards, on approval. Matched, coded and approved invoices, posted as vouchers.

  4. Confirmation

    JD Edwards to SoftCo, where configured. Posting and payment confirmation.

Approved invoices post through JD Edwards’ standard voucher and GL interface tables and are processed into the AP ledger. Posting and payment confirmation come back where configured.

03

How it’s secured

  • Connections can be outbound only, so no inbound access to your network is needed.

  • Files move over encrypted SSH and API calls use HTTPS with TLS. Access uses a dedicated, least-privilege JDE service account.

  • Approved vouchers post through JD Edwards’ standard interface tables, so activity stays traceable in JD Edwards’ own history.

Get the full technical overview for JD Edwards

WHAT CHANGES

From JD Edwards posting to automated AP. Here is what shifts.

  • Invoices post to JD Edwards automatically

    Approved invoices go from SoftCo into JD Edwards as vouchers, through the method documented for your setup. No manual re-keying.

  • Your JD Edwards data stays current

    Suppliers, GL codes, cost centres and payment terms sync from JD Edwards into SoftCo. Your AP team codes and matches against current data, not a stale extract.

  • Three-way matching uses your JD Edwards POs

    Purchase orders and goods receipts flow from JD Edwards into SoftCo for automated matching. Discrepancies are flagged before the invoice reaches JD Edwards.

  • Failures are visible

    When an invoice fails to post, you see it. Error handling and alerting are part of the integration design, so nothing fails silently.

JD EDWARDS MIGRATION

Moving on from JD Edwards? Your AP automation moves with you.

SoftCo connects to each ERP in its own right, so you can run JD Edwards alongside another platform. If you are moving from JD Edwards to Oracle NetSuite, Oracle Fusion or another ERP, SoftCo can connect to the platforms on either side of the move.

You do not need to finish the migration before you start. When it completes, SoftCo reconfigures the integration to the new platform as part of ongoing support.

Talk to us about your JD Edwards migrationSee Oracle ERP integration
SECURITY

Built on a dedicated, independently verified platform.

Every SoftCo customer runs on a dedicated instance, not a shared multi-tenant environment. The controls for JD Edwards are listed above.

  • 9.9/10

    RiskRecon rating, 100th percentile

  • ISO 27001

    Independently certified

  • SOC 1 and 2

    Independently audited

  • Dedicated

    One instance per customer, not shared multi-tenant

See SoftCo’s security in full
CLIENT SUCCESS

Proven in JD Edwards environments.

See all client success stories
FAQ

JD Edwards integrationquestions

1.Which JD Edwards versions does SoftCo support?

SoftCo supports JD Edwards EnterpriseOne 9.2 or later. The Tools Release needed depends on the method and is confirmed during scoping. If you run a different release, talk to us.

2.Which integration method is right for us?

That depends on your JD Edwards setup, your team’s capacity and your security requirements. SoftCo can run the integration for you through JD Edwards’ AIS REST interface, with your JDE administrator publishing the Orchestrations. If you would rather build the connection yourselves, JDE Orchestrator processes can deliver data to SoftCo by sFTP or web service. SoftCo recommends a method during scoping.

3.Is the data sync one-way or two-way?

Two-way. Supplier, GL, cost centre, payment terms, purchase order and goods receipt data come from JD Edwards. Approved invoices go from SoftCo to JD Edwards for posting. Posting and payment confirmation come back where configured.

4.Can SoftCo support JD Edwards alongside other ERPs?

Yes. SoftCo connects to each ERP independently, through the method that fits that environment. If you run JD Edwards alongside another ERP, both connect to the same SoftCo platform.

5.What happens if we move off JD Edwards?

SoftCo connects to each ERP independently, so it can connect to the platforms on either side of the move. You do not need to finish the migration before you start. When it completes, SoftCo reconfigures the integration to the new platform as part of ongoing support.

6.How are integration errors handled?

Error handling and alerting are designed with your team as part of the integration. Where SoftCo runs the integration, SoftCo configures and operates the error handling and monitoring.

7.What does my team need to provide?

It depends on the method. For SoftCo-managed integration through AIS REST, your JDE administrator builds and publishes the required Orchestrations, provides a dedicated service account and makes the JD Edwards AIS Server reachable, and SoftCo configures and operates the integration. For the Orchestrator method, your team builds the Orchestrator processes in JD Edwards. For the SoftCo REST API and sFTP method, your team handles extraction and delivery. None of the methods requires you to license SoftCo’s integration platform.

8.Who maintains the integration over time?

Where SoftCo runs the integration, SoftCo operates and maintains it, so ongoing maintenance is not your IT team’s project. Where your team runs part of the connection, such as Orchestrator processes, published Orchestrations or your own extraction and delivery, that part stays with your team. For a major platform migration, reconfiguration is required, and SoftCo handles it as part of ongoing support.

JD EDWARDS INTEGRATION

Tell us how you run JD Edwards. We’ll show you how it connects.

Every JD Edwards environment is different. Start with a conversation about yours. We’ll recommend the integration method that fits your setup, your security requirements and your team.

Book a demoExplore all ERP integrations

Trusted by finance teams. Recognised by analysts.