Implementación de un sistema de contabilidad basado en Microsoft Dynamics 365 Business Central On-Premises

✓The scope of the contract in this excerpt is only indirectly described.

✓Such as: it concerns services of implementation, migration, development, maintenance and support for accounting or financial ERP systems based on Microsoft Dynamics NAV and/or Microsoft Dynamics 365 Business Central, to be executed in Belgium.

❓Quantities, detailed deliverables, place of performance beyond “en Belgique”, contract duration, and exact period are not specified in the provided text and would have to be taken from other parts of the tender documents.

✓The candidate must ensure that their operational teams and references are relevant and “transposable à l’environnement visé par le présent marché,” but detailed scope metrics and award weightings are not given here.

❓Award criteria and weighting are not explicitly listed in the excerpt.

✓Instead, the text focuses on qualitative selection criteria (financial capacity, technical references, certifications, staff).

✓Such as: the ESPD “Partie IV : Critères de sélection” confirms whether the candidate meets these criteria, alone or with third parties, but does not disclose the evaluation scoring or weighting between price and quality.

✓On risks and special conditions, the text mainly addresses subcontracting and signatures.

✓Such as: if substantial or complex parts of the contract will be subcontracted, those subcontractors must be known at submission and identified; foreign firms must manage additional lead times (2–3 weeks) to obtain qualified electronic signatures; signatures must comply with Belgian e-Procurement regulations and eIDAS (qualified electronic signature, not a scanned handwritten signature), otherwise the dossier will be treated as “non-substantiellement irrégulière,” which is a risk of rejection.

❓Guarantees, penalties, validity period of offers, question deadlines, and possible site visits are not covered in the provided fragment.

✓Regarding contradictions or corrections, the text is largely consistent but repetitive.

✓Such as: the requirements for references, staff numbers, turnover, certifications, and electronic signatures appear multiple times in almost identical wording, reflecting different sections or annexes but not changing the substance.

✓Where the same obligation appears in several places (e.g. at least three references, one Dynamics NAV/BC reference; minimum 10 staff; turnover > 570,000 €; qualified electronic signature), the strictest or most specific wording is identical, so there is no clear substantive contradiction in this excerpt.

❓If an apparent inconsistency arose between sections, the ESPD Part IV and the detailed selection criteria tables would normally prevail, but based on the text supplied, the applicable statements are the repeated, harmonised requirements described above.

Answers on the required criteria

Must securities be provided (bid bond, performance or warranty guarantee)? If so: which, in what amount and by when?

❓Such as in relation to securities (bid bond, performance guarantee, warranty guarantee), the provided text does not mention any requirement to provide financial securities, nor does it specify any type, amount or deadline for such guarantees.

❓These elements may be covered in other parts of the procurement documents (e.g.

Is subcontracting allowed? If so: with which limits and which disclosure duties?

✓Such as with regard to subcontracting, the text explicitly allows the use of subcontractors and other entities whose capacities the candidate may rely on to meet qualitative selection criteria.

✓It explains that when the candidate relies on a third party to fulfil selection conditions, a separate dossier must be created for each such subcontractor or member of an economic grouping.

✓This dossier must include: an identification form (annex 1), a signed DUME/ESPD, a signed letter on making capacities available for the contract, and proof of signature rights.

✓Subcontractors whose capacities are not used for selection but who are already known at the time of submission must be disclosed in a specific table (Partie II, D), including their identification (e.g.

✓Belgian company number or equivalent for non‑Belgian firms), the relationship with the tenderer, and the share/role in the contract.

✓If substantial or complex/technical parts of the contract will be entrusted to a subcontractor (for example, the product supplier), this subcontractor must already be identified and mentioned at candidacy submission.

Is there a site visit, and is attendance mandatory? If so: when?

❓Likewise, regarding a site visit, there is no reference at all to an information session or site visit, nor any indication that attendance would be mandatory or at what date it would occur.

In which language must the tender and the supporting documents be submitted, and are documents in other languages accepted?

✓Such as concerning language requirements, the text states clearly that “Le dossier de candidature n’est disponible qu’en français mais peut être complété en néerlandais.

✓Het kandidatuurdossier is enkel beschikbaar in het Frans, maar mag in het Nederlands worden ingevuld.” This means the official template is only provided in French, but candidates may fill it out in Dutch.

✓For foreign companies, it is specified that authentic documents must be supplied particularly for exclusion criteria; if original documents are not in Dutch, French or English, or cannot be automatically translated by the contracting authority, they must be translated into one of these languages.

✓All such documents must be grouped into one structured folder.

✓This sets an implicit language regime: French and Dutch for the main dossier; French, Dutch or English accepted for supporting authentic documents, with mandatory translation into one of these if the originals are in other languages.

How long is the bidder bound by the tender (validity period), and is there a deadline for bidder questions? If so: until when?

❓Such as for the binding period of the tender (validity period) and deadlines for bidder questions, the text focuses on qualitative selection, DUME completion and signature formalities, but it does not state how long a bidder is bound by its offer nor any calendar or cut‑off date for asking questions.

❓Any precise validity period of offers and Q&A deadline must therefore be taken from other sections of the procurement documentation, as they are not contained in the text shown.

Further details

✓Tender requirements for a Microsoft Dynamics 365 Business Central public contract

✓The input text concerns a Belgian public procurement procedure (by Smals) for services around Microsoft Dynamics NAV / Dynamics 365 Business Central (implementation, migration, development, maintenance, support).

✓It is written primarily from the point of view of Belgian procurement law and practice, and explicitly addresses foreign (non‑Belgian) companies, including references to EU tools such as the ESPD (DUME) and EU trusted lists.

✓Countries are not listed one by one, but the text clearly takes a Belgian contracting authority / EU public procurement framework as its perspective.

✓Throughout, it is underlined that the candidate remains responsible for the coherence and correctness of the entire candidacy file, including parts related to subcontractors.

❓“cahier des charges”, technical specifications) but are not addressed in the excerpt of “01‑Dossier de candidature” provided.

✓It does, however, stress timing aspects for foreign bidders related to obtaining qualified electronic signatures (2–3 weeks lead time from private providers as an alternative to Belgian e‑ID) and recommends testing the e‑Procurement platform in advance and possibly seeking legal advice.