Find missing attachments in the accounting system

The firm signs in to Fiken and approves BilagPilot. Access is refreshed automatically.

Every Fiken company the signed-in user has access to is imported through a single connection.

The Fiken sync covers posted purchases, sales and journal entries.

Unused documents in Fiken Inbox are imported and can be followed up in BilagPilot.

The Fiken sync paginates as far as the time budget allows, newest first, and flags in the dashboard when a run was truncated.

Purchases, sales and journal entries get the file attached to the entry itself.

Fiken Inbox is used when direct linking is not possible.

“Send to Fiken Inbox” from uploads.

Accounts and official VAT codes are fetched and cached for 24 hours.

The Fiken API has no general unposted voucher draft. The posting is stored in BilagPilot without being booked.

Fiken's price for API access, excl. VAT. Paid to Fiken.

An owner or admin pastes in a Tripletex API user key. The key is validated against Tripletex and stored encrypted.

Every company where the firm's Tripletex user has login access is imported through a single connection.

Unposted vouchers are scanned alongside posted ones, so the request can go out to the customer before posting.

Documents in the Tripletex document inbox are imported and can be followed up in BilagPilot.

The firm sets rules per account number: hide the item, create a request automatically, or send it to manual review. The firm-wide default can be overridden per customer.

Complete pagination within the window, split into 31-day chunks.

Vouchers with a numeric voucher ID get the file attached directly to the voucher.

The Tripletex document inbox is used when the voucher has no numeric voucher ID.

“Send to Tripletex document inbox” from uploads.

The full chart of accounts is synced, and date-dependent VAT codes are checked against the VAT types allowed on the selected account.

A balanced, unposted voucher with the attachment is created after an explicit user action. The Tripletex token needs permission to create advanced vouchers.

The Tripletex Integrations module, excl. VAT. Paid to Tripletex.

An owner or admin pastes in an API key from Conta. The key is stored encrypted, and the firm only ever sees the last characters.

Every Conta business the API key grants access to is imported through a single connection.

The Conta sync covers posted transactions.

The Conta API does not expose the voucher inbox for reading.

Bounded to 3 pages x 100 transactions per business per run.

The Conta API has no documented endpoint for attaching a file to an existing transaction. The file goes to the voucher inbox instead.

Every file is sent to the Conta voucher inbox.

“Send to Conta voucher inbox” from uploads.

The chart of accounts is synced per business and cached for 24 hours. Locked and inactive accounts are filtered out.

The Conta API finalises the posting directly. BilagPilot therefore stores the suggestion internally instead of sending it.

Requires an active Conta subscription with API access. No separate integration fee.

BilagPilot's application key is added in PowerOffice, and the client key is pasted back into BilagPilot. With partner access the client list is fetched automatically.

With partner access the full client list is fetched. Without partner status, clients are added one by one with their own client key.

The PowerOffice sync covers voucher documentation and journal entry vouchers.

The PowerOffice API does not expose the voucher inbox for reading.

3 pages x 100 rows per source per run, highest voucher number first.

The file is added to the voucher documentation, or as a voucher page on the journal entry voucher.

Sending to PowerOffice requires a specific voucher. Loose files have to go to the client's voucher inbox by e-mail.

“Send to PowerOffice voucher inbox” sends the file as a PDF by e-mail to the client's voucher inbox address.

PDF for voucher documentation, JPG for voucher pages on journal entry vouchers.

Accounts and VAT codes are fetched and cached for 24 hours, including department and project requirements.

An unposted ManualJournal is created, and the file is added as a voucher page.

Partner or production access is agreed with PowerOffice.

BilagPilot's Application ID is approved in Finago under Administration and integrations. The Organization ID is then pasted into BilagPilot.

Every client in the Organization ID the firm connected is imported through a single connection.

The Finago sync covers posted transaction lines.

The Finago API does not expose the document inbox for reading.

3 pages x 100 transaction lines per client per run.

The Finago API creates a document ID, but has no documented endpoint for linking that document to a posted transaction.

The file is uploaded and gets a Finago document ID. The link to the voucher has to be checked manually in Finago.

Loose files with no link to a missing item cannot yet be sent to Finago.

Accounts and VAT codes are fetched per organization and cached for 24 hours.

The Finago API posts general transactions directly. The suggestion is stored in BilagPilot.

Requires a partner or API agreement with Finago.

The firm signs in to Visma and approves BilagPilot for the selected eAccounting company.

Visma eAccounting grants access to one company per sign-in. Several companies require one connection each.

Supplier invoice drafts are scanned alongside posted supplier invoices, customer invoices and vouchers.

Attachments in the Visma inbox that are not matched to a voucher are imported and can be followed up in BilagPilot.

2 pages x 100 rows for each of supplier invoices, invoice drafts, customer invoices, vouchers and loose attachments.

Customer invoices get the attachment directly. Supplier invoices, invoice drafts and vouchers go to the attachment inbox.

The Visma attachment inbox is used for everything except customer invoices.

Loose files with no link to a missing item cannot yet be sent to Visma.

Accounts and VAT codes are fetched for the fiscal year covering the voucher date, and cached for 24 hours.

An unposted voucher draft is created in the open fiscal year covering the voucher date, with the attachment linked.

Requires partner registration with Visma. Not publicly priced.