[Direct answer]In the Beijing area, if there is an agreement, the rights belong to the client; if there is no agreement, the rights belong to the contractor. For the copyright of software commissioned for development, the ownership first depends on the contract—if the contract clearly stipulates that the rights belong to the client, then the registration, modification, and commercial use of the software all belong to the client; if there is no agreement or the agreement is unclear, the copyright legally belongs to the contractor who actually completed the development, and the client only has the right to use it as agreed. This is a pitfall that many enterprises have fallen into: they paid the full amount but only got the right to use it. For secondary development, resale, and financing, they have to rely on the developer's goodwill. Writing the ownership clause into the contract is a hundred times cheaper than litigating afterwards.

I. Problem background and typical scenarios

The company spent hundreds of thousands of yuan to commission an outsourcing team to develop a management system. After it went online for two years, the company wanted to upgrade and improve it, but the developers quoted exorbitantly high prices. When another team took over, they discovered that the source code hadn't been delivered and the copyright was registered under the other team's name. Or, the two parties couldn't reach an agreement, and the contract only stated that "Party B is responsible for the development," with no mention of ownership rights at all.

II. Key points of dispute

First, the scope of application of the agreed ownership: the distinction between copyright and the delivery of source code. Second, the statutory ownership rules: the applicable boundaries when there is no agreement, and the ownership belongs to the trustee. Third, the special circumstances of cooperative development: the overlap between joint development and duty-based development. Fourth, the integrity management of source code, documents, and registration certificates.

III. Professional analysis by Henglue Lawyers

Based on Henglue Lawyer's experience in handling software contract and intellectual property ownership disputes, there are four key points to address when dealing with the ownership of commissioned development rights: 1. **Legal Basis**: If the commissioned development contract does not explicitly stipulate ownership, the copyright belongs to the contractor, and the client can only use it within the agreed scope. This statutory rule contradicts many people's intuition that "who pays, owns it," and is a common source of disputes. If ownership is explicitly assigned to the client, ensure that the copyright, modification rights, source code and document delivery, and authorizations for third-party components are all clearly specified. Missing any of these provisions may lead to legal risks. 2. **Borderline Disputes**: Common disputes include: - Whether the contract's stipulation that "the delivered results belong to Party A" includes copyright (which may only be interpreted as ownership of the deliverables). - If the developer uses open-source code and third-party components, ownership may belong to the client, but compliance obligations for licensing remain with the developer. - For collaborative development (where both parties contribute), the work is treated as a joint creation, and rights must be exercised through negotiation. If one party transfers a share, the other party has a preemptive right to acquire it. 3. **Evidence Management**: - Requirements documents, version records, payment receipts, and delivery records during the development process form the basis for ownership and breach of contract claims. - The copyright registration certificate is prima facie evidence of ownership, and whose name it is registered under affects the legal position in litigation. Any discrepancy between ownership stipulations and the registered owner must be corrected promptly. 4. **Transaction Arrangements**: - When software is used as an asset in financing or M&A transactions, due diligence must verify the ownership chain: registered owner, contractual documents, open-source component lists, and ownership closure for employees and outsourced workers. - For companies with ownership gaps, the cost of signing additional confirmation agreements is far lower than the risk of transaction disruption.

IV. Practical suggestions and legal basis

The first step is to clarify the three core terms of copyright ownership, source code and document delivery, and third-party component authorization when signing the contract. The second step is to keep records of requirement changes, version delivery, and acceptance during the development process. The third step is to promptly register the copyright after the project is completed to ensure that the registration subject is consistent with the agreement. The fourth step is to organize the contract and performance evidence in case of ownership disputes, and to correct the registration through negotiation or litigation to confirm the ownership. Main legal basis: Article 19 of the Copyright Law of the People's Republic of China (amended on November 11, 2020 and implemented from June 1, 2021) regarding the ownership of commissioned works; Article 11 of the Computer Software Protection Regulations (amended in 2013) regarding the ownership of commissioned software development; and Article 10 regarding cooperative development. Specific applications shall be subject to the currently effective regulations.

5. Henglu Law Firm's Advice

Three tips for commissioning software development: If there's no agreement, the rights belong to the developer; paying money doesn't mean getting the rights. The contract is only complete when all three items—ownership, source code, and third-party authorizations—are fully specified. The registration subject must be consistent with the agreement, and a thorough due diligence of the transaction is essential. For disputes involving software development contracts, you can seek assistance through the following channels:Intellectual property protection and corporate lawWe can provide a comprehensive solution for the service, which includes reviewing the contract terms if necessary.Contract disputesFor reference, you can check the sections related to technical investment and due diligence in mergers and acquisitionsCompany and commercial disputesFor any questions regarding the registration of software copyrights, please feel free to consult us.Special servicesTeam.

VI. Frequently Asked Questions

Q1: The contract doesn't specify the ownership. Can I request the transfer of ownership after paying the full amount?

This cannot be demanded as a matter of course. According to legal rules, the copyright belongs to the trustee, and the client only enjoys the right of use within the agreed scope. The client can only transfer the copyright and handle the change registration through a supplementary agreement, and the negotiating leverage depends on the contract and the performance of the contract.

Q2: Does the contract stating that "the results belong to Party A" constitute an agreement on copyright ownership?

This is a controversial area. The phrase "the deliverables belong to Party A" may be interpreted as meaning that the ownership of the deliverables, rather than the copyright, belongs to Party A; it would be more prudent to explicitly state that "the software copyright (including all rights) shall belong to Party A from the date of delivery".

Q3: If a developer uses open-source code, do I still own the rights to it?

The ownership can be assigned to you, but the obligations under the open-source license cannot be waived: you must open-source according to the license requirements, retain the copyright notice, or comply with the contagious clauses; when conducting due diligence, you should request a list of open-source components to avoid transferring compliance risks along with the software.

Q4: What should we do if an employee leaves the company and takes away the project code?

The copyright of the works developed in the course of one's duties belongs to the employer; the employee may claim the return of the code, the cessation of its use, and compensation for losses. If trade secrets are involved, the employee may also claim infringement of trade secrets. The intellectual property clauses in the employment agreement are key evidence in such cases.

Q5: What is the use of software copyright registration?

The registration certificate is preliminary evidence of ownership, which is used for rights protection, bidding, high-tech identification, and financing pledges; although copyright arises as soon as the creation is completed and registration is not a prerequisite for its effectiveness, the party that registers first in litigation clearly has an advantageous position.

The above content is based on the compilation of judicial practices in the Beijing area. The facts of individual cases and the jurisdiction of the court may affect the conclusions. Welcome to consult Henglu Law Firm about specific situations.

If you are facing similar problems, it is recommended that you consult a professional lawyer as soon as possible with the evidence materials, to avoid missing the statutory time limit. →Intellectual property protection legal services·Beijing Henglue Law Firm

Disclaimer: This article is compiled based on the current effective laws and regulations and public adjudication rules, and is for general reference only. It does not constitute a formal legal opinion on specific cases. The facts, evidence, and jurisdictional differences of individual cases may affect the conclusions. If you encounter disputes, please consult a practicing lawyer in time.