Skip to Content

Dig.IT grant settlement: the obligations after signing that you should know before you apply

Signing the Dig.IT agreement is the start of your obligations, not the end. Indicators, documentation and project durability decide whether the money stays.
September 17, 2026 by
HADRON FOR BUSINESS SP Z O O, Tomasz Leppich
| No comments yet

Note for readers outside Poland: Dig.IT is a Polish grant programme run by ARP. Under the call rules, only micro, small and medium-sized companies doing business in Poland can apply. The funding decision arrives by email, someone opens the champagne, and then nobody reads past the first paragraph of the contract. That is a mistake, because Dig.IT grant settlement begins at exactly that moment, not at the end of the project. A funding agreement is not a formality to sign and file away in a drawer. It is a set of obligations spread over years: indicators to maintain, documentation to collect on an ongoing basis, and a project durability period in which the company has to prove that the system actually works, not just that it was purchased. Nobody writes about life after the grant is awarded, because all the attention goes to the application itself. Yet it is this stage that decides whether the funding is paid out in full, or whether the company hands back part of the money years later.

A note on timeliness: this article describes the logic of obligations after signing the agreement, based on the rules of the Dig.IT 1/2025 pilot. Status as of 13 October 2026: the rules for the 2/2026 call are published on digit.arp.pl (applications from 2 to 30 November 2026), and the detailed provisions on indicators, documentation and the durability period may differ from the pilot. Before you sign an agreement, always check the current status of the call and the latest version of the rules directly on digit.arp.pl.

What happens right after signing the funding agreement

Signing the agreement in the Dig.IT programme (ARP, FENG 2.21) opens the project delivery stage, it does not close it. From that moment the company operates according to the physical and financial schedule attached to the agreement: which tasks, in what order, by when and for how much. Any departure from that schedule, for example a change of supplier, a shift in the implementation deadline or a different functional scope of the system than the one described in the application, usually requires notifying the funding institution, rather than being a decision the company can make on its own.

In practice this means that the digitalisation project stops being solely a management decision and becomes a matter of reporting. The company has to be able to answer at any moment: where are we against the schedule and budget from the agreement. Your company may qualify for support and sign an agreement, in line with the programme rules, but that is only the beginning of the relationship with the funding institution, not its end.

Project indicators: what has to be measured and why it is not a formality

Every funding application contains a set of project indicators: numbers that the company commits to achieving through the implementation. These may be output indicators, for example the number of system modules deployed or the number of employees trained, and result indicators, for example an increase in process efficiency or the level of use of new digital tools in the company. These numbers are not decoration on the application. They are the basis for settling the project and the basis for inspection in the years that follow.

The problem is that manufacturing companies often enter indicators into the application under the pressure of the call deadline, without thinking through how they will realistically measure them a year or two after the implementation is finished. The declaration "we will halve the time it takes to prepare a quote" sounds good in a business case, but it requires a system that actually records the quote preparation time, both before and after implementation. Without such measurement the company will not prove that it reached the indicator, even if it genuinely became faster.

That is why it is worth planning indicators together with the system configuration from the outset, not separately. An ERP-class system, implemented correctly, itself generates the data needed for settlement: order fulfilment time, inventory levels, the number of transactions processed automatically rather than manually. If that data has to be collected separately, in a spreadsheet next to the system, the risk of error and of a dispute with the funding institution grows.

Documentation: what has to be collected throughout the whole project

Settlement of a digitalisation grant rests on documents, not on declarations. In practice the company should gather on an ongoing basis, not only before an inspection:

  • Invoices and proof of payment for every cost item in the project budget, matching in amount and description what was recorded in the application.
  • Acceptance protocols for the implementation of the system, modules, training and other services covered by the funding.
  • Supplier contracts, including with the implementation partner for the ERP, MES or CRM system.
  • Proof of indicator achievement: reports from the system, numerical summaries and, in some cases, documentation confirming that employees were trained.
  • Correspondence with the funding institution, including all reported changes to the project and the approvals obtained for them.

Companies that collect these documents on an ongoing basis get through inspection and settlement far more smoothly than those that try to reconstruct the project history a month before the report deadline. It is also worth remembering that documentation of a digitalisation project naturally overlaps with another obligation that concerns practically every company in Poland regardless of funding: the obligation to receive invoices in KSeF from 1 February 2026, and for most B2B transactions also the obligation to issue invoices in KSeF from 1 April 2026 (for the smallest taxpayers, with gross sales up to PLN 10,000 per month, from 1 January 2027). An ERP system deployed under Dig.IT, if it includes an invoicing module integrated with KSeF, makes grant settlement and compliance with the new obligation easier at the same time, because invoices and cost evidence come from one consistent data source.

Project durability: obligations that continue after implementation ends

The least known element of a funding agreement is the project durability period. This is the time after the formal completion of implementation, in which the company still has obligations towards the funding institution: it must keep the purchased hardware and software, it may not dispose of it or stop using it in line with the project's purpose, and it has to be ready for an inspection confirming that the system actually works and that the indicators are holding at the declared level, not only on the acceptance date.

In practice this means that a company which deployed an ERP system with an MRP module thanks to the funding, and a year later gave it up, went back to manual planning or migrated the data to a completely different tool without reporting the change, exposes itself to an obligation to repay part or all of the funding. Project durability is one of the main reasons why the choice of system and implementation partner at the start matters far more than the implementation price alone. A system that the company abandons after a year, because it turned out to be too rigid or poorly matched to the production processes, creates a financial risk that does not end the moment the project is accepted.

Dig.IT grant settlement: a timeline of obligations over time

The table below sets out what the life of a project after signing the agreement actually consists of, from delivery to the end of the durability period.

StageWhat it coversTypical risk
Project deliveryImplementation in line with the physical and financial schedule from the agreementChange of scope or supplier without notifying the institution
Final settlementPayment request, complete set of invoices, acceptance protocols and indicator evidenceGaps in documentation collected at the last minute
Project inspectionVerification that expenditure and indicator achievement match the agreementIndicators that cannot be measured in the system, because they were not planned at the start
Durability periodKeeping the system and indicators for the period stated in the agreementGiving up the system, switching tools or the absence of real use

Why the choice of implementation partner decides settlement, not just implementation

Companies that treat funding and implementation as two separate tasks, one for the finance department and the other for the IT supplier, most often fall into the same traps: indicators written into the application that the system does not measure, documentation collected after the fact, and a system architecture that will not survive the durability period without costly fixes. An implementation partner who understands the logic of the grant designs the system from the outset so that it generates the data needed for settlement, not just so that it works operationally.

Wdrażamy systemy Odoo od 2011 roku, dla klientów w trzech krajach: w Polsce, Niemczech i Belgii, jako partner Odoo od około 2011 roku. Pierwszy klient dostał działające demo dzień po pierwszej rozmowie, a pełny system ruszył po dwóch tygodniach. Ta firma została później przejęta przez niemiecką grupę giełdową, a ten sam rdzeń systemu działa w niej do dziś, mimo zmiany właściciela. To dobra ilustracja tego, dlaczego system budowany z myślą o trwałości, nie tylko o odbiorze, opłaca się długo po podpisaniu ostatniego protokołu. Więcej o samym procesie wnioskowania o grant piszemy na naszym blogpage.

Frequently asked questions

When do the obligations connected with Dig.IT grant settlement begin?

The obligations begin on the day the funding agreement is signed, not after implementation is finished. From that moment the company operates according to the physical and financial schedule from the agreement, and every material change to the project usually requires notifying the funding institution.

What happens if the company does not reach the declared project indicators?

The consequences depend on the scale of the deviation and the provisions of the specific agreement, but failing to reach result indicators may lead to a partial repayment of the funding. That is why it is worth planning indicators realistically already at the application stage and measuring them with data the system actually generates, not with estimates.

How long does the project durability period last after implementing an ERP system?

The length of the durability period is set by the specific funding agreement, in line with the programme rules in force for the given call. Throughout that time the company must keep the purchased system and use it in line with the purpose described in the application, and the funding institution may carry out an inspection.

Does the documentation for grant settlement differ from the documentation needed for KSeF?

These are two separate obligations, but they overlap. The cost invoices needed to settle the grant will have to be handled through KSeF anyway, whose obligation to receive invoices applies to all taxpayers from 1 February 2026. An ERP system integrated with KSeF makes both easier, because the data comes from the same source instead of from separate spreadsheets.

Settlement and durability decide whether the funding stays in the company for good, or whether it will have to be repaid one day. Before you sign an agreement or choose a system supplier, check the full map of available sources of funding for an ERP implementation and the terms on which the individual programmes are settled, on the digitalisation funding page.

HADRON FOR BUSINESS SP Z O O, Tomasz Leppich September 17, 2026
Share this post
Tags
Archive
Sign in to leave a comment
CRM for a manufacturing company: why a regular CRM fails on technical quotes
Without a link to the ERP, the CRM prices quotes from the salesperson's memory, not from the real material cost and shop floor capacity.