CyberCode.ph · Philippines

Who Owns Software Created by an Employee in the Philippines?

Last updated September 28, 2026 · Practical privacy, cybersecurity and technology-law guidance
Software developer code for employee software copyright ownership in the Philippines

Last materially reviewed: September 6, 2026

Direct Answer

Section 178.3 of the Intellectual Property Code decides it. The employer owns the copyright where the software “is the result of the performance of his regularly-assigned duties, unless there is an agreement, express or implied, to the contrary.” The employee owns it where creating the work “is not a part of his regular duties even if the employee uses the time, facilities and materials of the employer.” Duties decide, not equipment. For the wider ownership and licensing map, see the Intellectual Property Philippines hub.

Key Takeaways

  • The test is regularly-assigned duties, not who paid for the laptop or the hours.
  • Section 178.3(a) expressly gives the employee copyright in out-of-duty work made using “the time, facilities and materials of the employer.”
  • Employer ownership under Section 178.3(b) yields to “an agreement, express or implied, to the contrary.”
  • No assignment or licence between living parties without “a written indication of such intention” (Section 180.2, as amended).
  • Patents follow a parallel rule in Section 30.2, and contractors are governed by Section 178.4 instead.

On This Page

Decision Snapshot

How the work arose Who owns the copyright What changes it Next step
Written as part of regularly-assigned duties The employer (§178.3(b)) An agreement, express or implied, to the contrary Check the employment contract and IP clause
Written outside regular duties The employee (§178.3(a)) A contract validly assigning future work product Read the work-product assignment language
Written outside regular duties but on employer time or equipment Still the employee (§178.3(a)) Confidentiality or acceptable-use obligations, which are separate Separate ownership from the policy-breach question
Written under a signed agreement dealing with ownership Whoever the writing says (subject to §180.2) Whether the writing indicates an intention to assign or license Confirm it is signed, dated and specific

Governing Law and Authorities

The controlling text is Section 178.3 of Republic Act No. 8293, which Republic Act No. 10372 (2013) did not amend, though that Act rewrote neighbouring provisions including Sections 180, 191, 198 and 216. The language below was read from the full text of RA 8293 published by the LawPhil Project and cross-checked against RA 10372. It reads in full:

“In the case of work created by an author during and in the course of his employment, the copyright shall belong to: (a) The employee, if the creation of the object of copyright is not a part of his regular duties even if the employee uses the time, facilities and materials of the employer. (b) The employer, if the work is the result of the performance of his regularly-assigned duties, unless there is an agreement, express or implied, to the contrary.”

No further condition appears. There is no work-made-for-hire doctrine in Philippine copyright law, and no provision making employer ownership automatic for everything produced during employment.

The Rule, Element by Element

“During and in the course of his employment”

The provision engages only where there is employment. For an independent contractor, Section 178.4 applies instead: the commissioner owns the work but “the copyright thereto shall remain with the creator, unless there is a written stipulation to the contrary” — see software created by a freelancer.

“Regularly-assigned duties” is the dividing line

The operative fact is what the developer was actually assigned to do. An engineer tasked to build the payment service performs regularly-assigned duties in writing it; the same engineer writing an unrelated game at weekends does not. The enquiry looks to the role, job description, tickets and instructions given — not to a generic clause claiming everything.

Employer resources do not decide it

This is the sentence people miss. Section 178.3(a) gives the employee copyright in out-of-duty work “even if the employee uses the time, facilities and materials of the employer.” The company laptop or working hours do not convert out-of-duty work into employer-owned work. That use may breach a policy or confidentiality undertaking — real exposures, but separate from who holds the copyright.

“Unless there is an agreement… to the contrary”

Employer ownership under 178.3(b) is a default that yields to agreement. Section 178.3(a) carries no equivalent proviso, so a company wanting to reach genuinely out-of-duty work should rely on an express assignment — which must satisfy Section 180.2, as amended: copyright “is not deemed assigned or licensed inter vivos, in whole or in part, unless there is a written indication of such intention.”

Patents are governed separately

Section 30.2 applies a parallel split to patents — employee where “the inventive activity is not a part of his regular duties,” employer where it results from regularly-assigned duties — but Section 22.2 excludes “programs for computers” from patenting, so for software the copyright analysis usually does the work.

Exceptions and Boundaries

Registration is not a condition of protection

Nothing here depends on filing anything: Section 191, as amended, provides that registration and deposit “is not a condition of copyright protection,” and IPOPHL says the same. Registration is evidentiary — it records who claimed what, and when. See software copyright in the Philippines.

A written agreement overrides the default

Section 178.3 is a gap-filler: where a signed contract, IP clause or deed addresses ownership, that writing normally governs, subject to Section 180.2. Most disputes are decided on the documents, not the statute.

Moral rights never move

Whoever owns the economic rights, the developer keeps the moral rights in Section 193, which under Section 198, as amended, “shall not be assignable or subject to license.” Separately, Section 230, inserted by RA 10372, requires schools and universities to adopt IP policies governing creation of IP by the institution and its employees.

Hypothetical Philippine Scenarios

These are illustrative hypotheticals, not real cases or legal advice.

Hypothetical 1: the assigned build

A Taguig BPO hires a “Software Engineer, Billing Platform” and assigns them an invoicing module. That is the result of regularly-assigned duties, so under Section 178.3(b) the employer owns the copyright absent contrary agreement, and the job description and ticket history prove it.

Hypothetical 2: the weekend side project

The same developer builds an unrelated budgeting app at home, occasionally on the company laptop. On the face of Section 178.3(a) the copyright is the employee’s: creating it was not part of their regular duties, and the provision expressly contemplates use of employer time, facilities and materials. Any employer grievance is about policy, not ownership.

Documentation and Records

Because the test is factual, the paperwork usually decides it:

  • The employment contract and IP clause — signed and dated, with assignment language meeting Section 180.2.
  • The job description and role definition — the primary evidence of regularly-assigned duties.
  • Assignment records and source control history — tickets, written instructions and objectives showing what was asked for, plus authored commits with timestamps and identities. Keeping side projects in a separate personal repository off company infrastructure makes the boundary easier to prove.
  • Deeds of assignment for anything moved after the fact, recorded with IPOPHL, plus separation records for devices, credentials and repository access.

What To Do, Step by Step

  1. Confirm the relationship. Employee or contractor determines whether Section 178.3 or 178.4 applies, and turns on the substance of the engagement, not the invoice label.
  2. Identify the specific work and date it, fixing the commits and versions in issue rather than arguing about “the software” in the abstract.
  3. Establish the duties as at that date — job description, assignments and instructions then in force.
  4. Read the contract for a work-product or invention-assignment clause, a side-project policy and any separate development agreement, and check that any assignment is a written indication of intention (Section 180.2).
  5. Apply Section 178.3. Duties, not resources. Outside regular duties, the employee owns it absent a valid assignment.
  6. Fix the position in writing with a signed, dated deed identifying the work precisely.
  7. Register if useful. Registration is voluntary and evidentiary: complete IPOPHL’s Copyright Registry Enrollment Form, file online, pay against an electronic Statement of Account and receive the certificate; IPOPHL also records transfers. Memorandum Circular No. 2026-007 revised these rules in 2026 and is reported to require a declaration of whether generative AI was used and which program, and to treat the “Author or Creator” as a natural person. That could not be verified against the circular’s text, which was not machine-readable when checked on 6 September 2026 — check IPOPHL’s current pages before filing, and answer any AI-use declaration truthfully.

Remedies and Realistic Outcomes

Civil. Section 216, as amended, provides for injunction, actual damages plus the infringer’s profits, impounding, destruction of infringing copies, and moral and exemplary damages, plus an election of statutory damages “in a sum equivalent to the filing fee of the infringement action but not less than Fifty thousand pesos (Php50,000.00).” Section 226, as amended, bars damages “after the lapse of four (4) years from the time the cause of action arose.” Where the real dispute is who owns what, a contractual route is often more useful than an infringement suit.

Criminal. Section 217.1 provides imprisonment and fines rising by offence, from one to three years plus ₱50,000 to ₱150,000 for a first offence. Prosecution requires proof beyond reasonable doubt and is rarely the right tool for a good-faith ownership dispute.

Administrative and employment. IPOPHL records transfers, and its copyright bureau has original jurisdiction under Section 9A.1 over certain licence-term disputes. Separately, a side project may raise disciplinary or confidentiality issues — a different body of law with different outcomes. Neither route guarantees recovery, and both take time.

Common Mistakes

  • Treating the company laptop as decisive. Section 178.3(a) says the opposite in terms.
  • Assuming the employer owns everything created during employment. The provision is limited to regularly-assigned duties.
  • Relying on an unsigned or oral understanding. Section 180.2 requires a written indication of intention.
  • Applying the employee rule to a contractor, where Section 178.4 governs instead, or confusing copyright with the separate patent rule in Section 30.2.
  • Believing registration determines ownership. It records a claim; Section 178.3 decides the right.
  • Promising to assign moral rights, which Section 198, as amended, makes non-assignable.

Ownership-Determination Checklist and IP Clause Points

Determining ownership

  • Was the developer an employee, or engaged as a contractor?
  • What was the written job description and actual role when the code was written, and was building this particular software within those duties?
  • Is there written evidence — tickets, instructions, objectives?
  • Does a signed contract address work product, and does it show an intention to assign (Section 180.2)?
  • Is the dispute really about ownership, or about confidentiality and policy breach?

What an IP clause should contain

  • A definition of work product covering source code, documentation, designs, data and repositories.
  • An express present assignment of copyright in work product, with a written indication of intention.
  • A statement of which duties are regularly assigned, aligned to the job description.
  • Pre-existing and personal IP carved out, plus a side-project policy saying plainly what is not claimed, and open-source rules.
  • Attribution and modification expectations stated expressly, since moral rights cannot be assigned.
  • Confidentiality kept distinct from ownership, and return of devices, credentials and repository access at separation.

Frequently Asked Questions

Does the employer own code written on a company laptop?

Not on that basis. Section 178.3(a) gives the employee copyright in out-of-duty work “even if the employee uses the time, facilities and materials of the employer.”

Does the employer need to register to own the copyright?

No. Ownership follows Section 178.3; Section 191, as amended, states registration and deposit is not a condition of protection.

What if the developer was a contractor?

Section 178.4 applies: the commissioner owns the work but copyright stays with the creator absent a written stipulation to the contrary.

Who owns code an employee generated with an AI assistant?

Section 178.3 allocates whatever copyright exists, but whether copyright subsists in machine-generated output is a distinct question — see who owns AI-generated code.

Official Sources

Disclaimer

Important: This article provides general educational information about Philippine law, regulation, cybersecurity, technology, or business compliance. It is not legal advice and does not create an attorney-client relationship. Laws, agency procedures, technical standards, platform rules, and the facts of each situation may change the result. Verify current requirements through the cited official sources and seek qualified professional advice when your rights, deadlines, money, safety, or legal exposure may be affected.

CyberCode updates

Get practical updates on Philippine technology law, data privacy, cybersecurity, and AI.

Email activity tracking

Unsubscribe any time. See our privacy policy below.