guide

Last updated June 25, 2026

Germany Work Permit Salary Comparability Without a Tarifvertrag: Internal Bands, Market Evidence, and BA Review

This article treats Germany Work Permit Salary Comparability Without a Tarifvertrag: Internal Bands, Market Evidence, and BA Review as a decision file rather than a generic overview. It explains understanding the visa, residence, work-permit, renewal, and refusal issues behind Germany Work Permit Salary Comparability Without a Tarifvertrag: Internal Bands, Market Evidence, 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 non-tariff employers still need comparability evidence 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 prepare salary-comparability evidence when the employer cannot simply cite a clear Tarifvertrag. It is written for HR teams, candidates, founders, recruiters, and filing advisers who need to make a German work permit or skilled-worker file understandable after a salary concern, BA question, or refusal.

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

If no Tarifvertrag clearly applies, build a salary-comparability pack around the actual role: job duties, weekly hours, assured gross salary, seniority, location, internal salary band, comparable employees if available, and external market evidence where appropriate. For Blue Card files, separately verify the current-year threshold. For BA-reviewed skilled-worker files, make the comparable-condition logic explicit rather than assuming the reviewer will accept a market claim.

Fast diagnostic table

Why non-tariff employers still need comparability evidence

The absence of a collective agreement is not the end of the salary analysis. It may actually increase the need for a clean explanation. A tariff-bound employer can often point to a defined pay scale. A non-tariff employer must show the authority how the salary and employment conditions make sense for the role being offered.

The central mistake is treating "we are not tariff-bound" as a complete answer. It is only a starting point. The file still needs to show salary, hours, role, seniority, and route fit. If the salary is close to a concern line, the employer should not rely on a vague statement that the offer is competitive. Competitive compared with what? Which role? Which location? Which hours? Which seniority? Which route requirement?

For Blue Card cases, threshold evidence is often more direct. The current Make it in Germany Blue Card page gives official salary figures and should be checked for the filing year. For 2026 it states EUR 50,700 gross annual salary for regular occupations and EUR 45,934.20 for shortage occupations and recent entrants. But skilled-worker files that rely on BA review can require broader employment-condition clarity. That is where internal bands and comparator evidence matter.

The best non-tariff package does not pretend that an internal pay band is law. It uses the band as evidence of the employer's ordinary compensation practice, then connects it to the actual job. The package should say: this is the role, this is the level, this is the working time, this is the assured salary, this is the employer's band for comparable employees, and this is why the offer is not an outlier.

Review module: tariff applicability check

The tariff applicability check issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the package never states whether a collective agreement applies. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes HR confirmation, industry context, and employment contract language. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is add a short tariff-status note before presenting alternative evidence. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: do not declare no tariff applies without checking the contract and employer context. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: the reviewer sees that the employer considered the right benchmark question. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: internal salary band

The internal salary band issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the employer has bands but does not disclose or explain them. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes band level, role level, salary range, and placement rationale. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is summarize the relevant band without exposing unnecessary confidential data. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: do not fabricate bands after a refusal. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: salary is anchored in ordinary employer practice. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: comparable employee evidence

The comparable employee evidence issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the offer is defended as normal without examples. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes anonymized comparable role data if lawful and available. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is show range, level, hours, and role similarity without personal data leakage. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: avoid privacy breaches or cherry-picked examples. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: the authority can see that the candidate is not being singled out for worse conditions. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: external market evidence

The external market evidence issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the employer cites a salary website headline. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes method, job match, date, geography, and role level. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is use external data only as support, not as the whole file. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: weak benchmarks can hurt if they do not match the role. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: market context supports rather than replaces contract evidence. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: occupation match

The occupation match issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the comparator is selected by title alone. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes duties, tools, seniority, reporting line, and output expectations. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is choose comparator by actual work, not branding. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: inflated titles can make salary look lower than it is. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: salary is judged against a realistic role. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: hours normalization

The hours normalization issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is salary is compared without weekly hours. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes contracted hours and annualized gross salary. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is normalize comparisons to the same working-time basis. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: part-time and reduced-hour files are easy to misread. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: the reviewer can compare like with like. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: regional context

The regional context issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the package ignores work location. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes location, remote arrangement, and workplace clause. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is state where the work is primarily performed. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: do not overclaim regional data if the role is remote or hybrid. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: salary context fits the actual employment setting. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: probation and step-up effects

The probation and step-up effects issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the comparator uses the later salary but the contract starts lower. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes salary timeline with dates and guarantee status. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is compare the salary that is actually assured for the relevant period. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: future raises do not automatically cure current low pay. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: the file avoids less visible timing traps. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: benefits and allowances

The benefits and allowances issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is non-cash value is mixed into salary. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes salary split, benefits schedule, and reimbursement policy. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is lead with gross cash salary and label everything else. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: do not use reimbursements as pay. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: the comparator analysis remains clean. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Review module: refusal response

The refusal response issue should be treated as a proof problem. In a German work permit file, the employer and candidate may already understand why the salary is fair. The authority does not share that context. The documents must show the salary, hours, route, occupation, and comparator without requiring the reviewer to reconstruct the company's pay philosophy.

The practical problem is the refile argues fairness without new evidence. This problem is especially common after a salary refusal because the team becomes focused on defending the offer rather than correcting the evidence. A defensive explanation can make the file longer while leaving the actual weakness untouched. The better move is to reduce the issue to a few verifiable facts.

Useful evidence includes refusal phrase, revised comparator table, revised contract or annex. The evidence should be current, named, dated where relevant, and tied to the specific route. A salary table without hours is incomplete. A market benchmark without job duties is weak. A contract annex without the employer declaration updated is inconsistent. A manager statement without payroll confirmation may sound helpful but still fail to prove the employment condition.

The correction action is map every concern to a corrected document. Write the action into the package as a document control, not just an internal instruction. If the file is being re-submitted, state what changed since the refusal: salary, hours, route selection, comparator, role description, or document consistency. A reviewer should be able to see the correction in the first few pages.

Warning: do not send a longer version of the same weak package. The purpose is not to game the review or create artificial documentation. The purpose is to make the real employment condition legible. Overstating a comparator, hiding a lower salary period, or pretending that discretionary compensation is assured creates a second problem even if it seems to solve the first.

Expected result: the second filing answers the actual reason for concern. That result is usually a cleaner file, not a assured approval. Immigration outcomes remain fact-specific, but a coherent evidence package gives the employer and candidate a much better basis for a filing decision, preliminary-consent request, or targeted refile.

Operating note: tariff-status owner

Owner: HR legal or compensation. The owner should maintain a tariff applicability note. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is everyone assumes no Tarifvertrag applies but nobody documented the check. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Operating note: band owner

Owner: compensation or finance. The owner should maintain a band-to-offer reconciliation table. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is the candidate's salary sits outside normal range without explanation. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Operating note: role owner

Owner: hiring manager. The owner should maintain a role-level memo. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is the comparator is chosen from a title that does not match the work. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Operating note: hours owner

Owner: HR operations. The owner should maintain a salary and weekly-hours normalization sheet. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is full-time and part-time figures are mixed. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Operating note: source owner

Owner: filing adviser. The owner should maintain current official links and date checks. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is old Blue Card figures or stale assumptions enter the package. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Operating note: privacy owner

Owner: HR or legal. The owner should maintain anonymized comparator protocol. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is comparable employee data is shared in a way that creates a new compliance issue. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Operating note: refile owner

Owner: case response lead. The owner should maintain a concern-to-document correction table. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is the response defends the employer instead of fixing the file. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Operating note: candidate owner

Owner: relocation contact. The owner should maintain a plain-language salary explanation. This is a practical control, not internal bureaucracy. Salary refusals often happen because no single person owns the connection between contract terms, employer declaration, route choice, and supporting evidence.

The risk is the candidate cannot explain what benchmark was used. If the risk appears in the package, stop and correct it before submission. A permit file can be technically long and still weak if the key facts contradict each other. A short, consistent file is usually more useful than a long bundle of unrelated attachments.

Use a simple final question: can someone outside the company understand the salary and role in three minutes, then verify the facts from attached documents? If not, the package needs another pass.

Template language for a non-tariff comparator memo

Use this as a drafting prompt, not as legal advice:

The employer confirms that no clear Tarifvertrag salary table is being used for this role after internal review. The assured gross salary is EUR [amount] per year for [hours] hours per week. The role is mapped internally to [level/band], with a normal salary range of [range] for comparable duties and seniority. The attached role description, salary table, and employer declaration use the same title, duties, working time, and salary figure.

Practical correction roadmap

First, answer the tariff question explicitly. If a tariff applies, use it correctly. If not, state why the file uses alternative evidence.

Second, build a comparator table. Put role, duties, level, hours, salary, and source next to each other. Do not rely on prose alone.

Third, reconcile the documents. The comparator table should match the employment contract, employer declaration, and cover memo. If it does not, fix the source documents first.

Fourth, avoid overconfidentiality. Employers do not need to expose entire compensation systems, but they do need enough evidence to make the offer understandable. A narrow band extract or anonymized range can be more useful than a vague statement.

Fifth, refile with correction discipline. If the refusal or delay was about salary comparability, the second package should visibly add comparator evidence or corrected salary terms. A new letter without new evidence is weak.

Practical next step

Create a one-page non-tariff salary memo before any refile: tariff status, role, level, hours, assured salary, internal band or comparator, external support if used, and document owner. If any box is blank, the file still has a comparability gap.

Final audit before filing

Run one final contradiction audit after the memo is drafted. Read only the contract, annex, employer declaration, role description, and comparator table. Ignore email explanations and recruiter notes for this pass. The question is whether those core documents say the same thing. If the role title changes, if weekly hours disappear, if the salary table uses total compensation while the contract uses base salary, or if the memo cites a level that the job description does not support, the package should not be filed yet.

Then test the package from the perspective of someone who has never met the candidate. Can that reader identify the legal employer, the job, the level, the working time, the assured salary, the route, and the comparator in under three minutes? If not, the issue is not only administrative formatting. The issue is that the evidence is still too dependent on private context. That is exactly the weakness a salary-comparability review exposes.

Finally, keep the correction proportional. Do not attach every compensation policy the company has ever written. Use the narrowest evidence that answers the question: a short tariff-status note, a role-level description, an internal band extract or anonymized range where appropriate, a current salary table, and the official route source checked for the filing year. A focused file respects the reviewer and protects the employer from creating avoidable contradictions.

Internal links for the cluster

• Why Germany work permits are rejected for salary and Tariflohn issues
• Tariflohn vs ortsueblich salary review
• Job description, degree match, and salary comparability
• Startup and small-employer salary evidence
• Response letters and contract language templates
• Post-refusal recovery roadmap
• Probation salary and step-up raises
• Employer BA filing checklist