[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Check NAV submission status of Számlázz.hu invoices

> Read the NAV submission status of each Számlázz.hu invoice you issued this week and list failed or warned ones. Runs daily, hosted.

Source: https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server/check-nav-submission-status

Számlázz.hu reports each invoice to NAV for you, but you only learn that one was rejected if you open it, or if the notification email reaches you.

Cotlet does it in your own Számlázz.hu account with list\_invoices and get\_nav\_status, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=szamlazz-hu) [All Számlázz.hu tools](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Számlázz.hu do this on its own?

The Számla Agent API has no operation for NAV status that its documentation describes (checked 14 Oct 2026). Its invoice query returns one invoice with items, totals and payments, and the page for it does not mention a submission status. The status lives in the web interface, in the invoice details and in the VAT list download.

## How you do it in Számlázz.hu today

1. Open Számla / Kimenő számláim and find the invoice, then click its number or choose Részletek megtekintése from the row menu.
2. In the right-hand column, open Számlához tartozó adatok.
3. Select Háttéradatok / NAV. The submission status shows there, with the transaction ID when the submission succeeded.
4. For many invoices, go to Listák / Áfalista, download the table and read the status in column S. The VAT list is in the #start, #digital and #profi packages only.
5. For a failed one, check the technical user details under the NAV Online connection in account settings, then contact customer support if it is a storno without a reported original or a duplicate invoice number.

## How to check NAV submission status of Számlázz.hu invoices

Prompt

```
List the invoices I issued in the last 7 days in Számlázz.hu. For each one, read the NAV submission status and tell me which are not Sikeres adatszolgáltatás, with the warning or reason if the app shows one.
```

1. 01  
### Collect the invoices to check  
Your agent pulls the outgoing invoices issued in your date window with list\_invoices, so the check covers a week of invoices without you opening each row.
2. 02  
### Read each status  
For every invoice it calls get\_nav\_status, which returns the status text exactly as the Háttéradatok / NAV tab shows it, the transaction ID and any warning.
3. 03  
### Group by outcome  
Sikeres adatszolgáltatás goes into the fine pile. A warning-accepted status and a Sikertelen vagy elutasított adatszolgáltatás go into a short list with the invoice number and buyer, so the failed ones stand out.
4. 04  
### Point to the likely cause  
For a failure the agent names the causes the knowledge base lists: technical user details, missing permissions, a storno or corrective invoice whose original was never reported, or a duplicate number in NAV.
5. 05  
### Report once, change nothing  
Both tools only read. The agent never retries or edits an invoice; it gives you the list and the fix to make in the app.

### What you get back

Example data

```
Invoices issued 7 to 14 Oct 2026: 12
Sikeres adatszolgáltatás: 10
Sikeres, de figyelmeztetéssel befogadott: 1 (ABC-2026-00145, see the warning in NAV Online Számla)
Sikertelen vagy elutasított: 1 (ABC-2026-00147, Blue Fern Studio Kft.)
Likely cause for ABC-2026-00147: storno of an invoice whose original was never reported. Contact Számlázz.hu support.
```

### Other ways to ask

- Every morning at 7, check yesterday's invoices and message me only if one is not Sikeres adatszolgáltatás.
- Check the NAV status of all invoices I issued in September and list the ones with a warning.
- Read the NAV status of invoice ABC-2026-00147 and tell me what to do next.

## What Számlázz.hu allows, and what to know first

- The three statuses the knowledge base names are Sikeres adatszolgáltatás, Sikeres, de figyelmeztetéssel befogadott adatszolgáltatás and Sikertelen vagy elutasított adatszolgáltatás.
- If NAV is slow or down, no action is needed: Számlázz.hu keeps retrying until NAV confirms receipt.
- A storno or corrective invoice is accepted by NAV only if the original invoice was already submitted successfully.
- For a failed submission, Számlázz.hu emails the notification address you set, which is why a daily check catches the cases where that email is missed.
- The VAT list download with the status in column S needs the #start, #digital or #profi package.

Every tool here only reads, so it can run daily from n8n, Make, Zapier or cron without waiting for your OK.

Sources: [Számlázz.hu knowledge base: How do I know whether my invoice was sent to NAV?](https://tudastar.szamlazz.hu/gyik/honnan-tudom-hogy-a-szamlamat-a-szamlazz.hu-bekuldte-e-a-nav-fele) · [Számlázz.hu knowledge base: What if the NAV submission fails?](https://tudastar.szamlazz.hu/gyik/mi-van-ha-nem-sikeres-a-nav-online-bekuldes) · [Számla Agent: Query document (XML)](https://docs.szamlazz.hu/agent/category/query-document-xml)

## Call get\_nav\_status from a script

curl

```
curl https://cotlet.dev/api/v1/szamlazz-hu/invoices/ABC-2026-00147/nav-status \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"invoice_number": "ABC-2026-00147",
"status": "Sikertelen vagy elutasított adatszolgáltatás",
"transaction_id": null,
"warning": null
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is szamlazz\_hu\_read → get\_nav\_status. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server.md#automations)

## Számlázz.hu tools this automation uses

__Cotlet Számlázz.hu tools used to check NAV submission status of Számlázz.hu invoices__
| Tool | Parameters |
| ---------------- | --------------------------------------------------------------- |
| list\_invoices | issued\_from, issued\_to, buyer, payment\_status, limit, cursor |
| get\_nav\_status | invoice\_number |

[All 8 Számlázz.hu tools with descriptions](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server.md#tools)

## Frequently asked questions

### Does Számlázz.hu retry a failed NAV submission?

For NAV delays or maintenance it keeps retrying until NAV confirms. For configuration or permission problems you fix the cause first; the knowledge base describes no manual resubmit step.

### Is it safe to connect Számlázz.hu to Cotlet?

Yes. You sign in to Számlázz.hu yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Számlázz.hu once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Számlázz.hu automations

- [Cancel a Számlázz.hu invoice with a storno invoice](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server/cancel-invoice-with-storno.md)
- [Record Számlázz.hu invoice payments from bank transfers](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server/record-invoice-payments.md)
- [Számlázz.hu API and MCP server: every tool](https://cotlet.dev/integrations/szamlazz-hu-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Számlázz.hu.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Számlázz.hu.

[Sign up free](https://cotlet.dev/app/signup?app=szamlazz-hu)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.