ABACUS API · INTEGRATION
Abacus API: AI connection to the Swiss ERP platform
Abacus web services connect ERP, payroll, and bookkeeping with AI workflows. REST endpoints, SOAP legacy, on-prem or cloud.
Researched & fact-checked by: DuneDive LLC · As of: 2026-05
What is the Abacus API?
Alongside Bexio, Abacus is the second major Swiss bookkeeping and ERP platform, with around 60,000 customers as of May 2026, mostly SMEs and fiduciary offices with a higher demand profile. In contrast to Bexio (cloud-only, Swiss cloud), Abacus offers two operating models in parallel: AbaWeb / Abacus Cloud on their own Swiss servers, and Abacus On-Prem for customers who run the ERP in their own data centre.
The Abacus API spans two generations. The older SOAP interface (Abacus Web Services, AWS) is XML-based and available since around 2008. It covers all modules (FibuLight, payroll, AbaImmo, AbaProject) and is the interface most existing integrations live on. The newer REST API (officially called AbacusOne API) has been available in the cloud since 2024 and is also supported in on-prem installations from version 2025.1 since May 2026.
For AI integrations the relevant REST endpoints are mainly for postings (/api/v1/accounting/postings), payroll data (/api/v1/payroll/employees), documents (/api/v1/documents), and addresses (/api/v1/addresses). Authentication runs via API keys (cloud) or Active-Directory integration (on-prem). The quota depends on the licence; standard is 100 calls per minute, higher tiers available.
Why it matters for Swiss fiduciary
Abacus is the platform for more complex mandates in Switzerland. Payroll with pension-fund variety, withholding-tax specifics, ELM-5 wage statements, real-estate management, project controlling, construction billing. If a mandate falls into one of these categories, it likely sits in Abacus.
AI connection is worthwhile for three reasons. First: the data volume is large and repetitive. An average Abacus mandate has 5,000 to 50,000 bookings per year and 50 to 5,000 receipts. These volumes are ideal for AI plausibility checks and anomaly detection. Second: data quality is high. Abacus mandates are usually run cleanly, which makes training AI workflows reassuring. Third: Abacus mandates demand more advisory. AI-supported client inquiries and plausibility reports justify hourly rates that are not feasible in classic bookkeeping service.
Here too the AI layer sits next to Abacus, not on top. We read postings, receipts, and payroll data, index them in a vector DB, and the LLM answers questions or generates proposals. Write operations run via the SOAP or REST API only after human release.
How it works
Setup depends on whether you target the cloud or on-prem variant. Both use the same endpoint layout, but authentication differs.
In the Abacus Cloud you receive an API key through the AbaWeb admin portal. The key is sent as an X-Abacus-API-Key header. In on-prem installations authentication runs via the Abacus Application Server with Basic Auth or NTLM. HTTPS is mandatory in both cases.
An example call to fetch all postings of a mandate in a date range:
```bash curl -X GET "https://cloud.abacus.ch/api/v1/accounting/postings?mandant=1234&from=2026-01-01&to=2026-03-31" \ -H "X-Abacus-API-Key: $API_KEY" \ -H "Accept: application/json" ```
The response contains a paginated array of posting objects with account, contra-account, amount, date, booking text, document number, VAT code. With more than 1,000 entries you paginate via ?page=2.
For AI use-cases the data pipeline typically runs nightly. We fetch new postings since the last run, process them through an anomaly-detection model, and write findings into a dashboard DB. The fiduciary sees the list of conspicuous cases from the day before in the morning. Corrective writes are currently still done manually in Abacus or via the SOAP service ImportPosting after explicit OK.
Abacus integration in 5 steps
- 01Check the operating model: AbaWeb cloud or on-prem? For on-prem check the version (>= 2025.1 for REST, otherwise SOAP).
- 02Set up API access: API key in the AbaWeb portal or AD integration on the Abacus Application Server.
- 03Set up the read pipeline: nightly sync of the relevant endpoints (postings, employees, documents), incremental via date filter.
- 04Define the AI layer: triage, plausibility, or client FAQ. Keep the use-case small first, then scale.
- 05Secure write operations with a staging mandate and a four-eyes principle; never write directly to production.
When to use
The Abacus integration is worthwhile mainly for three use-cases. First: payroll triage. Incoming personnel changes, sick reports, and expense receipts are pre-classified by AI; only unclear cases go to the payroll clerk. Second: P&L plausibility checks. Before the quarter or year-end close, an AI analysis runs over all postings and flags unusual patterns: accounts with unexpected movements, missing accruals, duplicate documents. Third: client FAQ over the ERP data. The client asks: how high were my personnel costs in Q1 compared to the previous year? The LLM reads the data via API and answers with sources.
The pipeline is also economically attractive. With a fiduciary office of 30 Abacus mandates and 2 hours of manual plausibility per quarter each, you save 240 hours per year. At an hourly rate of CHF 180 that is CHF 43,200 per year. The AI infrastructure costs a fraction of that.
When not to use
For very small mandates (under 1,000 postings per year) the pipeline effort is disproportionate to the benefit. Bexio is simpler here, or no AI layer at all.
If you can only use the legacy SOAP API (old on-prem version before 2025.1), the integration is more complex and slower. SOAP requests are verbose, the XML-to-JSON mapping is source-code-intensive, and performance is only 5 to 20 requests per second. An update to Abacus 2025.1 or later is the right precondition here.
For write-heavy bulk operations we recommend caution. Abacus bookkeeping is audit-relevant; a faulty bulk import can have accounting consequences. Write only via staging mandates and with double approval.
Trade-offs
STRENGTHS
- Full module coverage: bookkeeping, payroll, AbaImmo, AbaProject
- Choice of cloud or on-prem, Swiss hosting in both cases
- High data quality in existing mandates, ideal for AI use-cases
- REST API since 2025.1 with modern authentication
WEAKNESSES
- SOAP legacy in many installations, update to >=2025.1 needed for REST
- API in top tiers more expensive than cloud competitors
- Write operations are audit-relevant, caution required
- Setup effort higher than Bexio, typically 3-8 weeks
FAQ
REST or SOAP for new integrations?
REST, if the Abacus version is >= 2025.1. The REST API is simpler, faster (100 vs 20 calls/s), and better documented. SOAP only as fallback for legacy installations that cannot be updated.
Where does the cloud data sit?
AbaWeb hosts in Wittenbach (SG) and Bern. Swiss data centres, ISO-27001 certified. For FADP and professional-secrecy mandates the hosting is unproblematic.
Are there webhooks?
Abacus offers an event-subscription model from version 2025.2. You can subscribe to posting-created, payroll-completed, document-captured. In older versions you must poll, which noticeably raises performance load.
What does the API cost?
The API itself is included in the standard licences. Higher quota tiers (>100 calls/min) cost extra, typically CHF 50-200 per month. AI costs (LLM, embedding, vector DB) come on top.