[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create invoice

> Create an invoice for a relation from one or more lines, and optionally email it to the relation. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/e-boekhouden/create_invoice

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Create an invoice for a relation from one or more lines, and optionally email it to the relation.

e-Boekhouden MCP tools: https://cotlet.dev/docs/mcp/e-boekhouden.md

MCP tool: `e_boekhouden_write → create_invoice`

Access: write. Confirm: waits for the user's OK before it runs.

Creates one invoice in the books. Required: relation_id, term_of_payment in days, template_id and at least one line. Leave invoice_number empty and e-Boekhouden assigns the next one. Amounts are excluding or including VAT as in_ex_vat says; a line takes a fixed discount or a percentage, not both. Pass send_email to mail it to the relation straight away, otherwise it only exists in e-Boekhouden. The invoice is a legal document and cannot be edited or deleted through the API. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `relation_id` | integer | yes | Relation ID from list_relations. |
| `term_of_payment` | integer | yes | Payment term in days. |
| `template_id` | integer | yes | Template ID from list_invoice_templates. |
| `items` | array | yes | Lines: description, quantity, price_per_unit, vat_code, ledger_id, optional product_id, discount_amount or discount_percentage. vat_code is one of HOOG_VERK_21, LAAG_VERK_9, VERL_VERK, VERL_VERK_L9, AFW, BU_EU_VERK, BI_EU_VERK, BI_EU_VERK_D, AFST_VERK, GEEN. |
| `in_ex_vat` | enum | no | IN if line prices include VAT, EX if they exclude it. |
| `date` | date | no | Invoice date. Default: today. |
| `invoice_number` | string | no | Your own number, must end with a digit. Empty: next number. |
| `reference` | string | no | Payment reference. |
| `text` | string | no | Text on the invoice. |
| `send_email` | boolean | no | true to email the invoice to the relation now. Default: false. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "e_boekhouden_write",
    "arguments": {
      "operation": "create_invoice",
      "arguments": {
        "relation_id": 1042,
        "template_id": 3,
        "term_of_payment": 14,
        "in_ex_vat": "EX",
        "items": [
          {
            "description": "Consulting October 2026",
            "quantity": 10,
            "price_per_unit": 85,
            "vat_code": "HOOG_VERK_21",
            "ledger_id": 8000
          }
        ]
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "invoice_id": 9021,
    "invoice_number": "2026-0143",
    "date": "2026-10-12",
    "relation_id": 1042,
    "total_excl_vat": 850,
    "vat": 178.5,
    "total_incl_vat": 1028.5,
    "emailed": false
  },
  "isError": false
}
```

Previous: [Update relation](https://cotlet.dev/docs/mcp/e-boekhouden/update_relation.md)
Next: [Create mutation](https://cotlet.dev/docs/mcp/e-boekhouden/create_mutation.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.