Offering BEA employment certificates: Define the engagement

A customer asks your payroll office for help with a requested employment certificate. Your team may already handle routine payroll, or be asked to undertake this task alone. A suitable proposal needs clear boundaries: Which certificate has actually been requested, what information is confirmed, and who is responsible for missing facts? Clarifying this lets you offer an understandable processing route. The business also sees its necessary contribution and the work your office actually undertakes.

This guide concerns defining tasks and proposals for employment certificates under Germany’s BEA procedure. It is neither a completion manual nor a decision on benefit entitlement. Notes and examples are your own organisational aids, not webRichtung features. All examples are explicitly fictional. Your actual authority and professional handling of the individual case must be assessed. For unclear termination information, contradictory documents or technical exceptions, clarify the route with appropriate professionals and current official guidance before committing to specific work.

Start with the actual request

Ask the customer to identify the reason and precise certificate requested. Who requested which document for which person? Is there an actual request, or is the business organising a future process? These situations call for different next steps. A factual description without unnecessary personal details suffices for a sales note. The actual request should later be supplied through the agreed appropriate processing route and assessed professionally.

Pay attention to the precise term. An employment certificate for the agency, an employment reference and a copy of a payslip are different outcomes. Clarify when the customer uses the terms interchangeably. Understand the intended engagement before committing to scope. The customer gains a clear next step too: Provide the relevant request instead of an undefined demand for every employment document followed by an expectation of another service.

Define your office’s role explicitly

Ask whether certificate work already forms part of the actual agreement or needs a new proposal. Routine payroll does not itself define every additional task. Describe whether your office compiles information, prepares a professionally checked data set or undertakes specifically agreed transmission. These tasks may belong together, but should not silently become a complete package. Customers should see what they or another responsible party retain.

Check the proposed work with your team’s responsible professional. Who knows the procedure and can allocate unresolved substantive questions? Which completeness checks are included? For a limited contribution, describe the boundary positively through the result delivered. Promise no universal responsibility for every certificate or legal question. A named service is easier to commission than saying your team will handle everything with the employment agency.

Separate payroll data and employer information

Establish which required information may come from documents your office actually processed. Other facts may need confirmation by the employer. Record these origins separately. Having monthly payroll does not automatically mean every fact about duties or termination is known. Ask who is responsible on the customer’s side. Do not fill gaps from a plausible filename or an earlier conversation note.

For each missing detail, record the precise question and who can clarify it. “Documents missing” is too general. Describe what needs confirmation without prescribing a legal assessment. Contradictions remain visible until the responsible party resolves them. The proposal can describe necessary clarification work, but should not assume certain complete processing while central facts remain speculative.

Consider the period separately from current payroll

Which period does the request concern, and which parts did your office actually handle? The certificate may need information beyond the current month’s payroll. If another provider handled an earlier portion, the customer must explain the intended information route. Identify responsibility for the missing basis instead of assuming availability. This differs from taking over an ordinary new monthly processing version.

Also consider possible professional or technical exceptions, for example no complete payroll period being available yet. Record the facts for the responsible professional and check current official procedural guidance. Do not prescribe a universal electronic solution. First establish what route requires assessment and what support your office really offers. An available button does not establish that the method suits the case substantively.

Confirm the actual transmission route

If transmission is included, clarify the actual application and its confirmed capabilities for the case. Ask for the responsible contact and the provider’s current original guidance. Not every application supplies every certificate feature. General product descriptions do not promise support in the particular environment. Your team confirms work and procedure only after suitable assessment. Credentials do not belong in general proposal notes.

Separate transmission clarification and substantive completeness. A technical procedure does not show that the contents are settled. Conversely, a fully described request does not confirm the technical route. Record both prerequisites separately. The customer can see whether a substantive answer, product clarification or further engagement is missing. Promise no automatic exchange or universal portal support before assessing actual use.

Agree how questions will be handled

Discuss who receives subsequent questions. Do they concern transmission status, an employer-confirmed fact or an additional substantive detail? Different contacts may be needed. Your office can coordinate where this forms part of its real services, without replacing the relevant professional’s responsibility. Describe the information the customer receives and what remains their task when another business confirmation is required.

How should a later content change reach your team? It needs a reference to the original case and a confirmed new basis. Do not determine a substantive correction merely from someone wanting a change. The responsible person assesses the case against the current procedure. Organisationally, retain who explains the change and what processing was agreed. Follow-up becomes a defined task rather than an indefinite continuation without clear instructions.

Use a fictional handover case

An explicitly fictional business requests an employment certificate after a specific demand. Your office handled only part of the relevant employment period. Personnel administration cannot yet fully confirm termination information because a question to the responsible person remains open. Record two gaps separately: Earlier payroll information and pending employer confirmation. The example shows what your team can already use and which additional answer is required. It contains no supposed real personal data.

The business would like to commission a complete service immediately. Explain what your office can undertake under individually assessed authority and which prerequisite remains missing. One contact obtains the earlier information; another confirms the unresolved facts. Further steps depend on those particular answers. Promise neither a fixed completion date nor a particular unemployment benefit outcome. Your proposal concerns agreed certificate work, not deciding entitlement. Make that boundary clear to the customer.

Describe your engagement’s result

Summarise the particular certificate, available sources and missing customer information. Add assessed processing scope, intended transmission route and responsible contacts. A colleague should know what can actually be done next. If they would have to guess termination details or procedure, that point needs clarification. The customer gains a usable work description rather than a blanket promise concealing their own contribution.

Distinguish completion of your agreed work from later decisions by other bodies. What feedback demonstrates the agreed processing status, and which questions then fall outside scope? Record this without turning a technical notice into substantive acceptance or benefit approval. A later task can be discussed against this boundary. Both parties retain the same comprehensible status even if another employee handles subsequent questions.

Organise cover around the outstanding question

Finally check whether a replacement contact could understand what is pending. Who confirms the employer’s facts, who obtains earlier records and what response does your team expect? A short note following these three tasks suffices as your own aid. It replaces no assessment and collects no unnecessary personnel data. If the original contact is absent, cover can continue the right task. The certificate no longer depends organisationally on an unsupported personal recollection of the first discussion.

Keep several requests distinct

If the business mentions several certificates, assign each to the outcome actually requested. One message may concern different people, periods and missing foundations. For your proposal, establish which tasks are sufficiently described. One clarified certificate does not make all others ready. Initially use invented case labels to discuss structure without personal details. Professional processing can then use the correct originals through the agreed appropriate route. You can offer a defined task while another request still awaits its responsible confirmation.

Official basis and limits

Section 312 SGB III concerns employment certificates on request and relevant facts. Section 313a SGB III regulates electronic certification. The fully read Federal Employment Agency BEA page explains requests, appropriate transmission methods and exceptions. Not every termination automatically requires a certificate. The page currently identifies a paper route for the exception without a fully completed payroll period. This article replaces no completion guidance and guarantees neither software features nor a benefit decision. Current requirements and individual assessment govern.

Start suitable company discussions

Payroll leads from webRichtung reach companies in Germany considering external support. Employee range, current arrangements, preferred start, location and contact provide a starting point. Establish certificate needs and scope yourself; they are not promised enquiry fields. Register your service and prepare the order in webRichtung Customer. You see the current price before placing a binding order.