The invoice or order flow: from arrival to the system
What one process looks like when we take it on at the start: the document arrives, parsing extracts fields, a human stays with the uncertain field, the record goes to your system.
The most common picture in a company: an invoice or an order arrives by e-mail, as a scan or from KSeF. Someone opens the file, retypes the number, the amount and the NIP, checks whether the document has already been there, and waits for the approval of a person who is out today. Meanwhile someone fills in a form, the message lands in a shared inbox, and a week later nobody has it on their card.
That is one flow. We take it whole.
Five steps
- Arrival. The document enters the flow the moment it arrives — with the scan or the source file.
- Parsing. We extract the fields this flow needs: number, dates, parties, amounts, NIP, line items.
- The uncertain field goes to a human. The person approves or corrects one field — they don’t retype the whole document.
- Record. After the right person approves, the record goes to the system you already use.
- Visibility. You can see whose desk the document is on. If that person doesn’t react, the task moves to the substitute from the flow map.
What stays with the human
The human stays with what cannot be reconstructed from the file: a disputed amount, a missing order, an exception the rule doesn’t describe. The rest never goes back to manual retyping.
KSeF is an entry point, not a service
A structured invoice from KSeF has a number and can be moved to the ledger without retyping fields. That is one entry point — next to e-mail and a scan. KSeF alone doesn’t arrange approval in the company and won’t read an order pasted into a message body. That is why we don’t sell “KSeF deployment” as a separate thing.