Procountor

Procountor is the Finnish cloud accounting platform. Agents create sales and purchase invoices and drive their approval chain, manage business partners and products, record payments and ledger receipts, and pull dimensions and accounting reports.

1 trigger 41 actions OAuth available

Procountor website Platform Documentation Capability data verified 2026-08-24

A supplier invoice arrives in the accounts payable mailbox

Agent reads the supplier, the totals, the dates, and the rows the invoice charges for

Search Business Partners resolves the supplier, and Get Business Partner Defaults reads the accounts and dimensions it normally posts to

Create Invoice records it, which Procountor holds in its UNFINISHED state

Add Attachment files the original document against the invoice so the approver sees what was received

Change Invoice Status routes it to circulation and Add Invoice Comment supplies the context, tagging the person who has to look

A named approver verifies and approves the invoice, and the agent resumes on the payment event

What This Integration Enables

Procountor treats an invoice as a state machine rather than a record with a status field. A new invoice starts UNFINISHED whatever you send, and it moves forward only through named transitions: verify, approve, send, send to circulation, reject, mark unfinished, invalidate. That design is Procountor stating who is accountable at each step, and it makes the platform an unusually good fit for automation that respects an approval chain instead of routing around it.

FlowRunner agents assemble invoices from whatever the document actually was, resolve business partners and their posting defaults, attach the original file, and put the result into circulation with the context an approver needs. They record ledger receipts for anything with no invoice behind it, read the journal and the accounting reports, and follow payments through to settlement. The human-in-the-loop discipline is not bolted on here, because Procountor already has one. The connector's job is to do all the work either side of it and to leave the transitions that name a responsible person where they belong.

Without FlowRunner

Coding done twice The same supplier gets coded from scratch every month because the defaults live in someone's head

Approvals chased by email The chain exists inside Procountor but the reminders happen outside it, so they are inconsistent

Invoice state read by opening it Whether something is unfinished, approved, or sent means someone logging in to check

With FlowRunner

Defaults read before coding The agent asks Procountor what this partner normally posts to before it proposes anything

Circulation started automatically The invoice reaches the right approvers with its attachment and its context already on it

State drives the workflow Status, payment events, and ledger transactions are read directly, so downstream steps fire on fact rather than assumption

Use Case Scenarios

Supplier invoices coded, attached, and circulated

An invoice PDF lands in a shared mailbox monitored through Gmail. The agent extracts the header and the rows, resolves the supplier with Search Business Partners, and calls Get Business Partner Defaults to read the products, ledger accounts, and dimensions that supplier normally posts to. Create Invoice records the document, Add Attachment files the original against it, and Change Invoice Status sends it to circulation. Add Invoice Comment tags the reviewer with what the agent found and what it was unsure about. Nothing is approved, and nothing is paid.
An approval inbox that chases itself

List My Pending Invoices returns exactly what the connected user personally has to verify or approve. On a schedule, the agent reads that list, groups it by age and value, and posts a digest into Slack or Microsoft Teams naming the invoices that have been waiting longest. Approvers act inside Procountor, where the audit trail already lives. The agent supplies the nudge and the context, not the decision, and it stops reminding as soon as List My Pending Invoices stops returning the item.
Settlement reconciled without a spreadsheet pass

The trigger's catalog covers payments rather than invoices, so the agent listens for payment events and polls Search Invoices on its version date filters for everything else. When a payment event arrives, it reads List Invoice Payment Events and List Invoice Transactions to see how the invoice actually landed in the ledger, then updates the tracker in Google Sheets the finance team works from. Anything settled outside the bank is recorded with Mark Invoice Paid only after a person confirms the money arrived somewhere the flow can see.

Human-in-Loop Highlight

Procountor already gates the payment. Pay Invoices does not move money: it validates the request, answers a transaction identifier, and waits for a person to confirm it in the Procountor Key application before the payment exists at all. That tells you where the vendor thinks the risk is, and it also tells you where the risk is not. By the time an invoice reaches a payment run, the decision that mattered was already taken further upstream, at Change Invoice Status. Approve commits an invoice. Send actually delivers a sales invoice to the customer. Invalidate voids one. A Procountor connection is bound to one company and one user, so an agent calling Approve is signing off as that named person, which is precisely what the circulation chain exists to prevent. So the agent goes as far as assembling, attaching, and routing. It calls Send To Circulation and stops, posting the supplier, the amount, the coding it proposed, the defaults it took that coding from, and the specific field it was unsure about. A person approves in Procountor, under their own name, and the flow picks up again on the resulting event. Mark Invoice Paid sits behind the same gate for a related reason: it records a settlement without any money moving, which makes the ledger say paid while nothing has left the account.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

41 actions

Account and Company

Get Session Info Reads the session the access token belongs to, including which company and user it is bound to. The first call a flow makes to confirm it is pointed at the right place.
Get Company Reads the details of the company this connection is bound to.
Get Chart Of Accounts Reads the Finnish chart of accounts, which is where every ledger account code an agent uses comes from.
Get VAT Settings Reads the VAT settings, including which percentages and statuses are in use.
List Dimensions Lists the company's dimensions with their items, which are the reporting axes an invoice or receipt row can be attributed to.

Invoices

Search Invoices Searches invoices by type, status, and date range. The version date filters are what make an incremental poll work, since the webhook catalog has no invoice event.
Get Invoice Reads one invoice including its rows and payment information. The gathering step before any decision goes to a person.
Create Invoice Creates an invoice, which starts UNFINISHED. What is required depends on the type and the sending channel, and Change Invoice Status is what moves it forward.
Update Invoice Updates an invoice. Only one still in an editable state can be changed, so a sent or approved invoice is refused rather than silently altered.
Change Invoice Status Moves an invoice through its approval chain: verify, approve, send, send to circulation, reject, mark unfinished, or invalidate. Send delivers the invoice and Invalidate voids it, which is why this operation carries this page's human gate.
Mark Invoice Paid Records an invoice as paid without going through the bank, which is what an invoice settled elsewhere needs. Held behind the same gate, because it makes the ledger say settled with no money moving.
List Invoice Payment Events Lists the payment events recorded against an invoice.
List Invoice Transactions Lists the accounting transactions an invoice produced, which is how a flow confirms it actually landed in the ledger.
Download Invoice Image Downloads a page of an invoice as an image into FlowRunner file storage, for review threads and archives.
Add Invoice Comment Adds a comment to an invoice, which is how the approval chain communicates. A user can be tagged into it, so the agent can hand a specific question to a specific person.
List My Pending Invoices Lists the invoices waiting for the connected user to verify or approve. The approval inbox a reminder flow is built on.

Business Partners

Search Business Partners Searches the register that holds customers, suppliers, and people in one list, distinguished by type.
Get Business Partner Reads one business partner by its identifier.
Create Business Partner Creates a business partner, which is a customer, a supplier, or a person depending on the type.
Update Business Partner Updates a business partner through the partial update route, so a field left empty keeps its current value.
Get Business Partner Defaults Reads the defaults a partner supplies to a new invoice: its default products, ledger accounts, or dimensions. The read that lets an agent code an invoice the way this company already codes it.

Products

List Products Lists the company's products. A product belongs to one invoice kind, so a sales product cannot be used on a purchase invoice.
Get Product Reads one product by its identifier.
Create Product Creates a product. Its type, price, discount, currency, and active flag are all required, and the discount is required even at zero.
Update Product Updates a product. Procountor replaces the record on this route, so the fields being kept have to be sent as well.
Delete Product Deletes a product. Marking it inactive is the alternative once it has been used on invoices.

Payments

List Payments Lists the company's payment transactions.
Pay Invoices Requests payment of invoices. Procountor answers a transaction identifier and waits for a person to confirm it in Procountor Key, so the payment does not exist until that happens.
Confirm Transaction Reports the outcome of a two-factor transaction once the user has confirmed it. The polling alternative to the webhook.
Cancel Payment Cancels a payment that has not yet left the bank.
List Bank Accounts Lists the company's bank accounts, which is what a payment is made from.

Bookkeeping and Reporting

Search Ledger Receipts Searches the ledger receipts, which are the manual bookkeeping entries for anything with no invoice behind it.
Create Ledger Receipt Posts a manual bookkeeping entry as a ledger receipt. The debits and credits are added up first, and an unbalanced receipt is refused before it is sent.
Change Ledger Receipt Status Approves, invalidates, or reopens a ledger receipt. Approving commits it to the ledger, and invalidating writes a counter-entry rather than deleting anything.
Search Journals Reads the journal, which is the posted accounting entries behind every invoice, payment, and receipt.
Get Report Runs an accounting report: ledger account balances, the general ledger for one account, or the standard accounting reports, each over a period.

Attachments

Add Attachment Uploads a file into the attachment store by fetching it from a URL, so it can be attached to an invoice or a receipt.
Download Attachment Downloads an attachment into FlowRunner file storage.

Webhooks

List Webhooks Lists the webhooks registered on the company, including any the trigger installed.
Create Webhook Registers a webhook. The shared secret you supply is what signs the deliveries, since Procountor does not generate one.
Delete Webhook Removes a webhook from the company by its UUID.

Triggers

1 triggers

Event Triggers

On Procountor Event Fires when Procountor reports the chosen event. The catalog covers payments, salary payments, tracking periods, and users. There is no invoice event, so a flow that needs to know about new invoices polls Search Invoices on its version date filters instead of waiting for a delivery that will not come.

Frequently Asked Questions

What can FlowRunner do with Procountor?

FlowRunner agents can run Get Session Info, Get Company, and Get Chart Of Accounts in Procountor, plus 38 more actions.

Does connecting Procountor to FlowRunner require OAuth?

Yes. Procountor connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Procountor trigger a FlowRunner workflow automatically?

Yes. Procountor supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Procountor

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us