> For the complete documentation index, see [llms.txt](https://docs.skovik.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skovik.com/for-employees/invalid-receipt-or-invoice.md).

# Invalid receipt or invoice

Uploaded receipts are automatically analyzed to determine if it is a valid proof of purchase (a receipt or an invoice). 

If we suspect that the uploaded document is not a valid proof of purchase a warning is shown next to it, along with the document type we think it is and an explanation on why it probably is not a valid proof of purchase.

### Three examples

Rules around what constitutes a valid proof of purchase may differ between countries, but here are three examples of documents that rarely will be considered valid.

#### Shipping confirmation

Shipping confirmations are often sent after a purchase, and contain package tracking and delivery details. Those are usually not a valid proof of purchase.

#### Transaction statement

Transaction statements from a bank may contain some information about a purchase, but there is no details about the seller, the items bought and timestamps may be off. In short, it's generally not seen as a valid proof of purchase.

#### Event ticket

Event tickets, for example a concert or sports game, contain information about the event, but usually does not contain all the required details for a valid receipt.