A quick reference for writing prompts in nextAI. It works best to be concrete, use if-then logic, specify the source such as a text, column or field, use recognisable patterns and keep one clear instruction per prompt. The article also lists what works less well and the common prompt types.
Quick reference – Prompts in nextAI
✅ Do’s (what works well)
Be concrete
For example:
“Use the first line description as the invoice description”
Use ‘if–then’ logic
For example:
“If ‘reverse charge’ occurs, set VAT to reversed”
Specify the source (text, column, field)
For example:
“Take value from column ‘Description’ for line text”
Use recognisable patterns
For example:
“Recognise order number if it starts with ‘PO’”
Keep it simple
One clear instruction per prompt often yields the best result
❌ Don’ts (what works less well)
Too general instructions
For example: “Recognise the invoice better”
No clear action
For example: “Check the data”
Too much logic in one prompt
(better to split into multiple prompts)
Vague references
For example: “Use the correct column”
🔧 Common prompt types
Determine description
“Use first line as invoice description”
VAT logic
“If ‘VAT reverse charge’ occurs, set VAT to reversed”
Order recognition
“Use only order numbers that start with ‘PO’”
Additional costs
“Post lines with ‘freight’ as shipping costs”
Combining fields
“Combine article number and description into one text field”
Language / translation
“Translate German texts into English before processing”
💡 Practical use
- Start with one simple prompt
- Test on one invoice
- Refine if necessary
- Always check the result on first application
