Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specification BUG in EN16931 : BG-3 PRECEDING INVOICE REFERENCE #19

Open
homebeaver opened this issue Jan 28, 2021 · 3 comments
Open

Specification BUG in EN16931 : BG-3 PRECEDING INVOICE REFERENCE #19

homebeaver opened this issue Jan 28, 2021 · 3 comments
Labels
spec bug Bug outside this project. Need a workaround

Comments

@homebeaver
Copy link
Contributor

  • BG-3 hat die Kardinalität 0..n : in CII kann aber nur 0..1 abgebildet werden
  • in UBL ist 0..n möglich

Dieser Fehler wurde bereits gemeldet. Siehe ConnectingEurope/eInvoicing-EN16931#207 : Use of BG-3 in CrossIndustryInvoice

@homebeaver homebeaver added the spec bug Bug outside this project. Need a workaround label Jan 28, 2021
@homebeaver
Copy link
Contributor Author

Als Konsequenz daraus werde ich bei CII eine Warnung einbauen

homebeaver added a commit that referenced this issue Jan 29, 2021
WARNUNG: You try to add a second Preceding Invoice. In CII there is only one BG-3. NOT IMPEMENTED due to specification.
@homebeaver
Copy link
Contributor Author

homebeaver commented Jan 29, 2021

für CII gibt es keine Beispiele, daher habe ich den ReadmeTest erweitert:

WARNUNG: You try to add a second Preceding Invoice. In CII there is only one BG-3. NOT IMPEMENTED due to specification.

/* ubl-tc434-example5.xml :

    <cac:BillingReference>
        <cac:InvoiceDocumentReference>
            <cbc:ID>TOSL109</cbc:ID>
            <cbc:IssueDate>2013-03-10</cbc:IssueDate>
        </cac:InvoiceDocumentReference>
    </cac:BillingReference>

*/

homebeaver added a commit that referenced this issue Jan 29, 2021
@homebeaver
Copy link
Contributor Author

mit 9f26f1b ist das ticket fertiggestellt. Es bleibt aber offen bis das spec bug gelöst ist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec bug Bug outside this project. Need a workaround
Projects
None yet
Development

No branches or pull requests

1 participant