{"id":29551,"date":"2026-09-23T11:00:01","date_gmt":"2026-09-23T11:00:01","guid":{"rendered":"https:\/\/bilnex.io\/en\/peppol-four-corner-model\/"},"modified":"2026-09-23T11:00:03","modified_gmt":"2026-09-23T11:00:03","slug":"peppol-cetru-sturu-modelis","status":"publish","type":"page","link":"https:\/\/bilnex.io\/lv\/peppol-cetru-sturu-modelis\/","title":{"rendered":"Peppol \u010detru st\u016bru modelis: k\u0101 pien\u0101k e-r\u0113\u0137ins"},"content":{"rendered":"
\n
\n
\n

Peppol’s four-corner model (4-corner model) means an e-invoice travels between seller and buyer through four parties: C1 is the seller, C2 is the sending service provider the seller has chosen, C3 is the receiving service provider the buyer has chosen, and C4 is the buyer. The standard route is C1 \u2192 C2 \u2192 C3 \u2192 C4<\/a>, with C2 converting the seller’s invoice into a standard Peppol e-invoice and C3 converting it again into a form the buyer’s system can read. You don’t need the same operator or the same software as your customer, because one connection to one service provider is enough for any sender and any receiver<\/a> to reach the whole network. And in Estonia, an e-invoice requirement doesn’t automatically mean Peppol. The Ministry of Finance works from a principle of format freedom<\/a>, and both the Estonian and the European e-invoice standard are in use.<\/p>\n

\n

Key facts<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n
Fact<\/th>\nValue<\/th>\nValid from<\/th>\nSource<\/th>\n<\/tr>\n<\/thead>\n
The parties in the four-corner model<\/td>\nC1 the seller, C2 the seller’s service provider, C3 the buyer’s service provider, C4 the buyer<\/td>\nas of 2026-09<\/td>\npeppol.org<\/a><\/td>\n<\/tr>\n
One connection, the whole network<\/td>\nEvery sender and every receiver needs a connection to just one Peppol service provider (“connect ONCE, reach ALL”)<\/td>\nas of 2026-09<\/td>\npeppol.org<\/a><\/td>\n<\/tr>\n
Amendment to \u00a7 7\u00b9 of the Estonian Accounting Act<\/td>\nEntered into force on 1 July 2025; the business register records the e-invoice recipient’s e-invoice operator identifier or other receiving channel<\/td>\n01.07.2025<\/td>\nriigiteataja.ee<\/a><\/td>\n<\/tr>\n
A buyer’s right to demand an e-invoice in Estonia<\/td>\nThe right belongs to every accounting entity that has registered itself as an e-invoice recipient in the e-Business Register (Accounting Act \u00a7 7\u00b9 (7)); around 18,000 have registered<\/td>\nsince 2025<\/td>\nfin.ee<\/a><\/td>\n<\/tr>\n
Public-sector obligation to receive e-invoices in the EU<\/td>\nArticle 7 of Directive 2014\/55\/EU obliges contracting authorities to receive and process e-invoices compliant with the European standard; Peppol is not named as the only channel<\/td>\nin force, as of 2026-09<\/td>\neur-lex.europa.eu<\/a><\/td>\n<\/tr>\n
ViDA cross-border digital reporting<\/td>\nMember States must adopt the measures by 30 June 2030 and apply them from 1 July 2030; the package was adopted on 11 March 2025<\/td>\n01.07.2030<\/td>\neur-lex.europa.eu<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

How a \u20ac1,200 invoice gets from your software into your customer’s books<\/h2>\n

Take a concrete case. You invoice an Estonian client for \u20ac1,200, and that client is registered in the business register as an e-invoice recipient.<\/p>\n