What do I do if it doesn’t recognise the supplier on an invoice?
Without a supplier, the purchase invoice can’t be created and what was learned from their invoices can’t be saved. It is the first problem to solve when an invoice gets stuck in the inbox with ‘Supplier not identified’.
How does the program decide who the invoice is from?
It tries three routes, in this order.
First it looks in the PDF text for a Tax ID (NIF, NIE or CIF) with a correct check letter that isn’t your own company’s. It copes with it being stuck to its label, as in CIF:A58818501, and with it having dots or hyphens, and it also reads it when it runs vertically in the margin, like the legal footer on O2 invoices. It keeps the first one it finds that isn’t the recipient’s: not yours, nor the one the invoice puts after ‘Cliente’, ‘Bill to’ or ‘Titular’, nor the one the AI reads as the recipient’s.
Even so, enter your company’s Tax ID correctly on its record: it is the surest sign of which one is yours.
A European Union VAT number written without the country prefix (‘VAT Number: 10427474B’ from a supplier in Cyprus) is completed with the supplier’s country: CY10427474B.
If no valid Tax ID appears —usual when the supplier puts their details inside the logo—, it tries each supplier’s fingerprints: what appears on all their invoices and on nobody else’s (see the next section).
Finally, if the AI did manage to read the issuer’s Tax ID, that one is used. It is what rescues almost all scans, where before the reading there was no text to look at.
The exception: if the AI puts your own company as the issuer, another Tax ID is only taken when the invoice has a single one different from yours. The issuer section, further down, explains this.
With the Tax ID in hand, it looks among your suppliers for one with that Tax ID, comparing it without spaces, dots or hyphens. Tax IDs saved with separators also match.
What are a supplier’s fingerprints?
Every time you import an invoice from a supplier, the program notes what their layout has that identifies them: their Tax ID, their bank account, their website or email, their phone, a word from their name and some fixed phrase from the header or footer. Never anything from your company or from the recipient, nor amounts, dates or invoice numbers.
They aren’t all worth the same. The Tax ID and the bank account identify almost on their own; a website or the name help; a phrase, a little. To give the invoice to a supplier, enough of them must come together, and no other supplier must come close: if two end up similar, neither is chosen and the invoice stays to review. Better to ask you than to apply another supplier’s rules.
Fingerprints are refined on their own. With the supplier’s second invoice it already knows what is fixed in their layout: what doesn’t repeat gradually fades out (in the review it appears crossed out and stops counting). And what several suppliers share —the text of the platform that produces their invoices, for example— doesn’t distinguish any of them and hardly counts.
You see them in the Recognise this supplier block of the review, each with its type. You can remove the ones you aren’t sure about and add texts by hand: the ones you type must all appear on their invoices for them to count.
What if other customers already know that supplier?
What is learned from a supplier’s invoices is shared among Powergest customers: how their layout is recognised and where it puts each field. That way, the first invoice from a supplier that others already import arrives already read: the program knows who it is from and where to look, even if you have never imported one of theirs. You will see it in the message ‘Supplier recognised by the shared format base’.
That first invoice always goes through review: what others know is a hint, not a guarantee. When you import it, the supplier becomes validated for you and the next ones are read with your own rules.
What is shared and what isn’t:
- Only from companies. Nothing from a sole trader (their DNI or NIE) ever leaves your program.
- From them, their Tax ID, their bank account, their website, their phone, a word from their name and where they put each field on the invoice. Never the amounts, the lines or anything the invoice says about you.
- Nothing from your company: not your name, nor your Tax ID, nor your accounts, nor what you type by hand.
- Who each thing comes from isn’t saved: only how many customers have contributed it is counted.
Both can be turned off, each one separately, in the import Settings, Formats shared with other customers block: Use what others already know and Share what was learned from my suppliers. By default they are on.
What happens if the Tax ID and the layout don’t match?
It is checked from both sides: the Tax ID that is read and the fingerprints of the layout. If the Tax ID belongs to one supplier and the layout looks like another’s, the invoice doesn’t come in on its own: it stays to review with the message ‘Check the supplier: the Tax ID is …, but the layout looks like the invoices of …’. This happens when the AI misreads the Tax ID or when the invoice mentions another company’s Tax ID.
If the AI reads a Tax ID that isn’t valid and the fingerprints recognise the supplier, the Tax ID from their invoices is used and you are told so. The same if the Tax ID read differs by only one character from that of a supplier you already have (typical of a scan: a 6 read as a 5): theirs is taken with the message ‘The Tax ID read (…) is not valid: … has been used’, and the invoice doesn’t come in on its own. If there are two suppliers equally close, neither is chosen.
A misread Tax ID never creates a supplier: if it isn’t valid, the invoice stays to review so that you mark it.
What about a scanned invoice?
A scan has no text in which to look for fingerprints, so the supplier details the AI has read are used: their name, their email, their website, their phone. When you import a scanned invoice, the supplier learns from them; and on the next one, even if the Tax ID is misread, it is recognised by the rest. What is learned also applies in the other companies in your account.
What if an invoice has a different bank account?
If a known supplier sends an invoice with a different bank account from the one on their record or the one on their previous invoices, the invoice stays to review with a prominent warning. Before paying, confirm the change by calling the supplier on a phone number you already had, not the one on that invoice or in the email it came with. It is the most common kind of fraud against businesses: an invoice that looks genuine, from a regular supplier, with the fraudster’s account.
What happens if the supplier doesn’t exist yet?
The program creates it on its own, if Create the supplier if it does not exist is ticked in the import Settings —it is by default— and if the Tax ID read is valid. The record is created with the Tax ID as its code, and with the name, address, town / city, province, postcode, phone and email the AI has read from the invoice.
For that, the invoice must have the issuer’s name. If it couldn’t be read, the supplier isn’t created and a message like ‘could not create the supplier (The invoice does not include the issuer’s name)’ appears.
A supplier created this way starts without rules and not validated: their invoices go through review until someone checks that they are read correctly. The code is the Tax ID because it is unique and recognisable; you can change it later from their record without breaking anything, because the link doesn’t go by code.
What do I do if it still doesn’t recognise it?
When you see ‘Supplier not identified: mark its Tax ID in the PDF’ in the header of the fields, the way forward is to mark the supplier’s Tax ID:
- In the Supplier block, click Mark on the PDF next to Tax ID (NIF) and drag over the supplier’s Tax ID on the invoice (you can also type it). As soon as you do, the invoice goes to that supplier: if you already have them, their name appears; if not, the header says ‘Supplier is new: it will be created on import’.
- Do the same with the Name, especially if it is a new supplier: it is the name it will be created with.
- Review the rest of the fields and click Import (or Save zones). At that moment the supplier is created if needed, and the zones you have marked are saved as rules for that supplier: their next invoice will already be read from those zones.
- When importing, the program learns the supplier’s fingerprints from that invoice. If you like, add some text by hand in Recognise this supplier that only appears on their invoices.
What if the issuer it has read is my own company?
It happens often: on a purchase invoice your Tax ID appears next to ‘CIF’ or ‘N.I.F.’ in the customer block, while the supplier’s is sometimes without a label or with the country prefix (ESB22258982), and the AI mixes them up. A supplier with your Tax ID is never looked up or created.
- If there is a single Tax ID on the invoice that isn’t yours, that is the supplier’s: the program puts it in its place, marked as a doubtful field, and the invoice stays to review with the message ‘The AI took your Tax ID as the supplier’s. The other Tax ID on the invoice has been used…’. Check it on the PDF —the viewer takes you to that area when you click the field— and import.
- If there are two or more, it doesn’t choose any: the message is ‘The AI took your company as the issuer’. Mark the supplier’s Tax ID and name as in the steps above. What you mark is saved for that supplier, so it doesn’t happen again with their next invoices.
The same when the AI puts the recipient as the issuer even though it doesn’t know it is your company: the one that comes after ‘Titular’ or ‘Cliente’ with their Tax ID.
This also applies to invoices that were already in the inbox: when you open them they are corrected in the same way, without reading them again. The scheme and payment method already proposed don’t change on their own: use Read again if you want them to be proposed again.
What if two suppliers look alike?
It can happen with groups that issue almost identical invoices from several companies, or with suppliers that invoice with the same platform. If the fingerprints of two suppliers appear at the same time, the one that gathers clearly more wins; if they are close, it is considered ambiguous and neither is assigned, so the invoice stays to review.
It is the cautious decision: applying the wrong supplier’s rules would give a reading that looks right, with high reliability and the Tax ID swapped. It is better for it to ask you.
If it happens to you, refine the texts of the one that comes out worse: add one that only appears on their invoices, for example their Companies Register number or their exact address.
If something goes wrong
| What you see | What has happened | What to do |
|---|---|---|
| ‘Supplier not identified’ | The Tax ID wasn’t read and the fingerprints don’t recognise any supplier (a new supplier, or two that look alike) | Mark their Tax ID on the PDF |
| ‘Check the supplier: the Tax ID is … but the layout looks like…’ | The Tax ID read and the fingerprints of the layout point to different suppliers | Check on the PDF who issues the invoice and correct the Tax ID if needed |
| ‘Warning! The invoice shows account …’ | A known supplier with a new bank account | Confirm the change by phone with the supplier before paying |
| A fingerprint appears crossed out | It has been missing from their latest invoices: it no longer counts | Nothing; if it is no use to you, remove it |
| ‘The invoice does not include the issuer’s name’ when importing | The Tax ID is there, the name isn’t | Mark the supplier’s name and import again |
| ‘The AI took your company as the issuer’ | The reading swapped issuer and recipient, and the invoice has more than one Tax ID that isn’t yours | Mark the supplier’s Tax ID and name; they are saved for them |
| ‘The AI took your Tax ID as the supplier’s. The other Tax ID…’ | The reading swapped issuer and recipient; the program took the only other Tax ID on the invoice | Check that Tax ID on the PDF and the supplier’s name, and import |
| ‘The supplier’s Tax ID is missing (or invalid): mark it in the PDF’ when importing | The invoice has no supplier | Mark their Tax ID on the PDF |
| ‘Could not record the invoice: …’ | A field read can’t be saved | The invoice goes back to To review: correct the field the message mentions and import again |
| A duplicate supplier has been created | The Tax ID was misread, with one different digit | Correct the Tax ID and merge the records from Suppliers |
| The supplier exists but it doesn’t find it | Their Tax ID is wrongly typed on the record, or it doesn’t have the supplier role | Check the Tax ID on the record and that it is a supplier |
Previous: Teach the program a supplier’s invoices · Next: Track the status of imported documents
More about Invoice import
- How does it know whether an invoice is a purchase or a sale, and how does it decide its VAT scheme and its payment method?
- How does the program learn to read a supplier’s invoices?
- How do I choose the level of the AI that reads the invoices?
- How do I import a supplier invoice in PDF?
- Import your suppliers’ invoices
- Can it read my regular suppliers’ invoices without AI?
- How do I review and correct what the system has read?
- How do I see the status of each imported document?