Law Page 577 - 582 Final
Law Page 577 - 582 Final
Law Page 577 - 582 Final
operations of SMC. This also holds true with respect to the other workers who were made to
perform janitorial and messengerial services the nature of which has been jurisprudentially
recognized and considered as directly related to the principal business of the employer.
1
The validity of job contracting arrangement does not depend on whether the job,
work, or service is done within or outside the company premises of the principal. In Acevedo
(Acevedo v. Advanstar Co.. Inc., G.R. No. 157656, Nov. 11,2005) the Supreme Court, citing
a provision in the Labor Code’s Implementing Rules, (Rute WA, Bock III, Section 4[d] of the
Rules to Implement the Labor Code) emphasized that there is legitimate job contracting
regardless of whether the contracted job, work or service is to be performed or completed
within or outside the premises of the principal. This was also the holding in the 2018 case of
Mago (Mago v. Sun Power Manufacturing Umted. G.R. No. 210961, Jan. 24,2018). Thus, the
fact that the petitioners were working within the premises of the principal (Sunpower), by
itself does not negate the control of the job contractor (Jobcrest) over the means, method, and
result of the petitioners' work. Job contracting is permissible “whether such job, work, or
service is to be performed or completed within or outside the premises of the principal” for as
long as the elements of a labor-only contractor are not present. Since Jobcrest was a provider
of business process services, its employees would necessarily work within the premises of its
client companies in order for Jobcrest to perform its contractual undertaking. Mere physical
presence in Sunpower’s plant does not necessarily mean that Sunpower controlled the means
and method of the petitioners' work.
But in Babas, G.R. No. 186091, Dec. 15, 2010. the High Court cited as additional
basis for holding that the contractor, BMS1,1 was a labor-only contractor, the fact that
petitioners worked at the premises of respondent LSC and nowhere else. Other than the
provisions of the Agreement between respondent LSC and BMSI, there was no showing that
it was BMS1 which established petitioners’ working procedure and methods, which
supervised petitioners in their work, or which evaluated the same. There was absolute lack of
evidence that BMSI exercised control over them or their work, except for the fact that
petitioners were hired by BMSI
VIII-D.
LEGAL RIGHTS AND BENEFITS COMPLIANCE TEST
LIABILITY OF PRINCIPAL
At the outset, it bears stressing that the status of the principal as indirect employer
holds true only in situations where the job contractor with which it is dealing is engaged in
legitimate or permissible job contracting arrangement. If it were otherwise, then the principal
is deemed the direct employer of the employees supplied by the contractor which, in this
situation, should be considered merely a labor-only contractor.
The phrase “to the extent of the work performed under the contract, in the same
manner and extent that he is liable to employees directly employed by him” which is used in
the law (Used in the 2nd paragraph of Article 106, Labor Code and in Section 3[fc] and
Section9, Department Order No. 174. Series of 2017) underscores all too clearly the limited
scope and extent of the solidary liability of the principal. Thus, any violation of the Labor
Code and other social legislation by the contractor other than the ones covered by this phrase
no longer falls under the concept of solidary liability for which the principal may be so held
liable (Pa Automation Center, Inc, v. NLRC, G.R. No, 115920, Jan, 29, 1996; Ecalv. NLRC,
G.R, Nos. 92777-78, March 13,1991; Philippine Bank of Communications v, NLRC, G.R. No.
56598, Dec, 19,1986,146 SCRA 347; Cabe v. Tumang, G.R. No. I.-57682. March 18,
1985,135 SCRA 389; Mafinco Trading Corporation v. Ople, G.R. No. L-37790, March
25,1976,70 SCRA 139' See also Section 13, Rule Vlll-A, Book III, Rules to Implementthe
Later Code, as amended by Department Order No. 10, Series of 1997 (May 30,1997]).
Rosewood Processing is illuminating on this point (Rosewood Processing, Inc. Vs.
NLRC, GR. No. 116476-84m may 21, 1996, 290 SCRA408). In this case, the security guards
farmed out by the security agency to petitioner were assigned to its other clients. Withal,
fairness dictates that the petitioner should not be held liable for wage differentials incurred
while the security guards were assigned to other companies. Under Articles 106, 107 and 109
of the Labor Code, should the contractor tail to pay the wages of its employees in accordance
with law, the indirect employer (the petitioner in this case), is jointly and severally liable with
die contractor, but such responsibility should be understood to be limited to the extent of the
work performed under the contract, in the same manner and extent that he is liable to the
employees directly employed by him. This liability of petitioner covers the payment of the
workers' performance of any work, task, job or project. So long as the work, task, job or
project has been performed for petitioner's benefit or on its behalf, the liability accrues for
such period even if, later on, the employees are eventually transferred or reassigned
elsewhere. To reiterate, the principal’s (indirect employer's) liability to the contractor's
employees extends only to the period during which they were working for the petitioner, and
the fact that they were reassigned to another principal necessarily ends such responsibility.
The principal is made liable to his indirect employees because it can protect itself from
irresponsible contractors by withholding such sums and paying them directly (o the
employees or by requiring a bond from the contractor for this purpose.
The Rosewood principle was reiterated in GSIS v. NLRC, GR. No. 180045, Nov. 7,
2010. In this case, DNL Security Agency, the direct employer of the private respondent
security guards which assigned them to petitioner GSIS office in Tacloban City, informed
respondents in February 1993, that its service contract with petitioner was terminated. This
notwithstanding, DNL Security Agency instructed respondents to continue reporting for work
to petitioner. Respondents worked as instructed until April 20, 1993, but without receiving
their wages; after which, they were terminated from employment. The High Court ruled that
petitioner’s
liability does not cover only the payment of respondents’ salary differential and 13 th month
pay during the time they worked for petitioner but additionally, petitioner is solidarity liable
with DNL Security for respondents’ unpaid wages from February 1993 until April 20, 1993.
While 6 LAW OH LABOR STANDARDS AMD SOCIAL LEGISLATION
ANNOTATED
it is true that respondents continued working for petitioner after the expiration of their
contract, based on the instruction of DNL Security, petitioner did not object to such
assignment and allowed respondents to render service. Thus, petitioner impliedly approved
the extension of respondents’ services. Accordingly, petitioner is bound by the provisions of
the Labor Code on indirect employment. Petitioner cannot be allowed to deny its obligation
to respondents after it had benefited from their services. So long as the work, task, job, or