Small businesses shouldn't have to organize their day around invoicing software. The software should adapt to how the business sells, collects payments, and collaborates with its accountant.
That is BillKO's starting point.
The problem isn't just creating invoices
An invoice can be created in many programs. The hard part begins when that same business sells to consumers and companies, accepts cards, runs a webshop, sends e-invoices, works with an accountant, or has to track multiple payment methods.
That is when a simple job easily splits into several tools:
a payment terminal;
software for B2C invoices and fiscalization;
a second process for B2B or B2G eInvoices;
a webshop plugin;
a spreadsheet for payment reconciliation;
separate files for the accountant;
BillKO does not start from the idea that each of those tools is bad. It starts by asking why the user has to enter the same sale multiple times.
What BillKO does today
Today, BillKO covers invoices, quotes, and advance invoices, Fiscalization 1.0, Fiscalization 2.0, sending and receiving e-invoices, payment integrations, issuing invoices on POS terminals, an Android application, eCommerce automation, API processes, and reporting.
A user can start with a single simple task—for example, issuing an invoice—without having to set up every other part of the product right away. When they need a POS, e-invoice, webshop, or additional report, they stay within the same system.
Simple does not mean poor
Many programs choose one of two extremes. They either offer very little, so the user quickly has to look for another tool, or they offer so many possibilities that everyday tasks are hard to find.
BillKO tries to maintain serious capabilities, but present them through familiar actions:
create an invoice or quote;
select the customer and items;
send the document;
collect payment on a terminal or online;
check the status;
open the report you need;
A good product does not ask the user to understand the internal architecture, tax protocols, or technical details of each integration. That information must exist when it matters, but it must not stand between the user and the task.
Fiscalization is a central part, not an add-on
Croatian businesses encounter Fiscalization 1.0, Fiscalization 2.0, and e-invoices all at once. The correct path depends on the customer, tax status, and transaction type.
That is why BillKO does not treat fiscalization as a separate technical option. It is part of invoicing, POS sales, eCommerce processes, and reporting. The user needs to choose the correct business case, and the system should handle the corresponding steps.
Building with partners and users
Payment and POS integrations depend on reliable cooperation with partners. GDPR and security practices require expert processes. Good eCommerce automation requires an understanding of the platform, payments, and invoices.
However, the most important source of development remains actual user processes. When an owner says they enter payments twice, an accountant asks for a better export, or an integrator needs a clearer API event, that is not just a request for a new feature. It is a signal that everyday work can be simplified.
Development that mirrors real work
We are developing BillKO from concrete user tasks: less retyping, clearer statuses, simpler billing, and better collaboration with the accountant.
We will explain every major update through a real-world example and show how it fits into everyday work.
Get to know BillKO through your work
The best way to evaluate BillKO is not a general tour of every menu. Choose one real task: an invoice, an e-invoice, fiscalization, POS sales, a webshop order, or a report. We will use it to show how BillKO works and where it can eliminate a manual step.
