background

B2B signing statuses - Netherlands

Tags:agreementsb2bnetherlandsemachtigingzakelijkstatusstatussenstate
This article covers the Netherlands-specific bank-redirect session behavior for Digitaal Incassomachtigen (eMachtiging).

For the general B2B agreement lifecycle (Prepared, Signed, Cancelled, and so on) that applies across every country and mandate type, see Possible states of an agreement.

When a customer is redirected to their bank to sign a B2B eMachtiging, the mandate in your environment may pass through the following NL-specific session states before reaching Signed or reverting to Prepared:

Awaiting bank approval

  • Approval is normally instant — the bank confirms the eMachtiging before the customer is redirected back to Twikey.
  • If confirmation doesn't arrive right away, Twikey polls the bank for updates as a safety net, using an exponential back-off method: checks start at short intervals (seconds), then gradually increase to minutes and hours.
  • A manual status check can be performed via Verify with bank on the agreement details page — this button is only visible while the mandate is in this state. If the status remains unchanged after a manual check, the debtor's bank is the only source that can explain the delay.

Requires more signatures

  • The bank itself determined that a second authorisation is required — not something you or the debtor requested.
  • Unlike the general co-sign option (where the first signer forwards an email to the next signer), the bank manages this second-signer flow entirely on its own: it notifies the second signer directly, in-app or by e-mail. Twikey just waits.
  • Once the bank collects the second signature, it sends Signed to Twikey directly.
  • The mandate may stay in this state for up to 1 week.

Cancel in flow

  • The customer canceled the signing process at the bank.
  • The mandate reverts to Prepared, allowing you to resend the signing link.

Failed

  • The bank rejected the eMachtiging.
  • The mandate returns to Prepared and must be signed again.
  • If failures persist, contact the debtor’s bank for support.

Expired

  • The bank session expired (this is separate from Twikey’s invite link expiration).
  • Single-signer mandates typically expire after ~30 minutes.
  • Multi-signer mandates allow up to 1 week for the second signer.
  • Expired mandates revert to Prepared for re-signing.

Expired in Twikey, but customer claims signed

  • The mandate can be retrieved directly from your bank and uploaded to your Twikey environment to complete the activation process. The customer can be notified that the mandate is accepted.
Don't confuse the bank-triggered Requires more signatures state above with Twikey's own co-sign option: they look the same in the state name, but work differently. The bank-triggered version above is unique to eMachtiging and is entirely out of your hands — the bank runs it. Twikey's general co-sign option is something you or the debtor actively choose, and it's you (via the first signer forwarding an e-mail) who moves it forward, not the bank.

See Sign a mandate with two or more signers for the general co-sign flow, available for any agreement type.

Last Update: 2026-09-02