Skip to main content

Registration

To establish a financial data connection, the receiving system must be registered in the Számlázz.hu system.

Step 1: Basic Information​

Please provide the following information in your registration email:

  • Which billing account would you like to establish the connection for? (tax number + company name)
  • What is the purpose of establishing the data connection? (e.g., accounting automation, CRM integration, etc.)

Step 2: Technical Parameters​

Technical data required for the receiving system to function:

DataDescriptionHint
name*The name of the receiving systemThis will appear in the dropdown and on the Online financial connection page.
email*Contact email addressThis is where we send the system messages related to the connection.
contactname*Contact person's nameThe name of the person responsible for the connection who can be contacted in case of a problem.
keypostfix*Key postfix5 characters, this must be added to the end of every identifier key.
addkeytourl*Should the key be added to the end of the URL?Yes / No
urlszamlakiURL suitable for receiving outgoing invoices
pdfszamlakiAttach the invoice PDF when transmitting outgoing invoices?Yes/ No
urlszamlabeURL suitable for receiving incoming invoices
pdfszamlabeAttach the invoice PDF when transmitting incoming invoices?Yes/ No
urlbanktranzURL suitable for receiving bank transactions
urlnyugtaURL suitable for receiving receipts
Difference between identifier key and key concatenation
  • We always send the identifier key with every data package in the X-Szamlazzhu-Key HTTP header (default)
  • Key concatenation (addkeytourl) is a separate function that appends the key to the end of the URL (optional)
  • Two different things: one is in the HTTP header, the other is in the URL

Step 3: Send Data​

tip

If you want to connect your application with Számlázz.hu, we expect the above parameters from you. Only specify the URL for the type of data you want to receive. Fill out the above form or download this CSV, enter your receiving system data and send it to our email address.

Live account only

Sending data of incoming invoices, bank transactions, and receipts is impossible using a test account.

Receiving endpoint requirements

We can only set up a financial data connection with endpoints that answer each delivery with HTTP 200 (OK) and return the correct response XML for that operation in the body of a single HTTP response. Without this, Számlázz.hu cannot reliably tell that the payload was received and processed.

We do not support:

Endpoints that answer only with HTTP 302 (redirect) when receiving the request - we do not follow redirects; the response XML must appear in the response body with status 200. For example, Google Apps Script (or similar "web app") receiving endpoints often do not return a direct 200 response with the expected XML body the way the data connection requires.

If your environment cannot meet these requirements, set up a server or API that returns the response XML directly, as described in this documentation.

🔗 Connection Types​

In the Számlázz.hu system, two types of online data connection registration are possible:

  • Public connection is available to all our clients; it typically includes accounting software that is listed among our currently publicly accessible partners. If you wish to integrate your system with Számlázz.hu through a public connection, prior approval, thorough testing, and marketing cooperation are required for creating the connection.

  • Hidden connection is generally simpler to create; if you only want to connect your own ERP/CRM system with your own invoicing account, please indicate this during registration. The hidden connection does not appear on the list and can only be used in the account(s) you specify.

🌐 URL Configuration Guide​

How does data transmission work?

Számlázz.hu sends all partner data to the receiving system through a single URL. This means that:

  • You can receive all client data on one URL - no need for separate URLs for each company
  • The key helps distinguish - every data package contains the client identifier key
  • Distribution happens in your system - you decide how to handle different clients' data

What do you need to configure?

  • Provide the URL where you can receive all partner data
  • If you want, we can append the key to the end of the URL (addkeytourl setting)
  • The domain cannot change, only the key can be appended to the end of the URL

Example:

  • Base URL: https://yoursystem.com/receive/
  • With key appending: https://yoursystem.com/receive/clientkey123

This solution is simpler for you too, as you only need to maintain one endpoint!