Create and send e-invoices in accordance with the Austrian standard.
Current Version: 26.1.0.0as of Business Central 26. AppSource Name: E-Document - ebInterface
Manual
Creation date: 2025/09/15 The current version of this manual can be found at:
☰ Contents
General
E-Document - ebInterface E-Document - ebInterface allows you to create and send e-invoices for sales and service documents in accordance with the Austrian standard...
Setup
ebInterface Document Formats In the ebInterface Document Formats page you can define the various settings and defaults for ebInterface and assign them to a Code. The code can be specified for each customer on the Customer Card in the ebI Document Format field. The specified code determines the rules for creating XML files for the customer's sales and service documents...
XML Schemas E-Document - ebInterface provides freely configurable XML schemas for creating ebInterface XML files. Depending on which fields and data you define as mandatory in the XML schema, errors are displayed at the time of posting...
Payment Methods On the Payment Methods page, you must specify the appropriate payment types and bank accounts to be used for ebInterface...
VAT Posting Setup The Tax Categories must be specified in the VAT Posting Setup page...
Company Information On the Company Information page, basic information for ebInterface is specified in the ebInterface group...
E-Documents
E-Document Services E-Document - ebInterface extends Microsoft Business Central 365 e-documents with the ebInterface document format...
ebInterface Connection Setup The ebInterface Connection Setup page is used to set up the connection with the ebInterface service. As soon as Environment, Username and Password are specified, the action Check Connection can be used to check whether the ebInterface service is reachable and a connection with the stored settings is possible...
Real Data Permissions Real Data Permissions add an additional level of security to actions and processes. This is to prevent test data from being accidentally interpreted as real data. Particularly critical actions and processes (e.g. sending data to an external service) can therefore only be executed if a real data permission has been granted for the current environment...
Workflows A workflow for ebInterface e-documents must be configured for the set up of the ebInterface document sending profile...
Document Sending Profiles The final step in configuring electronic documents (e-documents) for ebInterface is to set up a document sending profile...
Working with the App
Customers On the Customer Card, you must specify the corresponding Document Sending Profile and the ebI fields so that e-documents will be created and sent to ebInterface for the customer...
Documents Sales documents and service documents are created, posted and printed as before. The Document Sending Profile specified for the Bill-to Customer determines whether or not an ebInterface e-document is created during posting...
E-Documents The following additional fields and actions are available for ebInterface on the E-Document page...
Archive
ebInterface Service Log The ebInterface Service Log page displays detailed information about what has been sent to and what was returned from ebInterface...
Information for Developers
Add Attachments If the Add Attachments field is activated in the ebInterface Document Format, a PDF file of the document based on the Report Selection is created by default and sent to ebInterface in addition to the XML file...
Event Request
Appendix
NAVAX License Management The NAVAX License Management page (in older versions NAVAX License Overview or NCEX License Overview) displays the current license status of the NAVAX extensions...
Installation Notes
Release Notes
Docs / E-Document - ebInterface / General E-Document - ebInterface
E-Document - ebInterface allows you to create and send e-invoices for sales and service documents in accordance with the Austrian standard.
For more information, see [WKO] What is ebInterface?
The app extends Microsoft Business Central 365 e-documents with the ebInterface document format.
For more information, see [Microsoft Learn] Business Central - E-documents overviewE-Document - ebInterface provides freely configurable XML schemas for creating ebInterface XML files. Depending on which fields and data you define as mandatory in the XML schema, errors are displayed at the time of posting.
Standard schemas can be downloaded from the download area of the app.
Navigation
Fields, actions, pages and reports originating from the extension are labeled with ebInterface or ebI.
The search terms "ebinterface", "nvxebi", "ncebi" and "navax" are also recognized by "Tell me what you want to do".
Note
E-Document - ebInterface was developed with the prefix NCEB resp. NVXEB.
NCEB resp. NVXEB stands for NAVAX Consulting resp. NAVAX E-Document - ebInterface.
Permission Sets
The following permission sets are available for E-Document - ebInterface:
Name
Description
NVXEB
ebInterface
You need these permissions to use E-Document - ebInterface.
NVXEB, SETUP
ebInterface Setup
You need these permissions to set up E-Document - ebInterface.
For more information, see Setup, ebInterface Document Formats.
In the ebInterface Document Formats page you can define the various settings and defaults for ebInterface and assign them to a Code. The code can be specified for each customer on the Customer Card in the ebI Document Format field. The specified code determines the rules for creating XML files for the customer's sales and service documents.
For more information, see Working with the App, Customers.
Fields
Code
Specifies the code for the document format.
Description
Specifies a description.
Invoice Recipient
Specifies whether the invoice recipient is the federal government or another invoice recipient.
Together with the ebi fields of the customer, this field determines the assignment of the ebI Order Reference in the sales and service documents.
For more information, see [e-Rechnung.gv.at] - Invoice Recipients
Supplier No.
Specifies the supplier or vendor number of the biller in the systems of the invoice recipient.
Specifies which schema should be used when creating the XML file for this document type.
For more information, see Setup, XML Schemas.
Add Attachments
Specifies whether additional files should be sent to ebInterface in addition to the XML file. If this field is activated, a PDF file of the document based on the Report Selection is created and attached by default. This logic can be changed via individual programming, and additional files can also be added.
For more information, see Information for Developers, Add Attachments.
XML Posting Preview
Specifies whether an entry for previewing the XML file should be added to the posting preview.
For more information, see Working with the App, Documents.
Opens the NAVAX License Management which displays the current license status of the NAVAX extensions.
For more information, see Appendix, NAVAX License Management.
Docs / E-Document - ebInterface / Setup XML Schemas
E-Document - ebInterface provides freely configurable XML schemas for creating ebInterface XML files. Depending on which fields and data you define as mandatory in the XML schema, errors are displayed at the time of posting.
The various schemas are set up on the XML Schemas - ebInterface page. The XML schemas can be specified in the corresponding document type fields on the ebInterface Document Formats page. The schema specified for a document type determines how and according to which rules the XML files for documents of this type are created.
For more information, see Setup, ebInterface Document Formats.
Tip
The Download Area action opens the Download Area from where you can download the standard schemas for ebInterface. This allows you to complete the setup quickly and easily.
On the Payment Methods page, you must specify the appropriate payment types and bank accounts to be used for ebInterface.
Fields
ebI Payment Type
Specifies the payment type for ebInterface invoices.
Note
For invoices, a payment type must be specified.
For credit memos, the payment type is ignored and the document is transmitted with No Payment.
ebI Bank Account No.
Specifies a bank account to be used if no bank account is specified in the Company Bank Account Code field on the invoice.
For ebI Payment Type = SEPA Direct Debit the Creditor No. must be specified in the bank account.
For ebI Payment Type = Credit Transfer this information is optional. If no account is specified, the bank details from the Company Information will be used.
The Tax Categories must be specified in the VAT Posting Setup page.
Fields
Tax Category
Specifies the VAT category in connection with electronic document sending.
The values are based on UN/CEFACT code list 5305, version D16B.
For more information, see https://unece.org/fileadmin/DAM/trade/untdid/d16b/tred/tred5305.htm
The following codes are used within the scope of ebInterface:
Code
Description
S
Standard tax rate (20%)
AA
Reduced tax rate (10%, 13%, etc.)
O
Not subject to VAT
D, E, F, G, I, J, K
VAT exempt
Note: K stands for intra-Community supply (IGL)
AE
Reverse charge - reversal of tax liability. The calculation formula is the same as for VAT exempt entries.
Z
Tax rate of 0%
Other codes (A, AB, AC, AD, B, C, H, L, M) are not relevant for Austrian invoices.
Docs / E-Document - ebInterface / Setup Company Information
On the Company Information page, basic information for ebInterface is specified in the ebInterface group.
ebInterface, Fields
ebI Company Headquarters
Specifies the company headquarters that should be communicated to ebInterface.
ebI Commercial Register No.
Specifies the commercial register number that should be communicated to ebInterface.
ebI Commercial Register Court
Specifies the commercial register court that should be communicated to ebInterface.
ebI Email
Specifies the Email address to which ebInterface should send the final acceptance (success) or rejection (error) of a document.
ebI Phone No.
Specifies the phone number for any further queries from ebInterface.
ebI Contact Person
Specifies the contact person for any further queries from ebInterface.
Payments, Fields
The fields Bank Name>, SWIFT Code and IBAN in the Payments group are used by default for Credit Transfers if no other bank account is specified in the Payment Method.
For more information, see Setup, Payment Methods.
E-Document - ebInterface extends Microsoft Business Central 365 e-documents with the ebInterface document format.
For more information, see [Microsoft Learn] Business Central - E-documents overview
The first step to configure electronic documents (e-documents) is to set up the E-Documents Service for e-document communication.
To do this, create a new service and fill in the fields as follows:
Fields
Only the following fields are relevant for ebInterface:
Code
Specifies a code for the service.
Description
Specifies a description for the service.
Document Format
Select the ebInterface option here.
Service Integration
Select the ebInterface option here.
Note
If no integration is selected here, only the XML file for ebInterface will be created later in the e-document. However, the file will not be sent to ebInterface automatically.
Via the Configure documents to export action, you can specify which document types are to be forwarded to ebInterface.
The following document types are supported by ebInterface:
Sales Invoice
Sales Credit Memo
Service Invoice
Service Credit Memo
Check the settings. If you want to exclude certain document types from ebInterface, remove the corresponding entry.
The ebInterface Connection Setup page is used to set up the connection with the ebInterface service. As soon as Environment, Username and Password are specified, the action Check Connection can be used to check whether the ebInterface service is reachable and a connection with the stored settings is possible.
General, Fields
ebInterface Environment
Specifies whether the ebInterface production environment or the ebInterface test environment should be used.
Real Data Permission
Indicates whether data may be sent from the current Business Central environment to the ebInterface production environment. This additional security level prevents test data from being accidentally interpreted as real data. Click on the field to manage the Permissions.
For more information, see Setup, E-Documents, Real Data Permissions.
Username
Specifies the Username for the ebInterface service.
Specifies the Password for the ebInterface service.
Timeout (Milliseconds)
Specifies the length of time in milliseconds that the service is allowed to use, before aborting with an error. If you don't set a duration, then a default value is used. The default value is currently 100000 ms (100 seconds).
History, Fields
Delete Service Log Date Calculation
Specifies the time period for deleting service log entries. If the field is empty, the period is assumed to be 1M (1 month).
For more information, see Archive, ebInterface Service Log.
Auto. Delete Service Log
Specifies whether to automatically delete all service log entries older than the period specified in the Delete Service Log Date Calculation field when creating new entries.
Actions
Check Connection
Checks if the ebInterface service can be reached and a connection with the stored settings is possible.
View or set up the Real Data Permissions of the Extension. This additional security level prevents test data from being accidentally interpreted as real data.
For more information, see Setup, E-Documents, Real Data Permissions.
Docs / E-Document - ebInterface / Setup / E-Documents Real Data Permissions
Real Data Permissions add an additional level of security to actions and processes. This is to prevent test data from being accidentally interpreted as real data. Particularly critical actions and processes (e.g. sending data to an external service) can therefore only be executed if a real data permission has been granted for the current environment.
Practical example
You create a new test database in an on-premises environment by copying the real database, which contains the fully set up fiskaltrust extension. The service of the fiskaltrust extension has the function to sign documents that are subject to the cash register obligation and to protect them against manipulation. Without an additional security level, data from the test database would also be forwarded to fiskaltrust, where it would be interpreted as real data and reported to the tax office. However, this is prevented by the real data permissions function.
Manage Real Data Permissions
The real data permissions of an extension can be viewed or managed via the setup page of the extension in the system area. In the setup of the real data permissions, an environment is defined by the company name, the database name and the server name.
Fields
Company Name
Specifies the company name of the permitted environment.
Database Name
Specifies the database name of the permitted environment.
Server Name
Specifies the server name of the permitted environment.
Current Environment
Specifies whether the permitted environment is the current environment.
Date and Time
Specifies the date and time when the environment was permitted.
User ID
Specifies the ID of the user who permitted the environment.
User Name
Specifies the name of the User ID.
Actions
Permit Current Environment
Grants a real data permission for the current environment.
Warning
Do not permit your current environment unless you are absolutely sure.
Once the environment is permitted, the secured action or process can be called or executed by all users. Although real data permissions can be deleted or removed at any time, this does not undo actions that have already been performed.
A workflow for ebInterface e-documents must be configured for the set up of the ebInterface document sending profile.
First, check whether the necessary E-Document Workflow Templates are available.
Check the templates
Open the Workflow Templates page.
If you cannot find the templates for E-Documents on the page, select the Reset Microsoft Templates action. The E-Document Workflow Templates should then appear.
Set up the workflow
Open the Workflows page.
Click on the New Workflow from Template action and select Send to one service.
Note
The values for the Code and Description fields are suggested by the system. Both can be changed to a different value (e.g., EBINTERFACE) as shown in this example.
The final step in configuring electronic documents (e-documents) for ebInterface is to set up a document sending profile.
To do this, create a new profile and fill in the fields as follows:
Important
The Printer, Email, and Disk fields must be set to No. If you enable any of these options, you will not be able to use the E-Document framework.
Fields
Only the following fields are relevant for ebInterface:
Code
Specifies a code for the profile.
Description
Specifies a description for the profile.
Electronic Document
Select the Extended E-Document Service Flow option here.
A default document sending profile must be available in the system. Therefore, set a different profile as the default if you do not want to automatically create ebInterface documents for all customers for which no profile has been specified.
For more information, see Working with the App, Customers.
Docs / E-Document - ebInterface / Working with the App Customers
On the Customer Card, you must specify the corresponding Document Sending Profile and the ebI fields so that e-documents will be created and sent to ebInterface for the customer.
Fields
Document Sending Profile
If you have set up multiple document sending profiles, or if the document sending profile for ebInterface is not defined as the default profile, you must specify here which profile should be used for the customer.
ebInterface e-documents are only created and sent to ebInterface for the customer if the corresponding document sending profile has been specified.
For more information, see Setup, E-Documents, Document Sending Profiles.
ebI Document Format
Specifies the rules according to which the customer's sales and service documents are to be created when they are forwarded to ebInterface.
For more information, see Setup, ebInterface Document Formats.
ebI Order Reference Prefix
Specifies a fixed prefix for determining the ebI Order Reference in the documents.
For more information, see Working with the App, Documents.
ebI Order Reference Suffix
Specifies a default value for the field in the documents or the determination of the ebI Order Reference in the documents.
For more information, see Working with the App, Documents.
Docs / E-Document - ebInterface / Working with the App Documents
Sales documents and service documents are created, posted and printed as before. The Document Sending Profile specified for the Bill-to Customer determines whether or not an ebInterface e-document is created during posting.
For more information, see [Microsoft Learn] Business Central - Use e-documents in the sales process
Fields
The following fields are available in the Order, Invoice and Credit Memo in Sales and Service.
Displays whether a fixed prefix is specified for the Bill-to Customer.
For more information, see Working with the App, Customers.
ebI Order Reference Suffix
Specifies a reference that, together with any prefix that may be present, is to be used as the order reference.
ebI Order No.
Specifies an order number to be used as the order reference.
ebI Order Reference
Displays the order reference for ebInterface. The reference is either an order number or a combination of prefix and suffix.
The order reference is the reference assigned by the invoice recipient (or possibly by the purchaser) from the associated order. The reference is used to route the invoice to the invoice recipient.
Lines, Fields
ebI Order Position No.
Specifies the reference assigned by the invoice recipient (or possibly by the purchaser) from the associated order position. If the receiver is the federal government and the order reference is an order number (10 digits numeric) an appropriate order position number must be specified for each line.
Unit of Measure Code
Sofern das XML-Schema nicht anders eingerichtet ist, wird die an ebInterface übertragene Einheit wie folgt ermittelt:
If no Unit of Measure Code is specified, the value N/A is transferred.
If a value is stored in the International Standard Code field for the Unit of Measure, this value is transferred.
Otherwise, the Unit of Measure Code is transferred.
Determining the Order Reference in the documents
The ebI Order Reference field in the documents is determined as follows:
If an ebI Order No. is specified in the document:
Order Reference = ebI Order No.
If no ebI Order No. is specified in the document, the type of Invoice Recipient in the ebI Document Format of the Bill-to Customer determines how the order reference is determined.
Federal Government:
Order Reference = ebI Order Reference Prefix (from the customer) + : + ebI Order Reference Suffix (from the document)
Note
The colon is automatically added if prefix and suffix are specified.
Other Invoice Recipients:
Order Reference = ebI Order Reference Prefix (from the customer) + ebI Order Reference Suffix (from the document)
If the XML Posting Preview field is set in the ebInterface document format of the customer, an entry for previewing the XML file is added to the posting preview.
Click on the No. of entries field or on the Show Related Entries action to display the preview.
Docs / E-Document - ebInterface / Working with the App E-Documents
View detailed information about what has been sent to and returned from the service. The information can be useful for technical support.
Delete entries older than...
Deletes log entries that are older than the period specified in the Delete Log Entries Date Calculation field in the ebInterface Connection Setup.
For more information, see Setup, E-Documents, ebInterface Connection Setup.
Delete all entries
Deletes all log entries.
Docs / E-Document - ebInterface / Information for Developers Add Attachments
If the Add Attachments field is activated in the ebInterface Document Format, a PDF file of the document based on the Report Selection is created by default and sent to ebInterface in addition to the XML file.
For more information, see Setup, ebInterface Document Formats.
This logic can be changed via individual programming, and additional files can also be added.
The following events are available in the codeunit "NVXEB Functions" for this purpose.
[IntegrationEvent(false, false)]
local procedure OnBeforeAddAttachments(SourceDocumentHeader: RecordRef; var AttachmentTempBlobList: Codeunit "Temp Blob List"; var AttachmentFileNameList: List of [Text]; var IsHandled: Boolean)
begin
end;
[IntegrationEvent(false, false)]
local procedure OnAfterAddAttachments(SourceDocumentHeader: RecordRef; var AttachmentTempBlobList: Codeunit "Temp Blob List"; var AttachmentFileNameList: List of [Text])
begin
end;
Docs / E-Document - ebInterface / Information for Developers Event Request
If you're building your own app and need something specific from us, like an event, you can help improve the general extensibility of our apps. We'll have a look at your request, and if we can we'll implement it asap. If we can't we'll let you know and briefly explain why not. When that happens, don't be discouraged. Go back to the drawing board, see if you can work it out, and then come back and submit another request.
The NAVAX License Management page (in older versions "NAVAX License Overview" or "NCEX License Overview") displays the current license status of the NAVAX extensions.
Fields
Name
Specifies the name of the Extension.
License Status
Specifies the current license status of the Extension.
Serial No.
Specifies the serial number of the Extension.
Version
Specifies the currently installed version of the Extension.
Trial Version
A NAVAX extension can be tested or used free of charge for 30 days after installation. After that, the extension can only be used with a valid license.
Request License
The license can be requested or checked via the Current Status action. This opens a new page.
The following example shows the NAVAX extension Excel Report Builder.
Fill in the fields in the page and then click Send License Request.
Please note that the licensing process may take some time.
In the next few days you will receive an email with further information.
Note
For licensing, calling the online help and performing some actions, access to https://www.navax.app must be granted.
Public IP from www.navax.app for setting firewall access: 94.136.22.236, Port: TCP/443
Checking the connection to https://www.navax.app using PS: Test-NetConnection navax.app -port 443 (PS must be performed with the M-Tier service user)
CRL Servers In addition, the following CRL Servers must also be accessible for the certificate check: https://certificates.godaddy.com/* http://crl.godaddy.com/* or their IP: 192.124.249.36
Activate/Update License
As soon as the licensing has been completed, you will receive an email and the license can be activated via the Update License action.
The license is company independent. So it does not matter in which company the action is called.
Note
The licence must be updated once a year via the Update License action.
The update is only possible or necessary within the last 30 days before the license expires, or afterwards. Within the last 30 days before the license expires, notes are displayed.
If the Automatic License Renewal is enabled, the Update License action is called automatically before the license expires. Note that the setting is only active after the license has been activated via the action.
This action can be used to open the Microsoft AppSource ratings page for the extension.
We would be very happy if you submit your rating and let us know about your experience with the Extension.
The following Granules are required for an On-Premises installation:
70714610 NAVAX E-Document - ebInterface
1010860 NAVAX Extension Base
External Addresses
https://www.navax.app
For licensing, calling the online help and performing some actions, access to https://www.navax.app must be granted.
Public IP from www.navax.app for setting firewall access: 94.136.22.236, Port: TCP/443
Checking the connection to https://www.navax.app using PS: Test-NetConnection navax.app -port 443 (PS must be performed with the M-Tier service user)
CRL Servers In addition, the following CRL Servers must also be accessible for the certificate check: https://certificates.godaddy.com/* http://crl.godaddy.com/* or their IP: 192.124.249.36
E-Document - ebInterface
The following document types are supported by ebInterface:
If you cannot find the templates for E-Documents on the page, select the Reset Microsoft Templates action. The E-Document Workflow Templates should then appear.
For more information, see [Microsoft Learn] Business Central - Set up e-documents
Click on the No. of entries field or on the Show Related Entries action to display the preview.
Fill in the fields in the page and then click Send License Request.
Please note that the licensing process may take some time.
In the next few days you will receive an email with further information.
