Date: 2026-03-31 Status: Research complete - critical unknowns require access to a running instance
abas ERP is a German manufacturing-focused ERP (make-to-order, engineer-to-order) founded in 1981 in Karlsruhe, acquired by Forterro (UK) in 2019. It serves ~4,000 mid-market manufacturing and distribution companies across 27 countries with ~120,000 users. The system runs on a proprietary object-oriented database (not SQL-based), typically on Linux, with cloud, on-premise, and hybrid deployment options.
The primary integration path is the abas REST API, a Docker-deployed middleware that exposes all ERP objects generically via obj/data/<table>:<group> URLs. It supports full CRUD through a workspace/editor/commit pattern, uses HATEOAS for state transitions, and authenticates via HTTP Basic Auth or OAuth 2.0 Client Credentials (Keycloak, from version 20+). There are no invoice-specific or accounting-specific endpoints -- everything goes through the same generic object addressing. The critical gap is that the specific table:group identifiers for accounting objects (AP invoices, vendors, GL accounts, cost centers, journal entries) are not publicly documented.
No unified API intermediary (Maesn, Celigo, Chift) supports abas ERP. No mainstream iPaaS (Make, Zapier) has a connector. The realistic integration path is direct REST API access, potentially supplemented by abas Connect (the vendor's included low-code integration tool) on the customer side. SoftProject X4 has a dedicated connector via the JEDP interface, and Alumio offers generic API-based connectivity.
| Capability | Available? | Method | Confidence | Notes |
|---|---|---|---|---|
| REST API (read) | Via generic obj/data/<table>:<group> endpoints |
GET with HATEOAS, selection criteria, full-text search | High | Demonstrated for customers (0:1), products (2:1), opportunities (3:30) |
| REST API (write/create) | Via workspace/editor/commit pattern | POST to open editor, set fields, commit | High | Demo shows creating opportunities; same pattern for any writable object |
| OAuth 2.0 authentication | From abas ERP 20+ | Keycloak Client Credentials flow | High | Token endpoint: /auth/realms/abas/protocol/openid-connect/token |
| HTTP Basic Auth | Yes | Standard HTTP header | High | Supported alongside OAuth 2.0 |
| VPN-less remote API access | Via abas Cloud Connect | Outbound HTTPS tunnel, TLS 1.3, OAuth 2.0 | Medium | No inbound ports required on customer network |
| AP invoice creation via API | Architecturally possible, not publicly demonstrated | REST API POST to unknown table:group |
Medium | REST API covers "all" ERP objects; no public example for AP invoices specifically |
| PDF attachment via API | Not confirmed | DMS module exists; REST API file upload not documented | Low | DMS supports linking documents to objects in UI; API-level attachment unclear |
| eInvoice (ZUGFeRD/XRechnung) | Yes, outbound and incoming | Built-in eInvoice module | High | Outbound creation + incoming ZUGFeRD processing |
| EDI support | Yes | EDIFACT, VDA, ODETTE, ANSI X12 | High | Graphical EDI configuration tool included |
| Master data: customers | Yes, via REST API | obj/data/0:1 |
High | Demonstrated in demo clients |
| Master data: vendors | Likely accessible, table:group unknown |
REST API obj/data/<unknown> |
Medium | Purchasing module references vendors |
| Master data: chart of accounts | Likely accessible, table:group unknown |
REST API obj/data/<unknown> |
Medium | Configurable chart of accounts exists in FA module |
| Master data: cost centers | Likely accessible, table:group unknown |
REST API obj/data/<unknown> |
Medium | Cost center accounting is a defined module |
| Journal entries / historical bookings | Likely readable, not publicly demonstrated | REST API read of accounting objects | Low-Medium | Commercient SYNC lists "GL" as syncable data |
| Webhooks / push notifications | Not found | N/A | High (absent) | No webhook capability in any documentation |
| Event-driven outbound | Via BPM event handlers | Screen events triggering workflows that call external REST | Medium | Requires server-side fop.txt configuration |
| SOAP web services | Mentioned, not detailed | SOAP | Medium | Multiple sources mention it; no WSDL or endpoint docs found |
| Object metadata discovery | Yes | GET obj/meta/ |
High | Self-describing API; enumerates all tables, fields, types |
| Sandbox / trial environment | Not publicly available | N/A | Medium | Docker images require partner/extranet credentials |
| Concurrent API connections | Configurable EDPSession pool | erp.connection-<id>.cfg |
Medium | Pool settings exist; default limits undocumented |
| API rate limits | Not documented | N/A | Unknown | No public information |
"Abas ERP is an enterprise resource planning (ERP) and e-business application for manufacturers such as those using make to order and other related sales models." -- Wikipedia
"On June 19th, 1980, the students Peter Forscht and Werner Strub, together with three fellow students, founded Abakus GmbH in Karlsruhe, Germany." -- abas 40th anniversary
"Abas was sold to United Kingdom-based industrial software company Forterro in 2019." -- Wikipedia
"a privately held ERP vendor headquartered in Germany with subsidiaries and partners in 27 countries [...] provides a complete ERP portfolio to 4,000 mid-market manufacturing and distribution businesses around the world" -- Forterro acquisition announcement
"abas uses its own open, object oriented database [...] called Abas Open Object Oriented Database, an alternative to traditional relational databases." -- abas FAQ
"ABAS is a commercial ERP System from ABAS AG in Karlsruhe, Germany" using "a server client model with a proprietary object oriented data base" -- jschwender/abas wiki
"The system is deployable via the cloud or on-premise and can be accessed via any desktop browser and its native mobile iOS and Android apps." -- Wikipedia
abas ERP is a vertically-integrated manufacturing ERP with its own proprietary object-oriented database -- architecturally unusual compared to systems built on PostgreSQL/SQL Server/Oracle. External data access goes through defined interfaces (REST API, JEDP/EDP protocol, ODBC, AJO) rather than direct database queries.
Founded 1980 in Karlsruhe, first product release 1981. Acquired by Forterro 2019. Targets mid-market manufacturing (make-to-order, engineer-to-order). ~4,000 customers, 27 countries, ~120,000 users. Covers purchasing, sales, production planning, materials management, warehouse management, service, and financial accounting (GL, AP, AR, cost accounting, cost centers, cash management). Server runs on Linux (RedHat/Debian). Latest documented version: abas 2024.Q3.
Confidence: High. Multiple consistent sources.
"Standardized communication between different systems is flexible and easy with the integration tool Abas Connect, which is included in the standard release." -- abas Connectivity & IoT
"Interfaces can be setup and maintained purely via configuration in a graphical user interface - without any programming." -- abas Connectivity & IoT
"The Abas ERP Connector connects to the Abas ERP system via its JEDP interface and performs various operations. The connector uses the JEDP library of abas (jedp-3.3.5.jar)." -- SoftProject X4 docs
"Alumio [...] offers many connection capabilities right out of the box: RestAPI, GraphQL, SOAP, Databases, and filesystems." -- Alumio
"Commercient's SYNC integration app for abas ERP and Salesforce gives you a two-way integration [...] compatible with all versions of abas ERP Cloud and on-premise." -- Salesforce AppExchange
Maesn supported integrations: "AbaConnect, Abacus, bexio, BuchhaltungsButler, DATEV Rechnungswesen, DATEV Unternehmen Online, Exact Online, fortnox, FreeAgent, FreshBooks, Holded, Lexware Office, Microsoft Business Central, Moneybird, Odoo, Pennylane, Qonto, QuickBooks, Sage Active, Sage Accounting, sevdesk, Snelstart, Twinfield, Visma e-conomic, Visma eAccounting (Spiris), weclapp, Xentral, Xero" -- docs.maesn.com/llms.txt
| Platform | abas ERP Support | Confidence |
|---|---|---|
| Maesn | No. Lists "Abacus" (Swiss system), not abas ERP | High (verified full list) |
| Celigo | No. Has AFAS ERP (Dutch), not abas | High |
| Chift | No | High |
| Make | No native connector | High |
| Zapier | No native connector | High |
| MuleSoft | Not found | Low |
| Dell Boomi | Not found | Low |
Platforms with confirmed abas ERP connectors:
| Platform | Type | Direction | Details |
|---|---|---|---|
| abas Connect | Native low-code integration tool | Bidirectional | Included in standard release. Graphical route editor. No programming required. |
| SoftProject X4 | Dedicated connector via JEDP | Read/write | German BPM/iPaaS. Uses jedp-3.3.5.jar library. Queries, updates, insertions. |
| Alumio | Generic API connector | Bidirectional via REST | Dutch iPaaS. Claims customers, products, orders, invoices. Likely a REST API wrapper, not deeply pre-built. |
| Commercient SYNC | Pre-built sync | Bidirectional | Syncs customers, invoices, projects, items, inventory, GL. Uses "abas ERP API/SDK/import routine." |
| Softzoll | EDI connector | Bidirectional | Dedicated abas connector supporting IHSS interfaces and EDP/DDE. |
No AP automation competitor has confirmed abas integration: DocBits (Infor+SAP only), Medius (Microsoft/Oracle/SAP/Infor/Sage), Basware (claims 250+ ERPs but no specific abas mention), Kofax/Tungsten (SAP/Microsoft/NetSuite/Oracle), Stampli (70+ ERPs, none named abas).
Confidence: High that no unified API or mainstream iPaaS covers abas. High for abas Connect and SoftProject. Medium for Alumio (marketing page, limited technical detail).
"From abas ERP 20, the abas REST API supports the OAuth2 protocol." -- abas REST API Guide
"M2M applications use the Client Credentials Flow to pass along their client ID and client secret to authenticate themselves and receive a token." -- abas REST API Guide
"To authenticate with client ID and client secret, you make a POST request to
http://<hostname>:<port>/auth/realms/abas/protocol/openid-connect/tokenwith grant_type=client_credentials, client_id=rest_api, audience=erp." -- abas REST API Guide
"The abas REST API server is installed as a Docker container and runs in an isolated environment." -- abas REST API Admin Guide
"Cloud Connect [...] creates a secured tunnel to the abas cloud [...] uses a connection via the outbound HTTPS port and acts as a reverse proxy between the on-premise network and the abas cloud." -- abas Cloud Connect docs
"No inbound port is required, and the on-premise infrastructure can be accessed securely via the Internet." -- abas Cloud Connect docs
"All examples use the common base URL
http[s]://{hostname}[:{port}]/mw/r/{clientId}/" -- abas REST API Guide
Authentication methods:
Token endpoint: http://<hostname>:<port>/auth/realms/abas/protocol/openid-connect/token
grant_type=client_credentials, client_id=rest_api, audience=erpBase URL pattern:
https://{hostname}:{port}/mw/r/{clientId}/obj/data/<table>:<group>
Where {clientId} is the abas mandant (tenant/company).
Deployment: REST API middleware runs as a Docker container alongside the ERP server. Connects to abas Essentials via EDPSession pools configured in erp.connection-<id>.cfg files.
Remote access: abas Cloud Connect creates an outbound HTTPS tunnel (TLS 1.3) from on-premise to abas cloud infrastructure. No inbound ports required. Supports enterprise IdPs (AD, LDAP, SAML, OIDC) via OAuth 2.0.
Data format: Custom media type application/abas.objects+json.
Developer portal / sandbox: No public self-service developer portal. API documentation is hosted by each REST API middleware instance itself (the 91.112.198.60 address in search results is a specific installation). Access requires a customer or partner relationship.
Confidence: High for authentication mechanisms and URL structure (directly from API guide). Medium for Cloud Connect details (single source).
"Routine activities such as recording, distributing and posting incoming invoices can be fully automated with automatic invoice processing." -- abas Document Management
"It is possible to directly allocate invoices to incoming packing slips that have not been paid yet, subsequently verify invoices, and automatically post them to the accounts payable." -- abas Purchasing
"Abas offers the option of creating outgoing eInvoices in the structured electronic formats ZUGFeRD and XRechnung in compliance with EU standards." -- abas E-Invoice
"[abas offers] a system-based processing procedure for incoming ZUGFeRD invoices, creating technical prerequisites for a step-by-step path to digitizing incoming invoice processing." -- abas E-Invoice
"The purchase order is the basis for the later account assignment of the incoming invoice." -- abas Purchasing
"Abas offers a REST API web interface [...] that enables read and write data access to Abas ERP in real time using the ERP core logic as well as all company-specific customizations." -- abas RESTful API blog
How invoices enter abas ERP:
table:group identifier is not publicly documentedThe generic REST API write workflow:
POST obj/data/<table>:<group> to open an editor in a workspacePOST field values to the editor (using HATEOAS links from the response)POST to urn:abas:rel:editor:COMMIT to savePOST to urn:abas:rel:workingset:CLOSE to release the workspacePDF attachment: The DMS module supports linking documents to ERP objects (drag-and-drop in UI, barcode assignment, DMS connector for third-party systems). No REST API endpoint for binary file upload was found in public documentation.
Required fields for AP invoices: Unknown. Would need to be discovered via GET obj/meta/<invoice-table>:<group> on a running system.
Confidence: Medium. The REST API architecture supports writing any object type, and AP invoices exist as objects. But specific addressing, field requirements, and whether business logic validation allows API-driven invoice creation are not publicly confirmed.
"Customers can be found at /mw/r/test/obj/data/0:1" -- abas REST API Guide
"The example searches at most 1000 products (objects in obj/data/2:1) with search words and prints fields such as nummer." -- GitHub: abas-rest-api-demo-clients
"The resources under obj/meta/ provide read-only access to the abas Essentials database's metadata, where information about field names and types can be found for all abas Essentials tables and infosystems." -- abas REST API Guide
"The API supports querying objects using ERP selection syntax, such as GET obj/data/0:1?criteria=sucherw=The Outdoor Store USA Inc." -- abas REST API Guide
"abas ERP allows you to set up a chart of accounts that meets your company's requirements." -- abas Financial Accounting
"Cost accounting in abas ERP includes cost center accounting, which shows which costs were incurred in which organizational units." -- abas Controlling
Known object addresses:
| Object Type | table:group | Source |
|---|---|---|
| Customers | 0:1 |
API Guide, demo clients |
| Customer contacts | 0:2 |
Community docs |
| Prospective customers | 0:6 |
Community docs |
| Products/Parts | 2:1 |
Demo clients |
| Web orders | 3:25 |
Community docs |
| Opportunities | 3:30 |
Demo clients |
| Feedback records | 9:2 |
Community docs |
Not publicly documented: Vendors/suppliers, GL accounts, cost centers, AP invoices, journal entries, open items. No complete table:group catalog exists in any public source.
Discovery mechanism: GET obj/meta/ enumerates all tables and infosystems with field names and types. This is the self-describing path to discovering all object types on a running system.
Querying: Supports ERP selection syntax via criteria parameter, plus full-text search with live field enrichment.
Confidence: High for customers and products (demonstrated). Medium for accounting master data (modules exist, API is generic, but specific addressing requires a running instance).
"The settlement of payments against outstanding items and the transfer of data from purchasing to financial accounting are possible in real time." -- abas Financial Accounting
"Most financial entries are generated automatically, such as purchasing and sales, payment, fixed asset and material entries." -- abas Financial Accounting
"Uni- or bi-directional SYNC that can integrate ERP data such as Customers, Invoices, Projects, Terms Payments, Items, Inventory, BOMs, Jobs, Estimates, Sales People, GL, and other ERP data." -- Commercient SYNC
The REST API's generic read capability should extend to journal entries and posted transactions since these are ERP objects in the abas database. Commercient SYNC explicitly lists "GL" and "Invoices" as syncable data, confirming these objects are programmatically accessible.
No public documentation demonstrates reading journal entries, open items, or posting history via the REST API. The specific table:group identifiers for these accounting objects are not publicly known. The obj/meta/ discovery endpoint would reveal them on a running system.
Confidence: Low-Medium. Indirect evidence (Commercient syncs GL; API is generic) suggests it's possible, but no direct demonstration exists.
"The response of a POST request with an action contains the changed field itself as well as all other fields whose values have changed implicitly." -- abas REST API Guide
"To use the trigger, you must enter the abas BPM event handler in fop.txt [...] enter the screen number, the screen event and the abas BPM event handler." -- abas BPM Toolkit
"You can start workflows via a selected screen event which has been defined in the trigger." -- abas BPM Admin Overview
"If a notification has been defined, notifications are sent for the following events: User Task has been created, User Task has been assigned, User Task has been completed." -- abas BPM Workflow Designer
No webhooks. No push notification mechanism from abas to external systems was found.
Synchronous response on write: REST API returns changed field values synchronously in the POST response. Validation errors would be returned immediately.
Event-driven outbound (via BPM): abas BPM provides event handlers that trigger on screen events (maskein = screen enter, maskpruef = screen validation, maskende = screen end/save). These can start workflows that call external REST endpoints. This is the closest thing to a webhook -- requires server-side configuration in fop.txt and BPM workflow definition.
Polling alternative: The REST API supports reading objects with selection criteria. If accounting objects have modification timestamp fields, polling for changes since a timestamp may be possible.
Confidence: High that webhooks don't exist. Medium for BPM-based outbound events (documented but requires significant server-side setup by the customer).
| Question | Why It Matters | What Was Tried | Next Step |
|---|---|---|---|
What table:group addresses AP invoices? |
Required to know the REST API endpoint for creating invoices | Searched API guide, demos, community docs; only found customer/product/opportunity examples | Access a running instance, query GET obj/meta/ to enumerate all object types |
What table:group addresses vendors, GL accounts, cost centers, journal entries? |
Required for master data reads and booking history | Extensive search; only 0:1 (customers), 2:1 (products), 3:30 (opportunities) found publicly |
Same: obj/meta/ enumeration on a live system |
| Can the REST API upload binary files (PDFs) and link them to objects? | Orcha needs to attach source PDFs to posted invoices | Searched for file upload, DMS API; found DMS UI capabilities but no REST API file upload endpoint | Check REST API guide on binary content types; test multipart POST on live system |
| What fields are required for AP invoice creation? | Defines the mapping from Orcha structured data | No public field-level documentation for accounting objects | Query obj/meta/<invoice-table> on a live system |
| Are there modification timestamp fields on accounting objects? | Enables change detection without webhooks (polling) | Not addressed in public docs | Check field metadata via obj/meta/ |
| What are EDPSession pool limits / concurrent connections? | Affects throughput and integration architecture | Found pool is configurable in erp.connection-<id>.cfg but no defaults documented |
Check config template in a REST API installation |
| Does the REST API expose infosystems for accounting summaries? | Alternative read path for financial data | obj/meta/ documented as covering infosystems; no accounting-specific infosystem identified |
Enumerate infosystems via obj/meta/ |
| What SOAP services exist and what WSDLs are available? | Alternative or additional API surface | Wikipedia and product pages mention SOAP; abas eB mentions a "Web service Editor"; no WSDLs found | Request WSDL catalog from abas partner |
| How do we get developer/partner access? | Docker images and full docs require partner credentials | No self-service signup found | Contact abas/Forterro partnership team |
Requires a running abas ERP instance with REST API middleware. Access would come through an abas partner or a customer's test system.
Step 1: Discover all object types
GET /mw/r/{clientId}/obj/meta/
Catalog all table:group identifiers. Identify which correspond to: vendors, GL accounts, cost centers, AP invoices, journal entries, open items.
Step 2: Read accounting master data
GET /mw/r/{clientId}/obj/data/<vendor-table>:<group>
GET /mw/r/{clientId}/obj/data/<gl-account-table>:<group>
GET /mw/r/{clientId}/obj/data/<cost-center-table>:<group>
Step 3: Inspect AP invoice field metadata
GET /mw/r/{clientId}/obj/meta/<invoice-table>:<group>
Document required fields, data types, validation rules.
Step 4: Create a test AP invoice Follow workspace/editor/commit pattern:
POST to open editor on invoice table:groupPOST field values (vendor, amount, date, line items, tax)POST to urn:abas:rel:editor:COMMITStep 5: Test file attachment Attempt binary upload (multipart POST) to associate a PDF with the created invoice.
Step 6: Read posted journal entries
Find table:group for journal entries. Attempt GET with date-range criteria.
Step 7: Test BPM event-driven outbound Configure a BPM event handler on AP invoice save, have it call an external webhook endpoint. Verify payload and timing.
| What | Finding |
|---|---|
| Maesn | Does NOT support abas ERP. Lists "Abacus" (different Swiss system). Name similarity is misleading. |
| Celigo | No abas ERP connector. Has AFAS ERP connector (different Dutch system). |
| Chift | No abas ERP connector. |
| Make / Zapier | No native abas connector in either marketplace. |
Public table:group catalog |
Does not exist. Only 7 groups documented across scattered sources. |
| Invoice-specific REST endpoints | Don't exist. API is entirely generic (obj/data addressing). |
| SOAP/WSDL documentation | Multiple sources confirm SOAP exists; zero public WSDL or operation documentation found. |
| Webhook/push capability | Does not exist. Outbound events only via BPM configuration. |
| Public developer portal | Does not exist. API docs are instance-hosted. |
| Self-service sandbox | Does not exist. Docker images require partner/extranet credentials. |
| Stack Overflow community | Zero abas questions found. |
| AP automation competitors | DocBits, Medius, Basware, Kofax/Tungsten, Stampli, Rillion -- none have confirmed abas integration. |
None. All claims are supported by cited sources. Where evidence is indirect or ambiguous, this is noted with reduced confidence ratings.