GetAccept supports Norwegian BankID signing, also known as NBIES (Norwegian BankID Electronic Identification Signing). The signing method must be configured when the document is created, or it can be updated at any point before the document is sent. It cannot be changed after sending.
Prerequisites
You must have an admin role on the GetAccept entity.
NBIES must be enabled on your entity as an add-on. Contact your GetAccept representative to have this activated.
Enable NBIES signing on a document
In the app
Note: NBIES is activated in stage 2 of 3 of the document creation flow (the signing settings step). It is easy to miss, and the signing method cannot be added or changed once the document has been sent.
In the document signing settings (either during the creation flow or via Update document settings > Signing on an existing draft), choose Norwegian BankID (NBIES) from the signing method tabs. The available tabs are:
Standard e-signature
Norwegian BankID (NBIES)
Qualified Electronic Signature (QES)
You can also check Require verification before viewing document to require recipients to authenticate with BankID before they can open the document.
Via API
When creating a document via the GetAccept API, set the external_eid_signature parameter on the document. If you do not have access to the API parameter reference, contact your GetAccept representative.
Note for API customers with NBIES enabled by default: If your entity has external_eid_signature set as the default, you can override this on a per-document basis by explicitly passing external_eid_signature: false in the API call. The document will then be sent using standard e-signature instead.
Personal number matching (optional)
NBIES personal number matching can be configured per recipient. When enabled, the recipient must authenticate with a BankID that matches a specific Norwegian personal identification number.
In the app: Open Edit recipient details and enter the recipient's Norwegian personal identification number in the NBIES personal number matching field.
If a number is entered, GetAccept validates that the BankID used matches that specific person.
If the field is left empty, the recipient is still authenticated via BankID, but no identity matching is performed.
Via API: Pass the personal identification number in the relevant recipient field on the API call.
Let recipients choose between Nordic BankIDs
NBIES uses Norwegian BankID for signing. If you want your recipients to be able to choose between several Nordic BankIDs on the signing page (Swedish BankID, Danish MitID, or Finnish BankID, in addition to the Norwegian one), this can be enabled as an extension to your NBIES entity.
Note: A per-signature cost applies for the additional non-Norwegian BankIDs. For that reason it is not enabled automatically. Contact your GetAccept representative or Tech Support to enable the Nordic BankID choice on your entity.
How the signing flow works after the extension is enabled
You continue using the same NBIES signing flow when creating and sending documents. There are no new fields or settings to configure on the document itself.
When the recipient opens the document to sign it, they see a choice of Nordic BankIDs on their signing page and pick the one that matches their national identity.
Important to know: The sender does not see any UI change after the extension is enabled. The document setup, the recipient details, and the signing settings all look exactly the same as before. The choice of Nordic BankIDs appears only on the recipient signing page. If you do not see a new option in the document, that is expected. To verify, send a test document to yourself and open the signing link.
Documents already sent or signed
New documents. The Nordic BankID choice applies to every document sent after the extension is enabled on your entity. No action is needed on each document.
Already sent, not yet signed. Existing documents that were sent before the extension was enabled do not automatically include the Nordic BankID choice. If you need it on a specific already-sent document, contact GetAccept Support and they can update that document.
Already signed by a participant. If at least one participant has already signed the document, it cannot be updated to include the Nordic BankID choice.
Recipient signing experience
When a recipient opens a document configured for NBIES, they are prompted to authenticate using their Norwegian BankID credentials. If Require verification before viewing document is enabled, this authentication happens before the document is accessible. Once authenticated, the recipient can review and confirm their signature.
Field updates sync to the core app and integrations
Information verified during a NBIES signing with BankID now writes back to the core GetAccept app automatically. The verified data updates the corresponding records in GetAccept and flows onward to any connected CRM through the standard integration sync, so the details captured at signing are reflected everywhere the document is tracked.
Before this update, the verified information sat inside the NBIES signing flow and was not pushed back to the core app or to the connected CRM, which meant users had to update records manually after signing. With this update, that step is no longer needed.
Note: This applies specifically to the NBIES (QES Norway) signing flow and the fields updated during it. Other signing flows and integrations are unaffected.
Allow handwritten signatures on a recipient level
When you set up signing methods for NBIES, you can now explicitly allow a recipient to use a handwritten signature instead of signing with BankID. This is configured per recipient on the document.
The behavior to be aware of:
A recipient who is allowed to use a handwritten signature will not be able to sign with BankID. The two options are mutually exclusive at the recipient level.
Allowing handwritten signatures on a recipient does not change the security of other signatures on the same document. The QES signatures applied through NBIES remain at the same assurance level as before.
A document that contains both QES and non-QES signatures will reflect that mix in its audit trail. Anyone inspecting the signed document may see that some signatures were applied at a lower assurance level (typically advanced or SES).
Note: Use this option only when you have a clear reason to accept a lower-assurance signature on the document (for example, a co-signer who cannot authenticate with BankID). For Norwegian regulatory contexts that require QES end to end, keep the recipient on BankID.