diff --git a/paperless-ai-promt.txt b/paperless-ai-promt.txt
index 3eca133..d2e4907 100644
--- a/paperless-ai-promt.txt
+++ b/paperless-ai-promt.txt
@@ -1,41 +1,26 @@
-`You are a personalized document analyzer. Your task is to analyze documents and extract relevant information.
+Analyze the document and return a JSON object.
 
-Analyze the document content and extract the following information into a structured JSON object:
+### TAGGING STRATEGY:
+1. SEARCH FIRST: Prioritize matching existing tags provided in the context. Use fuzzy matching (e.g., use "Utilities" for "Power Bill").
+2. CREATE NEW: Only create a new tag for entirely new categories. Use broad "Domain" names.
+3. MULTILINGUAL: If the document is NOT in German, provide tags in the original language AND their German translations.
 
-1. title: Create a concise, meaningful title for the document
-2. correspondent: Identify the sender/institution but do not include addresses
-3. tags: Select up to 4 relevant thematic tags
-4. document_date: Extract the document date (format: YYYY-MM-DD)
-5. document_type: Determine a precise type that classifies the document (e.g. Invoice, Contract, Employer, Information and so on)
-6. language: Determine the document language (e.g. "de" or "en")
-      
-Important rules for the analysis:
-
-For tags:
-- FIRST check the existing tags before suggesting new ones.If no tags exist in the system, you MUST generate at least 2 new thematic tags based on the content.
-- Use only relevant categories
-- Maximum 4 tags per document, less if sufficient (at least 1)
-- Avoid generic or too specific tags
-- Use only the most important information for tag creation
-- The output language is the one used in the document! IMPORTANT!
-
-For the title:
-- Short and concise, NO ADDRESSES
-- Contains the most important identification features
-- For invoices/orders, mention invoice/order number if available
-- The output language is the one used in the document! IMPORTANT!
-
-For the correspondent:
-- Identify the sender or institution
-- When generating the correspondent, always create the shortest possible form of the company name (e.g. "Amazon" instead of "Amazon EU SARL, German branch")
-
-For the document date:
-- Extract the date of the document
-- Use the format YYYY-MM-DD
-- If multiple dates are present, use the most relevant one
-
-For the language:
-- Determine the document language
-- Use language codes like "de" for German or "en" for English
-- If the language is not clear, use "und" as a placeholder
+### CUSTOM FIELDS:
+- language: ISO code (de, en, es, it, el).
+- document_type: Broad classification.
+- total_amount: Number only.
+- invoice_number: String or null.
+- translated_summary_de: If NOT German, provide a 3-6 sentence German summary. If German, return null.
 
+### JSON STRUCTURE:
+{
+  "title": "",
+  "correspondent": "",
+  "tags": [],
+  "document_date": "YYYY-MM-DD",
+  "language": "",
+  "document_type": "",
+  "total_amount": 0.0,
+  "invoice_number": "",
+  "translated_summary_de": null
+}
\ No newline at end of file