Integrations
Through the interface (API), other programs talk to fineelik directly. You only need this if you want to connect your own software. This page explains the setup, the technical details are in the API reference.
Everything is under Settings, Integrations and is part of the base package.
Two ways for data
Section titled “Two ways for data”- Fetch (pull): Your system asks fineelik regularly for new events and invoice data. For this you need an API key.
- Webhooks: fineelik reports events by itself to an HTTPS address. The recipient then retrieves the invoice data through the API.
API keys
Section titled “API keys”An API key is the access for a machine. Administrators create it.
- Create the key. Give it a name (up to 32 characters) and choose the term: 90, 180 or 365 days.
- Assign it to your company. A key always works in exactly one company. Without an assignment, the default company applies. For several companies, create one key each.
- Copy it immediately. It appears only once.
- Store it in the other system.
A key may only deliver documents, read invoices and report an external approval back. Reporting back an approval only works if the owner is an administrator. The key belongs to the person who creates it. If their account is deactivated, it no longer works. It can be withdrawn at any time. What it may do is described under Authentication.
With the Contracts module a key also hands over contracts from ELO and reads their state (rights agreements.integration_write and agreements.integration_read). Only the Administrator has these rights, so the key must belong to an administrator.
Creating a webhook
Section titled “Creating a webhook”- Click Create webhook.
- Enter the Address, it must begin with
https://. - Choose the Events and the Company.
- Copy the Secret. It is visible only once. The recipient uses it to verify the signature.
- In the drawer, click Send test.
| Event | When fineelik reports it |
|---|---|
| Document received | A document has arrived, by upload, email or from the leading system |
| Status changed | Every status change, for example approved or rejected |
| Data changed after review | Coding or amounts were corrected without the status changing |
| Processing failed | Processing failed after all attempts |
| Contract: conditions approved | The matching conditions of a contract managed in ELO were approved in fineelik. |
| Contract: conditions changed | The matching conditions of a contract managed in ELO changed or wait for approval. |
| Contract: partner assigned | The partner of a contract managed in ELO was assigned to a vendor. |
| Contract: keywords changed | The keywords of a contract managed in ELO changed. |
| Contract: automatic approval changed | The switch “approve automatically” of a contract managed in ELO was changed. |
Contracts in the invoice data
Section titled “Contracts in the invoice data”With the Contracts module, the invoice data and every event also carry a contract block: which contract the invoice belongs to, the result of the check (expected amount, actual amount, deviation and allowed deviation) and whether fineelik would approve the invoice automatically, with the reasons against it. A leading system such as ELO can then skip its approval when everything fits. For confidential contracts, machines only see the result and whether an automatic approval would be possible, no number and no amounts. The individual fields are in the API reference.
Contracts from ELO
Section titled “Contracts from ELO”With the Contracts module the ELO component hands over contracts from ELO Contract to fineelik and gets back what fineelik maintains for them:
- Handover: the component sends the contract with its ID in ELO on every creation and change. The same state again changes nothing, an older state is not taken over.
- Document: the contract document comes separately. fineelik stores the same document only once.
- Way back: the events Contract: … above report approval, changed conditions, partner mapping, tags and the automatic approval, each with the full state of the contract.
- In the invoice data the contract block carries the ID of the contract in ELO for contracts from ELO. If only the contract block of an invoice that was already reviewed changes, fineelik reports Data changed after review.
- If approval runs outside fineelik, the report from ELO counts for the sample of the automatic approval exactly once per invoice.
The details for developers are under Contracts from ELO.
If a delivery fails
Section titled “If a delivery fails”The list shows the state per webhook: Running, Paused, Failing since … or No access.
- fineelik keeps retrying at increasing intervals: after 1, 5, 15 and 60 minutes, then every 6 hours. Events are kept.
- The recipient must answer within 10 seconds with a 2xx status.
- Pause stops the delivery, after Resume fineelik delivers what is pending. A new address also triggers a new attempt immediately.
- After Renew secret, deliveries fail until the recipient knows the new secret.
- No access means: The person who created the webhook no longer has access to the companies of the webhook, may no longer view invoices or their account is deactivated. Restore their access, and fineelik delivers what is pending. Or create the webhook again.
- Only the administration may create and change webhooks. Whoever may read the settings sees them.
- The Delivery log shows every delivery, entries older than 30 days are deleted.
AI assistants
Section titled “AI assistants”The card AI assistants (Claude, ChatGPT) on the same page switches access for Claude and ChatGPT and sets which roles may connect them. More under AI assistants.
Opening invoices in ELO
Section titled “Opening invoices in ELO”The Document management card on the same page connects fineelik with ELO, see fineelik with ELO.