Findings and Their Solutions

A finding is a statement about what is not correct on the document. Findings are not counted by the client, but by the server, so they will occur both for documents submitted via forms and those received through the API, and API clients will receive them with the data.

Types of Findings

Each check can be disabled in the settings. If disabled, it will not be counted at all, so the document will not end up in the queue for verification.

What Happens with a Finding

A finding will never self-correct. Where it can be calculated, a button Fix to with a value will be offered, but you must fill it in. For IČO, a suggestion is not offered if it can only be identified by the control digit: this would pass through roughly every eleventh random number, so an automatic correction could produce a valid but incorrect IČO. Such an error is worse than a visible nonsense because no one would recognize it.

The exception is a company for which the document also carries the VAT ID. The company's tax number is CZ and its IČO, so the correct value is next to it on the document, and nothing needs to be calculated — a suggestion will be offered there. This does not apply to sole proprietors, who have their personal identification number as their VAT ID, and therefore, the IČO is not compared with the VAT ID at all.

A suggestion is also missing where the document would contradict itself after filling it in. In the case of the total of items on a document where the tax base plus tax equals the total amount, filling in the total would disrupt that relationship — thus, the finding remains, but the value is not offered.

Repeated Items

A multi-page document sometimes lists the same items twice under different headings: a cloud invoice details services and then lists them again by accounts, while a telecom operator's invoice breaks down services and then by phone numbers. The model receives both tables and reads both, so each item ends up in the data twice, resulting in a double total which would be recorded twice in accounting.

A finding will only occur if each item repeats the same number of times and there are at least three different items. An extra or missing item means no finding will occur — two identical pairs on one document are common, and deleting half of the details because of them would be worse than remaining silent.

For a finding, there is a button that keeps the first occurrence from each set and deletes the rest. The entire breakdown is changed at once because deleting one at a time would shift the line numbers under your hands. This will not affect the summaries: the tax base, tax, and total amount remain unchanged as they apply to the document.

Be careful with documents where items are in a different currency than the summary. Cloud invoices charge in dollars and only convert the summary into euros or crowns. Cleaning up repeated items will not fully fix such a document: the sum of items will not match the summary because it’s in a different currency. It is cleaner in accounting to leave one item for the entire invoice in such a document.

Items in a Different Currency than Summary

Foreign invoices from the cloud charge in dollars and convert only the summary into the payment currency: the itemized breakdown remains in USD, while the tax base and amount are in euros or crowns. The document has only one currency in the app, so the item total will not match the tax base, regardless of any repairs.

This can be seen from the transcript of the document, where the currency stands next to each amount. For a document that does not have a transcript — electronic invoices or turned-off OCR — the check will not run, and a regular finding about the total will apply.

For a finding to occur, foreign currency must be indicated for at least three different item prices, and the document's currency must not be represented at all. A document that prints both currencies on each line is merely a conversion and will not produce a finding.

The app does not offer a correction because the correct answer does not arise from the document. You have two options:

1. Leave the document currency and simplify the items to one, maybe Services 8/2026 for the amount from the tax base. The amount that is actually paid will go to accounting, and the breakdown by services will remain in its original form stored with the document. This is the cleanest option for accounting.
2. Rewrite the document to the currency of the items, including the summaries. The document will then match internally, but the amount to be paid and tax will be in a different currency than that which is being paid — that from the document should be included in the VAT return.

A finding can also be left alone and the document confirmed. Then, items will be sent to accounting in one currency, and summaries in another, so the program will calculate different numbers than those stated on the document.

The check for the sum of items does not run for such documents. It cannot match, and a second notice about the same thing would not provide any new information.

How to Resolve a Finding

Two paths:

1. Correct the value. The finding will disappear once the recalculation completes.
2. Leave it be. If the value is correct and the finding is a false alarm — e.g., a foreign supplier with a different VAT rate. Upon confirmation, a window will appear with a list of findings that remain in the document, and you can confirm them all at once. If you do not want the window, check Do not show again; it can be turned back on in the settings.

The activity will log who confirmed the document and whether they touched the data.

Supplier Account

The most common scam with invoices looks like this: an invoice arrives from a supplier you know, complete as usual, only that the account number is foreign. The control sum does not recognize anything because the fraudulent account is usually valid.

The application therefore remembers which accounts you have paid to for each supplier, and when a different one appears on the document, it is reported as a finding. This is not a blockage: accounts really change, and the document must be accounted for as it is. You just need to approve the finding upon confirmation like any other, and from that moment on, the new account is also known.

What is worth knowing:

• The account is remembered only after confirming the finding. Not just after recognition. If recognition were sufficient, the fraudulent invoice would register its account itself, before anyone opened it.
• The first supplier document reports nothing. There is nothing to compare with, it just sets the base. Banks operate the same way.
• Domestic entry and IBAN of the same account are one account. One invoice writes 19-2000145399/0800, the other CZ6508000000192000145399. No finding arises from this.
• Applies only to received documents. Your own account is on the issued invoice.
• The finding does not offer a correction. Replacing the remembered account instead of what is on paper would be a button “pay elsewhere than the invoice says”. The decision must be yours — and verify the new account elsewhere than on that invoice.
• Known accounts are visible to the counterparty. You can find them in the supplier detail under the tab Counterparties, along with who confirmed it last. The supplier's memory can also be forgotten there.

VAT ID and Payer Registry

The VAT ID of both supplier and buyer is verified in the European VIES registry. When the registry is temporarily unresponsive, no finding will occur — there’s no point in calling the supplier due to an outage in Brussels. Only European VAT numbers with the state prefix are verified.

Your own VAT ID is not verified, as you know your payer status. The VAT ID of the Czech supplier on the document without VAT is also not verified: a non-payer may have a VAT ID, just not be in the payer registry.

The VIES registry returns only yes/no, we do not compare the company name against it. The ARES registry is used elsewhere — when filling in your own company in settings.