---
title: "Comment by Ahmet Özel on \"A validation layer for AI invoice extraction, in Python\" | Hashnode"
description: "The review sketch currently applies inv['country'] to both supplier and buyer VAT checks. I would give those identifiers their own country information, since an"
url: "https://hashnode.com/posts/a-validation-layer-for-ai-invoice-extraction-in-python/6afb0a8d4c910ad7508227b7/comment/6afb71af91b1c666ea4e1e00"
---

[Discussion](https://hashnode.com/posts/a-validation-layer-for-ai-invoice-extraction-in-python/6afb0a8d4c910ad7508227b7)

Comment [A validation layer for AI invoice extraction, in Python](https://hashnode.com/posts/a-validation-layer-for-ai-invoice-extraction-in-python/6afb0a8d4c910ad7508227b7)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[6h ago](https://hashnode.com/posts/a-validation-layer-for-ai-invoice-extraction-in-python/6afb0a8d4c910ad7508227b7/comment/6afb71af91b1c666ea4e1e00)

The review sketch currently applies inv\['country'\] to both supplier and buyer VAT checks. I would give those identifiers their own country information, since an invoice can have a supplier and buyer in different countries. Otherwise a correctly extracted buyer identifier can be rejected by the supplier country's validator.

A useful next fixture would pair a domestic invoice with a cross-border one and preserve the original identifier text beside its normalized form. That would separate extraction mistakes from validation-routing mistakes before measuring how many of the 32 failed extractions the layer actually catches.
