KSeF for freelancers and sole proprietors: B2B invoices, costs and obligations

Freelancers and Polish sole proprietors should prepare two KSeF processes: issuing B2B sales invoices and receiving cost invoices on the business NIP. KSeF is not just another way to email a PDF to a client.

In practice, four elements matter most: FA(3) XML, KSeF number, UPO and a readable PDF visualisation. The PDF helps people read the document, but it does not replace the structured invoice or the acceptance confirmation from KSeF.

The safest process for a sole proprietor is a fixed routine: check incoming invoices, confirm costs, download UPO for your own sales invoices and send the accountant a complete data package. KSeFGPT can organise this workflow, but it does not replace an accountant or tax adviser.

If you issue B2B invoices as a Polish sole proprietor, you need to know when to issue them in KSeF, how to receive costs in the system and how to give your accountant the XML, PDF, KSeF number, UPO and document status.

This is not a generic guide to choosing software for a small company. It is a practical process for a self-employed developer, consultant, designer, copywriter, marketer or adviser who issues a few sales invoices per month and receives costs for tools, accounting, equipment or subcontractors.

Scope: domestic B2B invoices, cost invoices, foreign clients, the accountant, UPO, KSeF number and a monthly routine. For a wider software-selection perspective, start with KSeF for small businesses.

When freelancers and sole proprietors need KSeF

What do I issue as a sole proprietor

What changes in freelancer B2B invoices

Costs in KSeF

Sole proprietor, accountant and accounting office

Foreign client and invoice in the counterparty language

Freelance developer and monthly KSeF rhythm

Is the Taxpayer Application enough

Checklist before the first KSeF month

Common freelancer mistakes in KSeF

The table below organises the decisions a freelancer should make before the first full month of work with KSeF.

As of June 22, 2026, mandatory issuing of invoices in KSeF is being introduced in stages. From February 1, 2026 it applies to taxpayers whose 2024 gross sales with VAT exceeded PLN 200 million. From April 1, 2026 it applies to the remaining taxpayers covered by the obligation.

For the smallest taxpayers, a transitional preference applies until the end of 2026: invoices can still be issued outside KSeF if, in a given month, total gross sales documented by invoices covered by KSeF do not exceed PLN 10,000. After the limit is exceeded, the invoice that exceeds the limit and later invoices are covered by the obligation.

Receiving invoices in KSeF must be treated separately. A postponement for issuing your own invoices does not postpone incoming invoices. A freelancer may still use the sales preference, while a cost invoice from a larger supplier can already be waiting in KSeF.

The key distinction is this: domestic B2B with a NIP generally leads to KSeF once the issuer is covered by the obligation. B2C is not the standard mandatory KSeF case. Foreign transactions require a careful check of the specific case.

A freelancer should avoid one broad rule such as every invoice always goes to KSeF. It is safer to ask several questions: who is the buyer, whether they have a NIP, whether the invoice is covered by the obligation, whether the transitional preference applies and whether there is a foreign element.

Domestic B2B: a typical invoice for software development, consulting, marketing or design services to a Polish company with a NIP will generally need a KSeF process once the issuer is covered by the obligation.

B2C: consumer invoices should not be treated like the standard B2B KSeF obligation. If the issuer voluntarily uses KSeF, they must still make sure the consumer receives the document correctly.

Foreign client: an invoice for a foreign counterparty may require KSeF if the Polish taxpayer issues it under Polish rules, but this should not be turned into one rule for every VAT, export-of-services, intra-EU or self-billing scenario.

Once the invoice types are clear, we can move to the freelancer's B2B invoice process itself.

Before KSeF, a freelancer often ended the sales process by generating a PDF and emailing it to the client and accountant. In KSeF, that PDF is only a human-readable preview. The data source is the FA(3) XML structured invoice, and UPO confirms acceptance.

Sales process: first prepare the invoice data, then create the FA(3) XML, send the document to KSeF, check acceptance, save the KSeF number and UPO, and only then send the client a readable visualisation if needed.

Documents to keep: your own invoice number, the KSeF number assigned after acceptance, UPO, XML or data export and PDF visualisation. These elements do not serve the same purpose.

If you want the technical sending steps, see the separate guide on sending invoices to KSeF.

Once the sales invoice flow is covered, the most frequently missed topic is freelancer costs.

The biggest change for a freelancer may not be sales. With a few sales invoices per month, sending can be learned quickly. The real disorder often starts with costs: SaaS, accounting, coworking, leasing, phone, equipment, advisers and subcontractors.

A cost invoice may appear in KSeF on your NIP without a separate supplier email. That is why a sole proprietor needs a regular routine for checking incoming invoices, marking documents for clarification and telling the accountant which costs are business-approved.

Do not treat receiving an invoice in KSeF as automatic acceptance of the cost. The system shows an invoice issued to your company, but it does not confirm that the purchase was ordered, justified, business-related and ready for accounting.

Useful working statuses are: new invoice, for approval, ready for accounting, disputed, waiting for correction. This simple split is enough to keep the accountant from guessing what to do.

The detailed incoming-invoice workflow is described in the guide on receiving invoices through KSeF.

Since costs require decisions, the next step is the split of work between the owner and accounting.

KSeF does not remove the accountant's role. It changes which data should reach accounting and who is responsible for organising it before month-end. The accounting office may have access to invoices, but the owner should still know which costs are real, accepted and described.

Owner: confirms whether the purchase concerns the business, whether the invoice is not accidental, whether the cost needs clarification and whether a foreign client received a readable visualisation.

Accountant: assesses the bookkeeping and tax treatment, asks for missing descriptions, watches settlements and tells the owner which data or exports are needed.

KSeF tool: should make it easier to download documents, statuses, KSeF numbers, UPO, XML and PDF. It does not make tax decisions for the owner or accountant.

With the roles separated, we can move to a common B2B freelancer case: a foreign client.

Work with a foreign client requires separating two topics. The first is issuing the invoice correctly under the relevant rules. The second is giving the counterparty a readable document their finance team understands.

If a Polish taxpayer issues the invoice in KSeF, the source data remains FA(3) XML, the KSeF number and UPO. The foreign counterparty may still need an informational visualisation in English, German or Ukrainian to understand line items, payment date and party details.

What the language version does not decide: place of supply, VAT rate, intra-EU treatment, export of services or self-billing. These issues require accounting or tax review.

A practical email label is: an informational visualisation of an invoice issued in KSeF, prepared so the counterparty can read it conveniently.

Language variants are explained in KSeF invoice in English, German and Ukrainian.

With clients and costs covered, we can move to a concrete monthly routine for a B2B software developer.

A sample B2B software developer issues one to five sales invoices per month and has costs for SaaS, equipment, accounting, phone, coworking and sometimes subcontractors. This volume does not require a heavy ERP, but it does require repeatable order.

Weekly routine: do not wait until the last day of the month. Once or twice a week, check incoming invoices, mark costs that need clarification and add missing descriptions. At month-end, issue sales invoices, download UPO and send the accountant a ready data package.

Minimum archive set: XML or export, PDF, invoice number, KSeF number, UPO for sales invoices, cost description, payment status and information on disputed invoices. It is simple, but without a list it is easy to lose control.

In KSeFGPT, this process can be based on document imports and the invoice list. The screenshot below shows PDF data import, a typical case for a freelancer who receives documents from multiple sources and wants to reduce manual typing.

Once the monthly rhythm is clear, the remaining question is whether the official MF tool is enough or whether a private application is useful for organising the process.

Aplikacja Podatnika KSeF 2.0 is the free tool from the Polish Ministry of Finance. For a freelancer with a few simple invoices it may be enough, especially if the priority is manual issuing, invoice receipt and UPO download.

KSeFGPT makes sense when the problem is not simply entering KSeF, but keeping documents in order. Examples include PDF or CSV import, more costs, statuses, UPO control, fast invoice search, data export and working with an accountant without retyping.

A fair boundary: if you have one sales invoice, two costs and the accountant handles the whole process, the MF tool may be enough. If you start having a dozen documents, a foreign client, more costs or you want all invoices in one organised view, a private app can save time.

KSeFGPT is not an official MF tool, accounting office or bookkeeping program. It is a tool for working with KSeF invoices, document imports, data checks and preparing information for accounting.

Before the first full month in KSeF, do not start by choosing the most expensive tool. Start with who has access, who issues sales invoices, who receives costs and what exactly goes to the accountant.

Access: check whether you can log in to the tool and work in the context of the correct NIP.

Permissions: decide whether the accountant, employee or collaborator has the needed access, and if not, how documents will be handed over.

Authentication: choose a safe way to work with KSeF, and treat tokens or certificates like credentials that should not be shared casually.

Sales: prepare the invoice data template, numbering, sending method, UPO download and archive of KSeF numbers.

Costs: define days for checking incoming invoices, document statuses and purchase descriptions.

Foreign clients: prepare rules for sending a readable visualisation to the counterparty and a list of cases that require an accountant's review.

Archive: decide where you keep XML, PDF, UPO, KSeF number and the history of documents sent to accounting.

Once the starting plan is ready, the final step is avoiding repeatable mistakes.

The first mistake is focusing only on your own sales invoices. A freelancer can quickly learn sending while missing cost invoices waiting in KSeF.

The second mistake is confusing a PDF with a structured invoice. A PDF is readable, but the formal KSeF process is based on FA(3) XML, KSeF number and UPO.

The third mistake is missing UPO in the archive. An invoice that was prepared or technically sent should not be treated like a document accepted by KSeF and confirmed by UPO.

The fourth mistake is sending the accountant only a file without context. Costs often need a purchase description, project, approval status and information on whether the document is disputed.

The fifth mistake is treating the PLN 10,000 preference too broadly. It is a transitional deferral for specific invoices and a specific period, not a general permission to ignore KSeF.

The biggest risk for a sole proprietor is not that the owner will click the wrong button in KSeF. The risk is lack of process: a sales invoice is prepared but there is no UPO; a cost appears in KSeF but nobody checks it; the accountant receives a file but not its status or description.

For a freelancer, a reasonable process should be short, repeatable and possible without an admin department. A few fixed rules are enough: when you check incoming invoices, when you issue sales invoices, what you save after UPO and what data package goes to accounting.

It is also worth being careful with shortcuts such as PDF is enough or the accountant will see everything. KSeF organises the central invoice flow, but it does not replace the decision whether a cost was real, ordered and correctly described.

That is why this article deliberately does not go into PIT, KPiR, lump-sum tax or the tax timing of costs. Those topics require separate analysis. Here the priority is a safe invoice, data and responsibility workflow.

If you want to go further, start with four materials. KSeF for small businesses organises the wider software and small-company process. Sending invoices to KSeF explains the technical sales-invoice flow. Receiving invoices through KSeF helps set up costs and incoming invoices. KSeF invoice in English, German and Ukrainian explains how to give a counterparty a readable visualisation without creating a second invoice.