Preparing the requested content…
Online invoices, QR payments, PDF, XML, and sending workflows.
From company profile through PDF output to QR payment and payment follow-up.
Start with the business details, rather than the PDF design. The invoice must belong to the correct issuing company and customer. Issuing, sending and payment are separate steps; successfully saving one does not confirm the others.
Read articleAn invoice payment QR helps a customer enter a bank transfer without typing every detail. Scanning it is not payment. It differs from an eKasa receipt QR used to identify or verify a cash-register receipt.
Read articleBefore your first invoice, prepare the information you will reuse. This checklist focuses on getting started as a sole trader; the related guides cover detailed creation, numbering and QR checks.
Read articleA number helps identify a document unambiguously. Document type defines its purpose, while a recurrence schedule determines when another occurrence is prepared. Neither replaces the numbering sequence.
Read articleRecurrence reduces repeated data entry. It does not mean prices, dates and service scope remain correct every month. Review the schedule and the individual invoices separately.
Read articleNo single checklist applies without exceptions to every document. First establish who is invoicing, what is supplied and which treatment applies. This article provides a review workflow, not certification of a particular invoice’s tax compliance.
Read articleA spreadsheet can speed up preparing several invoices, but one incorrect column can affect the whole import. Review the preview first, then the resulting drafts, and only afterwards decide whether to issue them.
Read article
