Skip to Content

BMD-Schnittstelle

by
Odoo

$ 2769.60

v 18.0 Third Party
This module requires Odoo Enterprise Edition.
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
• Accounting (accountant)
Community Apps Dependencies
Lines of code 11057
Technical Name bmd_standard
LicenseOPL-1
Websitehttps://github.com/OCA/odoo-pim
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
• Accounting (accountant)
Community Apps Dependencies
Lines of code 11057
Technical Name bmd_standard
LicenseOPL-1
Websitehttps://github.com/OCA/odoo-pim

Austrian accounting interface for Odoo

BMD Interface

Export Odoo accounting data in a BMD NTCS compatible structure for Austrian tax consultants, including tax code mapping, partner account logic, OSS branch handling, and voucher handover.

Accounting export Customer invoices, vendor bills, bank entries, and ledger data.
BMD master data Configurable tax codes, booking symbols, and format profiles.
Virtual accounts Debtor and creditor numbers generated per partner.
Voucher files Export accounting data with optional PDF attachments.
BMD Interface app banner

BMD tax code mapping

Common BMD tax codes are installed automatically. Company-specific tax keys can be added and mapped to Odoo taxes when required.

Partner account numbering

Configure the debtor and creditor number length, choose sequences, and recompute generated partner account numbers when needed.

OSS and branches

Maintain country or branch numbers for OSS scenarios and coordinate them with the tax consultant before the BMD import is prepared.

Setup Workflow

The module supports the practical BMD setup steps described in the internal implementation guide.

1

Review BMD codes

Check the installed BMD tax codes and add company-specific mappings.

2

Configure accounts

Set personal account lengths, sequences, and collective accounts.

3

Prepare OSS

Maintain branch numbers, country references, tax rates, and tax accounts.

4

Export monthly data

Transfer invoices, vendor bills, and reconciled bank entries to BMD.

Virtual Partner Accounts

Odoo keeps receivables and payables on collective accounts while open items are identified by partner. For BMD and RZL communication, this module derives debtor and creditor account numbers per partner without requiring duplicate partner records.

  • Manual partner account numbers are supported.
  • Odoo sequences can assign the next debtor or creditor number.
  • Generated values respect the configured account number length.
  • Existing generated values can be recomputed after configuration changes.
Virtual partner account configuration

Export and Handover

Generate BMD files from Odoo for the selected company and period. Monthly handover usually separates customer invoices, vendor bills, and reconciled bank entries with matching information.

  • Export accounting data only with DATA.
  • Export accounting data and voucher PDFs with ATCH.
  • Use only reconciled bank entries for regular handover.
  • Prepare BMD archives with matching short codes such as AR and ER.
BMD file export options

OSS Branch Configuration

For OSS cases, configure country or branch numbers in Odoo and create the corresponding branches, tax rates, and tax accounts in BMD. The numbers should be aligned with the tax consultant before productive use.

  • Country numbers can follow BMD country codes or phone prefixes.
  • All OSS tax rates used in Odoo need matching BMD setup.
  • The UVA country should be set correctly before continuing in BMD.
  • Export one legal entity at a time for predictable BMD imports.
OSS branch and tax setup in BMD

Configuration Screens

BMD tax code mapping in Odoo
BMD tax code mapping on Odoo tax records.
Automatic debtor and creditor number settings
Automatic debtor and creditor number assignment.
Import range for partner accounts
Partner account import ranges for debtors and creditors.
BMD archive configuration
Archive setup for importing voucher PDFs into BMD.

BMD Import References

The module includes official BMD NTCS help PDFs in the module docu/ directory for importing bookings, personal accounts, and general ledger accounts.

BMD interface documentation reference
Interface documentation and import help references.
Multi-company export warning
Multi-company guidance for selecting one legal entity per export.

Maintained by it-fact GmbH

it-fact GmbH specializes in Austrian accounting workflows in Odoo and integrations with BMD, RZL, and DATEV. We can support the accounting setup, export configuration, and handover process with your tax consultant.

Contact

https://it-fact.com
o@it-fact.com
+43 660 84 65 580

Copyright it-fact GmbH. Odoo and the Odoo logo are trademarks of Odoo S.A. 
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.