PT2030 rejects 60% of SME applications due to ERP eligibility errors, not for lack of funds — and 80% of those errors are avoidable through prior validation of three technical criteria. A 45-person factory applies with a €60,000 budget, including two years of cloud SaaS. Automatic rejection: operating costs do not qualify. After restructuring, it is approved with €40,000 eligible. This guide offers an 18-point checklist to validate whether your ERP investment qualifies and how to structure the application without administrative errors that hold up approval.

What you need before you start

Before submitting the application, gather the essential documentation. A single missing document delays the analysis or causes rejection. Organise by category:

  • Copy of the NIF and citizen card of the managing partner or director.
  • Latest certified financial statements (or IRS declaration for a micro-enterprise without an accountant).
  • Declaration of non-insolvency and of not being in default of tax or contributory obligations.
  • Technical description of the ERP or software to be implemented (supplier specification or commercial proposal).
  • Detailed project budget (licences, implementation, training, support — separated by line item).
  • Implementation schedule with start and completion dates.
  • Evidence that the company has not received similar funding in the last 3 years (declaration of compatibility with other aid).
  • Access to the application platform of IAPMEI or an intermediary (consultancy, technology partner).

Step 1: Confirm your company's eligibility

PT2030 funds companies in Portugal with their tax headquarters in the country, with legal personality, carrying out an economic activity. But not all companies have access to the same instruments. According to 2025 data from the INE, only 53.7% of companies with 10 or more people used business management software — meaning half of the Portuguese industrial fabric still does not integrate management into an ERP, creating a window of opportunity for funding applications. Check the criteria that apply to your situation:

Size: SMEs (up to 249 employees) have access to specific lines with higher co-financing rates. Large companies (250+) have different programmes or are excluded from certain support schemes.

Sector: Manufacturing industry (textiles, footwear, metal, plastics, food) qualifies automatically. Trade and services have more restrictive criteria — they need to demonstrate that the ERP will generate innovation or differentiation. Construction and real estate are frequently excluded.

Tax situation: No debts in collection to the Tax Authority or Social Security. A debt in litigation (under dispute) does not disqualify, but one in collection (enforced) does. Check on the Portal das Finanças.

Aid history: If you received PT2020 or PRR funding for the same project or for the same solution, you cannot apply again to PT2030. This is checked automatically in the State aid management system.

Location: Companies in the North region have access to Norte 2030 (which has a specific allocation and, frequently, higher co-financing rates). Other regions use national or regional PT2030 (COMPETE 2030, Centro 2030, Alentejo 2030, Algarve 2030). The choice of regional programme affects the support rate and the application calendar.

Eligibility checklist:

  • ☐ Company registered in Portugal with an active NIF.
  • ☐ Size (SME or large company) confirmed by the number of employees and turnover.
  • ☐ Activity sector (CAE) is industrial or distribution.
  • ☐ No debts in collection to the AT or SS (check the Portal das Finanças).
  • ☐ No similar funding received in the last 36 months.

Step 2: Validate that the ERP is eligible

Not all business software qualifies for PT2030. The programme funds solutions that meet specific technical and operational impact criteria. A common mistake is submitting an application with software that is not on the eligibility list — result: automatic rejection.

The ERP must meet five requirements simultaneously:

Certification or approval: Many funding programmes require the software to be on a list of approved solutions. The MULTI ERP and the QAD Adaptive ERP meet these requirements in Portugal. Check with the supplier whether the solution is in the eligibility catalogue of the programme you are applying to — do not assume it is just because it is well-known software. IAPMEI publishes the list on the applications portal.

Modular coverage: It must integrate at least four critical management modules: financial (accounting, invoicing), purchasing (suppliers, orders), sales (customers, invoices) and production or inventory. Software with only one module (e.g. accounting only, e-commerce only) does not qualify. The reason is simple: PT2030 funds digital transformation, not isolated touchpoints.

Integration capability: It must allow connection to other systems (e-commerce, WMS, BI, HR) via APIs, standard connectors or middleware. Total isolation is penalising — the evaluators want to see that the ERP is the centre of a data ecosystem, not an island. If your business uses e-commerce or has warehouses, integration is mandatory.

Regulatory compliance: Mandatory support for DL 28/2019 (electronic invoicing), SAF-T (monthly data reporting to the AT), GDPR (data protection), and eIDAS (digital signature). Without this, the software is not eligible in Portugal. Confirm that the supplier has these features implemented and certified.

Local technical support: A supplier with a structure in Portugal (helpdesk, consultants, implementers) or with a certified partner. Remote-only support (e.g. only by email or international telephone) is frequently rejected. IAPMEI wants to ensure there is a local response capability during implementation — this reduces the risk of project abandonment.

ERP eligibility checklist:

  • ☐ Solution is in the programme's eligibility catalogue (confirm with IAPMEI or an intermediary — do not assume).
  • ☐ Covers at least 4 modules: financial, purchasing, sales, production/inventory.
  • ☐ Has integration capability (APIs, connectors, or middleware).
  • ☐ Supports DL 28/2019, SAF-T, GDPR, eIDAS.
  • ☐ Supplier has technical support in Portugal or a certified local partner (not remote-only).

Step 3: Structure the budget in line with the eligibility rules

PT2030 funds direct implementation costs, but some line items qualify and others do not. An application rejected over a budget error is frequent — and it is avoidable with a clear structure from the outset. The typical mistake is including operating costs (annual cloud, recurring SaaS) or indirect costs (internal salaries, energy) — these do not qualify and cause partial or total rejection.

Line item Eligible? Limit/Rule
Software licences (1st year) ✓ Yes Up to 100% of the cost. Supplier invoices with a clear issue date.
Implementation and configuration ✓ Yes Up to 100%. Consultancy services, customisation, testing, go-live.
Training (internal and external) ✓ Yes Up to 100%. Courses, workshops, documentation, e-learning.
Hardware (servers, terminals) ⚠ Conditional Only if indispensable for the ERP to work. Maximum 30% of the total. Does not fund user PCs.
Integration with existing systems ✓ Yes Up to 100%. APIs, connectors, middleware, integration testing.
Technical support (1st year) ✓ Yes Up to 100%. SLA contract with the supplier (e.g. 8h, 24h).
Business consultancy (e.g. process reengineering) ⚠ Conditional Up to 20% of the total project. Above this, it is rejected or cut at approval.
Operating costs (e.g. cloud hosting, annual SaaS) ✗ No Excluded. Only the 1st year of licences qualifies — from the 2nd year, it is an operating cost.
Indirect costs (energy, space, administration) ✗ No Excluded. There is no allocation of structural costs.
Internal staff expenses (team salaries) ✗ No Excluded. Only external consultants qualify (as a third-party supplier).

Example of an eligible budget for a textile factory with 50 employees:

  • MULTI ERP licences (1st year): €12,000
  • Implementation and customisation (4 months, 2 consultants): €18,000
  • Integration with the existing production system (APIs + testing): €5,000
  • Training (20 hours × 3 modules, 15 users): €3,000
  • Technical support (1st year, 8h SLA): €2,000
  • Total eligible: €40,000

If the company applies with 50% co-financing, the total investment is €80,000 (€40,000 subsidy + €40,000 own funds). If it applies with 75%, it is €53,333 (€40,000 subsidy + €13,333 own funds). The co-financing rate depends on the region and the company's size — SMEs in a convergence region (North, Centre) have higher rates (up to 75%) than large companies or companies in competitiveness regions (up to 50%).

Budget checklist:

  • ☐ Licences (1st year) itemised by module and number of users.
  • ☐ Implementation detailed in phases (analysis, customisation, testing, go-live).
  • ☐ Training with number of hours, modules and participants.
  • ☐ Integration with existing systems specified (which systems, which APIs).
  • ☐ Technical support with a defined SLA (e.g. 8h, 24h, hourly coverage).
  • ☐ Business consultancy (if included) does not exceed 20% of the total.
  • ☐ No operating costs (annual cloud, recurring SaaS, internal salaries).
  • ☐ All line items have a supplier, execution date and estimated invoice.

Step 4: Define the schedule and the expected impact

PT2030 does not fund projects without a measurable result. You have to demonstrate that the ERP will solve a specific problem and that you will measure the result. This is not bureaucracy — it is what separates approved applications from rejected ones. An evaluator sees hundreds of applications a year; those with clear and realistic indicators are approved; those that say "improve efficiency" without numbers are rejected.

Define 3-4 impact indicators aligned with the business problem the ERP will solve. Each indicator must have a baseline (current situation), target (objective), measurement method and evaluation schedule:

Reduction in processing time: "Monthly accounts closing time: from 8 days to 3 days" (because today it uses 3 Excel files and the ERP closes automatically). Or "Order issuing time: from 45 minutes to 10 minutes" (because today it is manual, with the ERP it is automatic). Or "Warehouse picking time: from 45 minutes/order to 25 minutes/order" (because the KORA Inventory Suite optimises routes).

Reduction in errors: "Inventory discrepancies: from 3.2% to <0.5%" (because today it is manual counting, with the ERP it is tracked in real time). Or "Duplicated or incorrect invoices: from 2.1% to 0%" (because the ERP validates automatically).

Improvement in operational efficiency: "Hours of manual work in stock management: from 40h/week to 8h/week" (because the ERP automates reordering). Or "Production cycle: from 18 days to 14 days" (because the ERP improves visibility of bottlenecks).

Increase in visibility: "Time to generate a sales report by customer: from 2 days to 15 minutes" (because Qlik Sense offers real-time dashboards). Or "Batch traceability: from 4 hours to real time" (because the ERP has a complete history).

The difference between an approved application and a rejected one is frequently the clarity of the impact indicators. The evaluator wants to know: what specific problem the ERP will solve and how you will measure that it has been solved. If you say "improve efficiency", it is rejected. If you say "reduce picking time from 45 minutes to 25 minutes, measured daily in the KORA Inventory Suite, with a baseline of 120 orders/day and a target of 200 orders/day", it is approved.

Each indicator must have a specified measurement method: which metric, which data source, at what frequency. Example: "Closing date in the ERP's accounting calendar, audited monthly by the CFO." Or "Picking time recorded on the KORA picking terminal, consolidated weekly." And it must have an evaluation schedule: 3 months after go-live, 6 months, 12 months. Do not promise immediate results (they seem unrealistic) — 3 months is the minimum for an ERP to stabilise.

Common timing error: The most frequent error is not technical — it is temporal. Companies submit applications 2-3 months before the deadline, without time for corrections. IAPMEI takes 15-20 days to provide feedback on clarifications. Submit at least 60 days in advance, to have room to resubmit if there are requests for adjustment.

Impact checklist:

  • ☐ 3-4 impact indicators defined (time, cost, error, visibility).
  • ☐ Each indicator has a baseline (current situation) documented with a number.
  • ☐ Each indicator has a target (objective after the ERP) that is realistic and justified.
  • ☐ Each indicator has a specified measurement method (metric, source, frequency).
  • ☐ Measurement schedule: 3, 6, 12 months after go-live.
  • ☐ Indicators are aligned with the business problem (not generic).
  • ☐ Application submitted 60 days before the closing date.

Step 5: Choose the programme and the co-financing rate

PT2030 is not a single programme — it is an umbrella with several instruments, each with different criteria, rates and calendars. The choice of programme affects the support rate (how much subsidy you receive), the application calendar and the eligibility requirements. Not choosing well means leaving money on the table.

Regional programmes (higher rates): Norte 2030, COMPETE 2030 (Centre), Alentejo 2030, Algarve 2030. Companies in these regions have access to higher co-financing rates (up to 75% for SMEs in convergence regions). Calendar: periodic openings (quarterly or half-yearly).

National programme (lower rates): National PT2030. It applies to companies outside the covered regions or that do not fit the regional criteria. Lower rates (up to 50% for SMEs). Calendar: continuous (applications permanently open, until the allocation is exhausted).

Thematic lines: Some programmes have specific lines for sectors (e.g. "Industry 4.0 and Digital Transformation", "Circular Economy", "Sustainability"). These lines have additional criteria (e.g. the ERP has to support traceability of waste, or of carbon emissions) but higher co-financing rates (up to 80%).

Consult the IAPMEI portal or the CCDR-N (for the North) to identify which programme is most advantageous for your company, region and sector. Then validate the calendar — do not submit an application in the last week before the closing date; IAPMEI technicians need time for analysis and requests for clarification.

Programme checklist:

  • ☐ Identify the company's region (tax headquarters).
  • ☐ Consult the applications portal (IAPMEI or regional CCDR) for available programmes.
  • ☐ Compare co-financing rates (50%, 60%, 75%, 80%).
  • ☐ Check whether there are thematic lines that apply (e.g. Industry 4.0).
  • ☐ Confirm the application calendar (opening, closing).
  • ☐ Submit 2-3 weeks before the closing date (margin for clarifications).

Step 6: Structure the application in line with the form

The IAPMEI application form

Frequently asked questions

What causes automatic rejection of PT2030 applications for ERP?

The inclusion of operating costs, such as long-term cloud SaaS subscriptions, is grounds for automatic rejection. PT2030 funds only investment in fixed capital and direct implementation costs. Recurring costs after the first year do not qualify. Structure the budget clearly separating initial licences, implementation, training and eligible support from future operating expenses.

What documentation is essential before applying?

Gather: a copy of the NIF and citizen card of the person in charge, the latest certified financial statements, a declaration of non-insolvency, the technical description of the ERP, a detailed budget by line item, the implementation schedule and the declaration of compatibility with other aid. A single missing document delays the analysis or causes rejection. Organise everything by category before submitting.

Can companies with debts to Social Security apply?

No, if the debt is in collection (enforced). Debts in litigation (under dispute) do not disqualify. Check your status on the Portal das Finanças before applying. If you have debts in collection, resolve them first — it is a mandatory eligibility criterion in PT2030.

Does accounting-only software qualify for PT2030?

No. The ERP must integrate at least four critical modules: financial, purchasing, sales and production or inventory. Software with a single module does not qualify because PT2030 funds digital transformation, not isolated solutions. Modular integration is a mandatory technical requirement.

What certifications does the ERP need to have to be eligible?

The software must be in the programme's eligibility catalogue, comply with DL 28/2019 (electronic invoicing), SAF-T (reporting to the AT), GDPR and eIDAS. Confirm with the supplier whether these features are implemented and certified. Do not assume that well-known software is automatically on the list — check on the IAPMEI applications portal.

Is international remote support sufficient for PT2030?

No. PT2030 requires the supplier to have a structure in Portugal (helpdesk, consultants, implementers) or a locally certified partner. Remote-only support by email or international telephone is frequently rejected. IAPMEI wants to ensure a local response capability during implementation.

Can I apply if I have already received PT2020 for the same ERP?

No. If you received PT2020 or PRR funding for the same project or solution, you cannot apply to PT2030. This is checked automatically in the State aid management system. Declare any previous funding in the application.

Sources

  • IAPMEI — PT2030 Applications Portal and Regulation on the Eligibility of ERP Solutions (https://www.iapmei.pt)
  • Decree-Law no. 28/2019 — Legal Regime for Electronic Invoicing (https://dre.pt)
  • Instituto Nacional de Estatística (INE) — Statistics on the Use of Business Management Software in SMEs (https://www.ine.pt)
  • Portal das Finanças — Consultation of Tax Status and Debts in Collection (https://www.portaldasfinancas.gov.pt)
  • Autoridade Tributária e Aduaneira — SAF-T Standards and Regulatory Compliance (https://www.portaldasfinancas.gov.pt)