financeapi_key

Lexoffice

Lexoffice is a cloud-based accounting software designed for freelancers and small businesses, offering invoicing, expense management, and integration with banks

Verdict

Lexoffice is a German cloud accounting platform for freelancers and small businesses. When connected to Switchy, your team can @mention it to pull invoices, check VAT status, retrieve contact details, and review financial reports without leaving the conversation. Finance leads and operations staff get the most value — they can answer billing questions in real time during client calls or sprint planning. Setup requires an API key from your Lexoffice account, and the integration respects your existing permission boundaries. Note that Lexoffice is Germany-focused, so currency and tax logic defaults to EUR and German VAT rules.

Common use cases

  • Pull invoice status during client check-ins
  • Verify VAT compliance before quarterly filings
  • Retrieve contact details for payment follow-ups
  • Summarize monthly revenue in team standups
  • Check outstanding receivables before budget meetings

Integration

Vendor
Lexoffice
Category
finance
Auth
API_KEY
Composio slug
lexoffice

Tools

Per-tool listings haven't synced yet for Lexoffice. The connection itself works - your Space can already @-mention it. Tool descriptions will fill in on the next Composio ingest.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Lexoffice and click Connect. 3. You'll be prompted to paste an API key — generate this by logging into your Lexoffice account, going to Settings > API, and creating a new key with read access to invoices, contacts, and reports. 4. Copy the key and paste it into Switchy, then click Authorize. 5. Switchy will confirm the connection and display which Lexoffice account is linked. 6. To test, open any Space and type '@Lexoffice list my recent invoices' — if the integration works, you'll see a summary of your latest billing activity. 7. Grant the integration access only to the data your team needs; you can revoke the API key anytime from Lexoffice settings.

What teammates see: by default, memories from Lexoffice are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Recent Invoice Summary

@Lexoffice show me the last 10 invoices with their amounts, due dates, and payment status.
Open in a Space →

Outstanding Receivables

@Lexoffice list all unpaid invoices from the past 60 days, sorted by amount.
Open in a Space →

Contact Lookup

@Lexoffice find the contact information for [Client Name], including email and billing address.
Open in a Space →

Monthly Revenue Report

@Lexoffice calculate total invoiced revenue for this month, broken down by paid and unpaid.
Open in a Space →

VAT Summary

@Lexoffice show me total VAT collected and owed for Q1 2025, grouped by rate.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@lexoffice show me all unpaid invoices from the last 30 days and their total outstanding amount

Output

Based on the Lexoffice data, you have 7 unpaid invoices from the last 30 days totaling €12,847.50. The breakdown includes: 3 invoices overdue by 5-12 days (€4,200), 2 invoices due within 3 days (€3,150), and 2 invoices not yet due (€5,497.50). The oldest unpaid invoice is #INV-2847 from January 15th for €1,850. This is an illustrative example showing typical invoice query results.

Notes

This example demonstrates read access to invoice data. Requires API key with invoice read permissions. The MCP returns structured financial data that the AI can summarize and prioritize. Actual response format depends on your Lexoffice account structure and invoice volume.

Prompt

@lexoffice create a new draft invoice for Acme Corp with line items: 10 hours consulting at €150/hour and 5 hours support at €100/hour

Output

Draft invoice created in your Lexoffice account with ID #DRAFT-9234. Line items added: Consulting Services (10 hrs × €150) = €1,500 and Support Services (5 hrs × €100) = €500. Subtotal: €2,000. VAT will be calculated based on your Lexoffice tax settings when you finalize the invoice. The draft is now visible in your Lexoffice dashboard for review and sending. This is an illustrative example of invoice creation workflow.

Notes

This example shows write capability — it creates a real draft invoice in your account. Requires API key with invoice write permissions. Always review drafts in Lexoffice before sending to clients. The MCP cannot send invoices directly; that final action happens in the Lexoffice UI for safety.

Prompt

@lexoffice analyze my revenue by client for Q1 2024 and identify which three clients generated the most income

Output

Analyzing Q1 2024 invoices from Lexoffice: Your top three clients by revenue were TechStart GmbH (€28,400 across 12 invoices), Innovate AG (€19,750 across 8 invoices), and Digital Solutions Ltd (€15,200 across 6 invoices). These three clients represent 61% of your Q1 revenue. TechStart shows consistent monthly billing, while Innovate had two large project invoices in March. This is an illustrative example combining Lexoffice data with AI analysis.

Notes

This example pairs financial data retrieval with AI reasoning to surface business insights. The MCP fetches invoice records; the AI performs aggregation and ranking. Useful for quarterly reviews or client prioritization. Results depend on how consistently you've tagged clients in Lexoffice.

Use-case deep-dives

Freelancer invoice lookups during client calls

When Lexoffice MCP helps solo consultants stay responsive

A freelance designer fields a client question mid-call: 'Did you bill us for the April revisions?' Without the MCP, she tabs out to Lexoffice, logs in, searches invoices, and loses thread. With the MCP connected, she asks Switchy to pull the invoice by client name and date range—answer in 8 seconds, call stays on track. This works because Lexoffice's API exposes invoice search and retrieval, and the MCP likely wraps those endpoints for natural-language queries. The trade-off: if you're a multi-person finance team reconciling hundreds of transactions daily, you'll hit the MCP's rate limits and want a dedicated dashboard instead. But for solopreneurs and small studios doing 10-30 invoices a month, this is the fastest way to surface billing details without context-switching. If you bill clients while you're talking to them, connect this MCP.

Monthly expense categorization for tax prep

Where Lexoffice MCP falls short for batch accounting work

A 3-person agency needs to categorize 200 expenses at month-end for their tax advisor. The Lexoffice MCP can fetch expense records and read categories, but it's not built for bulk edits or multi-step workflows—each update is a separate API call, and the MCP has no batch-update tool. You'll spend more time prompting Switchy than you would clicking through Lexoffice's native UI. The MCP shines when you need quick lookups ('show me all software expenses this quarter') or spot-checks during planning meetings, not when you're doing repetitive data entry. If your month-end close involves more than 20 manual categorizations, keep that work in Lexoffice's web app and use the MCP only for ad-hoc queries. Save the MCP for the questions, not the grunt work.

Real-time cash flow checks in budget meetings

When this MCP wins for live financial visibility

A 6-person SaaS team holds weekly budget syncs to decide whether they can afford a new contractor. The founder used to screenshot Lexoffice's dashboard and paste it into Slack—stale data, manual step. Now she connects the Lexoffice MCP to Switchy and asks 'what's our current account balance and outstanding receivables?' during the call. The MCP pulls live data from Lexoffice's API, Switchy formats it in the shared canvas, and the team makes the call in real time. This works because Lexoffice exposes account balances and invoice statuses via API, and the MCP translates those into conversational queries. The ceiling: if your finance stack spans 4+ tools (Stripe, Xero, bank feeds), the MCP only covers Lexoffice's slice—you'll still tab out for the full picture. But for teams using Lexoffice as their single source of truth, this is the fastest way to get numbers into a decision without leaving the conversation.

Frequently asked

What does the Lexoffice MCP do in Switchy?

It connects your Lexoffice accounting data to Switchy's AI workspace, letting your team query invoices, expenses, and financial records in natural language. Instead of logging into Lexoffice separately, you ask questions like "show unpaid invoices from Q1" and the AI pulls live data. Useful for finance teams who want fast answers without switching tabs.

Do I need admin access to connect Lexoffice?

You need a Lexoffice API key, which typically requires account owner or admin permissions to generate. The key lives in your Lexoffice settings under API or integrations. Once you paste it into Switchy, the connection is live for your entire workspace. Standard Lexoffice users without admin rights can't create keys.

Can the Lexoffice MCP create invoices or edit transactions?

That depends on which tools Lexoffice exposes via their API and which Switchy has implemented. Most finance MCPs start read-only for safety — you can query data but not modify it. If you need write access, check the tool list on this page once it's populated, or ask Switchy support to prioritise write operations for your use case.

How is this different from just using Lexoffice directly?

Lexoffice's UI is built for data entry and compliance workflows. The MCP lets you ask ad-hoc questions in plain English without navigating menus or exporting CSVs. It's faster for "what's our burn rate this month" queries, but you'll still use Lexoffice for invoice creation, bank reconciliation, and tax filing. Think of it as a query layer, not a replacement.

Who on the team should connect the Lexoffice MCP?

Whoever owns your Lexoffice account or has API key access. Once connected, everyone in your Switchy workspace can query the data according to your workspace permissions. If you want to restrict financial visibility, connect it in a separate Switchy workspace with only finance team members. The API key itself stays private in Switchy's credential store.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.