# Notification Transaction Configs

<p class="doc-lead">Transaction Configs connect documents to outbound messages — when to send (or manual send setup), which channel, provider, template, and recipient rule.</p>

<div class="doc-toc">
<p class="doc-toc-title">On this page</p>
<div class="doc-toc-section">
<div class="doc-toc-links">
<a href="#/settings/notification-transaction-configs?id=overview">Overview &amp; List View</a>
<a href="#/settings/notification-transaction-configs?id=manual-send">Manual Send Config</a>
<a href="#/settings/notification-transaction-configs?id=automatic-send">Automatic Send Config</a>
<a href="#/settings/notification-transaction-configs?id=fields">All Fields</a>
<a href="#/settings/notification-transaction-configs?id=faq">FAQ</a>
<a href="#/settings/notification-transaction-configs?id=related">Related</a>
</div>
</div>
</div>

<hr class="doc-section-divider">

<h2 id="overview">Overview &amp; List View</h2>

Go to <b>Settings → Notification System → Transaction Configs</b>.

<!-- screenshot pending -->

<b>List columns</b>: Id, Transaction Type, Use for Manual Send, Status, Channel, Recipient Rule, Delay (min).

<b>Quick filters</b>: WhatsApp Configs, Email Configs.

<b>Filters</b>: Transaction Type, Transaction Status (Draft/Approved/Cancelled), Channel.

<b>List actions</b>: New, View, Edit, Delete (multi).

<hr class="doc-section-divider">

<h2 id="manual-send">Manual Send Config</h2>

Used by the <b>Send Email</b> button on approved sale documents.

| **Field** | **Description** |
|-----------|-----------------|
| Use for Manual Send * | ✓ Check this for manual email setup. |
| Transaction Type * | Sale Invoice, Sale Order, Sale Quotation, or Pro Forma Invoice. |
| Channel * | Email |
| Default Provider * | Email SMTP provider. |
| Notification Template * | Email template for subject/body pre-fill. |
| Default Recipient Rule | Optional — <b>To</b> is usually set on compose screen. |

When <b>Use for Manual Send</b> is checked, these fields are **hidden** (not required):

- Transaction status, Secondary Status  
- Timing (Delay)  
- Fallback provider / channel  
- Conditions (Condition JSON)  

<b>Rule:</b> Only one active manual config per transaction type + channel.

<h3>Example — Sale Invoice manual email</h3>

| Field | Value |
|-------|-------|
| Use for Manual Send | ✓ |
| Transaction Type | Sale Invoice |
| Channel | Email |
| Default Provider | Company Sales Mail |
| Notification Template | Sale Invoice Email |

<p>Full guide: <a href="#/features/email-notifications?id=config-setup">Email Notifications → Config setup</a></p>

<hr class="doc-section-divider">

<h2 id="automatic-send">Automatic Send Config</h2>

Leave <b>Use for Manual Send</b> unchecked to send when a document reaches a configured status.

| **Field** | **Description** |
|-----------|-----------------|
| Transaction Type * | e.g. Sale Invoice, Credit Note, Pay Run. |
| Transaction Status * | Draft, Approved, or Cancelled — when trigger fires. |
| Secondary Status | Optional custom status filter. |
| Channel * | WhatsApp or Email. |
| Default Provider * | Provider for this channel. |
| Notification Template * | Template for message content. |
| Default Recipient Rule | Who receives the message. |
| Default CC / Default BCC | Email only — comma-separated defaults for automatic sends. |
| Delay (minutes) | Wait after trigger before sending (default 5). |
| Condition JSON | Optional filter (e.g. minimum total). |
| Fallback Provider / Fallback Channel | Alternate send if primary fails. |

<p>WhatsApp example: <a href="#/features/whatsapp?id=config-setup">WhatsApp Messaging → Config setup</a></p>
<p>Email example: <a href="#/features/email-notifications?id=automatic-send">Email Notifications → Automatic Send</a></p>

<h3>Example — Sale Invoice automatic email on approve</h3>

| Field | Value |
|-------|-------|
| Use for Manual Send | *(unchecked)* |
| Transaction Type | Sale Invoice |
| Transaction Status | Approved |
| Channel | Email |
| Default Provider | Company Sales Mail |
| Notification Template | Sale Invoice Email |
| Default Recipient Rule | Customer Email |
| Delay (minutes) | 5 |

<p>When a sale invoice is approved, the customer receives the email automatically after the delay. See <a href="#/features/email-notifications?id=examples">Email Notifications → Example E</a> for the full walkthrough.</p>

<hr class="doc-section-divider">

<h2 id="fields">All Fields</h2>

| **Section** | **Field** | **Description** |
|-------------|-----------|-----------------|
| General | Use for Manual Send | Enables Send Email button setup; simplifies form. |
| General | Transaction Type * | Document type. |
| General | Transaction Status | Trigger status (automatic only). |
| General | Secondary Status | Optional secondary status filter. |
| Provider & Rule | Channel * | WhatsApp or Email. |
| Provider & Rule | Default Provider * | Linked provider record. |
| Provider & Rule | Notification Template * | Linked template record. |
| Provider & Rule | Default Recipient Rule | Linked recipient rule. |
| Email Defaults | Default CC | Comma-separated CC for automatic emails. |
| Email Defaults | Default BCC | Comma-separated BCC for automatic emails. |
| Timing | Delay (minutes) | Minutes before send after trigger. |
| Fallback | Fallback Provider | Backup provider. |
| Fallback | Fallback Channel | Backup channel. |
| Conditions | Condition JSON | Optional JSON filter on document fields. |

<hr class="doc-section-divider">

<h2 id="faq">FAQ</h2>

<p><b>Send Email button says email not supported. What is missing?</b></p>
<p>Create an active Transaction Config with <b>Use for Manual Send</b>, correct Transaction Type, Channel <b>Email</b>, plus linked provider and template.</p>

<p><b>Can I have both manual and automatic configs for Sale Invoice?</b></p>
<p>Yes — one manual config (Use for Manual Send) for the Send Email button, and separate automatic configs (unchecked) for approve triggers.</p>

<p><b>What does Delay (min) do?</b></p>
<p>Waits the specified minutes after the status trigger before sending — useful to allow cancel/edit before WhatsApp or email goes out.</p>

<p><b>Must I create Recipient Rules first?</b></p>
<p>Required for automatic sends. Optional for manual email — user sets To on compose screen.</p>

<p><b>Can one document trigger multiple messages?</b></p>
<p>Yes — separate configs per channel or status each create a History row.</p>

<p><b>Do configs apply retroactively?</b></p>
<p>No. Only documents that change status after the config is active are queued.</p>

<p><b>Where is the message body defined?</b></p>
<p>On the linked <a href="#/settings/notification-templates">Template</a> — configs define when, who, and which provider.</p>

<hr class="doc-section-divider">

<h2 id="related">Related Topics</h2>

<ul>
<li><a href="#/features/email-notifications">Email Notifications</a></li>
<li><a href="#/features/whatsapp">WhatsApp Messaging</a></li>
<li><a href="#/settings/notification-recipient-rules">Recipient Rules</a></li>
<li><a href="#/settings/notification-templates">Templates</a></li>
<li><a href="#/settings/notification-transaction-history">Transaction History</a></li>
</ul>
