myDATA expense classification errors: 306, 307, 313 and the rest

AADE’s official message for each error, what it means in practice and how to fix it.

Error 306

AADE message: Invoice line: {lineNumber}. Sum of classifications are not equal to line's net value

What it means

The classification amounts of a line do not add up to the line’s net value.

How to fix it

The E3 classification amounts of the line must add up exactly to its net value. The same applies to the VAT classification (VAT_361 etc.): it is declared with an amount equal to the net value, not the VAT amount. Also check rounding when a line is split into several classifications.

Error 307

AADE message: Classification type {classificationType} is forbidden for Classification category {classificationCategory}

What it means

The E3 code is not allowed in the chosen category, whatever the invoice.

How to fix it

Choose an E3 code that belongs to the category, or change the category. See which codes each category allows in the E3 codes guide.

E3 codes guide →

Error 313

AADE message: Classification type {classificationType} is forbidden for Classification category {classificationCategory} combined with invoice type {invoiceType}

What it means

The category and E3 code combination exists, but is not allowed for this invoice type.

How to fix it

Check the invoice type (e.g. 1.1, 2.1, 13.1) and choose a combination from AADE’s official combinations table for that type.

E3 codes guide →

Error 308

AADE message: Classification category {classificationCategory} is forbidden for Invoice type {classificationType}

What it means

The category is not allowed at all for this invoice type.

How to fix it

Choose one of the categories the invoice type accepts.

Error 304

AADE message: All invoice rows or none should have classifications included

What it means

Only some lines of the invoice were classified.

How to fix it

Send the classifications of every line of the invoice together, in the same submission.

Error 305

AADE message: Invoice line: {lineNumber}. Duplicate classification type {classificationType} and category{classificationCateg ory}

What it means

The same line has two classifications with the same code and category.

How to fix it

Merge them into one classification with the total amount.

Error 230

AADE message: {Field} is mandatory for invoice detail (number} [Possible {Field} values: {E3 classifications, VAT classifications}

What it means

A mandatory field of the line is missing. In expense classification, usually the VAT classification on a line with VAT.

How to fix it

Add the missing classification, e.g. VAT_361 for domestic purchases and expenses, with an amount equal to the line’s net value.

All classification errors

Business errors in the “Classification” category (section 7.2 of the documentation), with the official message.

CodeAADE message
301Invoices with ΜΑΡΚ {mark} requested not found
302Duplicate classification line number {lineNumber}
303Line number {lineNumber} not found in invoice with MARK {mark}
304All invoice rows or none should have classifications included
305Invoice line: {lineNumber}. Duplicate classification type {classificationType} and category{classificationCateg ory}
306Invoice line: {lineNumber}. Sum of classifications are not equal to line's net value
307Classification type {classificationType} is forbidden for Classification category {classificationCategory}
308Classification category {classificationCategory} is forbidden for Invoice type {classificationType}
309{ClassificationMode} classifications are forbidden for invoice with mark {mark} on behalf of vat number {vatNumber} for invoice row with detail type {detailType}
310All classifications of invoice or none should have category value {classificationCategory}
311Classification with type {classificationType} and category " {classificationCategory} not found in invoice summary
312Sum of classifications with type {classificationType} and category {classificationCategory} not matching with related total in invoice summary
313Classification type {classificationType} is forbidden for Classification category {classificationCategory} combined with invoice type {invoiceType}
314All invoices should contain either income or expenses classifications section, not both or none
315VAT classifications have no category
316VAT classifications are not allowed in case of VAT exemption
317Invoice detail { lineNumber } : VAT classification must be of type 366 in case vatExemptionCategory = 16
321Classifications are not allowed only in the invoice summary
323User cannot use directly this service due to annual gross income limits
324Classification rejection or deviation is not allowed to be sent with this method
325Initial invoice's combination of vatCategory {vatCategory} and vatExemptionCategory {vatExemptionCategory} not found in ExpensesClassificationDoc
326Initial invoice's combination of vatCategory {vatCategory}, vatExemptionCategory {vatExemptionCategory}, amount {amount} and VAT amount {vatAmount} not matching classification’s
327Combination vatCategory {vatCategory}, vatExemptionCategory {vatExemptionCategory}: Amount must have same analogy with VAT amount
328Combination vatCategory {vatCategory}, vatExemptionCategory {vatExemptionCategory}: VAT amount exceedes the one of initial's invoice for same combination
329Combination vatCategory {vatCategory}, vatExemptionCategory {vatExemptionCategory}: Combination not found in initial invoice
330Unexpected technical error for classification line
331Could not load/found valid validation doc for classification with category {classification_category} and type {classification_type}
332In case of VAT exemption sum of E3 classifications' amounts and sum of VAT classifications' vat amounts must be equal to invoice total net value plus taxes to be classified plus excluded vat amount
333Sum of E3 classifications' amounts must be equal to invoice total net value plus taxes to be classified
334Combination vatCategory {field1} , vatExemptionCategory {field2} : In case of without VAT obligation, a classification with similar VAT exemption category, VAT category of 24% or 17% and classification type 366 is required [Possible {field1} values: {‘null’, [1-8]}] [Possible {field2} values: {‘null’, [εύρος τιμών των αιτιών εξαίρεσης από το σχετικό παράρτημα]}]
335SendExpensesClassificationP erInvoice method is not supported for fuel invoices or invoices of type 1.5
336In case of VAT exemption a percentage of vat amount must be referred in E3 classification with category 2.5
337Combination vatCategory {field1}, vatExemptionCategory {field2}: Fields vatAmount, vatCategory and vatExemptionCategory must be null when classifications are posted per line [Possible {field1} values: {‘null’, [1-8]}] [Possible {field2} values: {‘null’, [εύρος τιμών των αιτιών εξαίρεσης ΦΠΑ από το σχετικό πίνακα του παραρτήματος]}]
338Classification is forbidden for invoice row {linenumber} because of its recType or its detailType Value
339{msg} classification is forbidden for invoice row {linenumber} because of its detailType value [Possible {msg} values: {‘incomeClassification’, ‘expensesClassification’}]
340ClassificationPostMode field must not be contained in xml
341Expenses VAT classification code NOT_VAT_295 is not allowed to be posted for invoices of type 14.1 and 14.3

Errors that never reach AADE

Taktiko checks every classification against the official combinations table and the sums of every line before sending it. If AADE rejects something, you see the reason next to the invoice.

Start free

Source: AADE, myDATA REST API documentation v2.0.2 (September 2026) and classification combinations table v2.0.2.