Yes. Under Japanese law, copyright in work built by an outside contractor, freelancer, or development vendor belongs to the creator by default, not the company that paid for it. The automatic employer-ownership rule in the Copyright Act (著作権法) covers employees only. A company that commissions custom software, design, or written content without an explicit assignment clause typically ends up holding an implied license, not ownership.
What Is the Default Rule for Who Owns IP Created Under a Japan Contract?#
The default splits sharply along one line: who is the creator's employer. For an employee acting within the scope of their job, the Copyright Act's work-made-in-the-course-of-duties doctrine (職務著作) vests copyright in the employer automatically, with no assignment paperwork required. For anyone who is not an employee, including an independent contractor engaged under a 業務委託 (services commission) arrangement, the statute puts ownership with the individual who actually created the work.
This distinction surprises founders used to jurisdictions where "work for hire" extends more broadly to commissioned work. In Japan it does not. A company's own in-house engineer writing code is covered by 職務著作. A contracted development studio, a freelance designer, or an outside agency writing marketing copy is not an employee relationship at all under the Copyright Act, however exclusive or long-running the arrangement feels in practice. For that second case, the contract terms move ownership; a paid invoice on its own does nothing to copyright.
Why Doesn't Paying for Work Automatically Make the Company the Owner?#
Payment creates a services relationship. The Copyright Act ties automatic ownership to employment status alone, so a 業務委託 contractor retains copyright in what they build unless the contract assigns it to the commissioning company in writing.
This is the operational failure mode that shows up repeatedly in contract review: a Japan entity pays a vendor to build a custom application, assumes ownership because an invoice was paid in full, and discovers only when the relationship ends, or when the vendor reuses the codebase for a competitor, that the company holds an implied license to use the deliverable instead of title to it. An implied license can be narrower than the company assumes: it may not cover modification, sublicensing, or resale, and it leaves the former vendor with continuing leverage over a product the company considers its own. The fix belongs in the contract before the relationship starts. For contracts that also touch sensitive technical information during development, see the companion confidentiality clause and NDA guide; IP assignment and confidentiality obligations commonly sit as adjacent clauses of the same 業務委託 agreement.
Does the Same Gap Exist for Patents, Not Just Copyright?#
Yes, on a parallel but separate track. Employee inventions (職務発明) are governed by the Patent Act (特許法), which since a 2015 amendment allows an employer to obtain patent rights directly from the moment of invention if the employment regulations or an agreement provide for it, in exchange for "reasonable benefit" (相当の利益) owed to the inventor. That mechanism is built for the employment relationship; it does not automatically extend to contractors.
A contractor engaged to design hardware, develop a patentable process, or build technology with inventive elements falls into the same gap as the copyright case. Absent a contract term addressing it, the contractor is positioned as the inventor of record for patent purposes, leaving the commissioning company with no filing rights of its own. Where development work could plausibly generate patentable output, the contract should state who owns resulting inventions and who controls filing decisions, mirroring the assignment logic used for copyright. Aplash's contract review flags this gap during drafting; the filing and prosecution itself, and any resulting dispute, is referred to a registered patent attorney (弁理士) or attorney (弁護士), since that is specialist practice outside contract drafting.
What Does an Effective IP Assignment Clause Need to Say?#
A clause that only recites "all intellectual property shall belong to Client" leaves three gaps tied to how Japanese IP law works.
First, Japan's Copyright Act grants the individual creator non-waivable moral rights (著作者人格権) covering attribution and integrity of the work, and those rights cannot be assigned or waived even when the economic copyright itself is transferred in full. The market workaround, used broadly in Japan-governed development and services contracts, is a clause in which the creator agrees not to exercise moral rights (著作者人格権不行使) against the commissioning party. This does not eliminate the rights, since Japanese law does not permit that, but it neutralizes the practical risk that the original creator later objects to modifications or withholds attribution consent.
Second, the clause needs a present assignment tied to defined deliverables as they are created. A vague future-tense recital covering undefined "all IP" the contractor might produce leaves disputes over what was in scope of the transfer; tying assignment to specific deliverable categories, source code, specifications, designs, written content, as each is completed, closes that gap.
Third, most development engagements involve some pre-existing material the contractor brings in: internal libraries, prior frameworks, reusable components built for other clients. That background IP should be licensed to the commissioning company for use within the deliverable, since the contractor legitimately needs to keep using its own prior tools on other engagements. Conflating background IP with foreground IP in a single blanket assignment clause creates ownership disputes that drafting can avoid. A related drafting discipline, restricting a contractor's ability to assign the receivables due under the contract, is covered in the assignment of receivables restriction guide.
(a) Assign both copyright (著作権) and pair it with a moral-rights non-exercise clause (著作者人格権不行使), since moral rights themselves cannot be waived or transferred under the Copyright Act. (b) Draft a present assignment linked to specific, named deliverables as completed instead of a single forward-looking "all IP" clause. (c) License any pre-existing background IP the contractor brings into the engagement; reserve assignment for the deliverables themselves.
When Should the IP Assignment Take Effect, Signature or Payment?#
Assignment should take effect on payment or delivery of the relevant milestone. A clause that transfers ownership automatically at signature gives the company legal title to work before the contractor has been paid for it, which removes the contractor's practical leverage in a payment dispute and can read, to a reviewing court, as inconsistent with the parties' bargain.
Tying the transfer to payment keeps incentives aligned on both sides: the contractor retains ownership of each deliverable until paid, and the company acquires title only to work it has settled for. This timing point matters most in milestone-based development contracts where deliverables are released in stages, since an all-at-signature assignment clause can end up transferring ownership of work that has not even been built yet. Where a contract also caps liability or sets liquidated damages for late or defective delivery, that structure interacts directly with assignment timing; see the liability cap and liquidated damages guide, since both clauses should be drafted as one coherent set.
Getting this sequencing wrong is one of the more common gaps found during contract review of Japan-governed development and services agreements, alongside the broader checklist covered in the Japan legal consulting hub. Aplash's contract review and compliance service checks IP assignment clauses as a standard part of reviewing a Japan-governed 業務委託 agreement before signature, flagging missing assignment language, undefined deliverable scope, and incorrect effective-date triggers.
Frequently Asked Questions#
If we paid a Japanese freelancer to build our website, do we own the code?
Not automatically. Under the Copyright Act, an independent contractor retains copyright in what they create unless the contract contains an explicit assignment clause. Without one, the paying company holds an implied license to use the deliverable in most cases, which is narrower than outright ownership and can leave the original developer with ongoing rights over the code.
Does our standard employment contract already cover IP created by contractors we also use?
No. The automatic employer-ownership rule for work created in the course of duties (職務著作) under the Copyright Act applies only to employees. A contractor or outside vendor is a separate legal relationship, and IP ownership for that relationship has to be addressed in the services or development contract itself, not inferred from an unrelated employment agreement.
Can a Japanese creator give up their moral rights over a work entirely?
No, moral rights (著作者人格権) under the Copyright Act are non-waivable and cannot be assigned, regardless of what the contract says. The standard market approach is a moral-rights non-exercise clause (著作者人格権不行使), in which the creator agrees not to exercise those rights against the commissioning party. This achieves the practical result companies want without purporting to transfer rights the law does not allow to be transferred.
This article is informational only and does not constitute legal, tax, or regulatory advice. Consult a qualified advisor before acting on the content. Last updated: October 2026.