> For the complete documentation index, see [llms.txt](https://docs.tailent.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tailent.com/use-cases/use-cases/tap-studio-define-invoices-naming-convention.md).

# TAP Studio - Define Invoices Naming Convention

This use case presents how to define a naming convention for your invoices.

In this example, the robot will take 3 invoices that were exported from the invoice solution with file name "INV-" + Index (e.g. INV-000001) and rename them following the naming convention: \[Invoice Number]\_\[Customer Name]\_\[Invoice Year]\[Invoice Month].

In order to reduce the automation running time, we will take the invoice data from the excel file InvoiceReports, as we exported it already during the [previous use case](https://docs.tailent.com/hc/en-us/articles/360013972318).\
If you haven't had the chance to watch our [previous use case](https://docs.tailent.com/hc/en-us/articles/360013972318) about how to extract invoice data using OCR, we recommend you to do so.

Watch the robot in action:

{% embed url="<https://www.youtube.com/watch?v=977TZan-Ll8&feature=emb_title>" %}