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 →Governance notes on accountability, oversight, AI, cybersecurity, decision rights and the management structures needed for trustworthy technology.
47 articles tagged Governance on vesely.sk.
A case for structured invoices, Peppol and a public baseline that separates business automation from the allocation of compliance costs.
Read article →Structured data, common business rules and interoperable delivery solve different problems. A practical account of the benefits and limits.
Read article →An interoperability framework does not determine national reporting scope, contractual obligations, prices or public-service alternatives.
Read article →The EU's cross-border reporting timetable and Slovakia's earlier domestic regime are related but distinct policy choices.
Read article →Compare existing VAT reporting with e-invoice reporting by timing, coverage and detail, and require evidence of incremental value.
Read article →Peppol delivery has a real function. Making access to a public obligation depend on a commercial relationship is a separate policy choice.
Read article →One receiving route does not mean one supplier for every function. A practical map of invoice delivery, software, reporting and contracts.
Read article →A proposal for a bounded public e-invoicing channel that preserves Peppol interoperability and leaves value-added services to voluntary choice.
Read article →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 →Peppol migration can change a receiving route. Genuine supplier independence also requires portable archives, evidence, integrations and workable exit terms.
Read article →Separate invoice creation, transport, metadata lookup and tax reporting before assigning responsibility.
Read article →Classify invoice information accurately and protect useful detail without pretending every field is a trade secret.
Read article →A necessity test for fields or justified groups of fields in tax reporting, without overstating GDPR or trade-secret protections.
Read article →Distinguish security exceptions, professional secrecy and commercial confidentiality, then design usable procedures.
Read article →Use certification as scoped evidence, then verify access, recovery, incident handling and exit.
Read article →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 →An e-invoicing continuity plan must distinguish technical delivery, business acceptance, recovery and legally authorised fallback procedures.
Read article →Responsibility in e-invoicing must connect operational duties, contractual remedies and data-protection roles without pretending one contract settles everything.
Read article →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 →A defensible e-invoicing launch requires versioned interfaces, realistic testing, legal clarity, support and evidence-based go-live decisions.
Read article →Nordic public-sector invoicing shows how shared standards, commercial providers and publicly supported access can coexist without being the same policy.
Read article →Public invoicing tools, central exchange systems and approved platforms represent different allocations of cost, access and responsibility—not one European template.
Read article →Structured invoices improve records and matching, but tax evidence still requires context about delivery, business use and the substance of a transaction.
Read article →Tax analytics can prioritise investigation, but accountable decisions require evidence, meaningful review and careful treatment of AI Act and GDPR rules.
Read article →A proposed public baseline for invoice exchange should preserve Peppol interoperability while specifying data boundaries, failure handling and accountable operation.
Read article →Why tax reform should examine opportunities for fraud before adding surveillance, without promising a fraud-proof system.
Read article →A case for investigating wider VAT reverse charge, with explicit limits on cash-flow claims and legal feasibility.
Read article →Testing differentiated gross receipts taxation without confusing it with sales tax or promising effortless revenue.
Read article →A practical evidence standard for comparing differentiated receipts taxation and wider reverse charge with the existing system.
Read article →A staged route from reform ideas to lawful testing, independent evaluation and a reversible public decision.
Read article →The future of AI will not be decided only by larger models or longer context windows. It will be decided by the engineering process around them: workflow, memory, rules, verification, review and evidence.
Read article →Vibe coding is fast, but without durable memory, reusable skills, deterministic verification and independent review, AI-assisted development can quickly become chaos.
Read article →Autonomous AI agents change enterprise security assumptions. The next generation of cybersecurity will be about continuously proving that infrastructure is still trustworthy.
Read article →NIS2, AI and modern infrastructure change risk management from a static register into a continuous evidence problem. Existing open-source tools solve parts of it, but the missing layer is proof of trust.
Read article →Real compliance is not about collecting policies and audit screenshots. It is about proving that important controls work when the business actually needs them.
Read article →The future of AI will not be defined only by what systems can do, but by who can govern their risks, security, accountability and auditability.
Read article →When HR uses AI to screen, score or evaluate people, the question is not only whether it is useful, but whether it is legal, safe, fair and governed.
Read article →Many companies spend thousands on cybersecurity tools, audits and certificates, but still lack ownership, decision-making and a managed security system.
Read article →A firewall, antivirus, backups and logs are not enough. The real question is whether information security is owned, controlled, evidenced and repeatable.
Read article →Modern IT is no longer a printer-support function. It connects legal, operational, manufacturing and cybersecurity responsibility into one risk space.
Read article →AML and KYC require customer due diligence, but they are not a blank cheque for uncontrolled data collection, AI scoring and permanent profiling.
Read article →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 →If I came into a company with no real cybersecurity, I would not start by buying tools or running an audit. I would start with ownership, decisions and control.
Read article →The fastest way to test whether a company has real cybersecurity is not to ask about tools. It is to ask who decides, who communicates and who owns the impact.
Read article →Regular cybersecurity training may create certificates, but real security depends on whether people know how to react when something actually happens.
Read article →Companies are adopting AI quickly, but the hard question is who can prove what tools are used, what data enters them, what decisions they influence and who is responsible.
Read article →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 →