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

# Upgrading to a Direct Connection

> How to seamlessly integrate your ERP or logistics system with Procuros via EDI, API, or file-based exchange.

<Note>
  **Prerequisite:** You must be active on WebEDI before starting this process.
</Note>

## Overview

Once you're live on WebEDI, you can upgrade to a **direct (seamless) connection** — exchanging documents automatically between your system and your trading partners, with no manual steps required. The integration runs across **four phases**, structured to collect the right data efficiently and reach a working connection as quickly as possible.

<AccordionGroup>
  <Accordion title="Phase A — Focus: Qualification & Scope">
    | Step | What happens                                                                                                                                                                                                                                                                                                                   | Who acts |
    | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- |
    | A.1  | You signal interest in a direct connection (EDI, JSON, CSV, XML, etc.)                                                                                                                                                                                                                                                         | **You**  |
    | A.2  | Procuros assesses technical feasibility and clarifies scope: which messages, format, and transport protocol                                                                                                                                                                                                                    | Procuros |
    | A.3  | You review the available integration options and confirm your preferred setup with Procuros: [API](https://docs.procuros.io/en/api/v2/overview) / [AS2](https://docs.procuros.io/en/connectors/as2/as2) / [X.400](https://docs.procuros.io/en/connectors/x400/x400) / [SFTP](https://docs.procuros.io/en/connectors/sftp/sftp) | **You**  |
    | A.4  | Your GLN configuration is verified — sender/receiver IDs and routing are confirmed correct                                                                                                                                                                                                                                     | **You**  |

    <Tip>
      Not sure which option fits your setup? Reach out to [edi@procuros.io](mailto:edi@procuros.io) — we'll walk you through the differences during step A.2.
    </Tip>
  </Accordion>

  <Accordion title="Phase B — Focus: Technical Setup">
    | Step | What happens                                                                                          | Who acts |
    | ---- | ----------------------------------------------------------------------------------------------------- | -------- |
    | B.1  | You confirm your preferred setup: format, protocol, and any certificates required                     | **You**  |
    | B.2  | Procuros establishes and tests the transport connection (AS2 handshake, SFTP credentials, or API key) | Procuros |
    | B.3  | Procuros configures the mapping and transformation logic for your data                                | Procuros |
  </Accordion>

  <Accordion title="Phase C — Focus: Test Inbound Orders">
    | Step | What happens                                                          | Who acts |
    | ---- | --------------------------------------------------------------------- | -------- |
    | C.1  | Procuros sends a test ORDER through your new connection               | Procuros |
    | C.2  | You confirm the order arrived correctly — or flag any issues          | **You**  |
    | C.3  | Procuros makes mapping adjustments as needed, iterated until approved | Procuros |
    | C.4  | 🟢 ORDER connection goes live                                         | Procuros |
  </Accordion>

  <Accordion title="Phase D — Focus: Test Outbound Documents">
    Repeated for each return channel document in scope:

    **(PRICAT — Price catalogue) → ORDRSP — Order response → DESADV — Despatch advice → INVOIC — Invoice → (INVRPT — Inventory report) → (SLSRPT — Sales report)**

    | Step | What happens                                                                                                           | Who acts |
    | ---- | ---------------------------------------------------------------------------------------------------------------------- | -------- |
    | D.1  | Procuros activates the expectation for the return channel document                                                     | Procuros |
    | D.2  | You submit a test message for that document type                                                                       | **You**  |
    | D.3  | Procuros validates the message (required fields, structure, mapping) and provides automatic approval or error feedback | Procuros |
    | D.4  | 🟢 Return channel document goes live                                                                                   | Procuros |

    <Info>
      Steps D.1–D.4 run separately for each document type in your scope. Documents in brackets (PRICAT, INVRPT, SLSRPT) are optional — your Procuros contact will confirm which apply.
    </Info>
  </Accordion>
</AccordionGroup>

***

## Need help?

Reach out at any point - we're here to make the integration as smooth as possible.

📧 [edi@procuros.io](mailto:edi@procuros.io)