fineelik with ELO
If you work with ELO, ELO stays your archive and runs the workflow. fineelik takes over reading, reviewing and coding. The connection is part of the base package.
How an invoice runs
Section titled “How an invoice runs”- The invoice arrives in ELO, also by email. One file is one invoice.
- The fineelik component in ELO hands it over to fineelik. In the invoice list the source is “Archive”.
- fineelik reads and codes it.
- If the invoice needs a review, ELO sees that, and your accounting team reviews in fineelik as usual.
- After that, coding and status go back to ELO, and the workflow continues.
- If fineelik rejects an invoice, ELO learns that with the reason and forwards it to clarification (clearing). This applies to documents that are not invoices, duplicates, cancelled and rejected documents. It also applies if processing fails for good or the document is already in another company in fineelik.
If fineelik has coded an invoice completely and the Automation setting allows it to go on without review, step 4 is skipped. With the setting “Never” and for invoices with a notice, every invoice goes to review, see Accounts and coding.
Emails with several attachments
Section titled “Emails with several attachments”If an email has several files attached, for example an invoice and a payment receipt, it is not clear which one is the invoice. The email then becomes a task “Rechnungsanhang auswählen” for your clearing team.
- Select the invoice PDF and click Mark as invoice. ELO hands it over to fineelik, opens the invoice and reports “Invoice handed over to fineelik”. The task closes by itself.
- If none of the files is an invoice, click Not an invoice on the receipt case. ELO reports “Not an invoice: selection closed”.
Both buttons are only available on receipt cases from the email intake and on their attachments. A second click changes nothing: ELO opens the invoice that was already handed over and tells you so.
Documents that arrive in fineelik
Section titled “Documents that arrive in fineelik”Documents can also arrive in fineelik directly: with the fineelik app, with Upload, at the mailbox address or through the API. So that they are in ELO too and run through the workflow there, switch on Hand documents over to ELO on the company in the Documents and retention section. The switch appears once ELO is set up as document management (see Setting up), and it needs the fineelik component in ELO version 1.8.0 or later.
- Every five minutes ELO fetches one document and stores it as an incoming invoice in the Invoice workspace, like the email intake. After that it runs like an invoice from ELO (steps above).
- Only documents from the moment you switch it on count. Older documents, documents from ELO and sample invoices stay where they are.
- Until the document is in ELO, the invoice in fineelik shows Being handed over to ELO. Then Open in ELO WebClient appears, and the history shows Stored in ELO.
- If storing fails, the invoice shows the reason and when ELO tries again. fineelik never gives up on the document, the following documents keep running, and no document is created twice.
Without the switch such documents stay in fineelik only: they do not reach ELO and run through no workflow there.
Where the approval runs
Section titled “Where the approval runs”You have two options:
- In the ELO workflow: If you do not have the Approval module, approval always runs in the ELO workflow and you do not have to set anything. If you have the module, set “Invoice approval” on the company to “External system”. fineelik then creates no task, and ELO reports the decision back.
- In fineelik: with the Approval module, see Approving invoices.
If an invoice was approved in the ELO workflow, it can no longer be reopened in fineelik. You then make corrections in ELO. If it is rejected in ELO, it appears in fineelik as rejected and can be reopened after the clarification. With the Payments module, fineelik also reports “paid” back to ELO.
Contracts from ELO Contract
Section titled “Contracts from ELO Contract”With the Contracts module, the fineelik component in ELO (version 1.7.0 or later) hands the contracts from ELO Contract over to fineelik. What fineelik does with them and what you maintain there is described under Contracts. Setting this up is done together with eelik.
- When: If you save a contract in ELO, it goes to fineelik right away together with its contract document. In addition, ELO synchronises every 15 minutes: all contracts changed since the last run, and the state from fineelik. Unchanged contracts are not sent again.
- Which: all contract types of ELO Contract, eelik adds your own contract types when setting up. A contract without a status is not sent, the reason is then shown on the contract.
- On the contract in ELO: The fineelik tab is read only. It shows Status in fineelik (for example Approval of matching conditions needed or Ready for automatic approval), Open in fineelik, Message from fineelik, Matching conditions approved, Automatic approval possible with Reasons against automatic approval, Amount basis, the tolerances, Approve invoices automatically, Vendor in fineelik with Vendor number, Tags and Open points. If something changes in fineelik, it is shown there after the next synchronisation at the latest.
- On the invoice in ELO: The fineelik tab has a block with Contract number, Contract check result, Expected per contract, Actual per invoice, Deviation in percent, Automatic approval possible and Reasons against automatic approval. With ELO Contract, the contract itself is added as a reference (Contract). Invoices without a contract stay unchanged.
If fineelik reports Automatic approval possible on an invoice, the ELO workflow can skip the approval: the invoice goes to the next step without the formal check and without approval. fineelik learns about the approval with the next synchronisation, the approver shown there is “fineelik Vertragsabgleich”. This only applies together with replacing the formal check, so only for fully coded invoices. It is switched on at the ELO object “fineelik sync” with two switches, both set to 1: FINEELIK_SKIP_FORMAL_CHECK (replace the formal check) and FINEELIK_AGREEMENT_AUTO_APPROVAL (contract automation). Without the second switch, every invoice goes to approval as before.
Without ELO Contract, no contracts come over from ELO, the component reports this and does nothing else. Contracts you manage in fineelik itself are still matched against invoices, and the block on the invoice is shown in ELO in that case as well. Without the Contracts module, everything in ELO stays as before.
Posting in Business Central
Section titled “Posting in Business Central”With ELO Invoice, ELO takes the reviewed invoice to Business Central. fineelik does not post invoices there itself, see Leading system.
Setting up
Section titled “Setting up”The component in ELO is set up by eelik or your ELO partner. In fineelik this includes:
- As an administrator, create an API key per company under Settings, Integrations, see Integrations. The key is valid for one year at most. After that ELO reports nothing back until you enter a new key in the ELO credentials.
- Set the approval on the company, as described above.
- Under Settings, Integrations, on the Document management card, choose the provider ELO. Enter the WebClient address, without the part from the # character, and the workspace GUID for each company. Only someone who may manage the settings and has access to all companies can do this. The review then shows Open in ELO WebClient.
- If your ELO can be reached from outside, fineelik can report events itself (webhook). Otherwise ELO fetches the state regularly.
Through ELO, at most six further dimensions on the line go to Business Central.