{"id":29320,"date":"2026-09-08T07:00:01","date_gmt":"2026-09-08T07:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/peppol-invoice-response-sme-2\/"},"modified":"2026-09-08T07:00:01","modified_gmt":"2026-09-08T07:00:01","slug":"peppol-laskun-vastaus-pk-yritys-2","status":"publish","type":"page","link":"https:\/\/bilnex.io\/fi\/peppol-laskun-vastaus-pk-yritys-2\/","title":{"rendered":"Peppol-laskuvastaus: Milloin se on pakollinen pk-yrityksille?"},"content":{"rendered":"<article class=\"article-content-section article-content article-single\">\n<div class=\"container content-area\">\n<div class=\"text-content ce-answer\">\n<p>Peppol Invoice Response is a structured message the buyer sends the seller about the status of <a href=\"https:\/\/docs.peppol.eu\/poacc\/upgrade-3\/profiles\/63-invoiceresponse\/\">one specific invoice or credit note<\/a>. This is different from a plain delivery confirmation, which only confirms a message arrived on the network without touching what happens to the invoice afterward. No one is automatically required to use it. <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/release-notes\/\">As of 17 August 2026<\/a>, Peppol BIS Billing version 3.0.21 became mandatory across the network, and that version introduced an optional profile called &#8220;Billing with Response,&#8221; which comes with its own identifier and requires separate registration. If your business stays on the standard invoicing profile, nothing changes for you: invoice response only becomes something you need to handle if you or your customer deliberately switches to that specific profile.<\/p>\n<h2 id=\"how-is-invoice-response-different-from-a-delivery-confirmati\">How is invoice response different from a delivery confirmation?<\/h2>\n<p>A delivery confirmation moves inside the Peppol network and only proves the message landed. It says nothing about whether anyone acted on it. <a href=\"https:\/\/docs.peppol.eu\/poacc\/upgrade-3\/profiles\/63-invoiceresponse\/\">Invoice response<\/a> sits a level above that: it&#8217;s a business-level message where the buyer tells the seller whether the invoice has been accepted, conditionally approved, disputed, or already paid. The message only flows one way, buyer to seller, and the seller has no way to request it automatically.<\/p>\n<h2 id=\"is-using-invoice-response-a-legal-requirement\">Is using invoice response a legal requirement?<\/h2>\n<p><a href=\"https:\/\/docs.peppol.eu\/poacc\/upgrade-3\/profiles\/63-invoiceresponse\/\">The specification is explicit<\/a>: neither the buyer nor the seller is obliged to use invoice response. <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX%3A32014L0055\">Directive 2014\/55\/EU<\/a> requires public-sector buyers to accept e-invoices built to the standard, but it creates no duty to send status messages back. In Estonia, the <a href=\"https:\/\/www.riigiteataja.ee\/public-api\/api\/v1\/en\/akt\/510072025005\/blob-html\">Accounting Act<\/a> gives any company registered as an e-invoice recipient the right to demand e-invoices from 1 July 2025 onward, but that right has nothing to do with any invoice-response obligation. The <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX%3A32025L0516\">ViDA directive<\/a> brings cross-border digital reporting from 1 July 2030, but it doesn&#8217;t force small businesses onto the invoice-response profile either.<\/p>\n<h2 id=\"what-actually-changed-on-17-august-2026\">What actually changed on 17 August 2026?<\/h2>\n<p><a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/release-notes\/\">OpenPeppol published<\/a> version 3.0.21 on 20 May 2026, and it became mandatory from 17 August 2026. That release added <a href=\"https:\/\/docs.peppol.eu\/poacc\/billing\/3.0\/bis\/\">Profile 02, &#8220;Billing with Response&#8221;<\/a>, under which the buyer must send at least one response for every invoice received. Anyone who stays on the standard Billing profile is unaffected by that requirement.<\/p>\n<h2 id=\"which-statuses-apply-and-what-happens-if-an-invoice-gets-rej\">Which statuses apply, and what happens if an invoice gets rejected?<\/h2>\n<p><a href=\"https:\/\/docs.peppol.eu\/poacc\/upgrade-3\/profiles\/63-invoiceresponse\/\">The fixed statuses<\/a> are AB (accepted), IP (in process), UQ (under query), CA (conditionally approved), RE (rejected), AP (approved) and PD (paid). A buyer supporting the profile has to be able to send at least AB, RE and AP. For UQ, CA and RE, the buyer adds a code or free text explaining what the seller needs to fix. RE and PD are final statuses. Once an invoice hits AP, only PD can follow.<\/p>\n<h2 id=\"does-the-three-business-day-rule-count-as-a-payment-deadline\">Does the three-business-day rule count as a payment deadline?<\/h2>\n<p><a href=\"https:\/\/docs.peppol.eu\/poacc\/upgrade-3\/profiles\/63-invoiceresponse\/\">The process rule<\/a> says the buyer must send the first response within three business days. That&#8217;s an internal Peppol timing rule, not an Estonian statutory payment deadline. Sending a response doesn&#8217;t change the invoice itself or release the buyer from whatever payment obligation already applies under the contract.<\/p>\n<h2 id=\"what-to-check-before-switching-the-profile-on\">What to check before switching the profile on<\/h2>\n<p>Ask your Peppol access point whether it supports &#8220;Billing with Response&#8221; and which identifier it will register for your company. Agree with your trading partner on which optional statuses, UQ, CA and PD, each side actually needs, and confirm whether your accounting software can automatically match an incoming status message back to the original invoice.<\/p>\n<h2>FAQ<\/h2>\n<h3>Mille poolest erineb arve vastus k\u00e4ttetoimetamiskinnitusest?<\/h3>\n<p>K\u00e4ttetoimetamiskinnitus kinnitab ainult s\u00f5numi j\u00f5udmist v\u00f5rgus, mitte selle sisu menetlemist. Arve vastus on \u00e4rilise tasandi s\u00f5num, kus ostja teatab, kas arve on kinnitatud, tingimuslikult heaks kiidetud, vaidlustatud v\u00f5i tasutud. Vastus liigub ostjalt m\u00fc\u00fcjale ja m\u00fc\u00fcja ei saa seda automaatselt k\u00fcsida.<\/p>\n<h3>Kas arve vastuse kasutamine on seadusega kohustuslik?<\/h3>\n<p>Ei. Peppoli spetsifikatsioon \u00fctleb selgelt, et ei ostja ega m\u00fc\u00fcja pea arve vastust kasutama. Direktiiv 2014\/55\/EL kohustab avaliku sektori hankijaid vastu v\u00f5tma e-arveid, aga ei loo kohustust saata arve staatuseid. Eesti Raamatupidamise seadus ega ViDA direktiiv ei tee arve vastust kohustuslikuks.<\/p>\n<h3>Mis 17. augustil 2026 tegelikult muutus?<\/h3>\n<p>OpenPeppol avaldas versiooni 3.0.21, mis sai kohustuslikuks 17. augustist 2026. See lisas profiili \u201eBilling with Response&#8221;, mille korral ostja peab saatma v\u00e4hemalt \u00fche vastuse iga saadud arve kohta. Kes j\u00e4\u00e4b tavalise Billing-profiili juurde, sellele see kohustus ei laiene.<\/p>\n<h3>Kas kolm t\u00f6\u00f6p\u00e4eva on makset\u00e4htaeg?<\/h3>\n<p>Ei. Protsessireegel n\u00e4eb ette, et ostja saadab esimese vastuse kolme t\u00f6\u00f6p\u00e4eva jooksul, kuid see on Peppoli sisereegel, mitte Eesti seadusest tulenev makset\u00e4htaeg. Vastus ei muuda arvet ega vabasta ostjat kehtivast maksekohustusest.<\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Mille poolest erineb arve vastus k\u00e4ttetoimetamiskinnitusest?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"K\u00e4ttetoimetamiskinnitus kinnitab ainult s\u00f5numi j\u00f5udmist v\u00f5rgus, mitte selle sisu menetlemist. Arve vastus on \u00e4rilise tasandi s\u00f5num, kus ostja teatab, kas arve on kinnitatud, tingimuslikult heaks kiidetud, vaidlustatud v\u00f5i tasutud. Vastus liigub ostjalt m\u00fc\u00fcjale ja m\u00fc\u00fcja ei saa seda automaatselt k\u00fcsida.\"}},{\"@type\":\"Question\",\"name\":\"Kas arve vastuse kasutamine on seadusega kohustuslik?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Ei. Peppoli spetsifikatsioon \u00fctleb selgelt, et ei ostja ega m\u00fc\u00fcja pea arve vastust kasutama. Direktiiv 2014\/55\/EL kohustab avaliku sektori hankijaid vastu v\u00f5tma e-arveid, aga ei loo kohustust saata arve staatuseid. Eesti Raamatupidamise seadus ega ViDA direktiiv ei tee arve vastust kohustuslikuks.\"}},{\"@type\":\"Question\",\"name\":\"Mis 17. augustil 2026 tegelikult muutus?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"OpenPeppol avaldas versiooni 3.0.21, mis sai kohustuslikuks 17. augustist 2026. See lisas profiili \u201eBilling with Response\\\", mille korral ostja peab saatma v\u00e4hemalt \u00fche vastuse iga saadud arve kohta. Kes j\u00e4\u00e4b tavalise Billing-profiili juurde, sellele see kohustus ei laiene.\"}},{\"@type\":\"Question\",\"name\":\"Kas kolm t\u00f6\u00f6p\u00e4eva on makset\u00e4htaeg?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Ei. Protsessireegel n\u00e4eb ette, et ostja saadab esimese vastuse kolme t\u00f6\u00f6p\u00e4eva jooksul, kuid see on Peppoli sisereegel, mitte Eesti seadusest tulenev makset\u00e4htaeg. Vastus ei muuda arvet ega vabasta ostjat kehtivast maksekohustusest.\"}}]}<\/script><\/p>\n<\/div>\n<\/div>\n<\/article>\n<style>.ce-answer{max-width:760px;margin:0 auto;padding:8px 20px 48px;line-height:1.65}.ce-answer h2{margin:1.5em 0 .55em;line-height:1.3}.ce-answer h3{margin:1.1em 0 .45em}.ce-answer p{margin:0 0 1em}.ce-answer ul,.ce-answer ol{margin:0 0 1em;padding-left:1.4em}.ce-answer li{margin:.25em 0}.ce-answer table{border-collapse:collapse;width:100%;margin:0 0 1.2em}.ce-answer th,.ce-answer td{border:1px solid #ddd;padding:8px 10px;text-align:left}.ce-answer blockquote{border-left:3px solid #ccc;margin:1em 0;padding:6px 14px}.ce-answer sup a{text-decoration:none}.ce-answer-title{margin:.6em 0 .4em}<\/style>\n","protected":false},"excerpt":{"rendered":"<p>Billing with Response -profiili, joka on ollut k\u00e4yt\u00f6ss\u00e4 17. elokuuta 2026 l\u00e4htien, ei ole pakollinen kaikille. Se koskee vain niit\u00e4, jotka sen valitsevat.<\/p>","protected":false},"author":8,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-29320","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/pages\/29320","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/comments?post=29320"}],"version-history":[{"count":0,"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/pages\/29320\/revisions"}],"wp:attachment":[{"href":"https:\/\/bilnex.io\/fi\/wp-json\/wp\/v2\/media?parent=29320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}