Error handling

This page lists the error codes specific to delegated invoicing and self-billing, with the original Hungarian message, an English translation, when the error occurs, and what to do. General Agent error behaviour (headers szlahu_error and szlahu_error_code) is described in Agent error handling.

The errors are grouped by the steps of the process:

• how errors are returned - where to look for the error message and code,
• connection and account creation errors - errors of the action-agent_ceg_mb call,
• invoice prefix errors - errors of the delegated prefix logic,
• invoice operation errors - storno, correction, repeat,
• receipt errors - delegated receipt issuing,
• test account errors - specifics of test mode.

How errors are returned

• Számla Agent: the error message is returned in the szlahu_error HTTP response header, the numeric code in szlahu_error_code.
• action-agent_ceg_mb: on success the outcome arrives in the XML_AGENT_RESPONSE header; on failure the same szlahu_error / szlahu_error_code headers are used.
• Web UI: the same messages appear on the control panel.

Connection and account creation errors (action-agent_ceg_mb)

Code	Message (HU)	Meaning and what to do
3	Sikertelen bejelentkezés.	Login failed: wrong login name or password. Fix the credentials and retry.
7	Hiányzó adat: (mező).	Required data is missing from the request. It occurs in two cases: "Hiányzó adat: Számla Agent kulcs vagy bejelentkezési név/jelszó" (no authentication data was sent) and "Hiányzó adat: Számlaszám előtag" (<cegszamlaszamelotag> is empty - the prefix is mandatory in the API request). Send the missing field.
68	Már létezik cég ezzel az adószámmal és számlaszám előtaggal.	An account already exists with this tax number and prefix. Agree on a different prefix with the supplier.
101	Ez a bejelentkezési név már foglalt, kérjük, válassz másikat.	Occurs only when a new supplier account is created: the login name given in <usremail> is already used by a user. Use a new, dedicated email/login for the delegated user.
137	Jelenleg nincs jogosultsága ahhoz, hogy ilyen módon hozzon létre számlázási fiókot. Ha mégis szeretne, vegye fel a kapcsolatot ügyfélszolgálatunkkal (szamlazz.hu/kapcsolat)	The agent_ceg_mb interface is not enabled for your account. You can request access via customer support.
164	Ez a felhasználó (név) több számlázási fiókhoz is hozzáfér, így a funkció nem üzemképes.	The user given in the request has access to more than one account. Agent requests (XML files submitted via POST) can only be sent with a user that has access to exactly one account; remove the user's access from the other accounts, or use a dedicated user.
250	Ez a fiók nem használható, mert a fiókgazda még nem regisztrált. Üzenetet küldtünk a fiókgazdának, hogy vegye birtokba a fiókját (email address).	You tried to log in or invoice with the <usrMb> user before the supplier took ownership of the new account. If there is a pending account-owner invitation, the system automatically re-sends the invitation email to the supplier at this point. Wait until the supplier activates the account, then retry.
309	Érvénytelen adat: (mező).	Invalid data, for example a malformed tax number in <cegtaxnumber>. Fix the value and resend.
337	Az előtag csak nagybetűket és számokat tartalmazhat, és hossza legfeljebb 5 karakter lehet.	Malformed <cegszamlaszamelotag>. Send a prefix of max. 5 characters, consisting of uppercase letters and digits only.

Errors 3, 164, and 250 can occur not only here: they arise at login, so they can appear in any delegated Agent call (invoice or receipt issuing) as well.

Existing account with the given tax number

If an account already exists with the tax number given in <cegtaxnumber>, that is not an error: the call does not create a duplicate account; instead, depending on the situation, it sends (or re-sends) an email, and returns the outcome as a text response in the XML_AGENT_RESPONSE header:

Case	What happens	Response (XML_AGENT_RESPONSE)
The account has no account owner yet	The account-owner invitation email is re-sent.	"Már létező fiók, nincs fiókgazdája. Fiókgazdai meghívó (megbízott számlakibocsátás) email újraküldve." (existing account without owner, invitation re-sent)
Account owner exists, and a join request for the <usremail> user is already pending	The join request email is re-sent to the account owner.	"Már létező fiók fiókgazdával. A csatlakozási kérelem emailt újraküldtük a fiókgazdának." (existing account with owner, join request re-sent)
Account owner exists, no pending request for this user	A new join request is created; the account owner is notified by email.	"Már létező fiók fiókgazdával. Csatlakozási kérelmet küldtünk a fiókgazdának." (existing account with owner, join request sent)

In these cases the company data sent in the request (company name, address, bank account, email, etc.) does not modify the existing account; the notification email goes to the company email stored in the account and to the account owner's email address, not to the <cegemail> given in the request. Related errors:

• 68 - if the <cegszamlaszamelotag> prefix is already used with this tax number, the call fails with error 68 instead of the cases above. Agree on a different prefix with the supplier.
• 101 - occurs only when a new account is created; for an existing account the system uses the existing <usremail> user for the request.
• 250 - if the account owner has not taken ownership of the account yet and you try to log in with the <usrMb> user in the meantime (see the table above).

Invoice prefix errors

Code	Message (HU)	Meaning and what to do
200	Ezt az előtagot ugyanezzel az adószámmal jelenleg is használja egy számlázási fiók számla/nyugta előtagként. Kérjük, válassz másik előtagot!	The prefix is currently in use by another active account with the same tax number. It can occur in the action-agent_ceg_mb call, when the join request is accepted, and when a new prefix is registered. Choose a different prefix.
202	Ez a számlaszám előtag nem létezik vagy nincs engedélyezve: (előtag).	The invoice book of the prefix is disabled or blocked due to an invoice number collision found in NAV. A disabled book can be enabled in the supplier account on the Settings > Prefixes page; a NAV-blocked book cannot be unblocked - use a different prefix.
353	Nincs egyetlen érvényes számlaszám előtag sem.	No enabled invoice book exists in the account. Create or enable an invoice book.
354	Ez a számlaszám előtag nem használható.	The prefix belongs to another delegate, is a receipt prefix, or already has invoices and cannot be taken over. Use your agreed delegated prefix.
356	A megadott számlaszám előtag helyett használd ezt: (előtag).	You already have a delegated invoice book with this supplier. Use the prefix returned in the message.
357	Kérjük, add meg a számlaszám-előtagot.	You sent no prefix, and it cannot be selected automatically either, because you have no delegated invoice book or more than one. Send the agreed prefix in <szamlaszamElotag>.
360	Ez az előtag nem módosítható, mert már használták számlakiállításhoz.	Appears on the UI when a user with rights to edit prefixes (typically the supplier's account owner) tries to rename a prefix on the Settings > Prefixes page that already has documents issued with it. A used prefix cannot be modified; if a new prefix is needed, a new invoice book must be created.
362	Ezt az előtagot ez az adószám korábban már használta. Kérjük, válassz másik előtagot.	The prefix was used with this tax number before, in a since-disabled (no longer active) account. Choose a different prefix. (Counterpart of error 200, where the other account is still active.)

The decision logic behind these errors is explained in the decision tree on the Invoice prefix handling page.

Prefix blocked due to an invoice number collision found in NAV

When the NAV Online Számla connection is established (and whenever the NAV settings are saved), the system checks every invoice prefix of the account against the NAV system: it queries whether the next invoice number to be issued (e.g. PREFIX-2026-12) already appears in the NAV data reports. If it does - typically because another invoicing software has already submitted invoices with the same prefix - the system blocks the invoice book to prevent duplicate invoice numbers.

A blocked book is shown with a warning icon on the Settings > Prefixes page; it cannot be edited or re-enabled - use a different prefix instead. Invoicing with a blocked prefix fails with error 202.

Invoice operation errors (storno, correction, repeat)

Code	Message (HU)	Meaning and what to do
358	Ezt a számlát csak a fiók tulajdonosa sztornózhatja.	A delegated user tried to reverse an invoice issued by the supplier. Ask the supplier to reverse it.
359	Ez a számla megbízott számlakibocsátás keretében készült. A sztornózást kérd a megbízottól: (cégnév).	The supplier tried to reverse a delegated invoice. The message names the delegate to ask.
489	Ez a számla megbízott számlakibocsátás keretében készült. Az ismétlést kérd a megbízottól: (cégnév).	The supplier tried to repeat a delegated invoice. Ask the delegate.
493	Ezt a számlát csak a fiók tulajdonosa helyesbítheti.	A delegated user tried to correct an invoice issued by the supplier. Ask the supplier.
494	Ez a számla megbízott számlakibocsátás keretében készült. A helyesbítést kérd a megbízottól: (cégnév).	The supplier tried to correct a delegated invoice. The message names the delegate to ask.
17	Nem megengedett művelet.	You also get this error when you try to repeat an invoice as a delegated user; repeating is not available to delegates.

Receipt errors

Code	Message (HU)	Meaning and what to do
7	Hiányzó adat: nyugtaszám előtag.	The <elotag> field is required for receipts. Send the agreed receipt prefix.
8	Nincs jogosultságod vagy megfelelő díjcsomagod a művelet elvégzéséhez (művelet)!	The delegate account's service plan does not include receipt issuing via Agent (every plan except the free one includes it), or the dedicated user's role has no receipt issuing right assigned.
336	Ezt az előtagot a számlázás már használja, így nem lehet nyugta előtag.	The prefix is already an invoice prefix. Use a separate receipt prefix.
524	Ez a nyugtaszám előtag nincs engedélyezve.	The receipt prefix was disabled in the supplier account. It can be enabled on the Settings > Prefixes page, by selecting the prefix and ticking the "Engedélyezem az előtag használatát" (enable the use of the prefix) checkbox. Ask the supplier to do this, or use another one; reversing an existing receipt is not blocked by this.

Test account errors

Code	Message (HU)	Meaning and what to do
167	Teszt fiók számla darabszám túllépés. Kérjük, próbálkozz újra pár perc múlva.	A test account exceeded the number of invoices allowed via Agent within a few minutes. Wait a few minutes and retry. The limit does not apply to live accounts.

In test mode the Agent accepts only XSD-valid XML, so schema errors that a live account may tolerate are rejected. More on test-mode behaviour: Testing the flow.

General errors that also apply

All standard Agent errors can occur in delegated calls too, for example XML parsing errors, missing rights for a document type (proforma, delivery note, advance invoice), or NAV-related errors. See the general Agent error handling page.

Related pages

• Invoice prefix handling
• Issue invoices in third-party invoicing
• Issue receipts in third-party invoicing