PDLSign
For ERP and software vendors
Your clients are asking for electronic signature. Building a signature service of your own rarely pays off: certificates, seals, timestamps, audit trails and the form requirements of German temporary staffing law are a product in their own right, not a module. PDL Sign comes as a documented interface — you integrate once, and each of your clients signs their own contract with us.
This English page is a translation for information. The German version is the authoritative one: the service limits are tied to German legal terms (Textform, § 12 AÜG, § 14 (4) TzBfG).
Why not build it yourself
What appears on the surface as a signature field rests on infrastructure that has to be operated permanently and kept legally sound.
Signing keys in dedicated cryptographic hardware, an external timestamping service, a certificate chain anchored in the Adobe Approved Trust List, and an audit trail retained for ten years. That is a product of its own, with operations of its own.
For the staffing contract, Textform is sufficient. Fixed-term agreements under § 14 (4) TzBfG, by contrast, require the statutory written form and do not belong in a Textform service. PDL Sign does not produce a qualifizierte elektronische Signatur today and does not cover transactions requiring the statutory written form. A mistake at that boundary falls back on the software in which it happened.
Authorized-signer lists with two levels, forwarding inside the client company, admission requests, deputy rules, signature rules per document. This is precisely where generic signature platforms fail.
How the partnership works
The model is deliberately lean: you remain a software vendor and do not become the reseller of a service whose limits you would then have to stand behind.
You embed the documented, versioned interface into your solution. Access to the test environment for development, testing and demonstration is free of charge.
You show your clients the integrated function and present the approved documents: usage contract, service description, terms and the data processing agreement.
The contract is concluded directly between your client and Alpview. We review it, confirm it and set up a dedicated tenant with dedicated credentials for the client.
Your solution calls the interface with each client's own credentials. Billing runs directly between Alpview and your client.
What the interface does
The functional scope is the same across all clients. What differs is credentials, signer lists and brand profile — and those come from your application.
Create and cancel, hand over document, transaction type and counterparty.
Hand over and maintain the client company's authorized signatories across two levels.
Display name, logo and colour per client — a separate profile per company in group structures.
Retrieval by polling with a continuation marker: delivery, opening, signature, rejection, completion.
Retrieve the finished, sealed PDF with its audit page and file it in your own record logic.
Interface changes follow the same notice periods as for end clients; you are informed in parallel.
Plain terms
The same openness as on the product page. In the signature business, an overreaching promise is not a matter of style but of liability — so here is what we do not promise:
You do not acquire, licence or market the service in your own name; there is no sublicensing. It stays visible that PDL Sign is the service behind the signature, and the notes on the audit page remain unchanged.
We pay no commission and no other remuneration for referrals. The value lies in being able to offer your clients an integrated signature function without building and operating signature infrastructure yourself.
You may offer competing signature solutions. We also win clients directly and through other partners.
Alpview does not sell an ERP or an ATS of its own. Clients you referred are not actively marketed by us for services that compete with your core product.
Your client is the controller. You and we are each separately processors for our own part; no sub-processing relationship arises between us. Credentials are per end client; shared access across several clients is ruled out.
Statements about scope, security or legal effect are agreed with us beforehand. That is not paternalism — it is why the limits of this service are described the same way everywhere.
Responsibilities
First-level support for your solution including the integration: operation, presentation and workflows inside your software.
Support towards the end client within the scope of the usage contract: interface, signature process, documents and availability.
Named technical contacts on each side; requests are passed on to the responsible party without delay.
Next step
How many of your clients work in temporary staffing, which document types run there, and where in your application would the signature sit? After that we can get concrete about the integration — with one of your clients in the room if you like.
Request an integration call PDL Sign at a glance