In SME lending the outright fake is the easy case. The hard case is a pack of real documents that describe two slightly different companies.
A working-capital or trade-finance file arrives as a commercial registration, a clutch of invoices, a supply contract, bank statements and the owner's ID. Every one of them can be genuine and the file can still be wrong — because the invoices were issued by an entity that is not quite the borrower, or the contract covers goods the invoices do not. The fraud is in the joins.
Genuine documents, describing different things
The name problem is real, and it cuts both ways
"Al Noor Trading LLC" on the registration. "Al Nour Trading L.L.C." on the invoice — an invented pair, for illustration. In the Gulf this difference is overwhelmingly a transliteration artefact: an Arabic name rendered into Latin script by two different people, with a different vowel and a different punctuation habit. Treating it as fraud would flag half an honest portfolio.
And yet substituting a near-identical entity is a known trick, precisely because everyone has been trained to wave the difference through. The resolution is not to pick one answer. It is to check the name against something that cannot drift: the commercial registration number. Names vary in spelling; a CR number does not.
The same problem, in its personal rather than corporate form, runs through bilingual professional identity — one person, two scripts, several spellings.
What should agree with what
| This document | Checked against | What should agree |
|---|---|---|
| Invoices | Commercial registration | The issuing entity, by CR number and not only by name |
| Invoices | Supply contract | Goods or services, unit prices and payment terms |
| Invoices | Bank statement | That the payments described actually moved |
| Supply contract | Commercial registration | Signing authority and the activity the company is registered for |
| Owner's ID | Commercial registration | The same person as the registered owner or manager |
The third row is the quiet one. An invoice is a claim that a transaction happened; the statement is the only document in the pack that can corroborate it.
Invoices are becoming easier to check
A PDF invoice is a picture of a claim. A structured electronic invoice is the claim itself, in fields, issued through a channel that records it. As Oman's e-invoicing programme rolls out — the shape of it is in the Fawtara timeline and what Peppol means in Oman — the invoices arriving in a credit file will increasingly carry their own structure.
That does not retire the comparison; it sharpens it. A structured invoice still has to agree with the contract beside it and the statement behind it. What changes is that the figures no longer have to be recovered from a scan before anyone can compare them. Whether your own systems can produce and consume those documents is a separate readiness question, covered in ERP e-invoicing readiness.
Keep the pack together
The single most useful change in an SME review process is also the dullest: check the documents as one application rather than one at a time. Everything in the table above is invisible to a reviewer working document-by-document, and obvious to one reading them together — which is the argument of fraud hiding between documents in general.
DocHaqq checks each document on its own and then against the rest of the application, and reports what disagrees with the evidence behind it, on your own servers. See how it works, or talk to us about an SME file you have already reviewed by hand.
Related posts
-
eKYC in Oman: What Happens Between the ID Scan and a Verified CustomerFour steps for the customer. Five separate judgements for the system, and one decision.
11 September 2026 -
reKYC: Verification Is a Date, Not a StatusA customer verified three years ago was verified three years ago. That is all the record proves.
11 September 2026 -
10 Automated Checks Every Cheque Platform Should PerformA single successful OCR result is not enough. Confidence has to be built across the whole document.
31 August 2026