MTB-BATCH-02Invoice counter value repeated inside the ZIP

Mutabiq reports MTB-BATCH-02 when two files uploaded together in one ZIP carry the same invoice counter value under the same seller. Its severity is Warning, not Error: no published ZATCA rule reads two documents together, and two issuing devices of one seller may legitimately share counter values.

Recorded in Mutabiq's decisions log under “2026-09-29 — Rule pack 2.1.0: the invoice chain across a ZIP's members (TX16) and MTB-BR-DEC-23 per line (D29)”.

Validate 5 invoices free

Five checks a month on the Free plan. The file is checked in memory and is never stored.

What Mutabiq reports

One entry for each way this rule can be reported.

Reported as
What kind of value was found — empty, not_15_digits and the like — never the value itself.

Invoice counter value is repeated inside this ZIP

Reported ascounter.icv_repeated_in_archivethe same invoice counter value appears more than once in the archive

What is wrong

Two or more members of the uploaded archive carry the same invoice counter value (KSA-16) under the same seller VAT registration number, and this note is on each of them. ZATCA's E-Invoicing Detailed Guideline (Annex 2 of the E-Invoicing Resolution) describes the counter as a tamper-resistant sequence that cannot be reset and increments for each invoice or note issued; the XML Implementation Standard itself requires only that the counter is present and written in digits. In Mutabiq's reading, the counter belongs to the e-invoicing solution that issues the documents, so two solutions of one seller can carry the same numbers, while one solution cannot repeat one. If these files come from different devices, this is expected. This is reported as a risk rather than as a rejection: ZATCA's published rules read one document at a time and check only that a counter is present, so no assertion sees the repeat. While a value is repeated, Mutabiq does not judge the previous invoice hash link into it or out of it, because there is no single document before or after it.

What to check in your ERP

If the files come from one device, the counter is not being advanced or is being reset: look for a counter kept per user session or per process rather than once for the device, a value reset by a restart, a reissue or a year end, a document exported twice into two files, and a copy of one file placed in the archive twice. If they come from different devices, nothing is wrong, and the clearest way to read the report is to upload each device's documents in an archive of its own.

Check an invoice

Check your own invoice

© 2026 Hayatiq AI Solutions F.Z.E. All rights reserved.