Structural Billing and Tax Compliance Issues in QloApps Marketplace for EU

bluemoon288

I would like to outline a structural issue in the current QloApps Marketplace setup that affects tax compliance in the EU, especially in Germany. The problem becomes relevant when multiple independent hotels operate as sellers within one QloApps Marketplace installation.

Centralized invoicing is not legally compliant for EU hotel operations
When a guest completes an online payment, QloApps automatically generates an invoice in the name of the Marketplace Admin.
However, in the EU (and specifically Germany):

The hotel is the actual service provider.
The hotel must issue its own invoice with its own tax ID, address, VAT rate, and invoice number.
A platform operator (Admin) cannot legally issue invoices for hotel accommodation services unless acting as a travel operator under a completely different tax regime.
This means the current QloApps invoice is not legally valid for hotel accommodation in the EU.

Hotels require their own independent back office
To comply with EU tax law, each hotel needs:

its own invoicing profile
its own VAT configuration
its own invoice numbering
its own payment methods
its own accounting records
The existing seller dashboard is not sufficient because it does not allow hotels to operate as independent taxable entities.

Required billing model: two separate invoices
For EU compliance, the system must support:

Hotel → Guest: legally valid hotel invoice
Admin → Hotel: monthly commission invoice (or vice versa, depending on the business model)
This separation is mandatory.
The current system only generates one invoice (Admin → Guest), which is not correct.

Payment flow requirements
We do not need automatic split payments.
Instead, we need:

Hotels to receive payments directly for their own bookings
The Marketplace Admin to invoice hotels monthly for commissions
Marketplace bookings to be commission‑based
Direct hotel bookings (outside the marketplace) to remain commission‑free
This is the standard model for hotel marketplaces in the EU.

Summary of the core issue
The current QloApps Marketplace architecture assumes a single taxable entity (the Admin).
In the EU, each hotel is a separate taxable entity and must issue its own invoices.
Therefore, the system needs a way to:

assign independent invoicing and tax profiles to each hotel
generate hotel‑specific invoices for guests
generate monthly commission invoices between Admin and hotels
separate payment flows per hotel
Without these features, QloApps Marketplace cannot be used in a legally compliant way for multi‑hotel operations in Germany or most EU countries.