[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)

# Procountor API and MCP server

> Yes, Procountor has a REST API with write access to invoices, ledger receipts and business partners, but you cannot just switch it on (checked 14 Oct 2026). You request a test environment and client credentials, ask Procountor for production access, and the company needs a Procountor Financials environment with API access enabled; usage may carry monthly fees. There is no official MCP server.

Finnish cloud accounting and invoicing software (Procountor Financials, by Finago): sales and purchase invoices, journal receipts, a customer, supplier and person register, payments and accounting reports in one company account.

## What is the Procountor API?

Cotlet's Procountor API exposes 15 endpoints for your own Procountor account: list sales invoices, list unpaid sales invoices, get sales invoice, list purchase invoices, get purchase invoice, list partners, list journal receipts, get general ledger, create partner, create sales invoice, approve sales invoice, send sales invoice, verify purchase invoice, approve purchase invoice and create journal receipt. The list_sales_invoices endpoint returns sales invoices with customer, number, dates, totals and status. Each endpoint takes simple JSON inputs like invoice_id, limit or cursor and works both as an operation of the procountor_read or procountor_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 15 (8 read, 7 write)
- **Updated:** 2026-10-19

Yes, Procountor has a REST API with write access to invoices, ledger receipts and business partners, but you cannot just switch it on (checked 14 Oct 2026). Cotlet is a hosted MCP server and REST API for Procountor with 15 endpoints (8 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Procountor have an official API?

Yes, Procountor has a REST API with write access to invoices, ledger receipts and business partners, but you cannot just switch it on (checked 14 Oct 2026). You request a test environment and client credentials, ask Procountor for production access, and the company needs a Procountor Financials environment with API access enabled; usage may carry monthly fees. There is no official MCP server.

| Task | Procountor official | Cotlet |
|---|---|---|
| List and read sales invoices | Yes: Batch GET /invoices; needs API credentials | Yes |
| Create, approve and send sales invoices | Yes: POST /invoices; endpoints that trigger financial transactions can require approval in the Procountor Key app | Yes |
| Read and approve purchase invoices | Yes: Same invoices resource; docs we could open do not list the approval calls | Yes |
| List customers, suppliers and persons | Yes: GET /businesspartners | Yes |
| Add a partner | Yes: POST /businesspartners; name and type are required | Yes |
| Create and list journal receipts | Yes: Ledger receipts resource | Yes |
| Read the general ledger | Partly: Ledger receipts are readable; the General ledger report itself is not documented in the pages we could open | Yes |

Sources: [Procountor API developer portal](https://dev.procountor.com/), [Procountor API: general information](https://dev.procountor.com/general-information/), [Procountor API: authentication](https://dev.procountor.com/api-authentication/), [Procountor API: certification](https://dev.procountor.com/api-certification/)

## For AI agents

```text
Yes, Procountor has a REST API with write access to invoices, ledger receipts and business partners, but you cannot just switch it on (checked 14 Oct 2026). You request a test environment and client credentials, ask Procountor for production access, and the company needs a Procountor Financials environment with API access enabled; usage may carry monthly fees. There is no official MCP server.
Cotlet provides a hosted MCP server and REST API for Procountor: 15 tools (8 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=procountor, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    procountor_read, procountor_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/procountor, each operation at its own route, e.g. POST /api/v1/procountor/partners/{partner_id}/sales-invoices
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_sales_invoices, list_unpaid_sales_invoices, get_sales_invoice, list_purchase_invoices, get_purchase_invoice, list_partners, list_journal_receipts, get_general_ledger, create_partner, create_sales_invoice, approve_sales_invoice, send_sales_invoice, verify_purchase_invoice, approve_purchase_invoice, create_journal_receipt
Confirm      create_partner, create_sales_invoice, approve_sales_invoice, send_sales_invoice, verify_purchase_invoice, approve_purchase_invoice, create_journal_receipt (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/procountor-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=procountor, requests Procountor in the Cotlet console and creates an API key there.
2. The user signs in to Procountor once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Procountor for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Procountor server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Procountor in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Procountor only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Procountor login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Procountor's terms; Cotlet is not affiliated with Procountor.
```

## What can an AI agent do in Procountor?

Cotlet is best for Finnish finance teams and bookkeepers who want an AI agent to create, approve and chase Procountor invoices without running or fixing a server.

- **[Create and send sales invoices](https://cotlet.dev/integrations/procountor-api-mcp-server/create-and-send-sales-invoices.md)**: "Create a Procountor sales invoice for Nordic Print Oy: 10 hours of consulting at 80.00 EUR plus VAT, dated today. Save it, show me the totals, and after my OK approve and send it." → `list_partners`, `create_sales_invoice`, `approve_sales_invoice`, `send_sales_invoice`
- **[Verify and approve purchase invoices](https://cotlet.dev/integrations/procountor-api-mcp-server/approve-purchase-invoices.md)** (runs: daily): "List the Procountor purchase invoices waiting for my verification or approval. Approve the ones from suppliers I named in the list below that match the amounts, and leave the rest with a one-line reason." → `list_purchase_invoices`, `get_purchase_invoice`, `verify_purchase_invoice`, `approve_purchase_invoice`
- **[List unpaid sales invoices](https://cotlet.dev/integrations/procountor-api-mcp-server/list-unpaid-invoices.md)** (runs: weekly): "Every Monday list the Procountor sales invoices that are past their due date and still unpaid, grouped by customer with the days overdue, and tell me which customers have more than one." → `list_unpaid_sales_invoices`, `get_sales_invoice`, `list_partners`
- **Book journal receipts**: "Create a Procountor journal receipt dated 2026-10-31 named "October rent accrual": debit account 7000 for 1,200.00 and credit account 1900 for 1,200.00. Leave it Unfinished so I can check it." → `list_journal_receipts`, `create_journal_receipt`
- **Export the general ledger for your accountant**: "Pull the Procountor general ledger for September 2026 and list the journal receipts that are still Unfinished, so I can send both to my accountant." → `get_general_ledger`, `list_journal_receipts`

## Can Procountor automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Procountor connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to verify and approve purchase invoices, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/procountor/purchase-invoices. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/procountor/purchase-invoices with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Procountor.

### list_sales_invoices

Sales invoices with customer, number, dates, totals and status. Access: read. REST: `GET /api/v1/procountor/sales-invoices`. MCP: `procountor_read → list_sales_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | unfinished, not_sent, sent, partly_paid, paid, marked_paid or invalidated. |
| `partner_id` | string | no | Customer ID from list_partners. |
| `date_from` | string | no | Earliest invoice date, YYYY-MM-DD. |
| `date_to` | string | no | Latest invoice date, YYYY-MM-DD. |
| `limit` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists sales invoices, newest first. Filter by status (unfinished, not_sent, sent, partly_paid, paid, marked_paid, invalidated), by customer or by invoice date. Invalidated invoices appear only when you ask for that status. Pages hold up to 200 invoices; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "si_10482",
      "number": "10482",
      "customer": "Nordic Print Oy",
      "invoice_date": "2026-10-14",
      "due_date": "2026-10-28",
      "total": 1004,
      "currency": "EUR",
      "status": "sent"
    },
    {
      "invoice_id": "si_10451",
      "number": "10451",
      "customer": "Studio Kivi",
      "invoice_date": "2026-09-20",
      "due_date": "2026-10-04",
      "total": 1240,
      "currency": "EUR",
      "status": "partly_paid"
    }
  ],
  "next_cursor": null
}
```

### list_unpaid_sales_invoices

Sales invoices that are Sent or Partly paid, with days overdue. Access: read. REST: `GET /api/v1/procountor/unpaid-sales-invoices`. MCP: `procountor_read → list_unpaid_sales_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `due_before` | string | no | Only invoices with a due date before this day, YYYY-MM-DD. |
| `partner_id` | string | no | Customer ID from list_partners. |
| `limit` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns sales invoices whose status is Sent or Partly paid, oldest due date first. Paid and Marked paid are never listed. For a Partly paid invoice the open amount is shown next to the total. Pass due_before to see only invoices past a date. Pages hold up to 200 invoices.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "si_10451",
      "number": "10451",
      "customer": "Studio Kivi",
      "due_date": "2026-10-04",
      "days_overdue": 10,
      "total": 1240,
      "open_amount": 940,
      "currency": "EUR",
      "status": "partly_paid"
    },
    {
      "invoice_id": "si_10460",
      "number": "10460",
      "customer": "Nordic Print Oy",
      "due_date": "2026-10-07",
      "days_overdue": 7,
      "total": 800,
      "open_amount": 800,
      "currency": "EUR",
      "status": "sent"
    }
  ],
  "next_cursor": null
}
```

### get_sales_invoice

One sales invoice with rows, VAT, payments and status. Access: read. REST: `GET /api/v1/procountor/invoices/{invoice_id}/sales-invoice`. MCP: `procountor_read → get_sales_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Sales invoice ID from list_sales_invoices or create_sales_invoice. |

Returns the invoice header, every row with quantity, unit price and VAT, the totals and the payments allocated so far. Status is one of the Procountor sales invoice statuses. Use it before approve_sales_invoice to read the totals.

Example response:

```json
{
  "invoice_id": "si_10482",
  "number": "10482",
  "customer": "Nordic Print Oy",
  "status": "unfinished",
  "invoice_date": "2026-10-14",
  "due_date": "2026-10-28",
  "currency": "EUR",
  "rows": [
    {
      "name": "Consulting",
      "quantity": 10,
      "unit_price": 80,
      "vat_percent": 25.5,
      "net": 800
    }
  ],
  "net_total": 800,
  "vat_total": 204,
  "total": 1004,
  "payments": []
}
```

### list_purchase_invoices

Purchase invoices with supplier, amount and circulation status. Access: read. REST: `GET /api/v1/procountor/purchase-invoices`. MCP: `procountor_read → list_purchase_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | received, unfinished, verified, approved or payment_denied. |
| `waiting_for_me` | boolean | no | true lists only invoices waiting for your verification or approval. |
| `partner_id` | string | no | Supplier ID from list_partners. |
| `limit` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists purchase invoices, newest first. Filter by status (received, unfinished, verified, approved, payment_denied) or set waiting_for_me to true to see only invoices waiting for your verification or approval. Approval circulation must be turned on in the company for the circulation statuses to apply.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "pi_77120",
      "supplier": "Papertrail Oy",
      "invoice_number": "PT-5521",
      "due_date": "2026-10-30",
      "total": 372,
      "currency": "EUR",
      "status": "received",
      "waiting_for": "approval"
    }
  ],
  "next_cursor": null
}
```

### get_purchase_invoice

One purchase invoice with rows, stamps, comments and duplicate warnings. Access: read. REST: `GET /api/v1/procountor/invoices/{invoice_id}/purchase-invoice`. MCP: `procountor_read → get_purchase_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Purchase invoice ID from list_purchase_invoices. |

Returns supplier, amounts, dates, the verification and approval stamps already on the invoice, the invoice comments and any duplicate warning that matches by dates, invoice number, bank reference, sender or total sum. Use it before verify_purchase_invoice or approve_purchase_invoice.

Example response:

```json
{
  "invoice_id": "pi_77120",
  "supplier": "Papertrail Oy",
  "invoice_number": "PT-5521",
  "status": "received",
  "total": 372,
  "currency": "EUR",
  "due_date": "2026-10-30",
  "stamps": [],
  "comments": [],
  "duplicate_warning": null
}
```

### list_partners

Customers, suppliers and persons from the register. Access: read. REST: `GET /api/v1/procountor/partners`. MCP: `procountor_read → list_partners`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Part of the partner name or business ID. |
| `type` | string | no | customer, supplier or person. |
| `limit` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches the business partner register by name or business ID. Type is customer, supplier or person. Use the partner_id as the customer in create_sales_invoice. Pages hold up to 200 partners.

Example response:

```json
{
  "partners": [
    {
      "partner_id": "bp_20417",
      "name": "Nordic Print Oy",
      "type": "customer",
      "business_id": "1234567-8",
      "email": "billing@nordicprint.example"
    }
  ],
  "next_cursor": null
}
```

### list_journal_receipts

Journal receipts with name, date, VAT type and status. Access: read. REST: `GET /api/v1/procountor/journal-receipts`. MCP: `procountor_read → list_journal_receipts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | unfinished or approved. |
| `date_from` | string | no | Earliest receipt date, YYYY-MM-DD. |
| `date_to` | string | no | Latest receipt date, YYYY-MM-DD. |
| `limit` | integer | no | 1 to 200. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists journal receipts, newest first. Status is Unfinished (saved, still editable) or Approved (part of the official accounts). Filter by status or receipt date. Pages hold up to 200 receipts.

Example response:

```json
{
  "receipts": [
    {
      "receipt_id": "jr_3301",
      "name": "October rent accrual",
      "receipt_date": "2026-10-31",
      "vat_type": "No VAT",
      "vat_status": "Not applicable",
      "status": "unfinished"
    }
  ],
  "next_cursor": null
}
```

### get_general_ledger

The General ledger report for a period, by account. Access: read. REST: `GET /api/v1/procountor/general-ledger`. MCP: `procountor_read → get_general_ledger`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date_from` | string | yes | First day of the period, YYYY-MM-DD. |
| `date_to` | string | yes | Last day of the period, YYYY-MM-DD. |
| `account` | string | no | Limit to one account number. |

Returns the same account rows as Reports > General ledger for the dates you give: each account with its entries and balance. Entries carry the receipt they come from. Use it to hand the books to an accountant without opening the report by hand.

Example response:

```json
{
  "period": {
    "from": "2026-09-01",
    "to": "2026-09-30"
  },
  "accounts": [
    {
      "account": "3000",
      "name": "Sales",
      "entries": 12,
      "balance": -9400
    },
    {
      "account": "1700",
      "name": "Accounts receivable",
      "entries": 12,
      "balance": 9400
    }
  ]
}
```

### create_partner

Add a customer, supplier or person to the register. Access: write, asks the user first. REST: `POST /api/v1/procountor/partners`. MCP: `procountor_write → create_partner`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Partner name. |
| `type` | string | yes | customer, supplier or person. |
| `business_id` | string | no | Business ID, for example 1234567-8. |
| `email` | string | no | Contact email for invoices. |

Adds a partner with name, type and optional business ID, email and address. Default products, accounts and dimensions are not set; add them in Registers when needed. It reaches no one, but the partner stays in the register until you edit it there. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "partner_id": "bp_20418",
  "name": "Studio Kivi",
  "type": "customer",
  "created": true
}
```

### create_sales_invoice

Save a sales invoice as Unfinished and return the totals. Access: write, asks the user first. REST: `POST /api/v1/procountor/partners/{partner_id}/sales-invoices`. MCP: `procountor_write → create_sales_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `partner_id` | string | yes | Customer ID from list_partners. |
| `invoice_date` | string | no | YYYY-MM-DD. Default: today. |
| `rows` | array | yes | Invoice rows: name, quantity, unit_price, vat_percent. |
| `additional_info` | string | no | Text shown above the invoice rows. |

Creates the invoice the way Save does in Invoice view. Procountor generates the invoice number on save. The invoice stays Unfinished: editable, not sent and not yet counted in tax reports. Returns net, VAT and gross totals and the due date calculated from the payment terms. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "si_10482",
  "number": "10482",
  "customer": "Nordic Print Oy",
  "status": "unfinished",
  "invoice_date": "2026-10-14",
  "due_date": "2026-10-28",
  "currency": "EUR",
  "net_total": 800,
  "vat_total": 204,
  "total": 1004
}
```

### approve_sales_invoice

Approve an Unfinished sales invoice so it can be sent. Access: write, asks the user first. REST: `POST /api/v1/procountor/invoices/{invoice_id}/sales-invoice/approve`. MCP: `procountor_write → approve_sales_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Sales invoice ID from list_sales_invoices or create_sales_invoice. |

Does what Approve does in Invoice view. The status changes from Unfinished to Not sent, and Procountor counts the invoice in Accounting Act and tax reports. Only approved invoices can be sent. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "si_10482",
  "number": "10482",
  "status": "not_sent"
}
```

### send_sales_invoice

Send an approved sales invoice on its invoice channel. Access: write, asks the user first. REST: `POST /api/v1/procountor/invoices/{invoice_id}/sales-invoices`. MCP: `procountor_write → send_sales_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Sales invoice ID from list_sales_invoices or create_sales_invoice. |

Does what Send does in Invoice view. The status changes to Sent and the invoice joins the invoices-to-be-sent list. Procountor dispatches it automatically three days before the invoice date, or immediately if the date is today, within three days or in the past. A Sent invoice cannot be changed or invalidated. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "si_10482",
  "number": "10482",
  "status": "sent",
  "dispatch": "immediate"
}
```

### verify_purchase_invoice

Verify a purchase invoice in circulation, with an optional comment. Access: write, asks the user first. REST: `POST /api/v1/procountor/invoices/{invoice_id}/purchase-invoice/verify`. MCP: `procountor_write → verify_purchase_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Purchase invoice ID from list_purchase_invoices. |
| `comment` | string | no | Optional comment stored with the stamp. |

Does what Verify does in the Verification view: adds a stamp with your name, date, time and comment. It works only for invoices where you are a named verifier, and approval circulation must be on. When all specified verifiers have checked it, the status becomes Verified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "pi_77120",
  "status": "verified",
  "stamp": {
    "by": "You",
    "at": "2026-10-14T09:12:00+03:00",
    "comment": "Matches PO 4471"
  }
}
```

### approve_purchase_invoice

Approve a purchase invoice in circulation so it can be paid. Access: write, asks the user first. REST: `POST /api/v1/procountor/invoices/{invoice_id}/purchase-invoice/approve`. MCP: `procountor_write → approve_purchase_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Purchase invoice ID from list_purchase_invoices. |
| `comment` | string | no | Optional comment stored with the stamp. |

Does what Approve does in the Verification view: adds an approval stamp. If verifiers are specified, the invoice must be verified first. Once all approvers have approved, the status becomes Approved, the invoice counts as a business transaction and can be paid in the Payment view. This tool does not pay it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "pi_77120",
  "status": "approved",
  "stamp": {
    "by": "You",
    "at": "2026-10-14T09:14:00+03:00",
    "comment": "Matches PO 4471"
  }
}
```

### create_journal_receipt

Save a journal receipt with debit and credit rows as Unfinished. Access: write, asks the user first. REST: `POST /api/v1/procountor/journal-receipts`. MCP: `procountor_write → create_journal_receipt`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Receipt name. |
| `receipt_date` | string | yes | YYYY-MM-DD. |
| `vat_type` | string | yes | VAT type as named in Procountor. |
| `vat_status` | string | yes | VAT status as named in Procountor. |
| `rows` | array | yes | Accounting rows: account, amount (plus debit, minus credit). |

Creates the receipt the way New journal receipt does. Name, VAT type, VAT status and receipt date are required. Rows use plus for debit and minus for credit and must balance. The receipt stays Unfinished and editable; it is not part of the official accounts until someone clicks Approve in Procountor. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "receipt_id": "jr_3301",
  "name": "October rent accrual",
  "receipt_date": "2026-10-31",
  "status": "unfinished",
  "rows": [
    {
      "account": "7000",
      "amount": 1200
    },
    {
      "account": "1900",
      "amount": -1200
    }
  ]
}
```

## How do I connect Procountor to Claude Code, Codex or Cursor?

Connecting Procountor takes three steps: sign up, sign in to Procountor once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Procountor to your agent.

1. **Create an account** Sign up and add Procountor in the console. Your API key is there too.

2. **Sign in to Procountor in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Procountor there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Procountor tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Create a Procountor sales invoice for Nordic Print Oy: 10 hours of consulting at 80.00 EUR plus VAT, dated today. Save it, show me the totals, and after my OK approve and send it.
```

### Call Procountor from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/procountor with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/procountor/partners/bp_20417/sales-invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"invoice_date":"2026-10-14","rows":[{"name":"Consulting","quantity":10,"unit_price":80,"vat_percent":25.5}]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "invoice_id": "si_10482",
  "number": "10482",
  "customer": "Nordic Print Oy",
  "status": "unfinished",
  "invoice_date": "2026-10-14",
  "due_date": "2026-10-28",
  "currency": "EUR",
  "net_total": 800,
  "vat_total": 204,
  "total": 1004
}
```

## Why use Cotlet for Procountor?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Procountor yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Procountor changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Procountor to Cotlet?

Yes. You sign in to Procountor yourself, in your own Cloud Browser, and we never save your password. Your agents only get Procountor once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Procountor integration?**

No, Cotlet is independent of Procountor. Procountor's own API is open only to approved partners. Cotlet works through your own Procountor account, the way you use Procountor in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Procountor in your console: your agents lose access at once and you stay signed in. Signing out of Procountor in the browser works too, and Reset browser deletes the whole profile.

## Is there a Procountor MCP server on GitHub?

The realistic option is the official Procountor API. It is a full REST API, but it is built for software vendors: you request a test environment and credentials, apply for production access, implement OAuth 2.0 and keep a token for every company. Cotlet is that layer, hosted: your agent gets MCP tools and one REST key after you sign in to Procountor once.

|  | Official API | Cotlet |
|---|---|---|
| Setup | Request a test environment and client credentials, build and test against it, then request production access | Sign up, sign in to Procountor once, add one MCP server or API key |
| When Procountor changes | A new latest API version is published every month and supported versions every quarter; you track release notes and update your code | Our team tests it daily and fixes it for you; failed calls are free |
| Your credentials | Client ID and secret in your code, plus a refresh token you must keep secret | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Access tokens last one hour and refresh tokens six months; your code renews them and handles a removed user | Your Cloud Browser keeps you signed in; if Procountor logs you out, your agent gets a link to sign in again |
| Upkeep | You write, host and monitor the integration | Nothing to host or update |
| Where it runs | Your own server, with your own MCP wrapper for agents | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | API usage may carry monthly fees as an add-on to the company, and your own build time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Procountor changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Procountor API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Procountor API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Procountor account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Procountor yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Procountor only after you enable it. When Procountor signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Procountor, sign out of Procountor in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Procountor's terms:** You use your own Procountor account and stay responsible for following Procountor's terms. Cotlet is independent and not affiliated with Procountor. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Procountor in the console and press Request access. Then you create your API key and connect Procountor there.

**Do I need to be technical?**

No. You sign in to Procountor once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Procountor to Cotlet?**

Yes. You sign in to Procountor yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Procountor once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Procountor sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Procountor cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Procountor's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Procountor sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Procountor login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Procountor offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Does Procountor ask for approval in the Key app?**

In the official API, endpoints that trigger financial transactions or change user or company settings need approval in the Procountor Key app, and the user confirms within 5 minutes. Cotlet never bypasses MFA, so if Procountor asks for an approval, it stays with you.

**Which Procountor product does this work with?**

Procountor Financials. The official API targets that product, and the invoice and receipt screens Cotlet follows are its screens.

**Can my agent post or send messages in Procountor without asking me?**

No. Every call to create_partner, create_sales_invoice, approve_sales_invoice, send_sales_invoice, verify_purchase_invoice, approve_purchase_invoice or create_journal_receipt waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Procountor API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/procountor from the HTTP Request node.

---

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.