> For the complete documentation index, see [llms.txt](https://authic.gitbook.io/authic-product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://authic.gitbook.io/authic-product-guide/additional-features/receipt-scanning.md).

# Receipt scanning

Rewarding customers for their offline purchases has never been easier. With our **Receipt Scanning** feature, users simply upload a photo of their purchase receipt, and our AI automatically detects the total amount and assigns the corresponding points to their account — no manual input required.

#### How It Works

1. **Upload a Photo:** Customers take a clear photo of their receipt using their mobile device.
2. **AI Detection:** Our system analyzes the image and automatically reads the purchase amount.
3. **Automatic Point Allocation:** Based on your reward rules, points are instantly added to the customer’s account.

#### Receipt quality guidelines for accurate scanning

Our AI-powered recognition engine achieves around **95% accuracy**, ensuring reliable and fast results. To maintain this level of performance, it's important that receipts are captured under the right conditions. Receipts should be **well-lit**, **flat**, and **fully visible** in the photo. Blurry images, shadows, folds, or poor lighting may lead to incorrect (or declined) readings.

For you as a business owner, it's important that your receipts meet the following requirements:

1. **Clear business identification**\
   At least the **business name** should be clearly visible on the receipt so the system can correctly identify the issuing location. We also recommend to add the **business address** on the receipt, which will be mandatory if you have multiple locations.
2. **Visible total amount**\
   The **total transaction amount** should be shown on the receipt. This is required for validation and for any loyalty or reward logic based on spend.
3. **Date and time of the transaction**\
   Each receipt should include the transaction date and time to prevent misuse and ensure correct processing.
4. **Unique order or transaction ID**\
   Every receipt must contain a unique order ID or transaction number. This allows the system to:
   1. Prevent duplicate submissions
   2. Validate each purchase individually
   3. Maintain accurate tracking and reporting
5. **Readable layout**\
   The receipt should be printed clearly, without overlapping text or distorted characters. Faded or low-quality prints can reduce recognition accuracy.

{% hint style="info" %}
If your receipts don’t meet these requirements (yet), we recommend contacting your POS provider. These elements are standard and, in many cases, legally required.
{% endhint %}

#### Admin Control

From the **dashboard**, you can view all uploaded receipts and their detected values. If a receipt is unreadable or points were calculated incorrectly, you can **manually adjust points** — adding or deducting them directly from a customer’s account.

#### Benefits

* **Zero staff handling:** Customers upload receipts themselves — no action required from your team.
* **Perfect for busy environments:** Ideal for restaurants, cafés, or retail locations where staff don’t have time to manually manage loyalty points.
* **Frictionless experience:** Customers receive their points automatically, improving engagement and satisfaction.
* **Error oversight made simple:** Admins can review uploads and adjust points when needed.
* **Bridges offline and online:** Capture loyalty data from in-person purchases effortlessly.


---

# 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:

```
GET https://authic.gitbook.io/authic-product-guide/additional-features/receipt-scanning.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.