Skip to content

Fixes issue #800.#801

Open
Dirksche wants to merge 1 commit into
stephanstapel:masterfrom
Dirksche:issue/lineTotalAmountNotAutomaticallyCalculatedWhenUsingUBL_800
Open

Fixes issue #800.#801
Dirksche wants to merge 1 commit into
stephanstapel:masterfrom
Dirksche:issue/lineTotalAmountNotAutomaticallyCalculatedWhenUsingUBL_800

Conversation

@Dirksche

@Dirksche Dirksche commented Sep 9, 2025

Copy link
Copy Markdown
Contributor

When writing in UBL format and lineTotalAmount was omitted in AddTradeLineItem , it caused a validation error, because LineExtensionAmount was missing. We now calculate it in the same way as for the CII format.

When writing in UBL format and `lineTotalAmount` was omitted in `AddTradeLineItem `, it caused a validation error, because `LineExtensionAmount` was missing.
We now calculate it in the same way as for the CII format.

(cherry picked from commit be88067)
@stephanstapel

Copy link
Copy Markdown
Owner

@Dirksche, please see a new discussion on this here:
#836

@Dirksche

Dirksche commented Nov 25, 2025

Copy link
Copy Markdown
Contributor Author

@stephanstapel It's not only about automatic calculation (of omitted parameters) or not, it's also about consistency.
Currently it is automatically calculated (when lineTotalAmount was omitted in AddTradeLineItem()) for CII, but not for UBL.

Ideally, if someone has written code which generates a valid e-invoice in one format (CII or UBL) and they just change the call of the Save() function to save it in the other format, it should still generate a valid e-invoice with the same information.

@sonarqubecloud

sonarqubecloud Bot commented Feb 9, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants