Eesti Billing

• Screenshots
• Requirements
• Installation
• Options
• Configuration
• The issuer
• Numbering series
• Documents
  • From code
• Customers
• Returns
• E-invoicing
• Signing
• Receipts
• Expenses
• Repairs
• Commands
• Translations
• Testing
• Security
• License

Invoicing for companies established in Estonia, the way Estonian software does it — inside a Filament 5.x panel. Quotes, orders, delivery notes, proformas, invoices, receipts and credit notes in one numbered cycle; VAT decided by customer with the VIES proof stored; the payment reference (viitenumber) every Estonian bank matches on; the monthly KMD with its INF annexes, the VD and the quarterly OSS as the files e-MTA imports; e-invoices in EN 16931 or e-arve 1.2 through your operator; digital signing with ID-kaart, Smart-ID or Mobile-ID; receipts on thermal printers.

• Nothing is fiscalised. Estonia has no per-document reporting, no chained records, no tax QR. A document is a document; the returns are built from them once a month.
• VAT by customer. Estonian VAT at home (24 %, with 13 % and 9 % per line), reverse charge for EU businesses with a valid number, the customer's rate for EU consumers under OSS, zero-rated outside the Union, and an unregistered issuer handled correctly.
• Viitenumber on every invoice. 7-3-1 check digit per the Estonian Banking Association, per invoice or per customer, printed and carried in the e-invoice and the XML.
• Payment terms Estonian companies expect. Due date from the payment term, late interest per day printed on the invoice, bank accounts in any country.
• Everything else the fiscal plugin taught us: draft → complete → convert forward, template designer for A4 and receipts, ESC/POS and print agent, PDF through mPDF or Gotenberg, received invoices and expenses with OCR, recurring documents, catalog, audit trail, permissions.

#Screenshots

#Requirements

• PHP 8.4+, Laravel 13, Filament 5.x
• A PDF engine you choose: ->mpdf() (bundled) or ->gotenbergPdf() (Docker)
• For signing: komma-softhouse/asice-engine; for Smart-ID and Mobile-ID, a relying-party account at SK ID Solutions, entered on the Signing settings page

#Installation

composer require komma-softhouse/filament-eesti-billing
php artisan migrate
php artisan filament:assets
php artisan eesti:selftest

filament:assets publishes the plugin's browser assets (the Web eID library among them). Run it again after every update; hosts created with filament:install already do so from composer.json's post-autoload-dump. eesti:selftest reports what is missing, with the command to run for each item.

Register the plugin in the panel provider and switch on what you need:

use Komma\EestiBilling\EestiBillingPlugin;

->plugin(
    EestiBillingPlugin::make()
        ->navigationGroup('Billing')
        ->mpdf()                 // or ->gotenbergPdf('http://gotenberg:3000')
        ->customers()
        ->expenses()
        ->reports()
        ->einvoice()
        ->signing()
        ->escPos()
        ->printAgent()
        ->ocr()
        ->catalog()
        ->repairs()
        ->dashboardWidgets()
        ->brandingDisk('s3'),
)

Open Issuers, type your registry code and press the magnifier: name, address, contact and VAT number come from the Business Register. Add the bank accounts and save. Documents can be issued from that moment.

#Options

#Configuration

config/eesti-billing.php mirrors the options (EESTI_* env keys) and adds: connection for the tables, domestic_rate, VIES and Business Register settings, kmd.inf_threshold, and permissions — every panel action on by default, switchable per installation or per user through a Gate named eesti.{ability}. Signing credentials live on the Signing settings page; the signing.* keys are only a fallback.

Every identity field is masked and validated: registry codes, VAT numbers, IBAN, BIC, postal codes, phones and personal codes accept only what can be valid, and the Estonian check digits are verified.

#The issuer

Company (registry code with lookup, address, document language), VAT (registered, KMKR number with VIES check, OSS), bank & payment (accounts in any country, the one printed on documents, payment term, late interest, viitenumber policy), e-invoicing (operator and credentials, default format), signing (which ways, default signer), look (logo, accent, footer). Each tab has its own "How does it work?" slide-over.

#Numbering series

One series per document type and issuer, with {PREFIX}, {YEAR}, {STORE} and {TERMINAL} markers. The Estonian VAT Act asks for sequential numbers that never repeat and never go backwards, so changing a format closes the series and opens a new one. The form previews the next number and the payment reference it will carry.

#Documents

Drafts are free to edit. Complete takes the number from the series, freezes the document, decides the VAT regime and stores the VIES consultation number, computes the viitenumber, sets the due date and copies the late-interest rate. Completed documents never change; a mistake is corrected with a credit note that references the original. Quotes, orders, delivery notes and proformas convert forward into an invoice or a receipt.

Every completed invoice offers: PDF (A4 or receipt paper), XML EN 16931, XML e-arve 1.2, e-mail with the PDF, e-invoice through the operator, signing, and the signed container (.asice) once signed.

#From code

use Komma\EestiBilling\Facades\EestiBilling;

$invoice = EestiBilling::completeDocument($draft);
$pdf = EestiBilling::documentPdf($invoice);
$xml = EestiBilling::documentUbl($invoice);
EestiBilling::sendEInvoice($invoice);
$credit = EestiBilling::creditNote($invoice, CreditReason::Return);
EestiBilling::printTicket($receipt);

Veto issuing from the host (quotas, plans, anything):

EestiBilling::beforeIssuing(fn (string $operation, Issuer $issuer): ?string => $issuer->documents()->count() >= 100 ? 'Plan limit reached' : null);

Events after commit: DocumentCompleted, DocumentVoided, ExpenseBooked, IssuerActivated.

#Customers

A directory per issuer: business or consumer, registry or personal code, VAT number with VIES, the regime the engine would apply today, payment term, late interest, reference base (for per-customer viitenumbers), e-invoice format, and whether the customer is a registered e-invoice recipient. For an Estonian company, the Business Register lookup (by code or by name) fills name, address, contact, VAT number and the e-invoice flag.

#Returns

• KMD — monthly VAT return, boxes filled from completed sales and booked purchases (24/13/9 %, reverse charge, export, OSS, input VAT, acquisitions), INF A and INF B above the threshold, one XML for e-MTA (or X-tee).
• VD — intra-Community supply per customer VAT number, goods and services apart. XML and CSV.
• OSS — quarterly, per Member State and rate; shown only when an issuer is OSS-registered.

Each page: issuer and period, Calculate, e-MTA file, and a "How it works" slide-over.

#E-invoicing

Formats: EN 16931 UBL (default since July 2025) and e-arve 1.2 (by agreement, and for bank standing orders). Operators: Finbite and any Peppol access point with an HTTP API; register yours with app(EInvoiceService::class)->register('key', YourOperator::class). Before sending, the plugin checks the Business Register: a customer registered as e-invoice recipient is flagged in the dialog.

#Signing

Any completed document: PDF + XML into an ASiC-E container with an XAdES signature. ID-kaart through the Web eID browser extension; Smart-ID and Mobile-ID through SK's services with the verification code on screen. The container engine is komma-softhouse/asice-engine; bind another SignsContainers to use your own.

What each way needs:

Time-stamps come from tsa.sk.ee and revocation from SK's OCSP responder; both are reachable without any agreement. eesti:selftest checks the published library and the HTTPS scheme.

Credentials and endpoints for Smart-ID and Mobile-ID are set on the Signing settings page of the panel (encrypted at rest, with a Test connection button per service and a demo/production switch); the .env keys are only a fallback for hosts that prefer them.

What the ID-kaart dialog says when something is missing, and what it means:

#Receipts

A receipt is Estonia's simplified invoice, for sales up to the legal limit without a named customer. Templates for 80 and 58 mm paper, ESC/POS bytes for your own print stream or the print agent for a paired Windows printer; Z and X reports and movement lists as in the fiscal plugin.

#Expenses

Received invoices by hand or from a photo (OCR), booked with their input VAT and deductible share; they feed box 5 and INF B. Supplier credit notes subtract.

#Repairs

With ->repairs(): repair orders from reception (device, condition, accessories, reported issue, photos) through diagnosis, quote, parts, repair and delivery. A deposit receipt and a repair report print from their own template; the customer follows the order on a public tracking page; delivery issues the receipt or invoice from the labour and parts lines.

#Commands

• eesti:selftest — database, licence, PDF engine, VIES, Business Register, issuer completeness, operator, signing engine, Web eID library, HTTPS.
• eesti:recurring:run — generate the recurring documents due today.
• eesti:license — licence status.

#Translations

English, Estonian, Russian and Spanish for the panel; Estonian and English on documents.

#Testing

composer test

#Security

If you discover a security issue, email info@kommasofthouse.com instead of using the issue tracker.

#License

Commercial. Sold and activated through Anystack. See LICENSE.md.