> For the complete documentation index, see [llms.txt](https://docs.silverband.com.au/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silverband.com.au/home/paradigm-knowledge-base/invoicing-and-receipting/faqs/how-to-email-payment-receipts-with-the-communication-module-event.md).

# How to email payment receipts with the Communication Module/Event?

The instructions below are on sending a communication event per student, for the instructions on sending bulk communications, refer to the [**Communication Event**](/home/paradigm-knowledge-base/sending-communications/workflows/manage-sending-email-and-sms-communications/send-bulk-communications-with-attachment.md) knowledge article.

1. In the **Accounting** > **Summary** or **Payments** screen, go to the **STUDENT PAYMENTS LIST** section.
2. Click the **ACTIONS** button against the payment that you want to send, and select the **Email with Communication Event** option.

<figure><img src="https://1246578764-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC21t2SaV2eKaLxvtR27D%2Fuploads%2FmiXJRHGGPTdJZfZyesoe%2Fimage.png?alt=media&amp;token=61443c58-ff6c-40cb-b1c9-78aa3462ccca" alt=""><figcaption></figcaption></figure>

3\. In the **COMMUNICATION DETAILS** section, set the **Communication Status** to **Sent**, select the **Communication Template Message**, check/edit/update the email body as necessary and as required, as an optional step – scroll down to the **ASSOCIATED FILE ATTACHMENTS** section, check the attachment content.

After verifying all the communication details and attachments, click the **SAVE AND SEND** button.

<figure><img src="https://1246578764-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC21t2SaV2eKaLxvtR27D%2Fuploads%2FoApqeJOF1mTcCSL0zJmJ%2Fimage.png?alt=media&amp;token=c20e064f-904b-4b37-b77a-22e89d70bf52" alt=""><figcaption></figcaption></figure>

An email with the attachment has now been sent and a copy of both is saved into the Communication Event record.
