> For the complete documentation index, see [llms.txt](https://learn.getsparrow.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.getsparrow.co/tutorials/integrations/automatic-receipts-invoice-reader.md).

# Automatic Receipts/Invoice Reader

Sparrow has the ability to receive an email containing a receipt and file it into Sparrow for you.  Simply forward your receipt with some basic information to your unique receipts inbox and the automation will download the reciept, categorize it and upload it into Sparrow with the correct event and categorization.

{% hint style="info" %}
This feature is currently in beta and uses AI, so may experience errors.  Please report any issues to your account manager.
{% endhint %}

### Limitations and Notes

* Your unique receipts email address *must* be directly listed in the "To:" section.  **The automation will not work if the email is included in a forwarding address.**<br>
* Please only include the receipt or invoice as an attachment.  Multiple unrelated attachments cause an error in the automation.

### **Instructions**

1. **Email an attachment of the invoice/receipt to your unique receipts email address.** If you don't have a  unique receipts inbox, reach out to your account rep.\
   \
   Attachments can be: PDF, JPG, PNG, or GIF<br>
2. **In the body of the email, include:**\
   \
   Event Name:  <mark style="color:red;">required</mark>\
   Event Date:  <mark style="color:red;">required</mark>\
   Venue: optional\
   Category: Traditional, Digital or Other\
   Type: (e.g. Radio, Social, etc)\
   Notes: Any additional notes you want in Sparrows "details" field\
   \
   Example —\
   \
   &#x20; Event: LSDream\
   &#x20; Date: 11/03\
   &#x20; Venue: Vic\
   &#x20; Category: Traditional\
   &#x20; Type: Street Team\
   &#x20; Notes: Posters for street team


---

# 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://learn.getsparrow.co/tutorials/integrations/automatic-receipts-invoice-reader.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.