Preparing a foreign company's authority and access for CVP IS
Use Lithuania’s current CVP IS roles and submission instructions to connect the correct foreign legal entity, authorised people and final tender record.
A foreign company preparing to bid through Lithuania's CVP IS should establish who operates its account, who approves the commercial offer and how the final submission will be verified. Those responsibilities are related, but they are not identical. The person with the broadest platform permissions need not be the person authorised internally to approve the price and contractual commitment.
Current Public Procurement Office guidance is especially useful because it separates organisation administration, tender preparation and submission, and an announced authentication change. A supplier can use those documents to organise a reliable response without assuming that every old registration instruction describes the current production system.
Begin from the current official entry points
The Public Procurement Office's English guidance index links separate materials for registration, company roles, tender submission and two-factor authentication. It also distinguishes the current CVP IS environment from the earlier system. Start there when preparing a new account or checking a colleague's saved instructions.
The public production registration form separately asks for organisation identity, location and contact information. It distinguishes a legal-entity code from VAT and D-U-N-S fields, with the latter identified for foreign companies. The supplier should use its actual corporate details and the current field instructions rather than entering a branch or parent's identifiers interchangeably.
That identity decision belongs before account setup. A foreign parent, a Lithuanian subsidiary and a local branch may be part of the same commercial group, but the offer needs an identifiable bidder. The team should determine which entity is participating and how any other group resource is represented under the tender's requirements.
If the current form does not clearly accommodate the intended entity, obtain clarification from the Office using the specific field and factual situation. A broad question about whether foreign firms can bid is less useful than explaining the actual legal entity and the registration issue. Platform access does not itself settle eligibility for a particular procurement.
Use the platform roles deliberately
The Office's company-role presentation valid from 20 May 2026 distinguishes EO Admin and EO User. Both can prepare and submit tenders; the administrator also manages organisation information and users. The first registered user receives the administrator role, and the presentation describes activating and deactivating user accounts.
The practical implication is to choose the initial administrator intentionally. An external adviser helping with one response may not be the best long-term owner of the company's organisation record. Equally, giving every employee administrator rights is not necessary simply because several people contribute to the bid.
Consider a hypothetical German supplier of commercial facilities-management software. Its export manager coordinates a Lithuanian opportunity, its finance director approves pricing and a local adviser helps interpret the dossier. The company can give each person a defined task without assuming that they should all use the export manager's login.
The administrator should know who needs continuing access and who is involved only for the present response. The bid lead should know which colleague can perform the submission and which internal approval is required beforehand. A short account handover can preserve those decisions when the original administrator changes role or leaves the company.
Keep discovery alerts connected to the response team
The role presentation also explains that organisation CPV settings and user associations affect notifications. This is a reason to decide who monitors a relevant procurement and who must see its communications. It is not enough to assume that every user receives every message because they belong to the same company.
For the software supplier, the export manager could own opportunity monitoring while the bid coordinator maintains the specific tender record. Important changes should then reach the people responsible for the corresponding part of the offer. A revised implementation timetable needs the delivery lead's attention; a procedural clarification may require the person managing submission.
Use TED searches combining buyer names, procurement codes and keywords as a discovery layer, then carry the actual procurement identifier into CVP IS work. That connection helps the team recognise whether a notice, a clarification and its prepared response concern the same procedure.
A current response record should identify the dossier version and the unanswered questions affecting the offer. It should not become a parallel source of invented requirements. When the procurement documents change, update the team's understanding from the official record and preserve the reason for any resulting revision to the proposal.
The May role presentation also identifies the embedded ESPD functionality as unavailable at that time and directs suppliers to the separate ESPD service. Follow the current official route when preparing the declaration. A visible menu item is insufficient evidence that the function is ready to use for a particular response.
The export manager should settle who approves any reliance on another group company before the declaration is completed. That decision affects the factual account of the bidder’s resources. It should be consistent with the offer and supporting documents, rather than being made implicitly by the colleague filling in a form.
Prepare for the announced authentication change accurately
The Office's two-factor authentication presentation valid from 20 August 2026 says the feature is implemented in the demonstration environment and planned for production in mid-September. At this guide's 6 September review, that is an announced production rollout, not evidence that production already requires the second factor.
A company with a forthcoming deadline should check the current login instructions again before its submission window. The person responsible for the account should be able to complete the required access steps personally and know how to obtain support if something changes. Keep account recovery arrangements under the company's control without sharing personal credentials between colleagues.
The demonstration and production environments have separate access arrangements in the Office's guidance. Treat practice as preparation for the real process, not as proof that a response has entered the production procurement. The team should always be able to identify which environment it is using and which actual tender its work concerns.
Verify the completed submission, not only preparation
The tender-submission presentation valid from 20 May 2026 distinguishes creating and uploading a response from submitting it. It describes checking the response's Submitted status and reviewing the submitted documents. Those are useful checks for the person reporting completion to the business.
The software supplier should retain the final approved package and the available submission evidence together. The finance director's approval should relate to the price and scope actually sent, while the bid lead should be able to retrieve the transmitted documents. A folder containing the intended offer is incomplete evidence if the platform record contains an earlier version.
Leave enough time for that comparison. A final upload or signature action can reveal a document problem that was invisible during drafting. The practical schedule should include a period for checking the completed action before the external deadline, while following the actual procedure's requirements for any amendment or withdrawal.
If the supplier wins, carry the identified legal entity and purchasing relationship into the SABIS invoice workflow. Tender access, contract administration and invoicing are different stages, but a consistent company identity and a retrievable commitment make the handover between them much easier.
The resulting arrangement should identify the bidder, a durable administrator, named response responsibilities and evidence of the submitted offer. Those decisions allow a foreign supplier to use CVP IS as an ordinary part of commercial operations while remaining attentive to the current platform and the particular procurement.
Sources & evidence
- Current supplier methodical assistanceLithuanian Public Procurement Office
- Production economic-operator registration formCVP IS
- Economic operator company roles, 20 May 2026Lithuanian Public Procurement Office
- Developing and submitting a tender, 20 May 2026Lithuanian Public Procurement Office
- Two-factor authentication guidance, 20 August 2026Lithuanian Public Procurement Office
Current VPT guidance index, production registration form and actual May/August 2026 presentation files reviewed 6 September 2026. August guidance describes production two-factor authentication as planned for mid-September, not already universally implemented. Older demo registration material was not treated as current production instructions.
Suggest a correction