Offering digital payslips: Clarify provision and support

A company wants to provide payslips digitally and asks your payroll service for help. Your proposal then concerns more than creating a file. Customers want to know how employees actually obtain documents, who helps when access is missing and what remains their own team’s responsibility. A clear description makes your service comparable. You can decide whether to prepare the agreed payroll only or additionally offer a separately assessed document provision service.

This guide helps providers clarify that scope before proposing it. All processes are recommendations for your own organisation, rather than promised features of webRichtung or a particular application. Examples are explicitly fictional. The text makes no decision on legal introduction, employee representation rights, data protection arrangements or retention. The business needs the appropriate professionals and assessment of its actual procedure. Neither a product name nor the existence of a digital file replaces individual clarification.

Begin with employees’ actual tasks

Ask how employees receive payslips today and what should become easier. Do they want to find a document themselves, keep a copy or ask personnel administration a question? Record these actions separately. Another delivery channel can change the process without automatically resolving every subsequent issue. For your proposal, understand the employee’s route from learning that a payslip is available to obtaining the document they need.

Include employees without a permanent desk. A business with a workshop and administration may have differing starting points. What facilities actually exist, and who knows the people’s needs? Assume neither private smartphones nor home printers. Establish the real support required. Subsequent legal and technical assessment determines the specific route that can be offered; convenience requested in conversation does not itself authorise introduction.

Separate preparation and provision

Describe what your payroll team produces, then establish who transfers the document to the intended provision route. This may be a separate task with another responsible person. If your office only offers preparation, make that boundary visible. Additional provision needs its own description. “Digital payroll” alone leaves it unclear who undertakes each part and how the customer recognises the agreed result.

For an existing application, ask which product is actually used and who is responsible. Check the required capabilities against current original documentation or a suitable demonstration. Promise no storage, immutability, export or notification merely because something is called an employee portal. Include confirmed capabilities and prerequisites in the proposal. Unchecked points remain specific questions rather than assumed standard features.

Clarify how new employees start

Discuss who prepares participation when employment begins. What information does the person receive, where should their first question go, and how does the responsible office recognise an incomplete start? Invented people and a described process suffice initially. No real credentials or employee documents are needed in a sales discussion. Customer and office should understand the same route and assign the necessary work.

Consider a fictional new employee who cannot find her first document. Should she approach personnel administration, your office or the existing application provider? Which part does each handle? A named responsibility helps only where the person actually provides that support. Record it specifically. A technical product question and a question about payslip contents may need different answers and should remain distinguishable in the scope.

Include people without private equipment

Ask explicitly about employees unable to use the digital route privately. What option will actually be available at work? Who explains it and helps with missing documents? Discuss this as part of the customer’s organisation. Do not declare a particular facility automatically sufficient. Appropriate professionals must assess the planned route against the individual business and legal prerequisites. First establish what support your office is actually expected to undertake.

Review the route from the perspective of someone rarely in administration. Can they obtain the document during the intended usage period, or is the responsible office regularly unavailable then? A fictional field worker can make this tangible. You are not promising universal availability. Help the customer see an organisational gap before commissioning and decide who closes it within the proposed procedure.

Assign content questions to a clear recipient

Digital documents can still prompt questions. Distinguish finding the document from understanding its contents. An employee asking about an amount has a different issue from someone unable to see a file. Which questions does the customer answer internally and which will your office handle under the agreement? Undertaking a provision step does not automatically include unlimited individual advice for all employees. Describe the actual support clearly.

Discuss how a discrepancy reported by an employee reaches the appropriate person. Who checks the facts with the employer first and who supplies a confirmed processing question to your payroll team? Use a fictional amount requiring explanation without prescribing a correction. Your result is a traceable question route. It replaces no individual assessment and does not turn technical document provision into a promise to answer every employment or tax question.

Treat a new version as a separate event

Ask how a later professionally confirmed new payslip should be identified in the proposed process. Which document does it concern, and who explains the relationship to the previous version? Record the desired result before promising technical capabilities. Similar filenames may be ambiguous. The proposal should show what provision task you undertake and which substantive decision the customer or appropriate professional supplies first.

Do not infer blanket permission to overwrite or delete earlier versions. Document versions and continued availability require separate professional and legal assessment. For the organisational description, first identify how a confirmed new version can be assigned correctly and who addresses that question. This keeps scope concrete without adding unconfirmed storage capabilities or a general archive promise.

Clarify the end of the arrangement

Discuss what must be clarified when an employee leaves or the company changes provider. Which documents would the person want to retain for their purposes? Who answers subsequent questions and who is responsible for each provision route? Promise no access period based on an application’s name. Record the intended result and separately assess actual capabilities and applicable legal requirements. Include only the confirmed portion in your proposal.

Distinguish an employee leaving from termination of your customer engagement. A business choosing another payroll service may need different handover work from that required for one departing person. Who describes the transition and what work does your office really offer? Routine provision does not silently become comprehensive later data migration. Customers should distinguish ongoing scope from a separately agreed closing service.

Test the route with a fictional business

An explicitly fictional business has workshop and office staff. Administration wants digital document lookup, while one workshop employee cannot use private digital access. A new employee also asks about her first provision. Ask the customer to explain each person’s intended route. Your team describes its actual contribution. Unresolved introduction and product questions retain a named owner rather than being hidden by a general digital promise.

Add a confirmed new version and a question after someone leaves. Can everyone explain which office answers and which document is meant? Otherwise clarify that particular responsibility or prerequisite. This is a discussion aid, not proof that an application works or may lawfully be introduced. Before implementation, the responsible parties must assess the real route appropriately. The discussion prepares an understandable service decision.

Record the boundary of your support

Summarise preparation, intended provision, starting support, questions and separate changes in a short scope description. Assign a responsible role and outstanding assessment to each. A colleague should know whether to create payroll, undertake a confirmed provision step or refer a question to the customer. If that requires guessing application capabilities, confirmation is missing. Obtain it specifically before offering the task, allowing the customer to compare your support with their organisation.

Describe notices separately from documents

If the customer wants notice of new documents, treat that as another task. Who creates it, what does it refer to and what should an employee do next? A desired message does not establish an application feature. Check the available capability and distinguish it from document provision itself. If your office does not handle this additional step, identify the customer’s responsible team. Both tasks remain clear without inferring an unchecked message or particular transmission method from “delivery”.

Legal context and sources

Section 108 GewO generally requires a payslip in text form at payment, subject to the unchanged-information exception in paragraph 2. The Federal Labour Court judgment of 28 January 2025, 9 AZR 48/24, concerns employee mailboxes suitable in principle. It does not approve every portal: Paragraphs 14–18 address text form and the particular storage/access arrangement; paragraphs 26–30 leave the group works council’s competence unresolved, requiring remittal. Paragraph 36 considers employees without private access through workplace viewing and printing. Introduction, employee representation and data protection require individual assessment.

Reach new companies for your service

Payroll leads from webRichtung start discussions with companies in Germany. Enquiries include employee range, current arrangements, preferred start, location and contact. Establish digital provision needs and actual applications yourself; neither is a promised additional field. Register your service and prepare the order in webRichtung Customer. You see the current price before placing a binding order.