Executed is Aiwyn's word for an engagement whose execution requirements are complete. It is worth being precise about those requirements, because a letter that has been signed is not necessarily executed. A saved payment method and a successful prepayment are also separate events: in the default configuration, a prepayment can still be processing or fail after the letter becomes Executed.
The minimum condition
At least the primary contact must sign. This holds for every electronic engagement letter, without exception.
It carries a consequence for template design: every engagement letter template needs at least one client signature block placeholder somewhere in its sections. Without one there is nowhere to sign, and the letter can never execute.
On a dynamic letter template the rule is there must be at least one primary client signature block placeholder somewhere on the letter template.
Aiwyn replicates the signature area for each additional signatory itself, and a block holding the signature placeholder should not be given variants that could hide it. The template editor validates this before a template can be saved, so a preparer will rarely meet a letter with no signature block; if you do, the fix is in the template, not the letter.
The additional conditions
Beyond the signature, execution depends on how the letter was set up.
| Setup | Additional condition |
|---|---|
| All signatories must sign | Every additional signatory signs, not just the primary contact. |
| Payment method optional | None. Signatures are enough. The billing contact may save a method, choose Set up later, or skip the payment step entirely. |
| No payment method prompt | None. Signatures are enough. |
| Payment method required | The billing contact saves a valid payment method. Until then, the signed letter stays in Sent. |
| Consent document attached | The signatory either grants or declines consent and signs the consent document. |
Payment method setup versus prepayment
Saving a payment method and successfully collecting a prepayment are separate events.
By default, once all signatures and any required payment-method setup are complete, the engagement becomes Executed. A configured prepayment is charged after execution. If that charge fails, the engagement remains Executed; Aiwyn logs the failure and sends failure notifications.
A firm can enable enable_sync_engagement_prepayment to change this sequence. When it is enabled, an engagement with a prepayment stays in Sent until Stripe confirms that the payment succeeded.
Until then
The engagement stays in Sent, and reminder emails go to the primary and billing contacts every three days.
They do not stop on their own. They stop when the letter executes, or when someone with the rights to do so revises or cancels it.
When it executes
- The signatories receive the signed PDF and a link to view it in their client portal.
- The engagement partner, engagement manager and any collaborators receive the same PDF and a link to the firm portal.
- A certificate of completion is appended as the last page of the letter.
- The status changes to Executed, and only contacts, partner, manager, fiscal year and dates remain editable.
Firm-side execution bypasses payment checks
If a firm user selects Execute from the firm side, Aiwyn marks the letter Executed without checking whether the client saved a payment method or completed a prepayment. Outstanding client payment tasks do not block the action.