Changes in KSeF – how to prepare a billing system in 3 days

Day one: Inventory and audit of your 43 processes

The first step is brutal honesty towards your own accounting. You must check how you now issue documents for your contractors. Marek Wiśniewski, who has been dealing with taxes in our company for 9 years, noticed that the average IT company in Krakow uses 3 different methods of issuing bills. This is a mistake that with KSeF will end in a mess in the papers. You must collect all the buyers' data, tax IDs (NIP), and check if your current programs are at all capable of generating an XML file compliant with the Ministry of Finance schema. It's not a time for fluff, only for hard numbers and checking if your 43 or 87 invoices per month will pass through the government gateway.

During the audit, we focus on the weakest links. It often turns out that one person in the team issues invoices in Excel, and the other in an old program from 2017. KSeF will not forgive this. You must unify formatting. If you have 12 active subscription clients, each of them must be assigned to the new system. Without unnecessary talk, you need to sit down and write a list of all regular payments. We've seen cases where a missing comma in the company address caused the rejection of an invoice by the Ministry's servers. This is a waste of time that a small company cannot afford, especially when the payment deadline is chasing.

At Krakow Advisory Market, we recommend that on the first day you designate one person responsible for this transition. Even if your team has only 6 people, someone must keep their finger on the pulse. Don't look for perfect systems, look for the ones that work. Facts on the table: you must be sure that your data is clean. Check the correctness of the NIPs of all your 34 suppliers. This will take you about 4 hours but will save you from penalties that can amount to as much as 99.6% of the VAT value from an incorrect invoice. We speak with a human voice: better spend this Tuesday on cleaning than Wednesday crying in the tax office.

Facts on the table: either the invoice passes through the government gateway as a clean XML file, or it legally simply does not exist.

Day two: Technical connection and tests on 11 documents

On the second day, we move on to technique. Your software must be connected to the KSeF API. If you use cloud tools popular in Poland, the matter is simpler but still requires clicking appropriate consents and generating access tokens. Our team at Krakow Advisory Market has already helped 47 companies pass through this stage without sales paralysis. It is crucial that you generate a test token and try to send an 'empty' invoice to the demo environment. Don't wait for the last minute. If your API does not respond within 3.2 seconds, something is wrong with your connection or server configuration.

We had a client from the creative industry who thought it was enough to update the program. It turned out that their specific invoices for copyrights required additional fields in the XML file. We spent 6 hours on it to make everything work. Therefore, on the second day, take 11 of your most complicated invoices from the last 3 months and try to move them to the new format. Check if the discounts, net and gross amounts round as the ministerial algorithm wants. KSeF is merciless for mathematical errors at the level of pennies. The result matters, not the process, so the system will simply reject the document, and you will not get money on time.

Remember about permissions. You must decide who in your 5-person company has the right to send documents and who only to view them. In KSeF, every action leaves a trace. If your graphic designer accidentally sends an invoice for 12,500 PLN instead of 1,250 PLN, the correction will hurt more than before. You must set the process so that the invoice is checked by a second person before being sent to KSeF. This takes an additional 14 minutes a day but protects your cashflow. Technical implementation is not magic, it is a craft. You just have to click it out and check it on real examples, not on theoretical diagrams from brochures.

Day three: Team training and the first real dispatch

The last day is working with people. Even the best system will fail if your employee doesn't know where to click. At Krakow Advisory Market, we don't do boring lectures. We do a workshop. Sit down with the team for 2 hours and go through the process from issuing an order to confirming receipt of the invoice by KSeF. Your people must understand that the date of issuing an invoice is now the moment of its submission to the system, not the date entered in the PDF. This is a fundamental change that affects when you will get a VAT refund or when you will have to pay it. If you submit an invoice at 23:59 and the server accepts it at 00:01, you are in a different tax month.

Introduce a simple rule: we issue invoices by 2:00 pm. This gives you time to react if the government system has a technical break or if your internet connection fails. We have already seen situations where companies waited until the last day of the month and missed invoices for a total amount of 83,000 PLN due to a power outage. These are real risks that we speak about with a human voice, without legal jargon. On the third day, you should have a ready instruction on one A4 page for your team. Short points: check data, send, download KSeF identification number, archive.

At the end of day three, send the first real invoice. Choose a client with whom you have good relations and warn them that you are testing a new system. If everything passes, you can breathe a sigh of relief. Your company is secured. The whole process took you 3 days because you didn't waste time on nonsense, you just focused on facts. We at Krakow Advisory Market have been acting like this since 2016 – we take the problem into the workshop and solve it without unnecessary talk. Now you can return to earning money, knowing that the tax office will have nothing to catch at the next audit.

We speak with a human voice: the system is not for the office, the system is there so that you have peace of mind with the papers.

What if something goes wrong? Contingency plan

Despite the best preparations, technology can be malicious. You must have a procedure in case of a KSeF failure on the government side. The law provides for an offline mode, but you must know how to use it so as not to expose yourself to sanctions. In such a case, the invoice is issued traditionally but with an appropriate marking, and then you have 7 days to supplement the data in the central system. This is not black magic, but requires having current document templates at hand. In our consulting practice, we have already prepared 15 such emergency kits for Krakow design offices.

Another risk is human error. If someone sends an invoice with the wrong VAT rate, there is no 'delete' button in KSeF. You need to issue a corrective invoice, which also goes through the central system. This teaches financial discipline, which is often missing in dynamic IT companies. Therefore, we recommend that once a week, preferably on Fridays at 10:00 am, check the status of all sent documents. This takes 12 minutes and gives certainty that nothing is stuck in the queue. At Krakow Advisory Market, we believe that it is such small habits that build the security of your business.

In summary, KSeF is a big change, but manageable. Don't be intimidated by companies that offer 'comprehensive implementations' for tens of thousands of zlotys. Most small and medium-sized enterprises only need efficient software and a change of several habits in the team. If you get stuck at any stage, just ask someone who has already done it. Our experience with 187 consulting projects shows that the first step is the hardest. Then the system works in the background, and you forget about filing binders with invoices. This is a time-saver you will appreciate after the first full quarter.