I Support E-Invoicing. The Question Is How We Introduce It.
A case for structured invoices, Peppol and a public baseline that separates business automation from the allocation of compliance costs.
Read article →Category
Governance
35 articles in this category.
From EDI to Peppol: What Standardised Invoice Exchange Actually Delivers
Structured data, common business rules and interoperable delivery solve different problems. A practical account of the benefits and limits.
Read article →Peppol Is Not Slovakia's E-Invoicing Model: Separate the Standard from State Decisions
An interoperability framework does not determine national reporting scope, contractual obligations, prices or public-service alternatives.
Read article →ViDA and Slovakia's Path: Why Start with Domestic Trade?
The EU's cross-border reporting timetable and Slovakia's earlier domestic regime are related but distinct policy choices.
Read article →The VAT Control Statement Already Exists: What More Will the New Data Collection Deliver?
Compare existing VAT reporting with e-invoice reporting by timing, coverage and detail, and require evidence of incremental value.
Read article →An Obligation from the State, a Contract with a Private Company: Why Do We Need a Digital Postman?
Peppol delivery has a real function. Making access to a public obligation depend on a commercial relationship is a separate policy choice.
Read article →Receiving and Sending Invoices: How Many Services and Contractual Relationships Does a Business Need?
One receiving route does not mean one supplier for every function. A practical map of invoice delivery, software, reporting and contracts.
Read article →Why Not Directly Through the State? A Public Alternative to Commercial Postmen
A proposal for a bounded public e-invoicing channel that preserves Peppol interoperability and leaves value-added services to voluntary choice.
Read article →What eKasa Teaches Us: Does the State Have the Capacity for Direct E-Invoicing Too?
VRP 2 is evidence that a public baseline application is possible, not proof that Slovakia already has the capacity to operate an invoice-delivery service.
Read article →Changing Postmen Without Losing Data: Interoperability or Supplier Dependence?
Peppol migration can change a receiving route. Genuine supplier independence also requires portable archives, evidence, integrations and workable exit terms.
Read article →Where the invoice goes: ERP, Access Point, SMP and tax reporting are not the same thing
Separate invoice creation, transport, metadata lookup and tax reporting before assigning responsibility.
Read article →An invoice is not just a tax document: prices, business relationships and sensitive information
Classify invoice information accurately and protect useful detail without pretending every field is a trade secret.
Read article →How much data does the state need? GDPR, trade secrets and data minimisation
A necessity test for fields or justified groups of fields in tax reporting, without overstating GDPR or trade-secret protections.
Read article →Classified transactions and professional secrecy: where e-invoicing must have boundaries
Distinguish security exceptions, professional secrecy and commercial confidentiality, then design usable procedures.
Read article →Certified does not mean unbreachable: what to demand from a digital postman beyond a certificate
Use certification as scoped evidence, then verify access, recovery, incident handling and exit.
Read article →What Does an Open Port Prove? How to Assess a Provider’s Security Honestly
Why network exposure is a question to investigate, not proof of a breach, and what evidence businesses should request from an e-invoicing provider.
Read article →When the Service Goes Down: Delivery, Fallback Arrangements and Business Continuity
An e-invoicing continuity plan must distinguish technical delivery, business acceptance, recovery and legally authorised fallback procedures.
Read article →Who Is Responsible for an Error or Data Leak: The Business, the Delivery Provider, the Software Supplier or the State?
Responsibility in e-invoicing must connect operational duties, contractual remedies and data-protection roles without pretending one contract settles everything.
Read article →The Price of E-Invoicing Is More Than a Monthly Fee: Real Costs and Potential Savings
A transparent business case for e-invoicing should count implementation, exceptions, exit and realised savings—not just the price of sending a document.
Read article →Readiness Is Not Measured by a Date: APIs, Testing and the Conditions for a Safe Launch
A defensible e-invoicing launch requires versioned interfaces, realistic testing, legal clarity, support and evidence-based go-live decisions.
Read article →Peppol in Northern Europe: How the State, Providers and Businesses Divide the Work
Nordic public-sector invoicing shows how shared standards, commercial providers and publicly supported access can coexist without being the same policy.
Read article →Poland, Italy and France: What We Can Learn from Different Models
Public invoicing tools, central exchange systems and approved platforms represent different allocations of cost, access and responsibility—not one European template.
Read article →Televisions, Washing Machines and Services under Contract: What an Invoice Proves—and What It Does Not
Structured invoices improve records and matching, but tax evidence still requires context about delivery, business use and the substance of a transaction.
Read article →AI in Tax Audits: A Useful Signal Is Not Proof of Fraud
Tax analytics can prioritise investigation, but accountable decisions require evidence, meaningful review and careful treatment of AI Act and GDPR rules.
Read article →A Public Baseline for E-Invoicing: Conditions for Security and Competition
A proposed public baseline for invoice exchange should preserve Peppol interoperability while specifying data boundaries, failure handling and accountable operation.
Read article →Rules First, Oversight Second: Can We Change the Mechanism of Tax Fraud Itself?
Why tax reform should examine opportunities for fraud before adding surveillance, without promising a fraud-proof system.
Read article →Wider Reverse Charge: Options for Limiting Carousel Fraud and Freeing Liquidity
A case for investigating wider VAT reverse charge, with explicit limits on cash-flow claims and legal feasibility.
Read article →A Turnover Tax Instead of a Profit Tax? A Proposal, American Experience and Slovak Conditions
Testing differentiated gross receipts taxation without confusing it with sales tax or promising effortless revenue.
Read article →More Revenue, Less Administration? How to Test the Yield and Effects of Tax Reform
A practical evidence standard for comparing differentiated receipts taxation and wider reverse charge with the existing system.
Read article →From Proposal to Decision: How to Validate and Advance a Simpler Tax System
A staged route from reform ideas to lawful testing, independent evaluation and a reversible public decision.
Read article →Companies Are Building an Illusion of Security
Many companies spend thousands on cybersecurity tools, audits and certificates, but still lack ownership, decision-making and a managed security system.
Read article →Having a Firewall Is Not the Same as Having Security
A firewall, antivirus, backups and logs are not enough. The real question is whether information security is owned, controlled, evidenced and repeatable.
Read article →IT Is the Nervous System of Corporate Responsibility
Modern IT is no longer a printer-support function. It connects legal, operational, manufacturing and cybersecurity responsibility into one risk space.
Read article →Security Starts by Admitting You Do Not Have It
If a company believes compliance, tools and a passed audit mean cybersecurity is under control, it may only have an illusion of security.
Read article →Why IT Cannot Manage Cybersecurity Alone
Cybersecurity is not only a technical problem. It becomes real when IT and leadership are connected through decisions, risk ownership and business context.
Read article →