Kema Invoice

Mark invoice paid

mark_invoice_paid

Mark a Sent or Overdue invoice as Paid. Optionally set the payment date (defaults to now).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`paid_at`	No	Payment timestamp, ISO 8601 (e.g. 2026-09-07T10:00:00Z); defaults to now.
`invoice_id`	Yes	The Sent or Overdue invoice UUID.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Invoice UUID.
`type`	Yes	Document type: invoice, credit_note, provision or quote.
`notes`	Yes	Notes printed on the document.
`status`	Yes	Document status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.
`paid_at`	Yes	Payment timestamp (ISO 8601), null while unpaid.
`sent_at`	Yes	Issue timestamp (ISO 8601), null while Draft.
`currency`	Yes	ISO 4217 currency code (EUR, USD, GBP or CHF).
`due_date`	Yes	Due date, YYYY-MM-DD.
`matter_id`	Yes	Matter (dossier) UUID, null when unassigned.
`net_total`	Yes	Total excl. VAT, in the document currency.
`tax_total`	Yes	VAT amount, in the document currency.
`amount_due`	Yes	Gross total minus applied provisions, null when not computed.
`company_id`	Yes	Client company UUID.
`created_at`	Yes	Creation timestamp (ISO 8601).
`issue_date`	Yes	Issue date, YYYY-MM-DD.
`updated_at`	Yes	Last update timestamp (ISO 8601).
`gross_total`	Yes	Total incl. VAT, in the document currency.
`valid_until`	Yes	Quote validity limit, YYYY-MM-DD; null for other types.
`vat_scenario`	Yes	Fiscal scenario frozen at creation (e.g. domestic, eu_b2b_reverse_charge).
`payment_terms`	Yes	Payment terms: Net-15, Net-30, Net-60, Net-90 or Due on Receipt.
`advances_total`	Yes	Sum of provisions applied, in the document currency.
`created_source`	Yes	Origin of the document: manual (app) or mcp (agent).
`credit_note_id`	Yes	Credit note UUID that cancelled this invoice.
`internal_notes`	Yes	Private notes, never printed.
`invoice_number`	Yes	Human-readable document number.
`invopop_status`	Yes	Fiscal certification status from the provider, null before issuance.
`source_quote_id`	Yes	Quote UUID this invoice was converted from.
`delivery_channel`	Yes	Delivery channel: Email, e-Invoice or Manual.
`replaces_invoice_id`	Yes	Original invoice UUID when this is a rectificative.
`replaced_by_invoice_id`	Yes	Rectificative UUID when this invoice was rectified.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 7, 2026

addedInput schema / properties / invoice_id / description
```
Added value: +"The Sent or Overdue invoice UUID."
```

changedInput schema / properties / paid_at / description

Previous value: -"ISO datetime; defaults to now."New value: +"Payment timestamp, ISO 8601 (e.g. 2026-09-07T10:00:00Z); defaults to now."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "advances_total": {
+      "description": "Sum of provisions applied, in the document currency.",
+      "type": "number"
+    },
+    "amount_due": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Gross total minus applied provisions, null when not computed."
+    },
+    "company_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Client company UUID."
+    },
+    "created_at": {
+      "description": "Creation timestamp (ISO 8601).",
+      "type": "string"
+    },
+    "created_source": {
+      "description": "Origin of the document: manual (app) or mcp (agent).",
+      "type": "string"
+    },
+    "credit_note_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Credit note UUID that cancelled this invoice."
+    },
+    "currency": {
+      "description": "ISO 4217 currency code (EUR, USD, GBP or CHF).",
+      "type": "string"
+    },
+    "delivery_channel": {
+      "description": "Delivery channel: Email, e-Invoice or Manual.",
+      "type": "string"
+    },
+    "due_date": {
+      "description": "Due date, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "gross_total": {
+      "description": "Total incl. VAT, in the document currency.",
+      "type": "number"
+    },
+    "id": {
+      "description": "Invoice UUID.",
+      "type": "string"
+    },
+    "internal_notes": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Private notes, never printed."
+    },
+    "invoice_number": {
+      "description": "Human-readable document number.",
+      "type": "string"
+    },
+    "invopop_status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Fiscal certification status from the provider, null before issuance."
+    },
+    "issue_date": {
+      "description": "Issue date, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "matter_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Matter (dossier) UUID, null when unassigned."
+    },
+    "net_total": {
+      "description": "Total excl. VAT, in the document currency.",
+      "type": "number"
+    },
+    "notes": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Notes printed on the document."
+    },
+    "paid_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Payment timestamp (ISO 8601), null while unpaid."
+    },
+    "payment_terms": {
+      "description": "Payment terms: Net-15, Net-30, Net-60, Net-90 or Due on Receipt.",
+      "type": "string"
+    },
+    "replaced_by_invoice_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Rectificative UUID when this invoice was rectified."
+    },
+    "replaces_invoice_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Original invoice UUID when this is a rectificative."
+    },
+    "sent_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Issue timestamp (ISO 8601), null while Draft."
+    },
+    "source_quote_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Quote UUID this invoice was converted from."
+    },
+    "status": {
+      "description": "Document status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.",
+      "type": "string"
+    },
+    "tax_total": {
+      "description": "VAT amount, in the document currency.",
+      "type": "number"
+    },
+    "type": {
+      "description": "Document type: invoice, credit_note, provision or quote.",
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "Last update timestamp (ISO 8601).",
+      "type": "string"
+    },
+    "valid_until": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Quote validity limit, YYYY-MM-DD; null for other types."
+    },
+    "vat_scenario": {
+      "description": "Fiscal scenario frozen at creation (e.g. domestic, eu_b2b_reverse_charge).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "invoice_number",
+    "type",
+    "status",
+    "company_id",
+    "matter_id",
+    "issue_date",
+    "due_date",
+    "valid_until",
+    "currency",
+    "payment_terms",
+    "delivery_channel",
+    "net_total",
+    "tax_total",
+    "gross_total",
+    "advances_total",
+    "amount_due",
+    "notes",
+    "internal_notes",
+    "paid_at",
+    "sent_at",
+    "invopop_status",
+    "vat_scenario",
+    "source_quote_id",
+    "replaces_invoice_id",
+    "replaced_by_invoice_id",
+    "credit_note_id",
+    "created_source",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnlyHint false, destructiveHint false), the description adds that the payment date defaults to now, but it does not disclose side effects such as idempotency, whether already-paid invoices error, or whether any related records are updated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no redundant phrasing, making it easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple state-change tool, the description covers the essential intent and parameter semantics. It does not describe the return value or error conditions, but given the output schema exists and the action is straightforward, this is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters have clear descriptions: invoice_id is identified as the Sent or Overdue invoice UUID, and paid_at includes format and default behavior. This fully compensates for the schema's technical patterns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Mark) and the target resource (a Sent or Overdue invoice as Paid). It distinguishes this from siblings like cancel_invoice or issue_invoice by specifying the state transition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it (on Sent or Overdue invoices) but does not explicitly mention preconditions like verifying the current state or that it should not be used on already-paid invoices. It does clarify the optional payment date default.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kema Invoice tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.