---
title: Spending Money
description: Guidelines for spending money at Langfuse.
---

# Spending money

  Only applies if you are an employee of Langfuse GmbH

You can expense things you need for work. Don't worry about it if it's a small one-time purchase (sub USD 100) or a small recurring purchase (sub USD 50). If it's larger, it is useful to check with the founders.

You will receive a `Pleo card` when you join Langfuse. Pleo is a spend management tool.

## Using Pleo

- For us to be able to claim VAT back in Germany (and for proper accounting) **we need invoices for everything you pay for & they need to comply with the following**:
  - Be addressed to our company (Langfuse GmbH, see [imprint](/imprint))
  - Include our VAT ID (DE358330767) if it is a cross-border transaction
- Reimbursements & invoice payments: You can get purchases made for the company with your private cards/money reimbursed via Pleo. You are required to submit an invoice via Pleo in order to request this.

## Software Subscriptions

If you need software for work, put it on your Pleo Card.

Please cancel subscriptions that you no longer use.

Many things change rapidly; paying for optionality is often worth it (i.e., go for monthly plans even when the annual is 10-20% cheaper).

We like self-serve software; it reduces operational overhead of renewals/negotiations.

## Travel

Please use your Pleo Card to book travel & pay for reasonable expenses.

Again, you will need to have receipts for everything - have them be addressed to the company if possible.

We only cover economy travel (or 2nd class train). For long flights you can book extra legroom. Please use your discretion & common sense when making purchases with company money.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/handbook/tools-and-processes/spending-money.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.