Procountor fi

Skill apideck-libraries/api-skills/providers/cursor/plugin/skills/procountor-fi

One abstraction, 146 SaaS connectors. Agent skills for Apideck's Unified API — integrate Salesforce, QuickBooks, BambooHR, Jira, Shopify and 140+ more by changing one string.

Install

npx -y skills add apideck-libraries/api-skills --skill procountor-fi

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Procountor integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Procountor. Routes through Apideck with serviceId "procountor-fi".

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.5 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it

Procountor (via Apideck)

Access Procountor through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Procountor plumbing.

Quick facts

Apideck serviceId: procountor-fi
Unified API: Accounting
Auth type: oauth2
Gotchas: page
Procountor docs: https://dev.procountor.com
Homepage: https://procountor.fi/

When to use this skill

Activate this skill when the user explicitly wants to work with Procountor — for example, "create an invoice in Procountor" or "reconcile payments in Procountor". This skill teaches the agent:

Which Apideck unified API covers Procountor (Accounting)
The correct serviceId to pass on every call (procountor-fi)
Procountor-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

Accounting: https://specs.apideck.com/accounting.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List invoices in Procountor
const { data } = await apideck.accounting.invoices.list({
  serviceId: "procountor-fi",
});

Portable across 34 Accounting connectors

The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Procountor to another Accounting connector is a one-string change — no rewrite, no new SDK.

// Today — Procountor
await apideck.accounting.invoices.list({ serviceId: "procountor-fi" });

// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });

This is the compounding advantage of using Apideck over integrating Procountor directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

Procountor via Apideck Accounting

Procountor is a Finnish cloud accounting and financial management platform, part of Accountor Group. Popular with Finnish SMBs and accounting firms.

Entity mapping

Procountor entity	Apideck Accounting resource
Sales Invoice	`invoices`
Purchase Invoice	`bills`
Customer	`customers`
Supplier	`suppliers`
Payment	`payments`
Account	`ledger-accounts`
Product	`invoice-items`
Company Info	`company-info`
VAT	`tax-rates`
Purchase Order	`purchase-orders`
Journal	`journal-entries`

Coverage highlights

✅ Full CRUD on invoices, bills, payments, customers, suppliers
✅ Purchase orders
✅ Journal entries
✅ Finnish VAT handling
⚠️ E-invoicing (Finland uses Finvoice 3.0) — handled under the hood; specific formatting via Proxy
❌ Payroll — separate Procountor module
❌ Banking / reconciliation rules — use Proxy

Auth notes

Type: OAuth 2.0, managed by Apideck Vault
Company binding: one Procountor company per connection.
Finnish market focus: Procountor is Finland-specific. Regulatory compliance (Finnish Accounting Act, OmaVero) is built-in.
API version: Procountor v2 API; Apideck tracks current stable.

Example: list bills updated this week

const { data } = await apideck.accounting.bills.list({
  serviceId: "procountor-fi",
  filter: { updated_since: "2026-04-14T00:00:00Z" },
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Procountor directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Procountor's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: procountor-fi" \
  -H "x-apideck-downstream-url: <target endpoint on Procountor>" \
  -H "x-apideck-downstream-method: GET"

See Procountor's API docs for available endpoints.

Sibling connectors

Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):

access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.