Connecting your ERP

Method 1: SFTP

The SFTP method is the most common choice for enterprise deployments. Arvexi provides a dedicated SFTP endpoint where your ERP or middleware drops files on a schedule.

To set up SFTP, navigate to Settings → Integrations → SFTP and generate your credentials. You will receive:

• Host and port: The Arvexi SFTP server address.
• Username: A unique service account tied to your organization.
• SSH key pair: Arvexi generates an RSA-4096 key pair. Download the private key and configure it in your ERP’s SFTP client. Password authentication is not supported.

Once connected, drop files into the /inbox directory. Arvexi polls for new files every five minutes by default (you can adjust the interval in scheduled imports). Processed files are moved to /archive with a timestamp suffix.

The SFTP integration uses ssh2-sftp-client under the hood, supporting key exchange algorithms up to diffie-hellman-group16-sha512 and AES-256-CTR encryption.

Method 2: Webhook API

The webhook method is a push-based integration for real-time or near-real-time data flow. Your ERP sends HTTP POST requests to Arvexi’s webhook endpoint with structured JSON payloads.

To configure webhooks, go to Settings → Integrations → Webhooks and create a new endpoint. Each endpoint gets:

• Endpoint URL: A unique HTTPS URL that accepts POST requests.
• Signing secret: An HMAC-SHA256 secret for payload verification. Include the signature in the X-Arvexi-Signature header so Arvexi can verify the request originated from your system.
• Idempotency keys: Every request must include an Idempotency-Key header. Arvexi stores keys for 48 hours and returns the cached response for duplicate requests, preventing double-imports from retries.

The webhook API accepts payloads up to 10 MB. For larger data sets, use the SFTP method or split the payload into batches with sequential idempotency keys.

Method 3: CSV/XLSX upload

For ad-hoc imports or initial data loads, upload files directly through the browser. Go to Data → Import and drag a CSV or XLSX file into the upload zone. This launches the Smart Import Wizard, which handles column mapping automatically.

Supported formats:

• CSV: UTF-8 encoded, comma or semicolon delimited. Headers in the first row.
• XLSX: Excel workbooks with data in the first sheet. Multiple sheets are supported if you specify the sheet name during upload.

Maximum file size for browser uploads is 50 MB (roughly 500,000 rows). For larger files, use the SFTP method.

Pre-built ERP templates

Arvexi includes six templates that pre-configure field mappings, date formats, and segment structures for the most common ERPs:

1. SAP S/4HANA: Maps BKPF/BSEG fields, supports cost center, profit center, and business area segments. Handles SAP date format (YYYYMMDD) automatically.
2. Oracle Fusion: Maps GL journal import fields, supports segment strings up to 30 segments, and validates balancing segments on export.
3. NetSuite: Maps standard CSV import format, supports subsidiary, department, class, and location dimensions.
4. Microsoft Dynamics 365: Maps financial dimension combinations, supports posting profiles, and handles Dynamics date/number localization.
5. Sage Intacct: Maps Sage CSV journal entry format, supports locations, departments, projects, and custom dimensions.
6. QuickBooks: Maps QuickBooks IIF and CSV import formats with simplified account mapping for small portfolios.

To use a template, go to Settings → Integrations → Templates, select your ERP, and customize any field mappings that differ from the defaults.

Choosing the right method

The best integration method depends on your volume, frequency, and IT constraints:

• SFTP: Best for scheduled batch imports (daily, weekly). Works with any ERP that supports SFTP exports. Most common for enterprise deployments.
• Webhook API: Best for real-time data flow or event-driven architectures. Requires your ERP or middleware to send HTTP requests.
• CSV/XLSX upload: Best for initial data loads, one-time imports, or teams that export from their ERP manually. No IT setup required.

You can use multiple methods simultaneously. For example, many teams use SFTP for automated daily feeds and CSV upload for historical data migration during implementation.