SoftCo
Book a demo
ORACLE ERP INTEGRATION

AP automation that fits your Oracle environment

SoftCo works with your Oracle 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 Oracle environment
WHERE SOFTCO FITS

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

Oracle 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 Oracle: capture, matching, approval and exception handling.

HOW IT CONNECTS

How SoftCo connects to each Oracle platform

Each Oracle platform has a different architecture, so the way SoftCo connects differs for each. Choose your platform to see how it connects, what data moves, and how the connection is secured.

Oracle EBS

WORKS WITHOracle E-Business Suite R12.1.3 or higher. R12.2 recommended.

01

How it connects

MethodHow it worksWho runs it
Oracle Concurrent Program (sFTP or Web API)

Scheduled exports from EBS reach SoftCo as sFTP files or direct API calls. Approved invoices return through Oracle’s standard AP interface.

Shared.

Your EBS team sets up the Concurrent Programs. SoftCo runs the SoftCo side.

Oracle API / SQL

SoftCo retrieves data from EBS using SQL, and approved invoices are posted through Oracle’s standard AP interface.

Shared.

Needs your Oracle DBA.

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.

SoftCo can also push approved invoices to an Oracle endpoint that you provide.

02

What moves

Diagram of four data transfers between an ERP and SoftCo AP automation through the SoftCo integration layer. Master data and transactions flow from the ERP to SoftCo. Approved invoices flow from SoftCo to the ERP. Posting confirmation flows back from the ERP to SoftCo.

  1. Master data

    ERP to SoftCo, scheduled. Suppliers, GL codes, cost centres, payment terms, currencies.

  2. Transactions

    ERP to SoftCo, scheduled. Purchase orders and goods receipts, for three-way matching.

  3. Invoices

    SoftCo to ERP, after approval. Matched, coded and approved invoices, ready to post.

  4. Confirmation

    ERP to SoftCo, after the ERP has processed. Posting confirmation, payment status.

Approved invoices post through Oracle’s standard AP interface and AP Import.

03

How it’s secured

  • File transfers use encrypted SSH and API calls use TLS 1.2+. Access is restricted by firewall and IP allowlisting.

  • The database route is read-only. Invoices post through Oracle’s standard interface tables, not direct inserts.

  • Processed files are archived rather than deleted, with 30-day retention by default.

Get the full technical overview for Oracle EBS

Oracle Fusion

WORKS WITHOracle Fusion Cloud ERP, with Accounts Payable and Purchasing.

01

How it connects

MethodHow it worksWho runs it
Boomi Oracle Fusion Connector

SoftCo runs a certified connector on its own integration platform. It connects to Oracle Fusion through Oracle’s REST APIs, using OAuth 2.0.

SoftCo-managed.

No licence for the integration platform is needed from you.

Oracle Integration Cloud (OIC)

Your Oracle Integration Cloud instance connects Fusion to SoftCo by sFTP or web service.

Customer-run.

Your team builds and maintains the OIC flows, on your own OIC licence.

02

What moves

Diagram of four data transfers between an ERP and SoftCo AP automation through the SoftCo integration layer. Master data and transactions flow from the ERP to SoftCo. Approved invoices flow from SoftCo to the ERP. Posting confirmation flows back from the ERP to SoftCo.

  1. Master data

    ERP to SoftCo, scheduled. Suppliers, GL codes, cost centres, payment terms, currencies.

  2. Transactions

    ERP to SoftCo, scheduled. Purchase orders and goods receipts, for three-way matching.

  3. Invoices

    SoftCo to ERP, after approval. Matched, coded and approved invoices, ready to post.

  4. Confirmation

    ERP to SoftCo, after the ERP has processed. Posting confirmation, payment status.

Approved invoices post to the Fusion AP module. Fusion returns a transaction reference after a successful post.

03

How it’s secured

  • OAuth 2.0 with your own identity provider, using a dedicated non-person service account and role-based access scoped to the data the integration needs.

  • TLS 1.2+ on all API calls. Credentials are held in SoftCo’s encrypted credential store.

  • The SoftCo-managed connector can run inside your network and only make outbound connections, so no inbound firewall rules are needed.

Get the full technical overview for Oracle Fusion

Oracle NetSuite

WORKS WITHOracle NetSuite, including multi-subsidiary setups.

01

How it connects

MethodHow it worksWho runs it
Boomi NetSuite Connector

SoftCo runs a certified connector on its own integration platform. It calls NetSuite’s SuiteTalk web services.

SoftCo-managed.

No licence for the integration platform is needed from you.

SoftCo REST API / sFTP

Your ERP side pushes and pulls data or files 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.

02

What moves

Diagram of four data transfers between an ERP and SoftCo AP automation through the SoftCo integration layer. Master data and transactions flow from the ERP to SoftCo. Approved invoices flow from SoftCo to the ERP. Posting confirmation flows back from the ERP to SoftCo.

  1. Master data

    ERP to SoftCo, scheduled. Suppliers, GL codes, cost centres, payment terms, currencies.

  2. Transactions

    ERP to SoftCo, scheduled. Purchase orders and goods receipts, for three-way matching.

  3. Invoices

    SoftCo to ERP, after approval. Matched, coded and approved invoices, ready to post.

  4. Confirmation

    ERP to SoftCo, after the ERP has processed. Posting confirmation, payment status.

Approved invoices are created as vendor bills, and credit memos as vendor credits.

03

How it’s secured

  • Token-based authentication with a dedicated, least-privilege integration role. No administrative or configuration access.

  • HTTPS with TLS. Credentials are held in SoftCo’s encrypted credential store.

  • Every vendor bill and credit created by SoftCo carries a SoftCo reference for traceability, and NetSuite’s own audit trail records the calls.

Get the full technical overview for Oracle NetSuite

WHAT CHANGES

From Oracle posting to automated AP. Here is what shifts.

  • Invoices post to Oracle automatically

    Approved invoices go from SoftCo into your Oracle AP module through the method documented for your platform. No manual re-keying.

  • Your Oracle data stays current

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

  • Three-way matching uses your Oracle POs

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

  • Failures are visible

    When an invoice fails to post, you see it. Errors are logged and visible to your team, so nothing fails silently.

ORACLE MIGRATION

Moving between Oracle platforms? Your AP automation moves with you.

SoftCo connects to each Oracle platform in its own right, so you can run more than one at once. If you are moving from EBS to Fusion, or from JD Edwards to NetSuite, 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 Oracle migration
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 each Oracle platform are listed in the tabs 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 Oracle environments.

See all client success stories
FAQ

Oracle integrationquestions

1.Which Oracle platforms and versions does SoftCo support?

SoftCo supports Oracle E-Business Suite R12.1.3 or higher (R12.2 recommended), Oracle Fusion Cloud ERP with Accounts Payable and Purchasing, and Oracle NetSuite. Each has its own documented integration methods. JD Edwards EnterpriseOne connects through Orchestrator processes to SoftCo’s sFTP or Web Service API. Versions and modules are confirmed during scoping. If you run a different Oracle platform, talk to us.

2.Which integration method is right for us?

That depends on your Oracle platform, your team’s capacity and your security requirements. For Fusion and NetSuite, SoftCo can run the integration for you. For EBS, and for Fusion customers who choose Oracle Integration Cloud, your team sets up part of the connection. SoftCo recommends a method during scoping.

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

Two-way. Four data transfers run between Oracle and SoftCo. Master data and transaction data come from Oracle: suppliers, GL codes, cost centres, payment terms, purchase orders and goods receipts. Approved invoices go from SoftCo to Oracle for posting. Posting confirmation comes back from Oracle to SoftCo, and on Fusion and NetSuite so does payment confirmation.

4.Can SoftCo support multiple Oracle platforms or entities?

Yes. SoftCo connects to each Oracle platform independently, through the method that fits that environment. If you run Fusion in one region and NetSuite in another, both connect to the same SoftCo platform. For multi-entity NetSuite customers, subsidiaries are mapped to SoftCo organisations during scoping.

5.What happens during an EBS to Fusion migration?

SoftCo connects to each Oracle platform 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?

On Fusion and NetSuite, a failed posting surfaces in the SoftCo ERP Exceptions queue, where your team can review it and resubmit once it is resolved. On EBS, failed API calls return a response code and are logged, and file exchanges are monitored at file level.

7.What does my team need to provide?

It depends on the method. For SoftCo-managed connectors, your team provides access, a dedicated integration account and confirmation of your mappings, and SoftCo builds and runs the integration. For EBS, your team registers the Concurrent Programs or provides database access. For Oracle Integration Cloud, your team builds and maintains the flows on your own OIC licence. None of the methods requires you to license SoftCo’s integration platform.

8.How is the integration kept up to date when Oracle releases updates?

For version updates within the same platform, SoftCo-managed connectors are kept compatible at the platform level and your configuration carries forward. Where your team runs part of the connection, such as EBS Concurrent Programs or OIC flows, that part stays with your team. For major platform migrations, reconfiguration is required, and SoftCo handles it as part of ongoing support.

ORACLE INTEGRATION

Tell us which Oracle platforms you run. We’ll show you how they connect.

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

Book a demoExplore all ERP integrations

Trusted by finance teams. Recognised by analysts.