Asserting Copyright Ownership for Remote Developers: Drafting Contracts That Assign Code Rights to Foreign Employers (Philippines)

Introduction: Why ownership of PH-written code must be documented

Offshore companies often assume that when a Philippine-based developer is paid to write source code, the foreign company automatically owns the copyright. Under Philippine law, that assumption can be wrong. Copyright ownership depends on whether the work is created within regularly assigned duties, whether it is a commissioned work, and whether there is a written assignment (or written exclusive license) that clearly transfers economic rights.

This HR legal guide explains how offshore employers can contractually secure full ownership of software code written in the Philippines and properly document the transfer to the foreign parent company.

Governing Philippine law on software copyright ownership and transfers

1) Copyright in software exists upon creation; registration is not a condition

Philippine copyright protection attaches from the moment an original work is created and fixed in a tangible medium; software source code is protected as a literary work. Once created, the author (or other lawful owner) holds the economic rights unless the law or a valid contract provides otherwise. (Based on internal knowledge of Philippine law.)

2) Default rule: the author owns copyright, subject to statutory exceptions

As a starting point, copyright belongs to the author of the work. For works of joint authorship, co-authors are co-owners unless they agree otherwise. These rules are expressly stated in the Intellectual Property Code. (Intellectual Property Code of the Philippines, Republic Act No. 8293, approved June 6, 1997, Section 178.)

3) Works made “during employment” depend on regular duties

For works created by an author during and in the course of employment, Philippine law draws a sharp line:

a) Employee owns if creating the work is not part of regular duties, even if company time, facilities, or materials were used.

b) Employer owns if the work is the result of the employee’s regularly assigned duties, unless there is an agreement (express or implied) to the contrary.

These rules are found in Section 178.3 of the Intellectual Property Code. (Republic Act No. 8293, approved June 6, 1997, Section 178.3.)

4) Commissioned works: ownership of the “work” vs. ownership of copyright

For commissioned works under the current Intellectual Property Code, the person who commissioned and paid for the work generally owns the material “work,” but copyright remains with the creator unless there is a written stipulation to the contrary. (Republic Act No. 8293, approved June 6, 1997, Section 178.4.)

This matters in outsourcing: even if the offshore company “owns” the deliverable in a business sense, the default legal position is that the developer still owns copyright unless the contract clearly transfers it in writing.

5) Assignments and exclusive licenses must be in writing

Philippine law requires a written indication of intent for inter vivos transfers. A copyright is not deemed assigned (and under the amendments, not deemed assigned or licensed) unless there is a written indication of that intention. (Republic Act No. 8293, approved June 6, 1997, Section 180.2, as amended by Republic Act No. 10372, approved February 28, 2013.)

Exclusive licensing is also expressly recognized: economic rights may be exclusively licensed, and within the scope of the exclusive license, the licensee gets the rights and remedies the licensor had. (Republic Act No. 10372, approved February 28, 2013, amending Section 180 of Republic Act No. 8293.)

6) Copyright is separate from the physical or digital copy of code

Delivering the repository, source files, or compiled build does not automatically transfer the copyright. Copyright is distinct from the material object; transfer of the copy does not imply transfer of copyright. (Republic Act No. 8293, approved June 6, 1997, Section 181.)

Supreme Court guidance: what HR and legal teams should take from recent cases

1) Only the expression is protected; ideas and concepts alone do not confer authorship

The Supreme Court has emphasized that copyright protects the expression of an idea, not the idea itself. A person who merely contributes concepts or ideas is not deemed an author and does not acquire copyright over the resulting work. This helps clarify ownership disputes where managers or product owners claim authorship without writing code or producing protectable expression. (Republic of the Philippines v. Heirs of Tupaz, et al., G.R. No. 197335, December 7, 2020.)

2) Commissioned work under the IP Code: default is still creator ownership unless a written transfer exists

The Supreme Court has reiterated that under Section 178.4 of the Intellectual Property Code, a commissioned work generally leaves copyright with the creator, unless there is a written agreement transferring it to the commissioning party. The Court noted that disputes could be avoided by entering into a clear contract spelling out the parties’ rights. (Republic of the Philippines v. Heirs of Tupaz, et al., G.R. No. 197335, December 7, 2020.)

3) Recordal/publication is not a validity requirement for copyright assignments

In disputes involving copyright-related deeds or agreements, the Supreme Court has recognized that the law does not require publication in the IPO Gazette as a condition for the validity of copyright assignments, unlike certain rules in patents and trademarks. For HR and contracting, the main takeaway is that the written instrument is primary; recordal may help evidentiary posture but is not, by itself, a validity requirement. (Cosac, Inc. v. Filipino Society of Composers, Authors and Publishers, Inc., G.R. No. 222537, February 15, 2023.)

Common offshore setups and the ownership risk under Philippine law

Below are frequent arrangements and where the risk typically arises:

Scenario table: where contracts usually fail

Setup	Typical HR assumption	Legal risk under PH copyright rules	What the contract should do
PH developer hired as an employee of a local subsidiary/PEO, coding for foreign parent	Parent owns all code automatically	Employer ownership depends on whether coding is within regularly assigned duties; parent is not automatically the employer-owner	Define duties + add present-tense assignment from employee to the employing entity, plus an onward assignment to the foreign parent
Independent contractor in PH engaged by foreign entity	Paying invoices transfers ownership	Commissioned work: copyright stays with creator unless written stipulation transfers it	Add explicit written assignment of economic rights; include waiver/consent clauses for permitted modifications
Team output (multiple contributors, Git-based)	Company owns “the repo”	Possible joint authorship and fragmented ownership if assignments are missing	Require individual assignment from each contributor; treat merges/commits as covered works; require contributor agreements
Developer uses own prior code snippets or open-source libraries	Everything delivered is owned by company	Third-party code may be non-assignable; company may receive only a license or may breach OSS terms	Disclosure of pre-existing materials; license compliance obligations; approval workflow; warranties with defined carve-outs

Contract drafting approach: how to secure full ownership for a foreign parent

1) Identify who is the “employer” or “commissioning party” under PH law

Ownership clauses should match the real relationship:

• If the developer is an employee, align the job description and employment contract so coding is within regularly assigned duties under Section 178.3, and still add a written assignment as a belt-and-suspenders measure. (Republic Act No. 8293, approved June 6, 1997, Section 178.3.)
• If the developer is a contractor, treat the work as commissioned and rely on a written stipulation transferring copyright. (Republic Act No. 8293, approved June 6, 1997, Section 178.4.)

2) Use a present-tense assignment of all economic rights (and specify scope)

Use language that effects an immediate transfer (e.g., “hereby assigns”), covering all economic rights in the code and related materials created during the engagement. Under Philippine law, an assignment is not recognized without written indication of intent. (Republic Act No. 8293, approved June 6, 1997, Section 180.2, as amended by Republic Act No. 10372, approved February 28, 2013.)

Recommended scope definitions to include:

• “Work Product” to include source code, object code, scripts, documentation, tests, schemas, build files, and design files that contain protectable expression.
• Coverage for works “created solely or jointly,” addressing joint authorship risk. (Republic Act No. 8293, approved June 6, 1997, Section 178.2.)
• Territory: worldwide; term: full term of protection.

3) Add an “onward assignment” to the foreign parent (or direct assignment to parent)

If the Philippine developer’s contract is with a local entity (subsidiary/branch/PEO), the simplest chain is:

• Developer assigns to the local employing/contracting entity; then
• Local entity assigns to the foreign parent under a separate IP assignment or an IP clause in the intercompany services agreement.

This helps prevent gaps where the foreign parent claims ownership but lacks a written instrument directly connecting the developer’s authorship to the parent’s title.

4) Separate “delivery of code” from “transfer of rights”

Because copyright is distinct from the copy, contracts should clearly state that repository access, delivery of code, or turnover of devices does not replace a written IP transfer clause. (Republic Act No. 8293, approved June 6, 1997, Section 181.)

5) Decide between assignment vs. exclusive license (and when each is used)

Assignment is best if the foreign parent needs full ownership for M&A, licensing, or product commercialization.

Exclusive license can work when assignment is not feasible, but it must still be in writing and should clearly identify exclusivity and the economic rights covered. (Republic Act No. 10372, approved February 28, 2013, amending Section 180 of Republic Act No. 8293.)

6) Address pre-existing materials, third-party code, and open-source compliance

Contracts should include:

• Disclosure obligation for any pre-existing code the developer intends to reuse.
• License grant to the company for pre-existing code if it must be incorporated, since it may not be assignable.
• Approval and compliance process for open-source components (e.g., requiring a bill of materials and legal review).

7) Documentation and HR controls that support enforceability

Beyond contract text, implement process evidence:

• Signed employment/contractor agreement before repository access is granted.
• Signed IP assignment addendum per hire (especially for conversions from contractor to employee).
• Exit checklist confirming return of devices, credentials, and reiterating confidentiality and IP ownership.

Sample clause checklist (what to include in HR templates)

For offshore companies hiring PH-based developers, these contract elements are commonly used:

• Work Product definition tied to commits, tickets, and deliverables.
• Assignment clause (present-tense) of all economic rights to employer/commissioning party, plus confirmatory assignment on request. (Republic Act No. 8293, approved June 6, 1997, Section 180.2, as amended by Republic Act No. 10372, approved February 28, 2013.)
• Employment duties clause clearly stating software development is within regularly assigned duties (for employees). (Republic Act No. 8293, approved June 6, 1997, Section 178.3.)
• Commissioned-work transfer clause stating that notwithstanding Section 178.4 default rule, copyright is assigned to the company (for contractors). (Republic Act No. 8293, approved June 6, 1997, Section 178.4.)
• Joint authorship handling and obligation to secure assignments from all contributors. (Republic Act No. 8293, approved June 6, 1997, Section 178.2.)
• Representations and warranties (originality, no undisclosed third-party code), with reasonable carve-outs for approved open-source use.
• Confidentiality and trade secrets protections (separate from copyright).

Practical implications for foreign employers: what this means for audits and disputes

In due diligence, missing written assignments can create title defects: even if the company paid for development, the developer may remain the copyright owner for commissioned work absent a written transfer. (Republic Act No. 8293, approved June 6, 1997, Section 178.4.)

In disputes, a party who only contributed ideas is generally not treated as an author; authorship turns on actual protectable expression such as code and other original material. (Republic of the Philippines v. Heirs of Tupaz, et al., G.R. No. 197335, December 7, 2020.)

Conclusion: HR and legal steps that reduce ownership risk

To secure full copyright ownership of code written in the Philippines for a foreign parent entity:

• Use written IP assignment language (or written exclusive license) in every developer engagement. (Republic Act No. 8293, approved June 6, 1997, Section 180.2, as amended by Republic Act No. 10372, approved February 28, 2013.)
• For employees, align job duties so software development is clearly within regularly assigned duties. (Republic Act No. 8293, approved June 6, 1997, Section 178.3.)
• For contractors, do not rely on payment alone; treat the arrangement as commissioned and include a written stipulation transferring copyright. (Republic Act No. 8293, approved June 6, 1997, Section 178.4.)
• Implement contributor and exit processes that preserve evidence of assignment and reduce later disputes.

These measures directly address the ownership rules in the Intellectual Property Code and reflect the Supreme Court’s reminder that clear contracts prevent avoidable conflicts. (Republic of the Philippines v. Heirs of Tupaz, et al., G.R. No. 197335, December 7, 2020.)

About Nicolas and De Vega Law Offices

 Nicolas and de Vega Law Offices is a full-service law firm in the Philippines.  You may visit us at the 16th Flr., Suite 1607 AIC Burgundy Empire Tower, ADB Ave., Ortigas Center, 1605 Pasig City, Metro Manila, Philippines.  You may also call us at +632 84706126, +632 84706130, +632 84016392 or e-mail us at [email protected]. Visit our website https://ndvlaw.com.