Confirm the contract

If the buying organisation manages its contracts in e-Request, signing runs through the portal. Not every organisation does — if no request arrives, the contract is handled the usual way.

How it works

1. The buying organisation creates the contract and requests your signature.
2. You receive the request and review the contract.
3. You confirm — or you decline.

You can see the state of the contract at any time: still being drafted, signature requested, confirmed by you, or declined by you.

Confirming is a click, not a signature

Confirmation happens by clicking in the portal and is logged with a timestamp. It is not a qualified electronic signature under ZertES or eIDAS.

For most procurements that is exactly right. If a qualified signature is required for your contract, settle that with the buying organisation before you confirm — it is a contractual question, not a technical one, and not one we can answer for you.

Declining is a normal step

If something is wrong, decline rather than confirming and negotiating afterwards. Declining is a regular part of the process: the buying organisation can amend the contract and request your signature again.

Give your reasons through whatever channel you already use with your buyer. The decline itself is a state in the system, not a negotiation channel.

Read it first

Check that the contract matches what you offered: scope, quantity, price, term. The contract is what counts in the end — not your offer, and not the tender.

Deadlines in the contract

Reminders about contract deadlines go to the buying organisation, not to you. So do not rely on the system to remind you about an end date or a renewal option — keep track of the dates that matter to you yourself.