> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/marketing/emails/default-shopper-emails/invoice-email.md).

# Invoice email

## Overview

2Checkout automatically sends an **invoice email** to business customers, providing full details on their purchase and finalized transaction.

## Availability

All 2Checkout accounts.

## Email content

The email includes the following:

1. Card statement details.
2. PDF with the invoice.
3. Order details, including reference, payment method, paid on date, and total transaction value.

### Sample

![invoice email.png](/files/7fa391c7bee33ea0cc5c0e62e19b8a4fe0773bb4)

## Preview and test email

Navigate to the [Email template manager](https://secure.2checkout.com/cpanel/etm_templates.php) section to:

* Preview and test current templates for emails sent to your shoppers
* Customize the header and the footer sections by creating custom templates that you can assign to your emails

Access the **Invoice email** under the **Order** section in the Merchant Control Panel.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.2checkout.com/marketing/emails/default-shopper-emails/invoice-email.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.