How to terminate a B2B contractor agreement safely in Poland

Identify the legal nature of the agreement

Polish law does not define one universal “B2B contract”. The document may be a services agreement, a mandate, a contract for a specific work, an agency agreement, a management contract or a mixed agreement.

This classification affects termination. The rules on mandate contracts apply accordingly to services that are not separately regulated. However, this does not mean that every contractor relationship can be ended in the same way. Specific legislation and, most importantly, the wording of the agreement may change the position.

The review should therefore cover the whole contract, not only the termination clause. Provisions on duration, cure periods, notices, contractual penalties, ownership of deliverables and return of property may all affect the exit.

Ordinary notice and termination for serious reasons

An agreement may permit ordinary termination on one or three months’ notice. It may also restrict ordinary termination of a fixed-term arrangement or make it conditional on specified events.

Termination for serious reasons requires a separate analysis. Where the mandate rules apply, the parties cannot waive this right in advance. Merely labelling a reason “serious” in the termination letter is not enough.

Serious reasons may include a material confidentiality breach, permanent inability to provide a critical service, refusal to perform agreed duties or a loss of trust based on identifiable events. The assessment depends on the contract, the nature of the services, the severity of the breach and the parties’ previous conduct.

If the contract requires a cure notice, skipping it may weaken the terminating party’s position. In an urgent case, the company should also check whether it may immediately protect systems or suspend access while completing the contractual termination process.

Financial exposure does not end with the notice

A termination may be effective and still trigger a payment obligation. Under Article 746 of the Polish Civil Code, where applicable, the customer may have to reimburse justified expenses and pay the part of the fee corresponding to work already performed. Termination without a serious reason may also result in liability for loss.

The contract may contain additional rules concerning payment for a commenced stage, a notice period, a minimum term, an early-exit fee or contractual penalties for breaches of non-monetary obligations. Each mechanism needs a separate review of its validity, calculation and connection with the alleged breach.

Before serving notice, the company should prepare a draft closing account listing accepted deliverables, work in progress, disputed invoices, contractor expenses and potential claims on both sides.

Use the correct form and retain evidence of delivery

The notice must comply with the form required by law or the contract. If the agreement identifies a notice address, authorised recipients, written form or an accepted electronic channel, those requirements should be followed.

Delivery is often as important as form. Under Polish law, a declaration is effective when it reaches the other party in a way that enables that party to become acquainted with it. A message sent to an unused inbox, a Slack notification to a project team member or a scan that does not meet the required form may create an avoidable dispute.

The notice should clearly identify the agreement, legal and contractual basis, termination route, effective date and required exit actions. If breaches are relied upon, they should be described specifically and supported by preserved evidence.

Treat offboarding as a separate workstream

The final day of services does not eliminate operational risk. The exit plan should allocate responsibility for:

Where the contractor has extensive technical access, the order of steps should be agreed internally in advance. Cutting off access before securing the necessary data may disrupt the project, while leaving access open for too long may increase security exposure.

• handing over source code, files, documentation, project correspondence and open tasks;
• returning equipment, cards, tokens and storage devices;
• returning or deleting data in line with the parties’ roles and instructions;
• transferring control of administrative accounts, repositories, domains and cloud services;
• confirming the transfer or licensing of IP in completed deliverables;
• communicating with customers and staff in the agreed manner;
• complying with confidentiality, non-solicitation and other surviving obligations.

Consider employment reclassification risk

If the relationship operated in a way resembling employment, the post-termination dispute may go beyond contractual claims. The contractor may allege that work was in fact performed under the company’s direction, at a time and place determined by the company, despite the B2B label.

Neither a long relationship nor monthly invoicing is decisive on its own. The actual working model matters. A long-term and highly subordinated relationship should therefore also be assessed from the employment-law perspective before the exit is communicated.