ALPHAPLAN ERP
AI agents and workflows for ALPHAPLAN ERP
Uhrwerk.AI is an AI workflow platform for ERP systems in mid-sized companies. For ALPHAPLAN ERP, it has dedicated connectors for version 5 and version 6.
Uhrwerk.AI connects ALPHAPLAN with your inbox, PDFs, DMS, and Excel. Recurring processes run as guided AI workflows — with the permissions of your API key, approvals at critical steps, and traceable logs. For wholesale, that means orders, invoices, price lists, and order confirmations are prepared in the system instead of being keyed in by hand.
Last updated:
In short
- Uhrwerk.AI connects ALPHAPLAN 5 through the Webservice (REST) and ALPHAPLAN 6 through the REST API, with a dedicated connector per version and an own API key per user.
- Typical wholesale processes: AI order entry from email and PDF, incoming invoices, vendor price lists, and delivery-date reconciliation.
- By default, write steps reach ALPHAPLAN only after human approval; access, proposals, and approvals are logged.
- Uhrwerk.AI is not a product of CVS Ingenieurgesellschaft mbH. We clarify which fields and permissions your process needs per installation before production use.
- Two dedicated connectors, usable side by side
- Version 5 + 6
- No Uhrwerk app to install in ALPHAPLAN
- No extension
- Own connection, own API key
- Per user
- Data straight from ALPHAPLAN, no separate index
- Live
Typical wholesale workflows with ALPHAPLAN
Automate incoming invoices in ALPHAPLAN
Recognise invoices in email and PDF, match them against the purchase order and vendor in ALPHAPLAN, and prepare them for approval.
AI order entry for ALPHAPLAN with Uhrwerk.AI
Read customer orders from email and PDF, check items, prices, and stock in ALPHAPLAN, and prepare the order document for approval.
Delivery-date reconciliation
Compare purchase orders in ALPHAPLAN with vendor order confirmations and flag deviations.
Master-data maintenance
Prepare changes to addresses, items, and purchase prices from emails — applied only after approval.
Stock and prices on request
Query and summarise stock levels, customer pricing, and open documents from ALPHAPLAN.
More on the flow: Order entry automation
ALPHAPLAN and the systems around it
A process rarely ends in the ERP. Uhrwerk connects ALPHAPLAN with the systems where the work actually starts — from the inbox to the file share.
- ALPHAPLAN 5
- ALPHAPLAN 6
- Microsoft Exchange Online
- Exchange On-Premises
- SharePoint
- OneDrive
- Microsoft Teams
- Microsoft Excel
- Power BI
- DATEV
Examples: how processes run with ALPHAPLAN
Simplified examples with fictional data. We check scope and feasibility for your system.
An incoming invoice from email to ALPHAPLAN
Situation: Invoice RE-2026-08194 from Nordwerk arrives as a PDF in the invoice inbox.
- Uhrwerk extracts the vendor, invoice number, invoice date, line items, amounts, and tax.
- Uhrwerk matches the invoice against the purchase order and vendor address in ALPHAPLAN: quantity and goods value match, freight is 7.50 € above the order and within tolerance.
- An authorised employee reviews the proposal and approves it.
- Uhrwerk creates the document in ALPHAPLAN and logs every step.
For approval
Create invoice document
- Invoice
- RE-2026-08194
- Purchase order
- EB-260731-1188
- Amount net
- 4,942.50 €
- Variance
- +7.50 € freight, within tolerance
A customer order from email as an order document
Situation: Hansa Bau orders 40 flange bearings by email for 18 September, with the order attached as a PDF.
- Uhrwerk reads the customer, lines, quantities, and requested date from the order.
- Uhrwerk maps the lines to items in ALPHAPLAN and checks pricing and stock.
- One line uses an old item number: Uhrwerk proposes the stored successor item and flags it.
- Sales reviews the draft and approves it; Uhrwerk creates the order document.
For approval
Create order document
- Customer
- Hansa Bau GmbH
- Lines
- 3, including 1 successor item
- Net value
- 6,180.00 €
- Delivery date
- 18.09.2026
Update vendor prices
Situation: Nordwerk sends a new price list as a PDF, valid from 1 September.
- Uhrwerk reads the price list and maps the vendor items to items in ALPHAPLAN.
- Uhrwerk compares the new net prices with the stored purchase prices and shows each change as a percentage.
- Purchasing reviews the list and approves it.
- Uhrwerk applies the purchase prices in ALPHAPLAN, valid from 1 September.
For approval
Update purchase prices
- Vendor
- Nordwerk Komponenten GmbH
- Items affected
- 3
- Change
- −1.0 % to +3.8 %
- Valid from
- 01.09.2026
Secure a vendor's new bank details
Situation: Elbwerk reports new bank details by email, and two payments are open.
- Uhrwerk recognises the master-data change and reads the address and open payments from ALPHAPLAN.
- The change is not independently confirmed: Uhrwerk changes nothing in ALPHAPLAN and opens a check process for accounting.
- The check process includes a callback to the number stored on the address and a four-eyes check.
- Until the second approval, the existing bank details stay active.
For approval
Create check process for Elbwerk
- Vendor
- 10482 · Elbwerk
- Check path
- Callback + four-eyes check
- Open
- 2 payments · 19,200.00 €
- Bank details
- Existing stay active
Reconcile delivery dates
Situation: Eleven order confirmations from vendors arrive overnight.
- Uhrwerk reads dates and quantities from the confirmations.
- Uhrwerk compares them with the open purchase documents in ALPHAPLAN.
- Nine confirmations match. Two dates are later, and one of them puts a customer order at risk.
- Purchasing sees the deviations in one place and approves the new dates on the documents.
For approval
Adjust delivery dates
- Confirmations
- 11, 2 with deviations
- Largest delay
- +6 working days
- Affected
- 1 customer order
- Next step
- Inform the customer
Prepare a complaint as a support case
Situation: Meyer Verfahrenstechnik reports a pump that failed after six weeks.
- Uhrwerk matches the customer, delivery document, item, and serial number in ALPHAPLAN.
- Uhrwerk checks history and warranty: 22 months left, no earlier complaint for this serial number.
- Your process allows an advance replacement. Uhrwerk prepares the support record and the replacement delivery.
- The credit memo stays open until the technical inspection is complete.
For approval
Create support record
- Customer
- Meyer Verfahrenstechnik
- Item
- PU-5508-03 · process pump
- Warranty
- 22 months remaining
- Next step
- Advance replacement
How Uhrwerk works with ALPHAPLAN
Connect
Through the connector for ALPHAPLAN 5 or ALPHAPLAN 6, over HTTPS to the REST interface of your server.
Inherit permissions
Uhrwerk acts only within the permissions of the API key each user provides.
Approve
By default, write steps reach ALPHAPLAN only after human approval. Once a workflow has proven itself, individual steps can be applied automatically.
Trace
Every action is logged — who, what, when, and on what basis.
ALPHAPLAN 5 and ALPHAPLAN 6: interfaces and scope
Each version has its own connector, with its own connection and API key. A user can connect both side by side, for example during a version change.
ALPHAPLAN 5
- Connection
- Through the ALPHAPLAN 5 Webservice (REST) on your server
- Sign-in
- Own API key per user; optionally a webservice administration password for managing API keys and users
- Scope
- 141 operations, derived from the vendor's 140 published request examples: documents, master data, stock, prices, accounting, files, EDI, and more. SQL only after approval
- Network
- Approved HTTPS address with valid TLS, including private addresses in your network
ALPHAPLAN 6
- Connection
- Through the ALPHAPLAN 6 REST API on your server
- Sign-in
- Own, newly generated version 6 API key per user; permission masks limit it to the read and write rights needed
- Scope
- 211 operations: 59 reads, 149 business actions, and 3 document actions such as PDF export. SQL and administration are not included
- Network
- Approved HTTPS address with valid TLS, including private addresses in your network
Security and control
Own identity per user
Each user connects their own API key. Connections are private and never shared, and the permissions of that key in ALPHAPLAN apply.
Reads run, writes wait for approval
Queries run directly. Creating, changing, deleting, and posting steps wait for approval, even when ALPHAPLAN technically runs them as a read request.
No blind retries
Write requests are sent exactly once. If the outcome is unclear, Uhrwerk repeats nothing and asks you to check the state in ALPHAPLAN.
Live, not a copy
Uhrwerk reads ALPHAPLAN data live through the interface and keeps no separate index of your ERP data.
Audit trail
Access, proposals, and approvals are logged — who, what, when, and on what basis.
Approved servers only
Uhrwerk talks only to ALPHAPLAN servers explicitly approved in its operation. API keys are stored encrypted.
Step by step to automation
Prepare
Uhrwerk reads, structures, and matches against ALPHAPLAN. Your team keeps working on the case as usual.
Propose
Uhrwerk prepares the specific document or change. The responsible employee reviews and approves it.
Complete
Proven standard cases run automatically within clear rules. Exceptions are still escalated.
Compliance is part of the system
What you need for audits, data protection, and the EU AI Act ships with Uhrwerk — not as a separate project.
- EU AI Act risk assessment as the basis for your AI register
- Audit-proof logs as the foundation for GoBD evidence
- A building block for your process documentation
- AI literacy training under Art. 4
- Documents for data protection, data processing agreements, and works councils
ALPHAPLAN stays your leading system
Uhrwerk does not replace ALPHAPLAN. It starts where a process reaches beyond the ERP — into the inbox, PDFs, the DMS, and Excel — and runs it as a repeatable workflow with approvals. Uhrwerk.AI is a product of Locomind GmbH and not a product of CVS Ingenieurgesellschaft mbH, the maker of ALPHAPLAN.
Operation
- ALPHAPLAN 5 and ALPHAPLAN 6
- Hosting in the EU, in your cloud, or on-prem
- GDPR-compliant with a data processing agreement
- 200+ supported file formats
- Model-independent, fair-use licence instead of a token meter
Frequently asked questions about AI in ALPHAPLAN
Are there AI agents for ALPHAPLAN 5 and ALPHAPLAN 6?
Yes. Uhrwerk.AI has one dedicated connector for ALPHAPLAN 5 and one for ALPHAPLAN 6. Uhrwerk itself can run in the EU, in your cloud, or on-prem.
Which API or interface connects ALPHAPLAN?
ALPHAPLAN 5 through the Webservice (REST), ALPHAPLAN 6 through the REST API of your server, both over HTTPS. Each user provides their own API key, and Uhrwerk acts only with the permissions of that key. The server address must first be approved in the operation of Uhrwerk.
Does ALPHAPLAN need an extension installed?
No. Uhrwerk installs no app of its own in ALPHAPLAN. You need a REST interface reachable over HTTPS and API keys with the right permissions.
Does the AI post to ALPHAPLAN on its own?
Not by default. Uhrwerk prepares documents, posting steps, and master-data changes, and an authorised employee approves them. Once a workflow has proven itself in daily use, you can enable automatic application for individual steps.
Can ALPHAPLAN 5 and ALPHAPLAN 6 be connected side by side?
Yes. The two versions are separate connections and run independently. ALPHAPLAN 6 needs a newly generated API key, and an existing version 5 connection is not carried over.
Where is our ALPHAPLAN data processed?
That depends on how you run it. Uhrwerk itself runs hosted in the EU, in your own cloud, or on-prem, and is GDPR-compliant with a data processing agreement. Language models and other services are configured separately, and we disclose which services process data before you start. Uhrwerk can also reach ALPHAPLAN through private addresses in your network, provided TLS and routing are in place.
Is Uhrwerk.AI suited to wholesale with ALPHAPLAN?
That is what the workflows on this page are for: preparing orders from email and PDF as order documents, querying stock and pricing, and reconciling vendor price lists and order confirmations. We check fields and permissions per installation.
Which ALPHAPLAN processes are a good place to start?
Recurring processes with clear rules and a lot of manual work: incoming invoices, order entry from email, delivery-date reconciliation, and master-data maintenance.
Will this work with our ALPHAPLAN installation?
We check that together. Fields, permissions, and data differ per installation, and not every function is covered. So before production use, we clarify which fields and permissions your process needs.
Does Uhrwerk copy our ALPHAPLAN data?
Uhrwerk reads ALPHAPLAN data live through the interface and keeps no index of it. Results retrieved during a case can remain in the history of that case and be processed by the configured language model.
Talk through your ALPHAPLAN process
Book the 30-minute ERP potential analysis or request a callback. We show which process pays off — with your systems, not with slides.