canonical: https://jentic.com/apis/netaccounting.hu/netaccounting

# Netaccounting Hu Send in APIs

The Send in APIs push bookkeeping data into the Hungarian NetAccounting system: outgoing or incoming invoices as XML, journal entries grouped by date with debit and credit ledger numbers, bank statement items for an account number, and supporting documents labelled by type. A booked invoice returns the iktatoszam registration number NetAccounting generates on success. The spec's server is the NetAccounting test host, and the invoice XML follows the szamla schema that NetAccounting documents separately.

## For AI agents

Book incoming or outgoing invoices, post dated journal entries with debit and credit ledgers, import bank statement items, and upload typed documents into NetAccounting.

## Scope

Does not issue invoices to customers, file tax returns, or read reports back out of the ledger. Use for sending bookkeeping data into NetAccounting only.

## Capabilities

- Book an outgoing (ki) or incoming (be) invoice into NetAccounting as a szamla XML document and receive its iktatoszam registration number
- Post journal entries for one or more dates, each row carrying a debit ledger, a credit ledger, and an amount, with a logType journal code
- Import bank statement items against an accountNumber
- Upload a document with a name and a documentType such as Bevétel, Kiadás, Bankkivonat, or Pénztár, plus an optional label and note

## Use cases

### Agent posting invoices into a Hungarian ledger

A bookkeeping agent that receives invoices from a billing tool needs to book them in NetAccounting. Through Jentic the agent searches for 'book an invoice in NetAccounting', loads the bookInvoiceService operation with its input schema, sets direction to ki for outgoing or be for incoming, and posts the szamla XML. On success the response lists the iktatoszam NetAccounting generated for each invoice. The APIKey header value is attached by your own Jentic One instance at call time.

Example prompt: Call POST `/bookInvoiceService/ki` with an outgoing invoice in szamla XML and record the returned iktatoszam

### Daily journal entries

An accountant automating recurring postings sends journal rows grouped by date. Each row names a debit ledger number, a credit ledger number, and an amount, with optional fields such as costCenter and partnerName, and the logType query parameter selects the journal from codes including 3, 4, and 20.

Example prompt: Call POST /journalService with logType 3 and a body for 2025-01-02 containing one row with debit '113', credit '112', and amount 12000

### Bank statement import

Rather than keying bank lines by hand, a firm sends the statement for an account to NetAccounting with the account number and its transaction items. Supporting files such as the statement PDF can be registered separately with the document upload operation using the Bankkivonat document type.

Example prompt: Call POST `/bank/import` with accountNumber and the statement items, then POST /UploadService with name 'statement-2025-01' and documentType 'Bankkivonat'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/bookInvoiceService/{direction}` | Book an incoming or outgoing invoice |
| POST | `/journalService` | Create journal entries for given dates |
| POST | `/bank/import` | Import bank statement items |
| POST | `/UploadService` | Upload one document |

## Key resources

- **Invoices** — Book outgoing or incoming invoices as szamla XML and receive registration numbers
- **Journal** — Dated journal rows with debit and credit ledgers, amounts, and a logType code
- **Bank** — Bank statement item import for an account number
- **Documents** — Document upload with a name, type, optional label, and note

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 50 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 64 / 100
  - Developer Experience & Jentic Compatibility: 60 / 100
  - AI-Readiness & Agent Experience: 31 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 47 / 100
- **View full report:** https://jentic.com/apis/netaccounting.hu/netaccounting/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring NetAccounting by hand means building szamla invoice XML, nesting journal rows under date and row-number keys, picking the right logType code, and adding the APIKey header to every call. Through Jentic you install once, import the Send in APIs from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** NetAccounting puts the invoice direction in the URL path (`/bookInvoiceService/ki` or /be), so a rule can limit your agent to one direction, for example incoming invoices only. You choose the operations it may call, so journal posting or bank import is not included unless you add it.
- **Credential handling:** Your NetAccounting API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'book an incoming invoice' or 'import a bank statement', and Jentic returns the matching NetAccounting operation with its input schema so the agent sends the right body format.

## Related APIs

- **Billingo API v3** — Hungarian invoicing software that issues the invoices NetAccounting books
- **Xero Accounting API** — General ledger, invoices, and bank transactions in Xero
- **Xero Bank Feeds API** — Bank statement lines delivered into Xero

## FAQ

### What authentication do the NetAccounting Send in APIs use?

Per the OpenAPI spec, requests carry an API key in a header named `APIKey`. Through Jentic that key is stored encrypted by your own instance and added to each call, so it never appears in the agent's context.

### Can I book both incoming and outgoing invoices?

Yes. POST `/bookInvoiceService/{direction}` takes direction ki for outgoing invoices or be for incoming ones, with the invoice in the szamla XML format. A successful booking returns the iktatoszam registration number NetAccounting assigned, and an error returns a hibakod element.

### What are the rate limits for the NetAccounting Send in APIs?

The OpenAPI spec does not specify rate limits. Check https://netaccounting.hu or ask NetAccounting support for current limits before sending large journal or bank imports.

### Is there a NetAccounting MCP server?

You don't need an MCP server to give your agent NetAccounting. Jentic connects it directly from the API Directory: import it, store your APIKey value once, and your agent calls the invoice, journal, bank, and document operations it needs.

### How do I post a journal entry through Jentic?

Import the NetAccounting Send in APIs from the API Directory in your Jentic One instance and store your key. Your agent searches for 'post a journal entry', loads POST /journalService, and sends rows grouped by date with debit, credit, and amount, plus the logType query parameter. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the NetAccounting Send in APIs?

Yes. Write a rule that allows only POST `/bookInvoiceService/be`, and the agent can book incoming supplier invoices but cannot book outgoing ones, post journal entries, or import bank statements. Every call it makes is logged.