KSeF and cash flow - what remains invisible without bank account data?

KSeF organises invoice information, but it does not show the complete flow of money through a business. A document may contain the amount, the parties to the transaction and the payment due date. It does not automatically confirm that the customer has paid or that the business has settled the liability. That requires data about actual transactions.

Only by combining KSeF data with bank account information can a business distinguish an expected payment from a completed one, detect a delay, recognise a partial payment and check whether the cash flow forecast is reflected in the account balance. Even then, the result should show the source of the information and the level of confidence because invoices and transfers do not always match in a straightforward way.

KSeF shows the document. The bank account shows the movement of money

The fundamental difference lies in the type of information. KSeF records a structured invoice. A bank account records an actual inflow or outflow of cash. Both sources describe the same business relationship from a different perspective, but neither provides the full picture on its own.

If a business issues a sales invoice for PLN 30,000 with a 30-day payment term, KSeF records the document and the receivable. This does not mean that PLN 30,000 is already available in the bank account. We explain this mechanism in more detail in Cash Flow vs Profit - Why Your Business Looks Profitable on Paper but Has No Cash.

The same distinction applies to costs. A purchase invoice may indicate a future expense, but the document alone does not show whether it has already been paid, which account was used or whether the business settled the entire amount.

What information can KSeF contain?

Since 1 February 2026, structured invoices have been issued using the FA(3) logical structure. According to information published by the Polish Ministry of Finance, the structure can contain seller and buyer details, monetary values, tax rates and additional information concerning payments, among other data.

Depending on the type of invoice and how it is completed, the data may include the payment due date, payment method, bank account, partial payment, advance payment settlement or discount. Some fields are optional. The absence of information from a particular field does not necessarily mean that no commercial arrangements exist. It may simply mean that the issuer did not include them in the structured invoice.

The scale of the system makes this data an important source of operational information. According to government data as of 30 June 2026, KSeF contained more than 512.7 million invoices and the number of issuers exceeded 2.28 million. However, the volume of documents does not change the system's core limitation: KSeF describes the invoice, not the complete settlement process.

Invoice, receivable, due date and cash - four different types of information

In day-to-day analysis, these concepts can easily be combined into one status. In reality, each answers a different question. An invoice documents the transaction. A receivable shows that the business expects to be paid. The due date sets the agreed deadline. Only the bank transaction confirms that the money actually moved.

Why is an invoice due date not a cash inflow forecast?

The date stated on the invoice tells the business when the payment should be made. A cash flow forecast needs to answer a different question: when is the money likely to enter or leave the account? These dates are not always the same.

The risk is not merely theoretical. In a Polish Economic Institute survey from April 2025, 44% of businesses described payment bottlenecks as a strong or very strong barrier to their operations. Among medium-sized businesses, the figure reached 48%. The findings are available from the Polish Economic Institute.

If a customer regularly pays seven days after the due date, a forecast based solely on the invoice date will consistently be too optimistic. If another customer usually pays early, the forecast may be overly cautious. The history of actual transactions therefore helps determine whether the document date is a credible reference point.

How can an invoice be matched with a bank transaction?

The simplest case occurs when the transfer amount matches the invoice amount, the counterparty is the same and the payment reference contains the correct invoice number. In practice, a system should compare several attributes at once: amount, date, account, counterparty, currency and transaction description.

The more attributes match, the higher the confidence in the result. However, not every connection should be treated as certain. In some situations, the result should be marked as probable or requiring review.

When is automatic matching not straightforward?

Effective monitoring should not hide these exceptions. If the match is incomplete, the user should be able to see how it was created and how much of the receivable remains outstanding.

Example: a PLN 36,900 invoice and two different payment dates

A business issues a sales invoice for PLN 36,900 gross with a payment due date of 20 October. KSeF shows the document, counterparty, amount and deadline. This information can be used to plan an expected inflow, but the receivable cannot yet be marked as paid.

On 18 October, PLN 20,000 arrives in the bank account. The payment reference does not contain the full invoice number, but the counterparty, account and date range match. The system can indicate a probable match and show PLN 16,900 as still outstanding. It should not treat the entire invoice as settled.

The remaining PLN 16,900 arrives on 23 October. Only after both transactions are connected with the document can the receivable be marked as fully settled. From a cash flow perspective, the business received part of the money before the deadline and the remainder three days late. A single status based only on the final transfer date would not show the complete payment pattern.

What does combining KSeF and bank data change in cash flow analysis?

Combining both sources makes it possible to separate planned values from confirmed ones. The forecast can be updated in line with actual events instead of remaining a static list of invoice dates.

In practice, the business can see:

• which receivables have actually been paid
• which inflows arrived earlier or later than expected
• how much of an invoice remains outstanding
• which customers regularly miss their payment deadlines
• whether planned expenses are covered by confirmed inflows
• which discrepancies require review instead of automatic assignment

If a payment does not arrive after the deadline, a system status does not replace communication with the customer or further action. A practical process is described in Customer Has Not Paid an Invoice on Time - What Should You Do Step by Step?.

What remains missing even when invoices and transactions are combined?

Even after KSeF is connected with a bank account, the analysis still needs additional context. Not every future expense results from an invoice already available in KSeF. Payroll, taxes, ZUS contributions, financing instalments, planned purchases, refunds and card expenses may need to be added separately.

The data also does not automatically explain why an event occurred. A late inflow may result from a customer's financial difficulties, a formal error, a dispute or a simple oversight. An unusual expense may be a mistake, but it may also be a planned investment. The analysis should help identify the change and its source rather than imply certainty when a human decision is still required.

A broader set of signals for regular monitoring is described in Weekly Financial Analysis for Businesses - 7 Signals Worth Monitoring. That article focuses on the rhythm of a financial review, while this material concentrates on the quality of the connection between a document and an actual payment.

What should a reliable payment status show?

Marking an invoice simply as paid or unpaid can be too simplistic. Useful information should answer at least four questions: which document is being analysed, which transactions have been connected with it, how much remains outstanding and how reliable the match is.

It is also useful to preserve a direct link to the source. If a user notices an unusual amount or disagrees with a match, they should be able to move directly to the invoice or transaction instead of starting another search across several systems.

This principle is consistent with good monitoring practices. An alert should notify the user about a new event, while a broader analysis should show what that event means in the context of other data. We explain the distinction between alerts and reports in How to Implement KSeF Alerts in Your Company.

How does Brieffin connect KSeF monitoring with cash flow analysis?

Brieffin monitors KSeF and sends alerts when new activity appears. Free KSeF alerts work without connecting a bank account. Users can receive information by email or Telegram and follow a direct link to the source of the event.

Connecting a bank account is optional and supports broader cash flow and customer analysis. Brieffin compares invoices with actual bank transactions to show changes in context. These features are currently being developed in beta and appear in the Weekly Brief preview. The current scope is described on the Brieffin page.

Brieffin uses read-only access. It can monitor connected data, but it cannot transfer money, issue invoices or modify documents. Users decide which sources they want to connect and can use KSeF alerts without sharing bank account data.

How can a business start using KSeF data to monitor cash flow?

The first step is to separate the document status from the payment status. An invoice that has been issued, received or is approaching its due date should not automatically be treated as cash.

Next, the business should determine which statuses will be updated using bank transactions. At a minimum, the process should cover full payments, partial payments, late payments and situations that cannot be matched with confidence. It should also define who reviews exceptions and what happens when an invoice passes its due date.

Monitoring new documents can be introduced separately. KSeF does not send standard automatic notifications for every new invoice, so a business can use software integrated with the system. We describe the available approaches in KSeF Notifications - Does KSeF Notify You About New Invoices and How Can You Enable Alerts?.

Summary

KSeF provides standardised information about invoices, but a document alone does not confirm the movement of money. A payment due date is not the same as the date on which cash arrives, and the full invoice value does not show whether the customer paid the full amount, made a partial payment or settled several documents in one transfer.

Combining KSeF with bank data makes it possible to update statuses using actual events. The greatest value comes when the system also shows the source of the information, the outstanding amount and any uncertainty in the match. This helps the business notice delays and discrepancies sooner and base its cash flow forecast on more than the dates stated on invoices.