> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoflo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# ERP Integrations: SAP, Oracle, and NetSuite with Neoflo

> Connect Neoflo to SAP, Oracle ERP Cloud, or NetSuite to automate invoice processing, journal entries, reconciliations, and financial reporting.

Your ERP is the system of record for every financial transaction your business processes — which means Neoflo's most important integrations are the ones that connect directly to it. Rather than maintaining a parallel system, Neoflo works within your ERP: pulling documents and transactions that need processing, applying AI-led automation with human review where required, and writing the completed results back to the right ledger accounts, cost centers, and workflows. The data never leaves your ERP ecosystem, and your finance team always has a full audit trail inside the system they already use.

<Tabs>
  <Tab title="SAP">
    ## SAP Integration

    Neoflo integrates with SAP S/4HANA and SAP ECC — the two most widely deployed SAP environments in enterprise finance. The connector covers the full range of routine financial operations that Neoflo manages on your behalf.

    ### What Neoflo automates in SAP

    * **AP invoice processing** — Neoflo receives invoices, extracts header and line-item data, matches against purchase orders and goods receipts, and posts approved invoices directly in SAP.
    * **GL journal posting** — For accruals, reclassifications, and period-end entries, Neoflo creates and posts journal entries to the correct GL accounts.
    * **Vendor master data** — Neoflo can read and validate vendor records to support accurate AP processing and flag discrepancies for your team.
    * **Payment runs** — Neoflo prepares payment proposals aligned to your payment terms and due dates, ready for final approval and execution in SAP.

    ### How the connection works

    Neoflo connects to SAP using **SAP APIs and BAPIs** (Business Application Programming Interfaces) for modern S/4HANA environments, giving it the ability to read and write data directly through SAP's standard integration layer. For older SAP ECC deployments where API access is limited, Neoflo supports **file-based exchange** via secure SFTP — uploading and downloading structured files that SAP processes through standard batch jobs.

    Your Neoflo integration engineer will assess your SAP version and landscape during onboarding and recommend the appropriate connection method.

    ### Supported SAP versions

    | Product                            | Connection Method             |
    | ---------------------------------- | ----------------------------- |
    | SAP S/4HANA (Cloud and On-Premise) | SAP REST APIs / OData / BAPIs |
    | SAP ECC 6.0                        | BAPIs or file-based exchange  |
  </Tab>

  <Tab title="Oracle ERP Cloud">
    ## Oracle ERP Cloud Integration

    Neoflo's Oracle ERP Cloud connector targets finance teams running Oracle Fusion Cloud Financials. It automates the high-volume, rules-driven work in AP, cash management, and financial close so your team can focus on exceptions and analysis.

    ### What Neoflo automates in Oracle

    * **AP automation** — Neoflo ingests supplier invoices, validates them against purchase orders and receipts, and submits approved invoices for posting in Oracle Payables.
    * **Cash management** — Neoflo supports bank statement reconciliation, matching transactions against Oracle cash positions and flagging unreconciled items for review.
    * **Financial close** — Neoflo assists with period-end tasks including journal entry preparation, account reconciliation, and supporting close checklist completion.

    ### How the connection works

    Neoflo connects to Oracle ERP Cloud using **Oracle REST APIs**, which are the standard integration mechanism for Oracle Fusion Cloud applications. The connection is authenticated using OAuth 2.0 and operates through Oracle's published API endpoints — no custom development is required on the Oracle side.

    Your Oracle environment does not need any additional modules or licenses to support the Neoflo integration. Access is configured through Oracle's standard role-based access control, with Neoflo operating under a dedicated integration user account.

    ### Supported Oracle products

    | Product                        | Connection Method            |
    | ------------------------------ | ---------------------------- |
    | Oracle Fusion Cloud Financials | Oracle REST APIs (OAuth 2.0) |
  </Tab>

  <Tab title="NetSuite">
    ## NetSuite Integration

    Neoflo's NetSuite connector is designed for companies running Oracle NetSuite as their core financial platform — common in mid-market and fast-growing businesses. The integration covers accounts payable, accounts receivable, general ledger, and bank reconciliation.

    ### What Neoflo automates in NetSuite

    * **Accounts payable** — Neoflo processes vendor invoices end to end: extraction, PO matching, approval routing, and bill creation in NetSuite.
    * **Accounts receivable** — Neoflo supports invoice generation, cash application, and collections follow-up, updating AR records directly in NetSuite.
    * **General ledger** — Neoflo creates journal entries for accruals, adjustments, and intercompany transactions, posting them to the correct NetSuite accounts.
    * **Bank reconciliation** — Neoflo matches bank statement transactions against NetSuite records and flags exceptions for your team to resolve.

    ### How the connection works

    Neoflo connects to NetSuite using a combination of **SuiteScript** (NetSuite's native scripting layer) and **NetSuite REST APIs**. SuiteScript enables deep, native interaction with NetSuite records and workflows, while the REST API layer handles real-time data exchange. This dual approach gives Neoflo the flexibility to handle both standard transactions and custom NetSuite configurations.

    The integration is set up under a dedicated NetSuite integration role with scoped permissions — Neoflo only accesses the records and modules required for the processes it manages.

    ### Supported NetSuite versions

    | Product                                | Connection Method                |
    | -------------------------------------- | -------------------------------- |
    | Oracle NetSuite (all current editions) | SuiteScript + NetSuite REST APIs |
  </Tab>
</Tabs>

## Integration setup process

Regardless of which ERP you use, the integration setup follows the same structured process — managed by Neoflo's integration team with minimal lift required from your side.

<Steps>
  <Step title="Provide system access">
    Your team provides the necessary API credentials, integration user accounts, or SFTP access details for your ERP environment. Neoflo's integration engineer will specify exactly what access is needed during the kickoff call.
  </Step>

  <Step title="Neoflo configures the integration">
    Neoflo's integration team sets up the connector, maps data fields to your ERP's chart of accounts, cost centers, and approval workflows, and configures any environment-specific settings (such as company codes, business units, or currencies).
  </Step>

  <Step title="Test data flows">
    Neoflo runs end-to-end tests using sample transactions in your staging or sandbox environment. Your team reviews the output to confirm that postings, field mappings, and approval routing match your requirements.
  </Step>

  <Step title="Go live">
    Once testing is complete and signed off, the integration is promoted to your production environment and Neoflo begins processing live transactions. Your team monitors results through the Neoflo dashboard and your ERP as normal.
  </Step>
</Steps>

<Note>
  All ERP connections use encrypted, authenticated API calls over HTTPS. Credentials and access tokens are stored in Neoflo's secure credential vault, which is encrypted at rest and never exposed in logs or UI interfaces. Neoflo operates under the principle of least privilege — integration accounts are scoped only to the modules and record types required for the processes Neoflo manages.
</Note>