Ada is invented for this example. She makes cabinets, and a draft invoice is sitting on her screen, logo straight, total tidy, ready to email. Somewhere in the middle the rate and the tax amount have stopped speaking to each other. Filling the page and sending the page are not the same job.

Based on documentation, not a hands-on test. This is a reading of the consolidated directive and of one OWASP page. It does not decide whether a particular invoice is valid, and it does not state Latvian law.

What the consolidated Article 226 lists

For VAT, the directive names the particulars an invoice under Articles 220 and 221 has to carry. Ada’s pretty PDF does not get to invent a shorter list.

The consolidated text of Council Directive 2006/112/EC dated 14 April 2025, accessed 8 November 2026, Article 226, opens: “Without prejudice to the particular provisions laid down in this Directive, only the following details are required for VAT purposes on invoices issued pursuant to Articles 220 and 221.”

The particulars in that article include the date of issue, a sequential number, the supplier’s VAT identification number, the customer’s VAT identification number in the cases point (4) names, the full name and address of the supplier and of the customer, quantity and nature, the taxable amount per rate, the unit price exclusive of VAT, discounts or rebates not already in the unit price, the VAT rate applied, and the VAT amount payable except where a special arrangement excludes it.

The article continues with further points, including “Cash accounting”, “Self-billing”, an exemption reference, “Reverse charge”, and margin-scheme mentions. The link is the full list.

That opening phrase is an EU baseline for VAT particulars on those invoices, subject to other provisions in the same directive. It is not a sentence that every national rule stops there.

Article 227 of the same consolidation says member states may require taxable persons established in their territory, and supplying goods or services there, to indicate the customer’s VAT identification number in cases other than point (4) of Article 226.

Article 226b says that on simplified invoices under Articles 220a and 221(1) and (2), member states shall require at least five listed details, and “They may not require details on invoices other than those referred to in Articles 226, 227 and 230.”

This draft does not read Latvia’s VAT statute, so it does not say whether Latvia uses the Article 227 option or any other option in the directive. Checking the local rule is a separate step. Matching a draft to Article 226 is not a statement that the invoice meets that local rule. Ada’s workshop is not in the statute book either. She is here so the arithmetic has a desk to sit on.

A draft whose own figures disagree

Still hypothetical. Ada’s draft shows a taxable amount of 100.00, a VAT rate of 21 percent, and a VAT amount of 20.00.

100.00 × 0.21 = 21.00, not 20.00. The 21 percent is here so the multiplication is exact. It is not a rate taken from a Latvian return.

Line on the draftFigureWhat 100 × 0.21 gives
Taxable amount100.00
VAT rate21%
VAT amount printed20.0021.00

Points (8), (9), and (10) of Article 226 are the taxable amount, the rate, and the VAT amount. On this made-up draft they do not agree. One multiplication is the whole audit. It is also the least glamorous minute in the building, which is why it gets skipped.

Filling a draft and sending it

A form that copies name, date, quantity, and prices into a document has not sent the document. The send is a second decision, and it is the one the customer actually sees.

OWASP LLM06:2025, Excessive Agency, accessed 8 November 2026, describes agency as the ability to call tools and take actions. One mitigation it states is to require a person to approve high-impact actions before they are taken. Its mailbox example says a plugin chosen to read mail also contained functions for sending, and that one avoidance is an extension that only reads, or a manual review before send.

  1. Copy the fields into a draft
  2. Check rate against amount
  3. Send only after that check

If the tool can email the customer, OWASP’s stated mitigation is approval before that action, or not giving the model the send function. That is the control described on that page. It is not a finding that any product works this way.

GDPR Article 22(1), in the consolidation of 4 May 2016 accessed the same day, is about a decision based solely on automated processing, including profiling, which produces legal effects concerning a person or similarly significantly affects them. This draft does not treat every invoice approval as that kind of decision.

Name and address

Point (5) of Article 226 requires the customer’s full name and address. Where that customer is a natural person, GDPR Article 4 is the definition of personal data and of controller and processor.

Article 28 says that where processing is carried out on behalf of a controller, the relationship is governed by a contract or other legal act that sets out subject matter, duration, nature, purpose, and the type of personal data.

Article 5(1)(c) says personal data shall be adequate, relevant, and limited to what is necessary. None of those sentences is a finding that a vendor file meets them.

Sources