Add new comment

Employers questions on H-1 compliance

Printer-friendly versionPDF version
ANSWER: 

1. Are we OK in keeping an H1B worker without work as long as we pay him during the project break too - at the LCA wage level.

Ans. You must pay your H-1 workers the legal wage. This is the higher of the prevailing wage or the actual wage. Actual wage is defined as that which you pay other similar employees in the same geographical location. So, as long as you pay the legal wage, there is no problem.

2. Is it OK to give advances - besides paying LCA wages while the person in on project and then during the project break, run the payroll for LCA wages but recover the advances (post-tax obviously) and pay only balances if any?

Ans. In my view, this is illegal for many reasons.

3. Is it OK to pay all our consulting employees a wage of 60K or the LCA wage whichever is higher, irrespective of the skill set - by making this a standard wage policy in the company.

Ans. As long as you are following the wage guidelines and paying according to the seniority level of the job, I see no issue with this arrangement. But you cannot pay level, 1, 2, 3, and 4 employees $60,000. The wage must be paid according to the job they perform.

4. Further, is it OK to give discretionary bonuses above these levels to employees that the management considers are more valuable to the company?

Ans. As long as you can objectively justify the salary variance, I see no issues with this.

Unless the context shows otherwise, all answers here were provided by Rajiv and were compiled and reported by our editorial team from comments and blog on immigration.com

Add new comment

WYSIWYG

  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
  • Global tokens will be replaced with their respective token values (e.g. [site:name] or [current-page:title]).

Filtered HTML

  • Use [fn]...[/fn] (or <fn>...</fn>) to insert automatically numbered footnotes.
  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
  • You may post PHP code. You should include <?php ?> tags.
  • You may insert a link to a defined site with [link: title].
  • Tags allowed: a, em, strong, cite, code, ol, ul, li, dl, dt, dd
  • Typographic refinements will be added.
  • [faq] or [faq:123,questions_inline,categories_inline] - insert FAQ content based on the optional category, question style and category style.
  • Allowed HTML tags: <a> <p> <h2> <h3> <h4> <h5> <h6> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd><style>
  • Global tokens will be replaced with their respective token values (e.g. [site:name] or [current-page:title]).

Full HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
  • Global tokens will be replaced with their respective token values (e.g. [site:name] or [current-page:title]).

full_html

  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Global tokens will be replaced with their respective token values (e.g. [site:name] or [current-page:title]).

filtered_html

  • Use [fn]...[/fn] (or <fn>...</fn>) to insert automatically numbered footnotes.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • No HTML tags allowed.
  • [faq] or [faq:123,questions_inline,categories_inline] - insert FAQ content based on the optional category, question style and category style.
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Tags allowed: a, em, strong, cite, code, ol, ul, li, dl, dt, dd
  • You may post PHP code. You should include <?php ?> tags.
  • Global tokens will be replaced with their respective token values (e.g. [site:name] or [current-page:title]).
  • Typographic refinements will be added.
  • You may insert a link to a defined site with [link: title].

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
CAPTCHA
Sorry we have to put you through this. We need to prevent SPAM.