Service Contracts · Contract for Work vs. Mandate
Service Agreement (Contract for Work vs. Mandate)
What is a service agreement?
- Contract for work means delivering a result; mandate means handling affairs
- Scope, acceptance, and IP ownership drive most disputes
- A contract is judged by what it does, not what it is called
Deciding between a contract for work and a mandate is not about choosing a legal term; it is about settling when you are entitled to invoice. Written as a contract for work, the right to payment arises only once the deliverable is complete and passes acceptance. Written as a mandate, you can claim your fee simply by having handled the affairs diligently for the agreed period. On the same 8-month project, the former pays out once, 8 months later, while the latter bills every month. The type is determined by the payment clause and how the work is actually performed, not by the title of the agreement, so a contract headed 'consignment agreement' whose body says 'payment after acceptance approval' will be read as a contract for work.
Real-world contracts mix both types, so rather than forcing one, it is better to write the clauses separately. Group anything that leaves a tangible output, such as textbooks, diagnostic tools, and the final report, under the contract-for-work type and tie it to acceptance. Settle parts where the input itself is the performance, such as running training sessions, regular advisory, and on-site coaching, monthly under the mandate type. Splitting payment as 30 : 40 : 30 (start : interim : final) keeps cash flowing even if completion slips. The key to acceptance is fixing a deadline, so a single deemed-acceptance line, 'if no written comments are received within 10 business days of delivery, the work is deemed accepted,' determines when the final payment can be collected. State the number of revision rounds (for example, 2) and their scope, and move anything beyond that to a separate quote.
Termination and rights clauses also differ by type. A mandate can, in principle, be terminated by either party at any time, so it is hard to stop a client that gives notice of cancellation after just 3 months. Under a contract for work, the client may terminate before completion but must compensate for the loss. That is why the agreement itself should spell out whether, on early termination, work performed is measured by person-days invested or by completed milestones. The IP clause should also carry a reservation that the methodologies and templates we already owned are excluded from any transfer of ownership.
The most common failure point is a contract that says only 'payment at the end of the month following acceptance.' With no deadline, a change of contact person or a reorganization sends the deliverable into a drawer and the final payment stays tied up for six months, while we have already paid instructor fees and labor costs up front. The second is a misunderstanding about the label. Even if the cover says 'service agreement,' a consultant who is stationed at the client’s office, has set hours, and takes work instructions directly may be treated as a dispatched worker or an employee. Using a standard template as is is the riskiest move, because the deliverable definition and the acceptance and revision clauses differ by industry and are left blank.
Seungtae ParkAX practitioner-instructor who builds and teaches AI business development and marketing automation firsthand
Sangmi LeeInstructor specializing in customer service, leadership, and communicationThe Korean Civil Act separately defines a contract for work (Article 664 et seq.), where the goal is a completed result, and a mandate (Article 680 et seq.), where one party is entrusted with handling certain affairs. Many service agreements in practice blend both types, so their character is judged by the wording of the agreement and how it is actually performed.
Consider a hypothetical case. Company A, a training and consulting firm with 42 employees and KRW 6.8 billion (≈ US$5,087,500) in annual revenue, is about to sign an 8-month leadership program with a large manufacturer for KRW 240 million (≈ US$179,600). The work mixes materials development with on-site coaching twice a month, yet the draft contract had just one line: 'payment due upon acceptance after completion of services.' Having KRW 80 million (≈ US$59,900) of its final payment tied up for 5 months on its previous project, this time it rewrote the contract from scratch.
- When the business head listed every deliverable, it came to 12 items, including textbooks and workbooks, plus 32 coaching sessions. "The textbooks are deliverables; the coaching is selling our time," he said, and split the clauses between deliverables and time-based work.
- The payment terms were restructured into 30% at kickoff (KRW 72 million (≈ US$53,900)), 40% at materials review (KRW 96 million (≈ US$71,800)), and 30% at course completion (KRW 72 million (≈ US$53,900)), with coaching fees billed separately at the end of each month.
- When the client’s procurement manager balked at adding an acceptance deadline, the sales director offered a trade: "If you give us your comments within 10 business days, we’ll make up to 2 rounds of revisions free of charge." That is how the 10-business-day deemed-acceptance clause got in.
- Copyright in the delivered materials goes to the client, while the leadership assessment tool and slide templates Company A has used for 8 years were reserved as its own assets. The contract also states that, on early termination, progress payments are settled based on completed milestones.
- In practice, the client's training manager was replaced and the review of the course materials stalled. But thanks to a deemed-acceptance clause, the company billed KRW 96 million (≈ US$71,800) on day 11, and the time to collect the final payment fell from 5 months on the previous project to 38 days. Three out-of-scope revisions were added by separate contract at a KRW 11 million (≈ US$8,230) quote.