Legal and source review date: 4 October 2026. General information only. Current official texts, the executed contract and matter-specific facts must be checked before reliance. No outcome, timing, cost, recovery or enforceability is assured.
A foreign company may receive a Turkish-law agreement in which the risk section looks familiar: a liability cap expressed as a multiple of fees, an indemnity for third-party claims, service credits for delay and a fixed sum described as liquidated damages. Those labels are useful signposts, but they do not settle the Turkish-law analysis. The first task is to identify what each clause actually requires, when it operates and which mandatory limits may apply.
The review should separate three mechanisms. A limitation clause changes the extent of responsibility that would otherwise follow from breach. An indemnity allocates defined losses or claim-handling duties. A contractual penalty attaches an agreed consequence to non-performance, defective performance or delay. They can appear in the same provision, yet different statutory rules may govern their validity, operation and relationship with performance or proven loss.
Cross-border drafting adds another layer. Choosing Turkish law does not by itself choose a court. A foreign court clause, an arbitration agreement, access to interim measures and any pre-action mediation requirement must be considered separately. A clause that appears commercially balanced may still fail to answer basic questions about notice, evidence, affiliates, subcontractors, multiple claims and the procedure for handling a third-party demand.
This guide gives a structured way to read and negotiate those provisions. It does not decide whether a particular cap, indemnity or agreed sum is valid, and it does not predict a court or arbitral outcome. That conclusion requires the executed contract, the parties' status, the transaction, the alleged conduct and a current review on the relevant date. No case law is used here; the analysis is confined to the cited official statutory texts and official guidance.
1. Start with the clause's function, not its English label
Begin by marking the event that activates the clause. Is the trigger any breach, a specified delay, failure to meet an acceptance criterion, a third-party claim, an allegation, a final judgment, payment by the protected party or written demand? A clause that responds to a third-party allegation performs a different function from one that sets the consequence of late delivery. Turkish Code of Obligations article 19 makes the parties' real and common intention central to characterization.
Next identify the legal and commercial consequence. The provision may exclude a head of loss, set a monetary ceiling, require reimbursement, shift the cost of defending a claim, create a credit against future invoices, permit termination or require payment of an agreed penalty. Several consequences can coexist. They should be drafted as separate steps so that failure of one mechanism does not obscure the operation of the others.
The party protected by the clause also matters. The contracting company may want protection for its parent, subsidiaries, directors, employees, customers or end users. Those persons may not all be parties to the agreement. The clause should explain who may claim, who must perform, whether rights are held for another person and how the provision interacts with assignment, subcontracting and group reorganisations. This is drafting analysis, not an assumption that every named beneficiary automatically acquires an enforceable right.
Prepare a one-page clause map before negotiating prose. For each risk, record the relevant obligation, trigger, claimant, recoverable loss, exclusions, monetary ceiling, time period, notice route, evidence and dispute forum. The map exposes internal contradictions. It may show, for example, that the indemnity is described as uncapped in one schedule but included in the aggregate cap by the main terms.
2. Establish the liability baseline before negotiating the cap
A cap cannot be evaluated without first asking what liability would exist in its absence. Under article 112 of the Turkish Code of Obligations, when an obligation is not performed at all or is not performed properly, the debtor must compensate the resulting loss unless the debtor proves that no fault is attributable. The rule directs attention to the obligation, the breach, resulting loss and fault allocation rather than to a clause heading.
Article 114 states that the debtor is generally responsible for every degree of fault and that the scope is determined in light of the transaction's particular characteristics. The same article applies tort-liability provisions by analogy to contractual breach. The contract team should therefore identify the proposed standard of performance and the factual records that will show whether performance conformed to it.
Not every commercial disappointment is the same legal loss. Direct remediation cost, replacement cost, loss caused by delay, lost revenue, third-party liability and reputational harm present different questions of proof, causation and contractual allocation. Definitions such as “Loss” and “Indirect Loss” should not be imported uncritically from another governing law. They should identify the intended categories and how they relate to the underlying Turkish-law rules.
The agreement should also state how overlapping claims are handled. A single event may be pleaded as breach of warranty, breach of a service obligation, indemnity claim and penalty trigger. If every theory is counted separately, the cap may multiply unintentionally. If all theories are aggregated too broadly, distinct incidents may become one claim. A clear aggregation rule reduces that uncertainty without deciding the legal characterization in advance.
3. Review the architecture of a liability cap
A monetary ceiling should identify both its base and its period. “Fees paid” might refer to all fees under the agreement, fees paid in the previous twelve months, fees for the affected service or only amounts actually received. A newly signed contract may produce a near-zero cap if the formula looks backward. A long project may produce a very different result depending on whether the cap renews annually or applies once across the full term.
Decide whether the ceiling applies per claim, per event, per contract year or in aggregate. Define how related events are grouped and whether claims against affiliates or subcontractors share the same pool. If the agreement contains several statements that liability is “subject to the cap,” trace each cross-reference. A cap buried in one schedule may not clearly govern an indemnity, data-processing addendum or statement of work.
Exclusions and carve-outs need the same precision. Contracts often list fraud, wilful misconduct, gross fault, confidentiality, intellectual property, data protection, bodily injury or payment obligations. A carve-out may mean uncapped liability, a separate higher cap or simply that a particular exclusion does not apply. Those outcomes should not be left to inference. Mandatory law must still be considered even when the commercial wording is clear.
A cap must be tested against the mechanism it limits. Limiting damages for a service failure is not identical to limiting a reimbursement obligation after a third-party claim or limiting responsibility for an auxiliary person's conduct. The review should distinguish the debtor's own conduct from employees, subcontractors and other persons used in performance because article 116 contains a separate statutory framework.
Duration also matters. Termination does not automatically answer whether the cap, indemnities, confidentiality duties, claim-notice procedure or accrued penalties survive. The agreement should distinguish claims arising before termination from claims notified later and should align survival language across the main agreement and schedules. No generic survival period can replace analysis of the obligation and the applicable limitation rules.
4. Apply the mandatory limits and keep auxiliary liability separate
Article 115 of the Turkish Code of Obligations provides that an advance agreement under which the debtor will not be responsible for gross fault is absolutely void. This is a mandatory boundary. It should be addressed directly in the drafting rather than through an assumption that a negotiated agreement between sophisticated companies validates every exclusion.
Article 115 expressly addresses an advance agreement under which the debtor will not be responsible for gross fault. The statutory text does not set a numerical threshold for a liability cap. Whether a particular ceiling produces the prohibited exclusion requires the complete clause, the transaction and current full-text judicial research; no general outcome is stated here.
Article 115 separately makes void an advance agreement under which the debtor would bear no responsibility for any obligation arising from a contract of employment (hizmet sözleşmesi) with the creditor. It also makes void an advance exclusion of responsibility for slight fault where a service, profession or art requiring expertise may be carried on only with statutory or official permission. The actual legal relationship and licensing rule must be identified before either paragraph is applied.
Article 116 addresses persons used to perform an obligation or exercise a right arising from it. As a baseline, the debtor must compensate damage caused by those auxiliaries while carrying out the work. The text permits that responsibility to be removed wholly or partly by advance agreement. It then makes void an agreement excluding responsibility for auxiliaries where a service, profession or art requiring expertise may be carried on only with statutory or official permission. This structure remains separate from the debtor's own gross fault under article 115.
For a supply chain, list the persons likely to perform: employees, group companies, logistics providers, cloud vendors, consultants and subcontractors. Then state whether their acts count toward the same cap, whether the prime contractor remains the single point of responsibility and whether separate contractual recourse exists. A broad reference to “agents” may fail to reflect the actual delivery model.
The drafting record should show that the parties considered the cap and its exceptions in the real transaction. That evidence does not override mandatory law, but it helps explain the commercial allocation and avoids reliance on a formulaic recital. Keep the redlines, issue list, approvals and final agreed risk matrix with the executed contract.
5. Draft an indemnity as an operative mechanism
“Indemnity” does not operate as a self-executing common-law package simply because the English word appears in a Turkish-law contract. Article 19 requires attention to the parties' real and common intention. The clause should therefore state the obligation in operational terms: what loss is covered, who must pay, what event triggers payment and whether the provision supplements or replaces an ordinary breach claim.
Separate first-party and third-party situations. A first-party clause may address a loss suffered directly by the protected party after breach. A third-party clause may address a claim by a customer, regulator, rights holder or injured person. The latter needs a claim-handling process. It should not force payment or settlement before the indemnifying party receives enough information to evaluate the allegation.
Define recoverable amounts carefully. Reasonable defense costs, settlement sums, judgments, remediation costs, taxes, interest and internal expenses may be treated differently. Terms such as “all losses whatsoever” create breadth without explaining causation or proof. The contract should state whether costs must be reasonably incurred, whether mitigation is expected and how disputed amounts are handled.
A third-party process usually needs prompt notice, access to relevant documents, cooperation, control or participation in the defense and consent rules for settlement. The agreement should address what happens if notice is late: automatic loss of the claim, reduction only to the extent of prejudice or another stated consequence. A practical timetable should still leave room for urgent protective steps and statutory deadlines.
Control of the defense should come with safeguards. The party directing the defense may need to keep the protected party informed and may be prevented from accepting an admission, non-monetary obligation or reputational consequence without consent. The protected party may need separate counsel where interests diverge. These are negotiated protections, not universal statutory terms.
Finally, link the indemnity to the cap, exclusions and insurance provisions expressly. State whether it is inside the general cap, subject to a separate cap or carved out, and whether multiple indemnities share an aggregate. Align the survival clause and dispute forum. An indemnity that cannot be reconciled with the rest of the contract invites a characterization dispute at the moment it is needed most.
6. Distinguish contractual penalties from other agreed payment mechanisms
Articles 179, 180 and 182 of the Turkish Code of Obligations provide the central statutory framework used in this guide. Article 179 distinguishes a penalty for non-performance or improper performance from a penalty linked to performance at an agreed time or place. The first category generally presents a choice between performance and the penalty unless the contract indicates otherwise. The time-or-place category may permit both performance and the penalty under the statutory conditions.
Reservation can be decisive for a delay or place-of-performance penalty. Article 179 states that the creditor may seek the principal performance together with the penalty unless the creditor clearly waived the right or accepted performance without reservation. The contract team should design the acceptance certificate, delivery note and payment workflow so that commercial acceptance does not inadvertently contradict the intended reservation.
The third paragraph of article 179 preserves the debtor's ability to prove that payment of the agreed penalty was intended to permit termination or rescission. That possibility reinforces the need to distinguish a penalty securing performance from a genuine exit payment or termination option. The agreement's language, structure and commercial function should point in the same direction.
Article 180 provides that the agreed penalty may be claimed even if the creditor suffered no loss. If actual loss exceeds the penalty, the excess cannot be claimed unless the creditor proves the debtor's fault under the statutory text. This is different from an ordinary damages calculation and should be reflected in the pleading and evidence plan.
Article 182 allows the parties to determine the amount. It also links the penalty to the validity of the principal obligation and addresses later impossibility for which the debtor is not responsible. Its final paragraph directs the judge to reduce an excessive penalty. These rules should be read with the merchant-specific provision discussed below; they do not make every fixed sum automatically payable.
A service credit, termination fee, minimum-purchase payment, deposit forfeiture or clause labelled “liquidated damages” should not be classified solely by its name. Ask what event activates it, whether it pressures performance, whether ordinary performance can still be demanded and whether the sum is linked to an exit right or a price adjustment. The legal analysis follows function and context.
This guide does not add a separate proposition under article 181 and does not use case law. It therefore avoids conclusions about divisible or partial performance beyond the statutory provisions discussed here. If a real dispute turns on forfeiture of a part already performed, that issue needs fresh statutory and, where relied upon, full-text judicial research.
7. Read the merchant-debtor rule narrowly and accurately
Article 22 of the Turkish Commercial Code states that a debtor with merchant status cannot ask the court to reduce an excessive fee or contractual penalty in the situations identified by that provision, including the reduction rule in article 182(3) of the Code of Obligations. The statutory text makes party status and the debtor's position important.
That rule should not be converted into the statement that every agreed sum in a merchant contract is valid or automatically recoverable. The character of the payment, validity of the principal obligation, mandatory-law limits, incorporation of standard terms, the identity of the debtor and the actual breach remain separate questions. A party may also dispute whether the clause is a penalty at all.
Confirm merchant status for the relevant person and obligation. A group may include trading companies, special-purpose vehicles, public bodies, individuals and guarantors whose legal positions are not interchangeable. The contract should not assume that the status of one signatory answers the position of every affiliate or security provider.
No judicial exception or predicted result is stated in this package. Any advice about how article 22 and article 182 operate in a concrete dispute must be based on current full-text, fact-matched decisions and the complete agreement. Search snippets, summaries and general statements about court practice are not a substitute for that work.
8. Test pre-drafted terms and preserve real negotiation evidence
Articles 20 to 25 of the Turkish Code of Obligations contain a general-terms regime. Article 20 describes terms prepared unilaterally in advance for use in numerous similar contracts. Their location, scope or font does not control the classification, and small differences between contract versions do not necessarily prevent the terms from being general terms.
A sentence declaring that every provision was discussed and accepted is not sufficient by itself to remove the terms from that regime. Actual negotiation should be visible in the process: a clause-specific issue list, meaningful redlines, exchanged alternatives, approval notes and a record of the commercial trade-off. Boilerplate evidence should not replace what happened.
Article 21 ties incorporation of adverse general terms to clear information about their existence, a real opportunity to learn their content and acceptance. Terms foreign to the nature of the agreement or transaction can also be treated as unwritten. Provide the full document set before signature, identify incorporated schedules and avoid introducing a cap or indemnity only through an inaccessible hyperlink.
If a term is treated as unwritten, article 22 preserves the rest of the agreement and prevents the drafter from arguing that it would not have contracted without that term. This statutory consequence differs from a privately drafted severability clause. The contract should still be internally workable if a limitation or unilateral-change mechanism does not operate as intended.
Article 23 interprets an unclear or multi-meaning general term against the drafter and in favor of the counterparty. Article 24 treats as unwritten a general term that allows the drafter unilaterally to make adverse changes or introduce new adverse provisions. Change control should therefore distinguish objective adjustment mechanisms and mutually agreed variations from one-sided discretion.
Article 25 prohibits general terms that, contrary to good faith, disadvantage the counterparty or aggravate its position. Whether that control applies and what it means for a particular allocation remains fact-sensitive. A negotiated B2B agreement is not automatically outside articles 20 to 25, but neither should every clause be described as a general term without testing the statutory threshold.
9. Coordinate default, notices and electronic evidence
Under article 117 of the Turkish Code of Obligations, a debtor of a due obligation normally falls into default upon the creditor's notice. If the performance date was agreed jointly or was duly determined through a reserved contractual right, expiry of that date can produce default under the statutory rule. The contract should distinguish a due date, a notice to cure and a notice activating another remedy.
Article 118 makes a debtor in default responsible for loss caused by late performance unless the debtor proves absence of fault in entering default. Delay damages should therefore be kept separate from an agreed delay penalty. The same delay may engage both analyses, but their legal bases, proof and interaction are not identical.
Between merchants, article 18(3) of the Turkish Commercial Code lists the methods for notices of default, termination and rescission: notary, registered letter, telegram or registered electronic mail using a secure electronic signature. The parties should align their contractual notice clause with the statutory rule, identify addresses and authorized recipients and retain evidence of dispatch and receipt.
Operational messages still matter. Email, ticketing systems and platform logs may show what was delivered, discovered or discussed even when they are not the formal route for a notice covered by article 18(3). Article 199 of the Code of Civil Procedure recognizes electronic data and comparable information carriers as documents. Authenticity, completeness and evidential weight remain separate issues.
Article 5 of the Electronic Signature Law gives a secure electronic signature the same legal effect as a handwritten signature, subject to statutory exceptions. An ordinary email footer, scanned signature or click does not become a secure electronic signature merely because it is electronic. Formation, authority, attribution and integrity must be examined using the actual system and record.
Create an evidence protocol before a dispute. Preserve the signed contract and schedules, native emails with headers, registered electronic mail records, version history, system logs, acceptance evidence, notices, delivery confirmations and loss calculations. Restrict access, record exports and keep originals. A screenshot can be useful, but it should not be the only surviving form of a dynamic record.
10. Separate governing law, courts, arbitration and mediation
Article 24 of the Private International Law and International Civil Procedure Law subjects contractual obligations to the law expressly chosen by the parties; a choice that is unmistakably apparent from the contract or circumstances can also be valid. The parties may choose a law for all or part of the agreement. Without a choice, the statute applies its closest-connection framework.
A governing-law clause answers which substantive law applies. It does not by itself select a court, create arbitral jurisdiction or displace every mandatory rule. Draft the forum provision separately and test whether the chosen law covers the clause issues in dispute. A split choice for only part of the agreement can create difficult boundary questions and should be deliberate.
For eligible obligations with a foreign element, article 47 of the same statute permits agreement on a foreign court where territorial jurisdiction is not exclusively assigned. The agreement must be provable by written evidence, and the article defines when a Turkish court may nevertheless hear the case. Protected and exclusive jurisdiction provisions must be checked rather than assumed away.
An arbitration clause should identify the disputes covered, seat, institution or rules, number of arbitrators and language. Article 4 of the International Arbitration Law requires writing and recognizes specified electronic and incorporated-by-reference forms. It also treats the arbitration agreement separately from an objection that the main contract is invalid. The statute's own scope must be confirmed for the transaction.
Article 5 permits an arbitration objection when a covered dispute is filed in court. Article 6 states that seeking interim protection from a court before or during arbitration is not, by itself, inconsistent with the arbitration agreement. Neither rule assures that an objection or interim application will succeed. Timing, scope, waiver, evidence and the requested measure require separate analysis.
For commercial court actions within article 5/A of the Turkish Commercial Code seeking the listed monetary relief, pre-action mediation is a condition of suit. Article 18/A of the Mediation in Civil Disputes Law governs the procedure and the consequence of filing without completing the required step. The pleaded claim and chosen route matter; the statement should not be extended automatically to arbitration or every commercial disagreement.
A coherent dispute clause should also address notices, service details, confidentiality, interim measures, consolidation or joinder where relevant, and the relationship with technical determination or escalation steps. Avoid drafting an elaborate sequence that expires before urgent protection can be sought. The final clause needs a route-specific review in light of the parties, relief and assets.
11. Use a disciplined negotiation and approval workflow
Start with the risk schedule rather than the supplier's or customer's precedent. List the main obligations, plausible failure modes, maximum credible exposure, available insurance, dependencies and the records that will exist if something goes wrong. This keeps the cap and indemnities connected to the transaction instead of turning negotiation into a contest over familiar phrases.
Define terms once and trace them through every schedule. “Claim,” “Loss,” “Contract Year,” “Fees,” “Affiliate,” “Third-Party Claim” and “Gross Fault” should not change meaning between the master agreement, statement of work and data or service schedules. Establish an order of precedence that addresses conflicts without automatically displacing a carefully negotiated risk term.
Test the draft against scenarios. Consider one ordinary breach, repeated monthly failures, a single event affecting several customers, a third-party intellectual-property allegation, conduct by a subcontractor, termination after delay and a loss discovered after expiry. Calculate the cap under each scenario and record any assumption. This is a drafting stress test, not a forecast of legal liability.
Maintain a decision log for each major allocation. It should show the requested position, counterproposal, agreed wording, reason, approver and related insurance or pricing assumption. The log can demonstrate real negotiation for general-terms analysis, but it cannot validate a clause that conflicts with mandatory law. Keep it with the executed suite and final clean comparison.
Before approval, obtain a short written review covering the baseline liability, cap mechanics, mandatory carve-outs, auxiliary persons, indemnity procedure, penalty characterization, merchant status, standard-terms process, notices and dispute route. The approval should state unresolved assumptions. A concise, accurate exception list is more useful than a general statement that the agreement is market standard.
12. Build the file needed for a later claim or defense
When a problem arises, freeze the complete contract set first. Preserve the signed master agreement, schedules, amendments, statements of work, purchase orders and incorporated policies as they stood on the relevant date. A current web page is not proof of the version incorporated months earlier. Record file hashes and access controls where the integrity of electronic material may later matter.
Build a chronology from contemporaneous records. Identify the obligation, due date, performance, discovery of the issue, internal escalation, formal notice, cure attempt, acceptance or reservation, third-party communications and claimed loss. Mark disputed facts instead of silently choosing one narrative. This chronology helps separate default, delay damages, penalty and indemnity questions.
Maintain a loss ledger with source documents. Record invoices, credits, remediation expenditure, external defense costs, settlements, insurance proceeds and mitigation. Link each amount to the contractual theory relied upon and avoid double counting. If the claim exceeds a contractual penalty, article 180 makes the statutory fault issue relevant to the excess claim.
Before sending a termination, rescission or default notice between merchants, review article 18(3), the contract and the requested remedy together. Confirm the signatory's authority, recipient, address, method, cure period and reservation of rights. This guide does not calculate a personal deadline because that requires the executed contract, due date and delivery record.
Before relying on this guide in a transaction or dispute, obtain the current official texts and review the executed agreement, the parties, the transaction and the relevant facts. No judgment has been relied upon here, and no conclusion is given on a particular clause. The statutory map is a starting point for document-specific review, not a substitute for it.
13. Frequently asked questions
There is no universal answer. The clause's function, amount and operation, the parties and transaction, the degree of fault, articles 115 and 116, mandatory law and any general-terms control must be examined. A negotiated heading or merchant status does not settle validity.
No. The wording and the parties' real and common intention must be examined. The clause should identify the covered loss, trigger, claimant, third-party procedure, payment mechanics and relationship with ordinary breach remedies and the cap.
Article 115 makes an advance agreement excluding responsibility for gross fault void. Whether a monetary ceiling has that prohibited effect requires a functional review of the clause and circumstances; this guide does not give a universal conclusion for every cap.
Article 116 has a separate regime for persons used in performance. Its text permits responsibility for auxiliaries to be removed wholly or partly by advance agreement, while invalidating an exclusion in the specified field of expertise-dependent, officially permitted services, professions or arts. The delivery model, licensing rule, persons involved and wording require their own analysis.
Article 180 states that the agreed penalty may be due even without loss. A claim for loss above the penalty engages the separate statutory rule concerning proof of the debtor's fault. Validity and characterization still require review.
Article 179 addresses a penalty tied to performance at the agreed time or place and makes waiver or acceptance without reservation relevant. The contract, the event, acceptance record and reservation must be reviewed before reaching a conclusion.
Article 22 of the Turkish Commercial Code restricts that request in its statutory field. It does not establish that every fixed sum is a valid penalty or automatically recoverable. Party status, characterization, validity and current full-text authorities require case-specific review.
No. Governing law, court jurisdiction and arbitration are distinct choices. MÖHUK articles 24 and 47 and any applicable arbitration statute must be considered with the actual clause, mandatory rules and requested relief.
No general statement should be made for every dispute. Article 5/A covers specified commercial court actions concerning listed monetary relief, and article 18/A governs the procedure. The pleaded claim and dispute route, including any arbitration agreement, must be examined.
Electronic data may qualify as a document under article 199 of the Code of Civil Procedure, while a secure electronic signature has handwritten-signature effect subject to statutory exceptions. Authenticity, authority, integrity and evidential weight remain separate questions.
Official sources and scope boundaries
The official sources below were consulted in preparing this guide. The law, official forms and transaction-specific requirements must be checked again on the publication and advice dates. No judicial decision is cited.
- Turkish Code of Obligations No. 6098, consolidated official text.
- Turkish Commercial Code No. 6102, consolidated official text.
- Private International Law and International Civil Procedure Law No. 5718, consolidated official text.
- Code of Civil Procedure No. 6100, consolidated official text.
- Mediation in Civil Disputes Law No. 6325, consolidated official text.
- Electronic Signature Law No. 5070, consolidated official text.
- International Arbitration Law No. 4686, consolidated official text.
- Ministry of Justice guidance on mandatory mediation for commercial monetary claims.
