Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

Create Fortnox Invoice

fortnox_create_invoice

Create a new invoice in Fortnox from a customer number and line items. Add optional details such as dates, references, currency, fees, and send type to get an invoice with a document number.

Instructions

Create a new invoice in Fortnox.

Args:

  • customer_number (string): Customer number (required)

  • rows (array): Invoice line items (at least one required)

    • Each row: { description, quantity?, price?, article_number?, unit?, discount?, vat?, account_number? }

  • invoice_date (string): Invoice date YYYY-MM-DD (defaults to today)

  • due_date (string): Due date YYYY-MM-DD

  • our_reference (string): Our reference person

  • your_reference (string): Customer's reference

  • invoice_type ('INVOICE' | 'CASH' | 'CARD' | 'UNDEFINED'): Invoice type

  • currency (string): 3-letter currency code

  • terms_of_payment (string): Payment terms code

  • comments (string): Internal comments

  • remarks (string): Remarks printed on invoice

  • freight (number): Shipping cost

  • administration_fee (number): Admin fee

  • send_type ('EMAIL' | 'PRINT' | 'EINVOICE'): How to send

Returns: The created invoice with assigned document number.

Example rows: [{ "description": "Consulting services", "quantity": 10, "price": 1000 }]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYesInvoice rows/lines (at least one required)
freightNoFreight/shipping cost
remarksNoRemarks printed on the invoice
commentsNoComments on the invoice
currencyNoCurrency code (e.g., 'SEK')
due_dateNoDue date (YYYY-MM-DD)
send_typeNoHow to send the invoice
invoice_dateNoInvoice date (YYYY-MM-DD, defaults to today)
invoice_typeNoType of invoice
our_referenceNoOur reference person
your_referenceNoCustomer's reference person
customer_numberYesCustomer number (required)
response_formatNoOutput format: 'markdown' or 'json'markdown
terms_of_paymentNoPayment terms code
administration_feeNoAdministration fee
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so a write operation is expected. The description adds useful context beyond annotations: the return value (created invoice with document number), default for invoice_date, and example row structure. No contradiction.

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

Conciseness4/5

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

The description is organized into Args, Returns, and Example rows. It lists all parameters concisely without fluff. The example is valuable. Slightly longer than ideal but well-structured and every section earns its place.

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?

With 15 parameters and no output schema, the description covers all parameters, the return value, and provides an example. It doesn't address edge cases or error handling, but for a create tool this is reasonably complete, especially given the annotations.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description repeats parameter names but adds an example row structure and clarifies invoice_type/send_type enums. This is helpful but not a significant semantic addition beyond the schema's detailed descriptions.

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 'Create a new invoice in Fortnox' with a specific verb and resource. It distinguishes from sibling tools like fortnox_credit_invoice (credit) and fortnox_update_invoice (update) by being the create operation.

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 context is clear for a create operation, but it does not explicitly name alternatives or when-not-to-use scenarios. It provides defaults and an example, giving practical guidance, but lacks exclusions like 'use fortnox_credit_invoice for credit invoices'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/erp-mafia/fortnox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server