ERP Integration for Swiss Logistics: Abacus and Bexio Connections

Swiss SME logistics companies face a specific integration challenge: their accounting and invoicing runs on Abacus (market leader for Swiss mid-size companies) or Bexio (cloud-first alternative for smaller operators), while their operational data — deliveries, routes, proof of delivery — lives in their logistics software.

Without integration, staff re-enter data manually. Order confirmed in logistics software → manually entered into Abacus for invoicing → manually reconciled with bank statement → manually matched against payment. Each manual step adds cost and error risk.

Why ERP Integration Matters for Swiss Logistics

Swiss-specific factors:

• QR-bill standard: Every invoice must comply with SIX QR-bill standard. Logistics software must generate QR-bills that match Abacus/Bexio invoice records.
• MWST/TVA compliance: 8.1% VAT (standard rate 2025) must be correctly applied per service type. Logistics software generates the data; ERP processes the tax.
• Multiple currencies: Cross-border operators handle CHF, EUR, sometimes GBP. Currency conversion must be consistent across both systems.
• Abacus AbaConnect API: The standard integration interface for Abacus-connected software.

Abacus Integration Architecture

Abacus is the dominant ERP for Swiss companies with 10–250 employees. The integration pathway:

```

8Move BackOffice

↓ (API)

AbaConnect API (Abacus middleware)

↓

Abacus Financials (AbaFinance)

+ Abacus Debtors (AbaDebtors)

+ Abacus Orders (AbaOrder) [optional]

```

What syncs:

• Customer master data (new customers created in logistics software → pushed to Abacus debtors)
• Invoices (generated in logistics software from completed deliveries → posted to Abacus as debtors invoices)
• Payments (received in Abacus → marked as paid in logistics software)
• Credit notes (issued in logistics software for partial delivery → synced to Abacus)

AbaConnect technical requirements:

• Abacus version 2022 or later (AbaConnect REST API)
• API key from Abacus administrator
• Field mapping configuration (logistics software fields → Abacus account/cost center codes)

Integration depth options:

1. One-way push (basic): Logistics software pushes invoices to Abacus. No payment confirmation back. Minimum viable.
2. Two-way sync (standard): Invoices pushed, payment status pulled back. Requires scheduled sync (hourly or daily).
3. Real-time sync (advanced): Event-driven: invoice posted → immediately appears in Abacus; payment recorded → immediately marks invoice paid in logistics software.

Bexio Integration Architecture

Bexio targets Swiss SME with under 50 employees. Modern REST API makes integration simpler than Abacus.

```

8Move BackOffice

↓ (REST API)

Bexio API v2

↓

Bexio Invoicing + Contacts + Accounting

```

What syncs:

• Contact records (customers, suppliers)
• Invoices and credit notes
• Product/service catalog (delivery service types → Bexio positions)
• Payment confirmations

Bexio API advantages: OAuth 2.0, well-documented REST API, sandbox environment for testing, webhook support for real-time events.

Practical Integration Setup

Step 1: Data Model Mapping

Before writing any API calls, map your logistics data model to ERP accounts:

Logistics	Abacus/Bexio
Customer ID	Debtor account number
Service type: same-day delivery	Account 3200 (service revenue)
Service type: express	Account 3210
Fuel surcharge	Account 3230
VAT rate	Tax code (standard 8.1%)

This mapping is the most time-consuming part. Budget 2–4 days for a typical Swiss logistics operator.

Step 2: Invoice Generation Logic

In logistics software, define when an invoice is generated:

• Per delivery: Invoice for each completed delivery (common for B2C)
• Per route: Invoice for completed route (multiple deliveries to one customer)
• Weekly/monthly: Consolidated invoice for account customers (most common in B2B distribution)

Step 3: QR-Bill Generation

Swiss invoices require QR-bill format. The logistics software must:

1. Pull creditor IBAN from ERP configuration
2. Generate Swiss reference number (SCOR or QRR format)
3. Embed in invoice PDF in correct SIX QR standard format
4. Post to Abacus/Bexio with same reference for payment matching

Step 4: Payment Reconciliation

When customer pays via QR-bill scan → payment lands in your bank account with the reference number → bank statement imported to Abacus/Bexio → reference matched to outstanding invoice → payment confirmed back to logistics software.

Automated reconciliation eliminates the manual "who paid what" matching that consumes 2–4 hours per week in accounts receivable.

Common Integration Pitfalls

1. Cost center mapping errors: Logistics jobs get posted to wrong accounts in Abacus. Result: wrong financial reporting. Fix: validate first 50 invoices manually against ERP before going fully automated.

2. Duplicate customer records: Customer exists in both systems with slightly different names ("Mueller GmbH" vs "Müller GmbH"). Fix: establish golden record in Abacus and sync to logistics software, not vice versa.

3. VAT rate changes: Switzerland changed VAT rates in 2024. Hard-coded VAT rates in integration code need updates when rates change. Use configurable tax codes, not hard-coded percentages.

4. Currency mismatch: Delivery charged in EUR, Abacus account in CHF. Conversion rate must be explicitly configured per transaction date, not using a single fixed rate.

8Move BackOffice ERP Integration

8Move BackOffice has pre-built connectors for both Abacus (AbaConnect API) and Bexio (REST API v2). Configuration is done through a visual field mapping interface — no custom code required for standard integrations.

Combined with 8Move Fleet Planner, the full order-to-cash cycle is automated: route completed → delivery confirmed → invoice generated → QR-bill created → posted to Abacus/Bexio → payment matched automatically.

FAQ

How long does Abacus integration take?

Standard integration with field mapping: 5–10 days for a typical Swiss logistics SME. Complex configurations (multiple cost centers, cross-border VAT) add 3–5 days.

Does Bexio integration require an IT team?

No. Bexio's API is accessible to any developer with basic REST knowledge. 8Move BackOffice's pre-built connector requires only configuration, no coding.

What happens if Abacus is down?

The logistics software queues invoices locally and pushes when Abacus is back online. No data is lost; the queue is processed in order.

Can we use the integration if we're switching ERPs?

Integration architecture designed with clean separation (logistics software → middleware → ERP) makes ERP migrations easier — only the ERP connector changes, not the logistics software.