Key Takeaways
- In 2024, according to Forrester, 73% of SAP users maintain parallel Excel lists for physical assets. The gap is not within the ERP, but beneath it.
- seventhings synchronizes asset master data bidirectionally with SAP via REST API, without data migration or a dedicated IT project.
- The DATEV integration automatically transfers fixed assets into the asset ledger. Accounting values and physical reality stay permanently synchronized.
- Microsoft 365 connects via Azure AD for Single Sign-On and Teams notifications regarding maintenance tasks and inventory results.
In discussions with purchasing managers and IT administrators, one objection reliably arises: The company has SAP, so no further software can be introduced. Behind this statement lies a legitimate concern: parallel systems, duplicate data maintenance, unclear interfaces.
The concern is legitimate. The conclusion, however, is wrong.
SAP manages book values, cost centers, and depreciation. What SAP does not do: record the physical condition of an asset, track its location, document maintenance deadlines, or prove DGUV-V3 inspections. According to Forrester (ERP Usage Report 2023), 73% of SAP users maintain parallel Excel lists for precisely these tasks. This is not a sign of poor processes. It is a structural problem: ERP systems are built for book values, not for operational asset data.
seventhings closes this gap. Via API.
What seventhings synchronizes with SAP
seventhings' SAP integration uses a bidirectional REST API connection via the SAP Business Technology Platform (BTP) or directly via RFC/BAPI for on-premise installations.
Specifically, what is synchronized:
From SAP to seventhings (Pull): Asset master numbers, cost centers, book values, depreciation data, vendor numbers. seventhings uses these fields as a baseline and enriches them with: location, condition, user, maintenance history, scans.
From seventhings to SAP (Push): Location changes, condition changes after inventory, disposals and additions from the physical reality. The asset ledger in SAP thus reflects the actual inventory reality.
The result: SAP not only knows what was purchased, but also where it is located, its condition, and when it was last inspected.
According to Gartner (Asset Management Benchmark 2024), in 70% of organizations, the ERP target inventory and physical reality deviate by more than 30%. With bidirectional synchronization, this deviation drops to under 5%, measured after 12 months of operation.
How does asset software integrate with SAP?
Asset management software like seventhings connects to SAP via REST API or RFC/BAPI. Asset master data, cost centers, and booking values automatically flow into seventhings. Location changes and condition changes recorded in the field flow back into SAP. The result is a synchronized asset register without manual post-processing.
DATEV: Fixed Assets Without Duplicate Maintenance
For companies using DATEV as their accounting solution, the situation is different: DATEV is strong in financial accounting, but like SAP, it is structurally blind to the physical side of fixed assets.
The seventhings DATEV integration works via the DATEV import standard (CSV-based, DATEV chart of accounts SKR03/SKR04) and, for customers with DATEV Unternehmen Online, via the DATEV Developer Platform's REST API.
What this means in practice:
With every inventory in seventhings, additions, disposals, and location changes are automatically prepared as a DATEV-compliant export. The tax advisor or accounting department directly imports this export. Manual reconciliation between the inventory list and the DATEV asset register is eliminated.
In 2024, according to Deloitte (Financial Close Survey 2024), accounting teams spent an average of 40% more time on manual asset reconciliations than companies with digital inventory systems. For a medium-sized DACH company with 2,000 to 5,000 assets, this amounts to three to five working days per annual closing.
Microsoft 365: From Outlook to Teams
Microsoft 365 is the dominant collaboration platform in DACH companies. seventhings integrates at three points:
Azure Active Directory (Azure AD / Entra ID): Users log in via SSO with their existing Microsoft credentials. No separate passwords, no manual user management in seventhings. User profiles, roles, and location assignments are adopted from Azure AD.
Microsoft Teams: Maintenance tasks, inventory requests, and inspection deadlines are delivered as Teams notifications. Facility managers and maintenance supervisors receive their task stream directly in the environment where they already work.
SharePoint / OneDrive: Documents such as maintenance reports, device documentation, and DGUV-V3 inspection records can be directly stored from seventhings into SharePoint folders or linked from OneDrive.
Can seventhings be used with Microsoft Teams?
Yes. The seventhings Teams integration delivers notifications regarding maintenance deadlines, inventory tasks, and status reports directly to Teams channels or as personal messages. Login is via Single Sign-On using Azure Active Directory, eliminating the need for separate user management in seventhings.
n8n: When no native connector exists
Not every system landscape is SAP, DATEV, or Microsoft 365. For companies using proALPHA, abas, Dynamics 365, a helpdesk system, or their own database, seventhings provides a native n8n connector.
n8n is a self-hostable workflow automation platform that connects over 2,000 apps and can be operated in compliance with GDPR. The seventhings Community Node is installed directly via the n8n interface. The connection requires three pieces of information: Subdomain, email, and the Client ID from seventhings under Integrations → REST API. The authentication token is automatically retrieved and renewed.
The connection is set up in under five minutes. Here's what's possible:
When a new asset is created in seventhings, an entry is automatically generated in the ERP and a notification is sent to the team chat. Overdue maintenance tasks trigger a helpdesk ticket and a reminder email to the responsible person, without manual transfer. If an employee returns a loan device, invoicing is initiated and inventory is updated. If a dataset changes in seventhings, CRM fields and tables remain automatically synchronized.
A total of 11 trigger events are available. Workflows can be created with a click or via AI voice command in natural language. A development team is not required for this.
A workflow step we regularly use in our team: Export an existing workflow as JSON from n8n and paste it directly into Claude or ChatGPT. Credentials are not included; they remain in n8n. The language model then either explains the workflow's logic in simple terms or specifically adds branches and conditions. The result comes back as JSON, is imported into n8n, and appears as a new workflow alongside the old one. The old one is deleted. No clicking through the frontend, no IT ticket.
What an integration does not do
A question we regularly ask during evaluations: What exactly should the integration achieve, and what should it explicitly not achieve?
seventhings is not an ERP replacement. Financial accounting, cost center accounting, and depreciation planning remain in SAP or DATEV. seventhings complements these systems with the operational side: Where is the asset located, who uses it, what is its condition, when is the next inspection due.
What the integration does: provide synchronized data between book value and physical reality. What it does not do: replace accounting logic or overwrite existing ERP workflows.
This boundary is deliberately set. It's why IT managers typically approve the implementation of seventhings without a dedicated project budget: The system operates in parallel, not in competition.
Does seventhings replace the ERP system? No. seventhings is middleware for physical assets. The ERP manages book values, depreciation, and cost centers. seventhings records what goes beyond that: location, condition, users, maintenance history, and inspection records. Both systems remain in place and exchange data where it makes sense.
How the integration process works
Here's how an SAP integration process typically works:
Step 1 (Week 1): Clarify API access credentials and authentication. For SAP BTP: OAuth 2.0 credentials. For On-Premise: RFC user with restricted permissions. For DATEV: API key via DATEV Developer Portal.
Step 2 (Week 1-2): Define field mapping. Which SAP asset numbers correspond to which seventhings asset fields? For most customers, this involves 8 to 12 fields. The mapping is configured once.
Step 3 (Week 2): Initial data import. Existing asset master data from SAP is imported into seventhings and linked with QR codes or RFID tags. For 1,000 assets, this step typically takes two to three business days.
Starting Week 3: Live operation. Changes made in seventhings automatically flow back into SAP. The asset register remains permanently synchronized.
For Microsoft 365, the effort is significantly lower: Azure AD integration and the Teams connector are usually set up within half a day.
Frequently Asked Questions
Can seventhings be connected to on-premise SAP installations?
Yes. An RFC/BAPI connection is available for SAP On-Premise. This requires a dedicated RFC user in SAP with restricted read permissions for asset master data and write permissions for defined feedback fields. Technical configuration typically takes less than one day.
What happens to existing data in SAP when seventhings is implemented?
Nothing. Existing data in SAP remains fully intact. seventhings imports asset master data from SAP as a baseline and supplements it with operational fields. There is no data migration in the traditional sense. SAP remains the leading system for accounting values.
Does seventhings support Single Sign-On with identity providers other than Microsoft?
In addition to Azure AD (Microsoft), seventhings supports SSO via Google Workspace and SAML 2.0-compatible identity providers like Okta or Keycloak. The configuration effort is comparable in all cases: half a day with the respective IT administrator.
How many integrations can seventhings operate simultaneously?
There is no technical limit to parallel integrations. Customers using SAP, DATEV, and Microsoft 365 operate all three connections simultaneously. Each integration operates independently and is configured separately.
Is an IT service provider necessary for the integration?
Usually not. Configuring the SAP interface requires an SAP Basis administrator for RFC setup, typically two to four hours of effort. The Microsoft 365 integration is set up by an Azure AD administrator. For DATEV, an API key issued by the company's DATEV consultant is sufficient.
What's next?
1. Clarify your system landscape: Which systems are in use? SAP, DATEV, Microsoft 365, or another combination? An overview of available integrations can be found at seventhings.com/integrationen.
2. Request an integration demo: We will show you the specific connection with your system, including field mapping and data flow. No presentation, directly in the system.→ Request an integration demo
3. Asset potential analysis: How many assets in your inventory are currently not in your ERP, incorrectly assigned, or untraceable? This analysis provides a reliable basis for your integration decision.
.svg)
.svg)
.svg)