KSeF as an entry point, not a standalone service
A structured invoice from KSeF has fields ready for extraction. But KSeF alone doesn't set up approvals in your company.
KSeF is a system where invoices carry structured fields: number, dates, parties, amounts, NIP, line items. This means the document can be transferred to the ledger without re-typing fields. It’s one entry point — alongside email and scans.
KSeF doesn’t replace the workflow
KSeF doesn’t arrange approvals in your company. It won’t tell you who should approve an invoice when the responsible person is absent. It won’t read an order pasted into an email body. It won’t remind you of deadlines.
That’s why we don’t sell “KSeF implementation” as a standalone thing. KSeF is one of the channels through which a document enters — the same as a mailbox or a scanner.
What KSeF changes in practice
When an invoice arrives from KSeF, the extraction already has structured fields. This shortens step two in the workflow: instead of pulling fields from a PDF or scan, the system receives them ready. But the rest of the workflow stays the same:
- Entry — the document enters the system from KSeF.
- Extraction — fields are already structured.
- Uncertain field — if something needs confirmation, it goes to a person.
- Approval — the right person approves.
- Save — the document goes to the ledger.
KSeF accelerates step 2. It doesn’t replace steps 3, 4, and 5.
What about documents outside KSeF
Not everything comes from KSeF. Orders in email bodies, scans, photos — these are also entry points to the workflow. That’s why we build one process that handles all channels: KSeF, email, scan, PDF. One workflow, not three separate ones.
KSeF is a good entry point. It’s not a service in itself.