guide

Last updated June 25, 2026

Germany Work Permit Employer Declaration Mistakes: Salary, Hours, Job Title, and BA Review

The practical question behind Germany Work Permit Employer Declaration Mistakes: Salary, Hours, Job Title, and BA Review is which facts, documents, costs, and deadlines change the next step. It explains understanding the visa, residence, work-permit, renewal, and refusal issues behind Germany Work Permit Employer Declaration Mistakes: Salary, Hours, Job Title, and BA Review, then shows how to separate eligibility, sponsor or employer evidence, official forms, timing, refusal risk, and appeal or reapplication choices. The later sections connect official sources to keep open, fast diagnostic table, and why the declaration is not just paperwork so the next step is easier to judge. Read it before an appointment, application, renewal, refusal response, or document request so the evidence file is built in the right order.

This guide explains how to audit employer declarations before filing, after offer changes, and after a salary refusal. It is written for HR operations, recruiters, payroll teams, founders, candidates, and filing advisers who need the form to match the contract and route strategy.

Source check date: May 19, 2026.

Official sources to keep open

• Make it in Germany: Zustimmung der Bundesagentur fuer Arbeit explains BA consent and employment-condition comparison.
• Bundesagentur fuer Arbeit: Vorabzustimmung fuer auslaendische Beschaeftigte explains preliminary consent.
• Bundesagentur fuer Arbeit: Fachkraefte aus dem Ausland beschaeftigen is the employer hub.
• BMAS: Beschaeftigungsverordnung overview provides regulatory context.
• BAMF: Blaue Karte EU gives official Blue Card context and refusal-ground context.
• Make it in Germany: Blaue Karte EU lists Blue Card requirements and salary thresholds. For 2026, it states EUR 50,700 gross annual salary for regular occupations and EUR 45,934.20 for shortage occupations and recent entrants. Verify current-year figures before filing.
• Make it in Germany: Visum zum Arbeiten fuer Fachkraefte explains skilled-worker routes.
• Make it in Germany: Fachkraefteeinwanderungsgesetz summary gives broader skilled-immigration context.

Direct answer

The employer declaration should match the current contract, salary table, weekly-hours clause, role description, start date, work location, employer entity, and route memo. Do not treat it as an administrative duplicate. In salary-sensitive files, a wrong declaration can make the authority review the wrong employment condition.

Fast diagnostic table

Why the declaration is not just paperwork

In many files, the declaration is the authority-facing summary of the employment condition. If it is wrong, the file may be judged on a wrong salary or role. Even when the contract is accurate, a mismatched declaration creates friction because the reviewer must decide which document to trust.

The risk grows after changes. Salary is raised after refusal, but the old declaration remains. Hours become part-time, but the declaration still shows full-time. The job title changes, but the form uses the recruiter title. The legal employer changes, but the old entity remains. These are not cosmetic issues in a salary-sensitive package.

For Blue Card files, the declaration should support the same gross annual salary calculation used for threshold review. For skilled-worker files involving BA employment-condition review, the declaration should make salary, hours, duties, and employer facts clear enough to support comparability analysis.

Review module: salary field

The salary field issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is declaration salary differs from contract. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes contract, salary table, declaration. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is update form to match current gross salary. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is leaving old salary in form. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: weekly hours

The weekly hours issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is hours are blank or inconsistent. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes working-time clause and salary table. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is state hours consistently. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is salary without hours. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: job title

The job title issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is form uses marketing title. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes role description and contract title. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is use current filing title. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is multiple titles across documents. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: job duties

The job duties issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is duties are generic or outdated. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes current role memo. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is summarize actual duties. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is copying old job ad. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: start date

The start date issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is date changed but form did not. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes contract and start-date note. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is reconcile dates. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is old appointment pack. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: employer entity

The employer entity issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is wrong group entity appears. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes legal entity map. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is name legal employer accurately. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is brand name replaces entity. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: work location

The work location issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is office, remote, or client site is outdated. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes workplace note. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is update location. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is location treated as minor. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: contract duration

The contract duration issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is fixed term omitted. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes term dates and renewal status. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is show actual term. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is form implies indefinite job. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: probation salary

The probation salary issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is form uses post-probation salary only. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes salary timeline. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is show current assured salary. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is hiding lower starting pay. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: bonus and allowances

The bonus and allowances issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is total package entered as salary. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes component split. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is enter assured salary basis. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is counting reimbursements. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: part-time role

The part-time role issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is form assumes full-time. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes part-time hours and salary table. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is normalize salary to hours. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is full-time default. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: change of employer

The change of employer issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is old employer declaration reused. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes new employer declaration. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is create new current form. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is copying old approval pack. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: internal role change

The internal role change issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is form reflects old duties. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes old-new table. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is update role facts. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is same employer assumption. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: candidate briefing

The candidate briefing issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is candidate sees different numbers. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes candidate fact sheet. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is align candidate answers. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is appointment contradiction. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Review module: refusal response

The refusal response issue should be treated as a proof problem. German work permit salary review is not a negotiation summary; it is a document-based review of the employment condition being offered. The file should let the reviewer identify the current gross salary, weekly hours, route, employer, role, and source document without reading internal email history.

The practical issue is response memo corrected but form remains wrong. This matters because calculation and form errors often look minor inside HR but material in a salary-sensitive file. A wrong monthly figure, missing payment frequency, outdated employer declaration, or mixed gross and net number can make an otherwise fixable package look unreliable.

Useful proof includes revised form and correction table. The proof should be current, dated where useful, and reconciled across contract, annex, employer declaration, salary table, and cover memo. If two documents use different figures, the file should not be sent until one figure is selected and the wrong one is corrected or superseded.

The correction is fix form before memo. Correct source documents first, then explain the correction. A strong memo points to a clean contract and declaration; it does not ask the reviewer to ignore contradictions still present in the bundle.

The common trap is memo-only correction. That trap creates avoidable refusal risk because it forces the authority to decide which number or form field is real. Salary-sensitive filings should not depend on guesswork.

Final control: ask whether the same answer appears in the contract, salary table, employer declaration, and candidate briefing. If not, the package needs another pass.

Minimum declaration audit

Audit the declaration against the contract, annex, salary table, role description, employer entity, working-time clause, start date, and route memo. Any mismatch should be marked as source correct, source wrong, or superseded. Do not leave mismatches unexplained.

Template declaration reconciliation

Field checked: [salary/hours/title/date/entity/location]. Current source document: [contract/annex/table]. Declaration value: [value]. Status: [matches/update required/superseded]. Owner: [person]. Final package uses: [current value].

Practical FAQ

Can the cover memo fix a wrong declaration? It can explain a correction, but the declaration itself should be updated when it is wrong.

Who should own the declaration? One package owner should reconcile HR, payroll, manager, and adviser inputs.

What is the most dangerous field? Salary and hours together, because they drive threshold and comparability logic.

What after a refusal? Correct the form before resubmission; do not only send a longer explanation.

Final audit before filing

Read the declaration last. If it disagrees with the corrected package, the package is not ready.

Expanded audit playbook

Start with the contract and the declaration side by side. Do not audit the declaration in isolation. The key question is whether the declaration accurately summarizes the current source documents. If the contract was amended, the declaration must follow the amended contract. If the salary table was corrected, the declaration must follow the corrected table. If the role changed, the declaration should not preserve an old title.

Then check salary and hours together. A salary field without weekly hours can be misleading. A weekly-hours field without annual salary can also be misleading. The declaration should support the same gross annual salary calculation that appears in the route memo. If salary was annualized from monthly pay, the declaration should not introduce a different number.

Next, check title and duties. Many employers copy a recruiting title into forms and use a different title in the contract. That can be harmless when explained, but weak when left unresolved. The declaration should use the current filing title or make clear how internal titles relate to the role being approved.

Then check dates and employer entity. Start date, contract term, work location, and legal employer are not decorative fields. After offer changes, intra-group moves, fixed-term renewals, or employer changes, those fields are often stale. A stale declaration can make the file look careless even when the contract was corrected.

Finally, assign one declaration owner. The owner does not need to know every legal answer, but they must control version consistency. They should collect HR, payroll, manager, and adviser inputs, then freeze the declaration only after the source documents agree.

Example correction scenarios

Scenario one: the contract was corrected from EUR 48,000 to EUR 52,000 after a salary concern, but the declaration still says EUR 48,000. Do not send a memo explaining the higher salary while the form says the lower salary. Update the declaration first.

Scenario two: the manager changes the job title from analyst to data engineer, but the declaration keeps analyst. Add a role-duty map and decide which title is current. Then update declaration, contract annex, and candidate fact sheet consistently.

Scenario three: the candidate moved from full-time to part-time before filing. The declaration should show the current weekly hours and salary basis. If it still shows full-time, the salary review may be based on the wrong employment condition.

Scenario four: an intra-group transfer uses the parent company name in one document and the German subsidiary in another. The declaration should name the legal employer or responsible entity in a way that matches the contract and route memo. Brand shorthand belongs in explanation, not in the legal employer field.

Declaration-to-permit translation checklist

Every declaration field should answer a filing question. Salary answers what is assured. Hours answer the working-time basis. Job title and duties answer role identity. Entity answers who employs or sponsors. Start date and term answer timing. Location answers where the work is performed. If a field does not match the source documents, the package invites follow-up.

After refusal, do not assume the declaration is still valid. A salary refusal often triggers contract changes, annexes, role clarifications, or corrected hours. Each correction should trigger a declaration review. The final response package should not contain the same form error that contributed to the first problem.

The candidate should also see a simplified fact sheet derived from the declaration. That fact sheet helps prevent appointment contradictions. If the candidate's answer differs from the declaration, the authority may question whether the employer and candidate understand the same job.

Who should sign off

HR operations should own the declaration because it is normally closest to the form process. Payroll should verify salary and payment frequency. The hiring manager should verify title and duties. Mobility or the filing adviser should verify route-sensitive fields. The candidate-facing contact should verify that the candidate briefing matches the declaration.

This signoff protects speed. Without it, the team may discover a mismatch only after submission. With it, each person checks the field they actually control. That is faster than asking one adviser to guess whether payroll, HR, manager, and candidate all mean the same thing.

Red flags before submission

Stop the filing if the declaration has an old salary, missing hours, old title, old start date, wrong entity, or a different location from the contract. Stop if an amended contract exists but the declaration was not regenerated. Stop if the declaration was copied from a previous case. Stop if the candidate's appointment pack contains a different salary than the form.

These red flags are operational, not theoretical. They are common because declarations are often treated as routine paperwork. In a salary-sensitive file, the form is evidence. Treat it accordingly.

Practical examples by declaration field

For salary, use the same current gross salary that appears in the salary table. If the salary table was revised after a refusal, regenerate or correct the declaration.

For hours, use the contracted weekly hours. If the role is part-time, do not leave a full-time default in the declaration. If hours are flexible but contracted, state the contracted basis.

For title, use the title that matches the role description and contract. If the company has an internal title and an external job title, explain the relationship rather than scattering both labels across the file.

For duties, avoid generic text copied from a recruiting page. The declaration should help the authority understand the actual skilled work being offered.

For employer entity, use the legal entity that signs or sponsors the employment arrangement. If a group brand or client name is also relevant, explain it separately.

For start date and term, match the signed contract or latest annex. If the date moved, update the declaration before submission. If old dates remain in the file, the package looks stale.

For location, match the workplace, remote, hybrid, or client-site evidence. Location can affect the story of employment conditions and should not be left to assumption.

Final cold-read test

Ask someone outside the case team to read only the declaration, contract, salary table, and role description. They should be able to answer six questions: who employs the person, what job is offered, what salary is assured, how many hours apply, where the work is performed, and which start date applies. If any answer is uncertain, the declaration should not be sent.

This cold-read test is deliberately simple. It catches the problems that internal teams miss because they already know the story. The authority does not know the story. The form must carry it.

After a refusal

After a salary refusal, the declaration audit should be repeated from scratch. Do not assume the form remains correct just because the contract was fixed. A corrected salary, corrected hours, corrected title, or corrected employer entity should all trigger a fresh declaration review.

The response pack should include a short before-and-after note. It does not need to be defensive. It should say which declaration field was corrected, which source document now supports it, and which old document is superseded. That is more useful than a long explanation that leaves the form unchanged.

If the declaration was not the cause of the refusal, the audit is still useful. It prevents the response from solving one salary issue while leaving a separate form mismatch for the next review cycle.

A clean declaration keeps the corrected package coherent.

The final owner should archive the reviewed declaration with the salary table. If a later appointment, refile, or employer question appears, the team can show exactly which fields were approved for submission and which older values were replaced.

Practical next step

Create a declaration reconciliation table for every salary-sensitive filing. If salary, hours, title, date, employer, and location do not match the source documents, correct the form before submission.

Internal links for the cluster

• Intra-group transfer salary and host assignment
• Internal role change and salary review
• Gross versus net salary, deductions, and allowances
• Bonus, benefits, and assured salary
• Salary refusal response pack
• Salary comparability without a Tarifvertrag
• Response letters and contract language templates
• Post-refusal recovery roadmap