Software Development Agreements in the Philippines: Ownership and Acceptance

A software development agreement in the Philippines is a contract that governs how custom software is built, who owns it, and how it is accepted and paid for. Philippine law does not have a single statute governing this kind of contract. Instead, the rules come from the Intellectual Property Code (Republic Act No. 8293), the Civil Code on contracts, and the parties' own written terms. The most important point: ownership of the software does not automatically pass to the client just because the client paid for it. The contract must say who owns the code, the data, and the deliverables — ideally in clear, express language.

What a software development agreement should cover

A well-drafted agreement for software development in the Philippines typically addresses:

• Scope of work. What the developer will build, the features, the platforms, and what is expressly excluded.
• Deliverables and milestones. The code, documentation, source files, and any third-party components.
• Ownership of intellectual property. Who owns the copyright in the software, the source code, and any derivative works.
• Acceptance testing. How the client will test the software and what counts as acceptance.
• Payment terms. Fixed fee, milestone-based, or time-and-materials, plus any retainer.
• Confidentiality and data privacy. How each side protects the other's information.
• Warranties, support, and maintenance. What happens after launch.
• Dispute resolution. Whether disputes go to courts or arbitration.

Who owns the software under Philippine law

Under the Intellectual Property Code, copyright and related rights are among the recognized intellectual property rights (Section 4.1). The Code also treats the licensing of computer software as a form of technology transfer arrangement, except for computer software developed for mass market (Section 4.2).

For commissioned works, the general rule under the Code is that the person who commissions the work owns the patent, unless otherwise provided in the contract (Section 30.1). The same logic — that the contract controls — is the practical takeaway for software: if the client wants to own the code, the agreement must say so expressly. If the developer retains ownership, the agreement should grant the client a clear license to use, modify, and maintain the software.

Two common structures:

1. Client owns the custom code. The developer assigns all rights to the client upon full payment. The developer may retain rights to pre-existing tools, libraries, and frameworks.
2. Developer retains ownership; client gets a license. The client receives a perpetual, non-exclusive license to use the software, sometimes with source code escrow.

Whichever structure is chosen, the agreement should list what is not included — third-party libraries, open-source components, and the developer's pre-existing code — so ownership is not later disputed.

Acceptance testing and payment

Acceptance is the point where the client agrees the software meets the agreed specifications. A good agreement defines:

• Acceptance criteria. Measurable tests tied to the scope of work.
• Acceptance period. How long the client has to test before the software is deemed accepted.
• Deemed acceptance. What happens if the client does not respond within the period.
• Remedies for failed acceptance. The developer's right to cure defects and the client's right to reject.

Payment is usually tied to milestones: a down payment, progress payments, and a final payment upon acceptance. The agreement should state whether payment is due on delivery, on acceptance, or on a fixed schedule, and whether late payment carries interest.

Key risks to watch

• Silent contracts. If the agreement does not address ownership, the parties may end up in a dispute that Philippine courts resolve by looking at the contract, the conduct of the parties, and the applicable provisions of the Intellectual Property Code.
• Open-source contamination. Using open-source components can impose license obligations on the client's software. The agreement should require the developer to disclose all third-party components.
• Data ownership. Client data, user data, and personal information should be expressly owned by the client and handled in line with the Data Privacy Act.
• Source code access. If the developer retains ownership, the client should negotiate source code escrow or a source code license to avoid being locked in.

Frequently asked questions

Who owns the software if the contract is silent? Philippine law does not automatically transfer ownership to the client. The Intellectual Property Code provides that for commissioned works, the person who commissions the work owns the patent unless the contract provides otherwise (Section 30.1). For software, the safest approach is to put ownership in writing.

Is a software development agreement required to be in writing? Philippine law does not require every software development agreement to be in writing, but a written contract is strongly advisable. It is the best evidence of the parties' intent on ownership, scope, and payment, and it reduces the risk of disputes.

Can the developer reuse code built for one client? Only if the agreement allows it. If the client owns the custom code, the developer cannot reuse it without permission. Developers typically retain rights to generic tools, libraries, and frameworks, and the agreement should list these clearly.

Practical takeaways

• Put ownership of the software, source code, and data in writing — do not rely on default rules.
• Define acceptance criteria and the acceptance period so both sides know when payment is due.
• Disclose all third-party and open-source components and state who owns them.
• Address data privacy, confidentiality, and post-launch support in the same agreement.
• Consider dispute resolution clauses, including arbitration, to avoid costly litigation.

Primary sources

The rules discussed above are drawn from the following primary sources, as published in the Official Gazette and the national statute book.

• REPUBLIC ACT NO. 8293 - AN ACT PRESCRIBING THE INTELLECTUAL PROPERTY CODE AND ESTABLISHING THE INTELLECTUAL PROPERTY OFFICE, PROVIDING FOR ITS POWERS AND FUNCTIONS, AND FOR OTHER PURPOSES

• REPUBLIC ACT NO. 11232 - AN ACT PROVIDING FOR THE REVISED CORPORATION CODE OF THE PHILIPPINES

This article is general information and not legal advice. For your specific situation, consult a lawyer or ask ASG Legal AI.