Software Development Contract in Indonesia: 8 Clauses That Decide Who Owns the Code

A software development contract in Indonesia stands or falls on six points: who owns the code, what the vendor may do with your data, where scope ends, when the work counts as finished, how long the warranty runs, and what you keep if it ends early.
Here is what surprises most buyers: Indonesian law does not default in favour of whoever pays. Under Article 36 of Law No. 28 of 2014 on Copyright, the copyright holder of a commissioned work is the party that created it — not the one that ordered it, unless agreed otherwise. Say nothing about ownership and the app you paid for in full stays the vendor's.
Not a trap — a starting position that one sentence changes.
The eight clauses a software development contract in Indonesia needs
The eight clauses behind most IT project disputes, and what happens when one is blank.
| Clause | What it must say | If left blank |
|---|---|---|
| Scope of work | The agreed features and modules, plus what is out of scope | Every new request becomes an argument |
| Copyright in deliverables | Copyright passes to the client on final payment, in writing | The creator keeps it, under Article 36 |
| Source code and access | Handover of code, repositories and credentials at acceptance | The system runs, but nobody else can continue it |
| Customer data | The vendor processes data only on your instruction; sub-processors need consent | Liability stays with you, without knowing where the data sits |
| Acceptance criteria | A test list both sides signed off, not "running normally" | The project never formally ends and final payment hangs |
| Payment milestones | Each milestone tied to an inspectable output, not a date | Payment runs ahead of the work |
| Warranty and support | Bug warranty period, response times, and what it excludes | Bug fixes become billable extras at once |
| Termination | Duty to hand over documents, code and a data export in open format | Changing vendor means rebuilding from zero |
Priority order, not a complete list. On a small project these fit in three to five pages.
Paid in full is not the same as owned
Copyright moves through a specific route here. Article 16(2) of the Copyright Law lists a written agreement among the ways the right passes, so the sentence has to be on paper. Payment alone does not move it.
It need not be long. One line saying copyright in the deliverables passes to the client on final payment, and that code and documentation are handed over at acceptance, closes most of the exposure.
Some vendors refuse, and sometimes that is reasonable. Where the product is a licence or a platform shared across many clients, assigning full copyright is impossible. The usual middle ground: a perpetual, irrevocable licence plus source code held in escrow.
One thing must not stay ambiguous: who continues the work when people change. We write that in from the start on software development engagements, because a system that lives five years almost always changes hands partway through.
Customer data: the liability stays with you
Law No. 27 of 2022, the Personal Data Protection Law, closed its two-year adjustment window on 17 October 2024. Your company is the data controller, the vendor the processor. Article 51 requires the processor to act on the controller's instruction; Article 37 puts the duty to supervise on the controller.
If customer records leak from a contractor's laptop, the party facing the customers and the regulator is you. Four things belong in that clause:
- Purpose — which data the vendor may touch, for what, and for how long.
- A ban on copying production data to personal devices; work happens on masked test data.
- Deletion of every copy and revocation of all access within a stated number of days after handover.
- Notification within hours of an incident, not after somebody asks.
For systems holding customer data at scale, corporate clients want evidence, not assurances. At that point a security audit before signing costs far less than negotiating after an incident.
What "finished" means
This is the most common reason a final milestone sits unpaid for months. The contract says the work is done once the system "runs normally", and the two sides read that differently.
The fix is dull and effective: attach an acceptance test list. Ten to twenty scenarios both sides tick off — a user logs in, stock drops when a transaction saves, the report matches the ledger. Dates may slip; the list does not.
A distributor in Sidoarjo once held back 30 percent of a project for four months because no such list existed. The vendor considered the work done, the client did not, and no document settled it.
Stamp duty and signatures: the small things people get wrong
Agreements carry Rp10,000 stamp duty under Law No. 10 of 2020, in force since 1 January 2021. The Rp5,000,000 threshold quoted all over the internet applies to documents acknowledging receipt of money, not to agreements in general.
Electronically signed contracts use e-meterai, covered separately in our guide to buying and using e-meterai. Stamp duty does not make an agreement valid: validity comes from the four conditions in Article 1320 of the Civil Code — consent, capacity, a defined object, a lawful cause.
Tight terms have a price
In our experience a twenty-page template causes more trouble than four pages written for the project. But strict terms do raise the price: full copyright assignment, a twelve-month warranty and late-delivery penalties usually add 10 to 20 percent. That is fair — the risk moved to the vendor. A cheap quote carrying none of these clauses is not. Before judging the number, check the vendor's portfolio first.
We signed without an ownership clause. Can it be fixed?+
The vendor refuses to hand over source code. Is that normal?+
How long should the bug warranty run?+
If a vendor draft is in front of you, start with ownership of the deliverables and the definition of done. Those cost the most to fix later. We are open to a short conversation through our IT consulting page.
IT consultants helping Indonesian businesses choose and manage cloud infrastructure, develop software, and keep IT operations running smoothly. Based in Sidoarjo, serving clients across East Java and Indonesia.
Related Articles

NIB Registration in Indonesia for IT Service Companies: Your KBLI Code Changed in June 2026
NIB registration in Indonesia for IT firms: KBLI codes were renumbered on 15 June 2026, how OSS calculates your risk tier, and every step to the NIB.

Cheap vs Business Web Hosting in Indonesia: Compare the Renewal Price, Not the Promo
Cheap vs business web hosting in Indonesia: a Rp12,900 promo renews at Rp54,900. Real renewal prices, what each tier actually gives you, and when to move up.

Office Wi-Fi Slow at Peak Hours: What Runs Out, and Four Tests You Can Run Yourself
Office wifi slow at peak hours is rarely the internet package. The causes that are real, four free tests, and a repair order that starts at zero rupiah.