Invoice Workflow in a Company: Where It Stalls and What to Do About It

"Has anyone seen that invoice?" — what invoice workflow looks like in practice

This question is asked in companies every single day and it usually means the same thing: the document is sitting on someone's desk, in someone's inbox or in a pile awaiting approval, and the payment deadline passed last week. Nobody did it on purpose. The process simply has no place where you can see where the invoice is right now.

This article describes what the invoice workflow process looks like in a company of 5–50 people, where it actually stalls and what can be done about it. A warning up front: in some cases the answer is not buying an electronic document workflow system. Sometimes it is enough to tidy up what you already have and automate three steps. We will say when that is the case and when it is not.

What is invoice workflow and what the invoice workflow process consists of

Invoice workflow is the path a cost document travels from the moment it arrives at the company through to posting, payment and archiving. In most companies it consists of seven stages — whether or not anyone ever wrote them down.

Stage	What happens	Typical duration with paper invoice workflow
1. Arrival	A VAT invoice arrives by email, by post, through KSeF or is carried in by an employee	0–3 days
2. Document registration	Someone assigns a number, enters it in the register, scans it	1–2 days
3. Substantive verification	The person who ordered confirms the goods or service were actually delivered	2–7 days
4. Cost coding	Assignment to a cost centre, project, ledger account	1–3 days
5. Multi-level approval	Manager, then the board above a value threshold	2–10 days
6. Document entry and payment handling	Posting in the system, issuing the transfer	1–2 days
7. Invoice archiving	A binder or a folder nobody opens until an audit	—

Add up the right-hand column. It comes to somewhere between one and four weeks, and the records in companies without an organised process run longer still. Payment terms are usually 14 or 30 days. It is worth noting that other documents travel the same path — a proforma invoice, corrections, debit notes — and each of them needs its own route, though usually nobody has defined one.

Electronic invoice workflow — how it differs from paper

Digital invoice workflow is the same process, except the document does not move physically and every stage leaves a trace. In practice, electronic invoice workflow changes three things:

• Parallelism instead of sequence. Substantive verification and cost coding can happen at the same time, because they are not competing for the same piece of paper. This is the shortest route to reducing invoice cycle time.
• Transparency of document workflow processes. At any moment you know who is holding the document and for how many days. This eliminates the question in the title.
• Fast invoice search. Finding a document from a year ago takes a dozen seconds instead of half a day in the archive.

Benefits of electronic document workflow — what you actually measure

Electronic invoice workflow is often sold with slogans about digital transformation. Below is the same thing, only in numbers you can check after a quarter.

The benefits of electronic workflow are worth reducing to indicators from the outset, because only those survive contact with reality six months after go-live:

• Invoice cycle time — the average number of days from arrival to posting. With a well-designed process the reduction is typically 30–70%.
• Share of overdue documents — how many invoices missed the payment deadline because of the process rather than a lack of funds.
• Number of corrections and errors — error reduction after invoice workflow automation usually falls in the 80–95% range.
• Budget control during the month — whether management knows how much cost has already arrived before accounting closes the period.
• Time needed to find a document — the single best indicator of the quality of document archiving.

These are ranges, not promises. The result depends mainly on how many stages you manage to remove, not on how good a tool you buy. Invoice workflow management starts with a decision about the shape of the process, not with choosing a vendor.

Five places where the invoice workflow process stalls

1. Invoices arrive through five channels at once. Email to accounting, email to a salesperson, paper at reception, a supplier portal, and now KSeF on top. Each channel has a different person at the entry point and a different moment of document registration. Until there is a single point of entry, you cannot measure how long anything takes.

2. Nobody knows who is supposed to approve. The approval rule lives in the head of the bookkeeper and goes roughly like this: "up to five thousand it is the manager, above that the CEO, but if it is marketing then it is always Kate." When Kate is on holiday, the process stops. Multi-level approval without written rules and without deputies is the most common cause of delays in companies of this size.

3. Duplicates. The supplier sends the invoice by email, then again through KSeF or by post. Without duplicate invoice identification the same document enters the workflow twice, sometimes gets approved twice, and in the worst case gets paid twice. Recovering an overpayment from a counterparty takes months.

4. Why the invoice was rejected — and nobody found out. The invoice comes back from approval with the reason "does not match the order" or "no proof of delivery." The reason stays in one person's mailbox. The supplier calls two weeks later to ask about payment, and the investigation starts from zero. In an organised process the rejection reason is attached to the document and visible to anyone who opens it.

5. Manual re-keying of invoice data. Number, tax ID, net amount, VAT, payment date, line items — all the invoice data typed from the screen into the accounting system. At two hundred documents a month that is over a dozen hours of work and dozens of chances for a typo that will only surface at month-end close.

What handling invoices without automation actually costs

Before you start talking about tools, do the maths on the process. The formula is simple and needs no consultant:

Annual process cost = (invoices per month × average handling time per invoice in hours × hourly labour cost) × 12

An example for a company receiving 202 cost invoices issued by suppliers each month — let us round it to 200 — where handling one takes 25 minutes spread across four people, at an hourly cost of 60 PLN:

200 × 0.42 h × 60 PLN × 12 = roughly 60,000 PLN a year — in human labour alone, before the cost of delays.

On top of that come costs nobody books separately: lost early payment discounts, interest on missed deadlines, management time spent firefighting at month-end close, and the cost of mistakes — overpayments, double payments, invoices paid even though the goods never arrived.

The real saving from automating this process is usually 0.5–2 full-time equivalents, and the return on investment comes in 6–18 months. If your calculation comes to less than 20,000 PLN a year, it is probably not worth implementing anything — and that is an honest answer you will rarely hear from someone selling a system. Cost management in a company starts with being able to calculate what the act of managing itself costs.

KSeF and electronic invoice workflow — the national workflow system does not solve it

This is the most common misunderstanding of recent months, so it is worth defusing.

Poland's National e-Invoicing System (KSeF) has been mandatory since 1 February 2026 for the largest taxpayers and since 1 April 2026 for all other companies. Until 31 December 2026 a transitional period applies, with a limit of 10,000 PLN gross per month for invoices issued outside the system. From 1 January 2027 the transitional period ends, and B2B invoices outside KSeF carry penalties of up to 100% of the VAT amount.

What the path of an invoice looks like in KSeF and in document workflow

KSeF is responsible for one stage: delivering the document. The invoice lands in the system and can be downloaded from there. That is all. The national document workflow system does not know who in your company is supposed to approve it, which cost centre it belongs to, whether the goods actually arrived, or whether the same invoice already came by email.

In other words: KSeF replaces stage one from the table above. Stages two through seven remain exactly as they were. Companies that expected the KSeF obligation to solve their chaos are now discovering that they have gained one more entry channel into an already fragmented process.

On the other hand, KSeF provides something that did not exist before: structured data. The invoice arrives as an XML file with unambiguously labelled fields, so there is no need to recognise it with OCR or re-key it. This genuinely makes automated accounting processes easier — provided that someone picks up that data and routes it onward. KSeF integration and automating what happens after an invoice is downloaded is covered on a separate page.

Do you actually need an electronic document workflow system?

Here begins the part you will not find on software vendors' websites. There are three scenarios and buying a system makes sense in only one of them.

Scenario A: you do not need to buy a workflow system

When: fewer than 50 cost invoices a month, one or two approvers, simple rules, everyone sits in one office.

An electronic workflow system would cost more here than the entire process it is meant to improve. It is enough to tidy up what you have: one email address as the point of entry, a shared folder with a consistent file naming convention, an approval rule with deputies written down on a single sheet of paper. It takes an afternoon and costs nothing. Document management in an organisation of this size does not require a platform — it requires one shared convention that everyone follows.

Scenario B: invoice workflow automation on the tools you already have

When: 50–500 invoices a month, several approvers, you already have an accounting system and email, and the problem is that none of it is connected.

This is the situation of most companies with 5–50 people and the most frequently overlooked option. You do not buy a new platform. You take the tools you already have and connect them with automation that performs specific tasks:

• collects documents from every channel, including KSeF, and brings them into one place
• checks whether a document with that number and tax ID has already been through — duplicate invoice identification at the entry point
• reads the invoice data with OCR or straight from the XML and handles document entry into the accounting system without re-keying
• routes the invoice to the right person according to the value threshold and cost category
• reminds after two days, escalates after five
• triggers a counterparty check — VAT white list verification happens before the payment is issued, not after
• archives with an index you can actually search

Automation of invoice workflow processes in this variant costs a fraction of the price of a platform, and delivery time is measured in weeks rather than quarters. You do not get a pretty dashboard for it — you get a working process. This is what process automation looks like in practice, as opposed to implementing a system.

Scenario C: implementing electronic workflow as a separate system

When: more than 500 invoices a month, multi-level approval with genuinely complex rules, several companies or branches, audit requirements, budget control at project and cost-centre level.

Then a dedicated electronic document workflow system is justified and implementing a workflow system will pay off despite the high entry threshold. An honest caveat: even in this scenario, buying the licence settles nothing on its own. Implementing electronic workflow on top of a disorganised process gives you a disorganised process, only faster and more expensive.

Comparison of systems: Symfonia eDokumenty, Comarch BPM, Plus Workflow and ELO

If you landed on scenario C, below are the four solutions most commonly encountered on the Polish market. We do not sell any of them, so the description is what it is.

System	Works best for	What to watch out for
Symfonia eDokumenty	Companies already running on Symfonia — invoice workflow integrated natively with Symfonia Finanse i Księgowość and Symfonia Handel, with no bridges to build	Outside the Symfonia ecosystem the advantage disappears; integration with a foreign ERP is an ordinary integration project
Comarch BPM	Companies on Comarch ERP for which business process management is a broader topic than invoice workflow alone	A tool more powerful than the needs of a typical 5–50 person company; it is easy to overpay for features nobody will use
Plus Workflow	Elaborate, multi-level approval paths and processes reaching beyond invoices themselves	Requires the process to be genuinely designed before you start — it does not work as an out-of-the-box solution
ELO	Financial document management in the broader sense — archive, retention, compliance with legal requirements	The centre of gravity is on document management rather than the workflow itself; for a narrow need it can be excessive

Choosing between Symfonia eDokumenty, Comarch BPM, Plus Workflow and ELO comes down in practice to two questions: which accounting system it has to integrate with, and how unusual your approval rules are. If you run on Symfonia, Symfonia eDokumenty saves you an integration project. If on Comarch — Comarch BPM does the same. For unusual approval paths Plus Workflow gives more freedom, and where the emphasis falls on archiving and compliance with legal requirements, ELO comes out stronger.

And one point that runs through all four: none of these systems will design the process for you. Comarch BPM, Plus Workflow or Symfonia eDokumenty will reproduce whatever you describe to them — including the mess, if that is what gets described.

Integration with ERP systems — does invoice workflow require it

Not always, but almost always worth it. Without integration with ERP systems the workflow ends at approval, and somebody still has to re-key the data into the accounting system — which leaves the most labour-intensive and most error-prone stage of the whole process in place.

In practice, integrating invoice workflow with an accounting system means one of three things:

• Via API — the cleanest solution, available in newer systems. Data flows both ways, the document status is consistent everywhere and integrated invoice workflow runs without manual synchronisation.
• Via file import — the system generates a file in a format accounting can load. Less elegant, works well.
• Via a robot — if the application has neither an API nor an import, the typing itself can be automated. A last-resort solution, but sometimes the only one possible in older systems.

The most common in companies of this size are Comarch ERP, Symfonia Finanse i Księgowość and Symfonia Handel. All of them can be connected to a workflow — what differs is the amount of work.

Symfonia Finanse i Księgowość and Symfonia Handel exchange data with a workflow most easily when Symfonia eDokumenty stands on the workflow side. With Comarch ERP, Comarch BPM plays the analogous role. In both cases integrating invoice workflow with a foreign system is feasible, it simply stops being configuration and becomes a project — and that is how it has to be priced.

Symfonia Handel tends to be overlooked in the analysis, even though part of the purchasing documents originate there; if the workflow cannot see it, cost invoices issued on the trading side go back to manual re-keying. More on how we approach connecting systems can be found under systems integration.

How to implement electronic workflow for cost invoices — five steps

Step 1: measure the current process. For two weeks, note against every invoice the arrival date, the channel, the registration date, who approved it and when, the posting date and the payment date. It is boring and it is exactly the work everyone skips. Without it you will have nothing to compare the effect against and you will not learn which stage is actually the bottleneck — and it is almost never the one everyone bets on.

Step 2: simplify before you automate. Look at the measured process and ask of every stage: what happens if we remove it? Usually it turns out that one approval is historical, one register duplicates another, and one person in the chain only passes things along. This is the moment when the most important decision of the whole project is made. Automating a bad process gives you a bad process running faster — chaos in higher resolution, with a cost invoice for the implementation.

Step 3: write down the rules. Value thresholds, who approves what, who deputises for whom during absences, after what time escalation happens, what becomes of a rejected invoice. One sheet of A4. If it will not fit on one page, the process is too complicated and you go back to step two.

Step 4: choose the scope of the first rollout. Not the whole process at once. One category of documents — for instance only cost invoices from regular suppliers, no project ones and no foreign ones. One team. Two to four weeks. You measure the effect on that slice and only then extend.

Step 5: measure after go-live. The same indicators as in step one: invoice cycle time, share of overdue documents, number of duplicates, number of corrections. If after three months there is no visible difference, something went wrong and it needs to be named rather than left to fix itself.

Invoice archiving and compliance with legal requirements

In electronic invoice workflow, document archiving is the stage you think about last and the one that decides whether an audit takes an hour or a week. Invoices must be kept until the tax liability limitation period expires, in a form that guarantees legibility, integrity and authenticity of origin.

For the workflow this means three practical requirements. Invoice archiving has to preserve the document in the form in which it arrived, not merely the data extracted from it. It has to be retrievable — meaning there has to be an index that lets you find a document without going through everything. And it has to preserve the approval trail, because that is what answers the auditor's question of who approved a given cost.

Invoices from KSeF have an advantage here, because the system stores them on its side for 10 years. That does not, however, release you from the obligation to keep your own archive of documents that do not pass through KSeF.

Common mistakes when implementing a workflow system

• Treating the purchase of a tool as the start of the project. Electronic invoice workflow starts with a decision about the process, not with signing a licence agreement.
• Buying a tool before measuring the process. The order is backwards. The result: a system fitted to an idea of the process rather than to the process.
• Reproducing paper invoice workflow one to one. If there were four signatures in the paper version because the document physically travelled, there do not need to be four approvals in the digital one.
• No deputies. The most common reason people go back to email after a month. One absence blocks everything and the process loses credibility.
• Implementation with nobody accountable on the company side. A project without an owner ends as a platform sitting unused after six months.
• Automating the exceptions instead of the rule. Eighty percent of invoices follow the same path. Automate those eighty and leave the exceptions to people — trying to handle every edge case doubles the cost and triples the delivery time.
• Skipping documents other than the VAT invoice. Corrections, the proforma invoice, debit notes and bills also go through the process. If they have no path, they will go back to email and drag the rest with them.

Frequently asked questions

What is electronic invoice workflow and how does it work in practice?

It is a process in which an invoice exists only in digital form from arrival through to archiving, and every stage — document registration, verification, cost coding, approval, posting — leaves a record of who did what and when. In practice it means that at any moment you can see who is holding the document and for how many days.

What are the benefits of electronic document workflow?

Shorter invoice cycle time, fewer overdue documents, no double payments, fast invoice search during an audit, transparency of document workflow processes for management and real budget control during the month rather than after it closes.

Does invoice workflow require ERP integration?

Technically no, practically almost always worth it. Without integration with ERP systems you are left with manual document entry into the accounting system, the most time-consuming stage of the whole process.

Does KSeF solve invoice workflow?

No. The national invoice workflow system is responsible for delivering the document, not for what happens to it inside the company. Approval, cost coding, substantive control and payment handling remain on your side.

How long does implementing electronic invoice workflow take?

It depends on the scenario. Tidying up the process without tools — a few days. Invoice workflow automation on existing systems — 2–4 weeks. Implementing a workflow system in the class of Symfonia eDokumenty or Comarch BPM together with ERP integration — from several months.

From how many invoices a month does automation pay off?

There is no single threshold, because what counts is the time spent handling invoices, not their number alone. Use the formula from the cost section. Below roughly 20,000 PLN of annual process cost it is hard to justify any implementation at all.

What next

If after reading this you do not know which scenario you are in, that is normal — without measuring the process it cannot be settled from an armchair.

During a free consultation we walk through your current invoice workflow process, calculate the annual cost of handling invoices and tell you which scenario you qualify for. If it turns out to be scenario A and tidying up what you have is enough — we will say so plainly and there will be no invoice for the consultation. Book a free call, check the implementation pricing or see what document reading by AI agents looks like at the registration stage.