Give LAC complete read-only access to your existing accounting and bank data in one pass.
Choose your system below. Give Last Accounting Company every available
read or view permission, then paste the credentials in LAC.
Read-only means no create, edit, approve, pay, delete, or invalidate access.
LAC stores credentials securely and never shows them again.
Fennoa
Procountor
Netvisor
Wise
The Fennoa key has no separate scope screen. Access belongs to the API
user that owns the key.
1
Create one API user for LAC
A Fennoa administrator or the current accounting firm opens
Users → Create new API user. Choose Yleinen API-käyttäjä
(General API user) and name it Last Accounting Company.Open Fennoa’s API-user guide
2
Give it every read right
If Fennoa shows a bulk read/view choice, use it. Otherwise, enable
every permission labelled read or view. Leave every create, change,
approve, payment, and delete permission off.Fennoa does not publish one universal read-only preset. Check the
wording before you save.
3
Paste the credentials in LAC
Copy and paste the API username and API key.
Read coverage: 28 available, 23 used today
Area
Available reads
Used today
Grant
Accounting
8
7
All read/view rights
Sales invoices
6
5
All read/view rights
Purchase invoices
8
8
All read/view rights
Customers
3
1
All read/view rights
Dimensions
3
2
All read/view rights
Total
28
23
All read/view rights
Used today
Accounting: GET /accounting_api/get/ledger/{start}/{end},
/accounting_api/get/accounts, /accounting_api/get/vatcodes,
/accounting_api/get/periods,
/accounting_api/get/opening_balances/{period_id},
/accounting_api/get/locking_periods, /accounting_api/get/budgets
Sales: GET /sales_api/, /sales_api/{id},
/sales_api/get/payments/{start}/{end}, /sales_api/get/pdf/{id},
/sales_api/get/delivery_errors
Purchases: GET /purchases_api/get/list, /purchases_api/{id},
/purchases_api/get/approval_queue, /purchases_api/get/finvoice/{id},
/purchases_api/get/attachment/{id}/{attachment_id},
/purchases_api/get/tags/{id}, /purchases_api/get/unbooked,
/purchases_api/get/suppliers
Customers: GET /customer_api/
Dimensions: GET /dimension_api/, /dimension_api/get/types
A Procountor API key has no permission picker. It inherits the rights of
the user for whom it was created. Use a dedicated user so access stays
read-only and easy to revoke.
1
Create a dedicated user
A company administrator opens Management → Users and user rights
and creates a user named Last Accounting Company.Open Procountor’s user-rights guide
2
Set all safe viewing rights
Use Management / Auditor as the starting role. Set every available
permission to Viewing rights. Set Only allow API M2M login to
Yes. Remove personal-invoice and dimension-only limitations.Leave any right that only offers write-capable All rights at
No access. In particular, do not grant payment, salary payment,
approval, import, or editing authority.
3
Create and paste the API key
Sign in as a company administrator. Open Basics → API client keys →
New API key. Select the dedicated LAC user and paste the LAC client
ID shown on the connection screen. Create the key and paste it in
LAC.Open Procountor’s API-key guide
Read coverage: 104 available operations, 16 used today
Procountor’s public API currently contains 101 GET operations and
three read-only report operations that use POST. Product, role, country,
and two-factor rules can limit some operations for an M2M user.
API area
Available
Used today
Attachments
2
1
Bank accounts
2
0
Bank statements
1
1
Business partners
9
2
Chart of accounts
1
1
Company
9
1
Currencies
4
0
Dimensions
2
1
Employees
11
0
Factoring contracts
2
0
Fiscal years
1
1
Health status
1
0
Integrations
2
0
Invoices
12
3
Journal
1
0
Ledger receipts
2
2
Multi-factor authentication
1
0
Payments
6
0
Payrolls
10
0
Persons
5
0
Products
6
0
Reference payments
1
1
Reports
3
1
SIE file
2
0
Session information
1
0
Users
3
0
VAT
3
1
Webhooks
1
0
Total
104
16
Used todayGET /company, GET /fiscalyears, GET /coa, GET /dimensions,
GET /vats/default, GET /businesspartners,
GET /businesspartners/{id}, GET /ledgerreceipts,
GET /ledgerreceipts/{receiptId}, GET /invoices,
GET /invoices/{invoiceId}, POST /reports/ledgeraccounts,
GET /bankstatements, GET /referencepayments,
GET /attachments/{attachmentId}, GET /invoices/{invoiceId}/image.All available read operations
Attachments: GET /attachments, GET /attachments/{attachmentId}
Bank accounts: GET /bankaccounts, GET /bankaccounts/{id}
Bank statements: GET /bankstatements
Business partners: GET /businesspartners, /businesspartners/groups,
/businesspartners/groups/{id}, /businesspartners/personaldetails,
/businesspartners/{id}, /businesspartners/{id}/defaults/accounts,
/businesspartners/{id}/defaults/dimensions,
/businesspartners/{id}/defaults/dimensions/{dimensionId},
/businesspartners/{id}/defaults/products
Netvisor grants access to a custom integration, not to a generic key
scope. The connection screen shows the LAC integration key that identifies
the correct resource list.
1
Create the LAC integration
Open Company menu → Software API identifiers. Create a dedicated
identifier named Last Accounting Company. Then open Company menu
→ API resource permissions → Custom integrations and add LAC with the
LAC integration key shown on the connection screen.Open Netvisor’s resource-permissions guide
2
Enable the complete LAC read bundle
First scan the resource actions shown inside the LAC integration.
If every action is read or export, turn on Integration allowed.
This is Netvisor’s clean bulk option.
If you see any import, add, create, edit, update, approve, pay,
delete, or invalidate action, leave Integration allowed off.
Enable only the 22 read/export resources listed below.
If the LAC panel is missing one of the 22 resources, stop and message
us. LAC must correct the registered integration bundle with Netvisor;
you should not need to troubleshoot our setup.
3
Finish in LAC
Paste the API identifier and API key. LAC already knows your
company Business ID.
Read coverage: 22 requested resources, 10 used today
The extra reads are limited to accounting completeness: source deletion
detection, bank-account identity, invoice payment links, purchase
evidence, voucher/dimension interpretation, and Netvisor’s obligation
and ledger-reconciliation status. “Deleted…” resources only read deletion
history; they do not delete data. Several of Netvisor’s deletion reads
expose only a seven-day history, so LAC must poll them without gaps.Payroll, user administration, customer/vendor masters, orders, products,
warehouse data, imports, approvals, payment initiation, and every source
mutation are excluded. If one of the 22 resources is missing from the LAC
panel, message us: only Netvisor partner support can add it to the
registered integration bundle.Sources: Netvisor’s accounting,
sales,
and purchase
resource guides; its deleted-voucher guide
documents the seven-day deletion-history constraint.
Wise puts the access choice directly on the token. You do not need to
choose individual API routes.
1
Open API tokens in a browser
Sign in to the correct Wise Business profile on the web. Open Your
account → Connect and manage apps → API tokens. Wise does not offer
token creation in the mobile app.Open Wise’s API-token guide
2
Create the safe bulk token
Choose Add new token, name it Last Accounting Company, and set
the access level to Read only. Complete two-step verification.
3
Paste it in LAC
Wise shows the token only once. Copy it and paste the API token in
LAC before you close the dialog.
Read coverage: one read-only token, 4 routes used today
Wise does not ask you to grant routes one by one. The Read only access
level is the full safe choice. LAC currently uses:
GET /v2/profiles
GET /v4/profiles/{profile_id}/balances
GET /v1/profiles/{profile_id}/balance-statements/{balance_id}/statement.json
GET /v1/transfers
Wise can limit statement access by account country and token product.
LAC shows any missing statement months after the first sync.