[Direct answer]In the Beijing area, the ownership of the software commissioned for development first depends on the contractual agreement. If there is no agreement, the ownership shall belong to the trustee according to law. According to Article 11 of the "Computer Software Protection Regulations" (amended on January 30, 2013), the copyright of the software developed by others on behalf of others shall be agreed upon by the client and the trustee in a written contract; if there is no written contract or the contract does not make a clear agreement, the copyright shall belong to the trustee. According to Article 19 of the "Copyright Law of the People's Republic of China" (effective on June 1, 2021), the copyright of the works created on behalf of others shall be agreed upon by the contract. If there is no clear agreement in the contract or no contract is concluded, the copyright shall belong to the trustee, but the client may use it free of charge within the scope of use agreed upon in the contract. Therefore, if the client wants to obtain the software copyright, it is necessary to clearly stipulate it in the contract, and the client may refer to the relevant provisions for reference.Business and contract disputes in enterprisesColumn.

1. Problem background and typical scenarios

Such disputes often occur in several situations: First, when an enterprise entrusts an outsourcing team to develop management software or mini programs, the contract only stipulates the development fee and delivery time, but not the ownership of the rights; Second, when an employee leaves the company and takes away the source code of the company's projects, the company claims rights but finds that no agreement has been made. For related labor relations issues, please refer to the relevant provisions.Work-related injuriesFirst, there are disputes over the ownership of the software and the subsequent profits from its commercialization after the development is completed. Second, there are disputes over the ownership of the software and the subsequent profits from its commercialization after the development is completed. Third, there are disputes over the ownership of the software and the subsequent profits from its commercialization after the development is completed. Fourth, there are disputes over the ownership of the software and the subsequent profits from its commercialization after the development is completed. Fifth, there are disputes over the ownership of the software and the subsequent profits from its commercialization after the development is completed. Beijing is home to a large number of technology companies, and such disputes account for a significant proportion of disputes over commissioned development contracts, which can serve as a reference for the legal needs of enterprises involved in such disputesIntellectual propertyColumn.

II. Key points of contention

Focus One: The legal effect of the contract. Where the ownership is explicitly stipulated in writing, it shall be handled in accordance with the agreement, which is the primary rule. Focus Two: The statutory ownership when there is no agreement. In this case, the copyright of the commissioned software belongs to the contractor, and the client may only use it within the scope stipulated in the contract or as necessary. This may fall short of the expectations of most clients. Focus Three: The distinction between source code and copyright. Even if the client does not enjoy copyright, they can still claim the delivery of source code and documents according to the contract. Focus Four: The distinction between works created in the course of employment and commissioned works. Software developed by employees during their employment may constitute works created in the course of employment, and the ownership of such works is subject to separate rules. Focus Five: Where the copyright of jointly developed software cannot be separated for use, the copyright shall be jointly enjoyed by all parties and exercised through consultation. Focus Six: Determining the ownership of subsequent upgraded versions. Focus Seven: The burden of proof. The party asserting rights shall prove the facts of development, the contractual relationship, and the content of the agreement. Specifically, the provisions of currently effective laws and regulations and judicial rulings shall prevail.

III. Professional analysis by Henglue Law Firm

Based on the practical experience of lawyers from our firm in handling similar disputes, the outcome of ownership disputes is often determined at the contract stage. Common risks include: the contract only stipulates "delivery for use after completion of development", without specifying the ownership of copyrights, resulting in the developer later claiming rights and demanding additional licensing fees; the client only receives the deployment package after making payment, fails to obtain the source code, and is subsequently restricted by the developer in business operations; vague provisions such as "ownership belongs to Party A", without distinguishing between copyrights, patent application rights, and the obligation to deliver the source code, leading to conflicting interpretations during performance; oral commissions without written contracts, making it difficult to prove the scope of development and delivery standards in the event of disputes. Lawyers from our firm recommend: The contract for commissioned development should specify in detail the ownership of copyrights, the obligation to deliver the source code and documents, the ownership of subsequent upgraded versions, confidentiality and non-competition clauses, and liability for breach of contract. For systems involving core business operations, it is also advisable to stipulate arrangements for copyright registration and code hosting to ensure the traceability of ownership. For disputes that have already occurred, first review the contract terms, payment records, communication records, and materials related to the development process, then evaluate the paths of claims. Key points of relevant texts can be referred to for reference.Special services and other casesColumn.

IV. Practical suggestions and legal basis

Action suggestions: 1. Before signing the contract, clarify the ownership clauses and specify whether the copyright belongs to the client or the contractor, and whether it includes the obligation to register the transfer; 2. Include a fixed delivery list in the contract, including source code, design documents, interface specifications, and deployment materials; 3. Agree on the ownership of subsequent maintenance and upgraded versions; 4. Retain requirement confirmation forms, phase acceptance records, and payment receipts during the development process; 5. Promptly register the software copyright after completing important software projects to strengthen ownership proof; 6. In case of disputes, first review the contract terms. If no agreement exists, claim rights within the scope of use according to the Copyright Law. Legal basis: - Article 11 of the *Regulations on the Protection of Computer Software* (amended on January 30, 2013) stipulates that the ownership of commissioned software shall be determined by the written contract, and if no agreement exists, it shall belong to the contractor; - Article 19 of the *Copyright Law of the People's Republic of China* (effective on June 1, 2021) stipulates that the ownership of commissioned works shall be determined by agreement, and if no agreement exists, it shall belong to the contractor; - Article 509 of the *Civil Code of the People's Republic of China* (effective on January 1, 2021) stipulates that parties shall fully perform their obligations according to the agreement, and Article 577 stipulates the liability for breach of contract. For software copyright registration and protection, refer to the following documents:Intellectual propertyColumn.

5. Henglue Law Firm's Reminder

Risk Warning: Firstly, paying money doesn't necessarily mean obtaining copyright. When there's no agreement, the law presumes that the copyright belongs to the developer, which is the most common pitfall for clients. Secondly, a mere "delivery for use" clause cannot infer a transfer of copyright. The ownership must be explicitly stipulated in the agreement. Thirdly, the obligation to deliver the source code must also be explicitly stated in writing. Otherwise, the developer may only deliver the deployment package. Fourthly, different rules apply to employee-developed and collaboratively developed projects. Confusing them may easily lead to disputes. Fifthly, after a dispute arises, avoid using code of unknown origin without authorization to prevent overlapping infringement risks. It is recommended to consult a professional lawyer during the contract negotiation and acceptance stages to ensure legal compliance.Beijing Henglue Law FirmThe same type of column on the official website.

VI. Frequently Asked Questions

Q1: If the contract does not specify ownership, who owns the software developed by the contractor?

According to Article 11 of the Regulations on the Protection of Computer Software and Article 19 of the Copyright Law, the ownership of the copyright of the software commissioned for development shall be agreed upon in a written contract. Where there is no written contract or no clear agreement, the copyright shall belong to the party commissioned to develop the software. Although the client does not obtain the copyright, he/she may use the software normally within the scope of the purpose of the commissioned development. If the business relies on the software for a long time, it is recommended to sign a supplementary ownership or use license agreement with the developer as soon as possible to avoid being restricted in the future.

Q2: What if the client can't get the source code?

First, check whether the contract explicitly stipulates the delivery of the source code. If there is such a stipulation, the party may, in accordance with Article 577 of the Civil Code, demand continued performance, take remedial measures, or claim compensation for losses; if there is no such stipulation, it is difficult to enforce the delivery in practice, and the parties can only negotiate to supplement the purchase. It is recommended that the client list the source code, design documents, and deployment materials as deliverables in the contract and stipulate acceptance standards. If the dispute persists, the party may also claim to terminate the contract and request a refund and compensation in accordance with the contract.

Q3: How much does it cost to litigate a software development ownership dispute in court?

The fees include the case acceptance fee and attorney's fees. Such disputes are mostly contract disputes. The acceptance fee is charged according to the amount of the litigation request, and the claims for the return of development fees and compensation will increase proportionally to the subject matter; the attorney's fees are determined based on the organization of evidence and whether technical comparison is involved, with no uniform standard. If it is necessary to conduct technical appraisals of the completion time and identity of the software, additional appraisal fees will be incurred. It is recommended to first sort out the evidence and evaluate the basis of the claims before deciding on the scale of investment.

Q4: How long will it take to resolve the ownership dispute over the commissioned development project?

For disputes resolved through negotiation or mediation, a supplementary agreement can be signed and finalized within a few weeks at the earliest. For litigation under the ordinary first-instance procedure, it generally takes no more than six months, but may be extended by several months if technical appraisal is involved. The second-instance procedure typically takes about three months. The focus of the dispute lies in the interpretation of ownership clauses and the determination of delivery obligations. Cases with clear evidence progress more quickly. The key is to fix the contract text, payment and communication records as soon as possible to avoid delays leading to the loss of evidence or the developer making other arrangements.

Q5: How should a contract for commissioning software development be signed?

There are five key points: First, clarify the ownership of copyright and whether it includes the obligation to register a transfer; Second, list the deliverables, including source code, documents, and deployment materials, and agree on the acceptance criteria; Third, agree on the ownership and fees of subsequent upgrades and new modules; Fourth, set confidentiality clauses and a payment mechanism based on milestones; Fifth, clarify the liability for breach of contract and the dispute resolution method. Check each item during the signing process, and if necessary, have a lawyer review it. You can refer to the following for more information:Business and contract disputes in enterprisesColumn.

The above answer is based on the judicial practice in Beijing. The adjudication standards in other provinces and cities may vary. For specific cases, please refer to the local rules and evidence situations.

If you are currently facing similar problems, it is recommended that you consult a professional lawyer as soon as possible with the relevant evidence materials, to avoid missing the statutory time limit. →Business and commercial legal services·Beijing Henglu Law Firm

Disclaimer: This article is compiled based on the current effective laws and regulations and publicly available 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.