zugferd / quba-viewer Goto Github PK
View Code? Open in Web Editor NEWQuba is a viewer for electronic invoices
License: Apache License 2.0
Quba is a viewer for electronic invoices
License: Apache License 2.0
Quba Release 1.4.0 startet nicht auf M1 MacBook Pro mit MacOS 14.5.
Die Fehlermeldung lautet:
"„Quba“ ist beschädigt und kann nicht geöffnet werden."
Die Version zu #23 (https://quba-viewer.org/files/issue23_quba_intel.dmg) funktioniert jedoch.
Some people, like Eileen and Jonas (Linkedin) have requested a mac version
in factur-x invoices and order-x it may be neccessary to save the embedded xml file
so that StandardBusinessDocument does not always have to be removed manually to display a peppol file
Large PDF attachments cause an error so that invoices can't be opened in the viewer.
Karam reported that the display XML shows a black area like this
when he tries to visualize an official zf 2.0 sample.
zugferd_2p0_EXTENDED_Warenrechnung.pdf
Maybe this is due to the fact that the filename is zugferd-invoice.xml not factur-x.xml?
I have set up Quba as a stadard application for XML to make it easier to work with X-invoices. If you open the first file with Quba everything works fine. If you then open the second file and Quba is still open with the first, then the second file does not open. It seems that Windows tries to open Quba a second time, but closes it immediately. This is also the case when Quba is open without an open file. Once Quba is already started, no other file can be opened directly.
Is it possible to define Quba so that it can be started multiple times, or within Quba also a second tab is opened when a file is opened directly from Windows.
Hey,
It would be helpful if quba would provide a view where every invoice positions are listed as they will be on a PDF invoice.
I've seen, that itplr-kosit provides such a template, but I was not able to add it to qoba.
https://github.com/itplr-kosit/xrechnung-visualization/blob/master/src/xsl/xr-pdf.xsl
I get transformation errors:
Transformation failure: Error XTDE0044
No source input supplied for apply-templates invocation
and errors at runtime
Transformation failure: Error FODF1310 at xr-content.xsl#201
Invalid picture: mantissa contains no digits
We need to check manually if the delivered articles match with the positions on the invoice. For that case a table-like view is much better than the box view.
Can somebody look at this or help me with the errors above?
The app shows a dialog with
“Quba.app” is damaged and can’t be opened. You should move it to the Bin.
Software:
System Software Overview:
System Version: macOS 13.3.1 (22E261)
Kernel Version: Darwin 22.4.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Computer Name: Tobias-MBP-14
User Name: Tobias Anhalt (tobiasanhalt)
Secure Virtual Memory: Enabled
System Integrity Protection: Disabled
Time since boot: 4 minutes, 37 seconds
Hardware:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: Mac14,9
Model Number: MPHH3ZE/A
Chip: Apple M2 Pro
Total Number of Cores: 10 (6 performance and 4 efficiency)
Memory: 16 GB
System Firmware Version: 8422.100.650
OS Loader Version: 8422.100.650
Serial Number (system): FWYPNYKVDP
Hardware UUID: 580133E3-C9DB-52C0-B311-876C804521EE
Provisioning UDID: 00006020-001C51A01E6B401E
Activation Lock Status: Disabled
"File format not recognized" for UBL-CreditNote.
I was not able to open:
when viewing a FX one sometimes needs to reduce or increase the pdf part of the screen but thats currently fixed to always 50%
after valdidation the report could be shown
When a invoice file is dropped on the quba window, it should load it
I get a validation error.
But no explanation why the file is invalid.
The XML data itself validates.
And according to https://erechnungsvalidator.service-bw.de/ it's also valid
The PDF is in the format PDF/A-3B.
How can I get details about the validation error?
Typecodes
default: invoice(=id380)
381 Gutschrift/Credit note
384 Stornorechnung/Corrected invoice
389 kaufmännische Gutschrift/Credit note
220 Bestellung/Order
231 Auftragsbestätigung/Order response
Could you add the possibility to open a file from command line (or File > Open...) ?
Quba myfile.xml
Thanks. Regards. Michael
There are several standards (e.g. WAI WCAG) and several tools to check compliance (e.g. the lighthouse plugin for Chrome or https://wave.webaim.org/. To simulate one might turn to text mode browsers like w3m (available for windows e.g. in the https://www.cygwin.com/ context), open-source (https://nvda.bhvd.de/) or other free (e.g. Windows Narrator, in german windows just search for "Sprachausgabe") screenreaders.
The blind person I asked was a "digital native" but nevertheless never got along very well with NVDA, mentioned that recognized vision impaired people in Germany would most likely get subsidiaries to a commercial screenreader (like the 1000$ software called JAWS, which he recommended) and otherwise recommended Windows Narrator.
We're using a open-source project (https://github.com/itplr-kosit/xrechnung-visualization) to generate the HTML for the display of our electronic invoices. The generated HTML is "100%" WCAG and electron forwards the accessibility for screenreaders already available in Chrome but it turns out there nevertheless is still an issue:
All "sections" are described but for screenreaders, the whole document looks like only one section. Which means that NVDA reads everything which takes very long, and Narrator basically reads nothing, unless prompted very hard.
Visually one immediately recognizes multiple sections, Recipient information ("Informationen zum Käufer") seller information ("Informationen zum Verkäufer") and data ("Rechnungsdaten") in the screenshot
The patch seems to be trivial, most likely it would suffice to add a tabindex="0" attribute to all visual sections, which also makes it much easier to navigate using keyboard (i.e. cursor keys and tab). We just need somebody to implement that on the Kosit XSLTs, and PR us and them. We would very much like to help but we won't do it on our own initiative.
Naser reported: Basisquantity is 10 in the attached invoice but that's never shown to the user
Testrechnung.txt
Hi,
Would it be possible to have items displayed as a simple list/table ?
Thanks,
Regards,
Michael
it would be nice if the user could search in the invoice or at least on the page e.g. using CTRL+F
We build the Mac version on a M1, i.e. on a ARM platform. Apparently this does not give us universal binaries so the >70% of intel users cant start Quba? (What error message do they get?)
Is somebody affected and can someone assist, e.g. by helping us build on a intel mac or pointing to a good build service (which works, https://github.com/electron-userland/electron-build-service seems to be down) ?
PS: I attributed previous issues on the mac (#14, #19) mainly to the old version of electron we used, which should be fixed now. If I was wrong and it was in fact this issues pls let me know.
quba_viewer-1.2.0.AppImage doesn't run on Ubuntu 22.04LTS, quits with the first line (xxx not found)
also can't install from github-repo, too many dependencies can't be resolved
I give up.
Is there any linux-release?
I've been trying to follow manual electron-build instructions (npm install & npm run start) trying to get it working.
This is the stack-trace appearing after trying to open a PDF-File from file-dialog. No matter if using npm or yarn for package-management and also it doesn't make any difference trying to prepend "--unhandled-rejections=strict" after yarn or npm command.
Require stack:
- /opt/quba-viewer/main.js
- /opt/quba-viewer/node_modules/electron/dist/resources/default_app.asar/main.js
-
at Module._resolveFilename (internal/modules/cjs/loader.js:972:15)
at Function.n._resolveFilename (electron/js2c/browser_init.js:249:921)
at Module._load (internal/modules/cjs/loader.js:848:27)
at Function.f._load (electron/js2c/asar_bundle.js:5:12633)
at Module.require (internal/modules/cjs/loader.js:1032:19)
at require (internal/modules/cjs/helpers.js:72:18)
at /opt/quba-viewer/main.js:233:38
(node:8951) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:8951) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
e.g. instead of Leitweg-ID it could say Leitweg-ID (BT-10)
currently only the selected language is saved in config. We could use safeStorage for that (menuconfig l.221) and then also store the last username, password, client id and client secret (encrypted) so the user does not have to enter every time. When the app is started and there's a login config the user could even automatically be logged in.
"print" and "validate" should be inactive if e.g. no document is opened at all
Would a Mastodon account for the project be possible?
Instead of codes for attributes like for unit ("H87" for "piece") the actual attribute values ("piece") should be displayed.
The codelists are https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Registry+of+supporting+artefacts+to+implement+EN16931
Maybe this can help
https://github.com/jcthiele/xrechnung-visualization-codelist-resolve
Hi there,
we tried to open the dmg file we downloaded from the homepage on 3 different macOs ventura notebooks. In german it says the file is "damaged".
Are we the only ones?
transform to intermediate format works but in the second step zahlungsdaten should be completely removed and it should not say käufer verkäufer rechnungsdaten gesamtbeträge der rechnung, Aufschlüsselung der Umsatzsteuer auf Ebene der Rechnung but
Empfänger Absender Bestelldaten, Gesamtbeträge der Bestellung, Aufschlüsselung.... der Bestellung
EN16931_Elektron.pdf
shows #ef= before filename and empty window when clicked on Öffnen
unknown why there is a src/transaltion/de.json and a app/locales/de/translation.json
In order to be able to anonymize XML invoices (CII and UBL) I could provide xpaths.
I looked for software like " xml gdpr", " xml obfuscation" or " xml anonymization" or "xml redaction" and tried e.g. Arx (which seems to support only xls), anonimatron (only for DBs) or Amnesia (only CSV).
There seem to be two open source anonymizer projects in the making which may somewhen release something noteworthy and may be fed with xpaths but https://github.com/cdaller/multi_anonymizer seems to require Microsoft Visual Studio and https://github.com/babblequest/XMLAnonymizer is not
Can anonymize, e.g. shuffle (replace number by random number , lowercaps by random lowercaps and uppercase by random uppercase, the following xpaths with quba?
Any BTs no needed/addtionally required?
ID | BT | Desc. | UBL-Path | CII-Path |
---|---|---|---|---|
BT-20 | Payment terms | A textual description of the payment terms that apply to the amount due for payment (Including description of possible penalties). | /Invoice/cac:PaymentTerms/cbc:Note | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:Description |
BT-22 | Invoice note | A textual note that gives unstructured information that is relevant to the Invoice as a whole. | /Invoice/cbc:Note | /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IncludedNote/ram:Content |
BT-27 | Seller name | The full formal name by which the Seller is registered in the national registry of legal entities or as a Taxable person or otherwise trades as a person or persons. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:RegistrationName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Name |
BT-28 | Seller trading name | A name by which the Seller is known, other than Seller name (also known as Business name). | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedLegalOrganization/ram:TradingBusinessName |
BT-30 | Seller legal registration identifier | An identifier issued by an official registrar that identifies the Seller as a legal entity or person. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedLegalOrganization/ram:ID |
BT-31 | Seller VAT identifier | The Seller’s VAT identifier (also known as Seller VAT identification number). | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID |
BT-32 | Seller tax registration identifier | The local identification (defined by the Seller’s address) of the Seller for tax purposes or a reference that enables the Seller to state his registered tax status. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID |
BT-34 | Seller electronic address | Identifies the Seller’s electronic address to which a business document may be delivered. | /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUniversalCommunication/ram:URIID |
BT-35 | Seller address line 1 | The main address line in an address. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:StreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:LineOne |
BT-36 | Seller address line 2 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:AdditionalStreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:LineTwo |
BT-162 | Seller address line 3 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cac:AddressLine/cbc:Line | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:LineThree |
BT-37 | Seller city | The common name of the city, town or village, where the Seller address is located. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:CityName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:CityName |
BT-38 | Seller post code | The identifier for an addressable group of properties according to the relevant postal service. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:PostalZone | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:PostcodeCode |
BT-39 | Seller country subdivision | The subdivision of a country. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:CountrySubentity | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTradeAddress/ram:CountrySubDivisionName |
BT-41 | Seller contact point | A contact point for a legal entity or person. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedTradeContact/ram:PersonName |
BT-42 | Seller contact telephone number | A phone number for the contact point. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedTradeContact/ram:TelephoneUniversalCommunication/ram:CompleteNumber |
BT-43 | Seller contact email address | An e-mail address for the contact point. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedTradeContact/ram:EmailURIUniversalCommunication/ram:URIID |
BT-44 | Buyer name | The full name of the Buyer. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:RegistrationName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:Name |
BT-45 | Buyer trading name | A name by which the Buyer is known, other than Buyer name (also known as Business name). | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyName/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:SpecifiedLegalOrganization/ram:TradingBusinessName |
BT-46 | Buyer identifier | An identifier of the Buyer. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:ID |
BT-47 | Buyer legal registration identifier | An identifier issued by an official registrar that identifies the Buyer as a legal entity or person. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:SpecifiedLegalOrganization/ram:ID |
BT-48 | Buyer VAT identifier | The Buyer’s VAT identifier (also known as Buyer VAT identification number). | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:SpecifiedTaxRegistration/ram:ID |
BT-49 | Buyer electronic address | Identifies the Buyer’s electronic address to which a business document should be delivered. | /Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID |
BT-50 | Buyer address line 1 | The main address line in an address. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:StreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTradeAddress/ram:LineOne |
BT-51 | Buyer address line 2 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:AdditionalStreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTradeAddress/ram:LineTwo |
BT-163 | Buyer address line 3 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cac:AddressLine/cbc:Line | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTradeAddress/ram:LineThree |
BT-52 | Buyer city | The common name of the city, town or village, where the Buyer’s address is located. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:CityName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTradeAddress/ram:CityName |
BT-53 | Buyer post code | The identifier for an addressable group of properties according to the relevant postal service. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:PostalZone | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTradeAddress/ram:PostcodeCode |
BT-56 | Buyer contact point | A contact point for a legal entity or person. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:DefinedTradeContact/ram:PersonName |
BT-57 | Buyer contact telephone number | A phone number for the contact point. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:Telephone | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:DefinedTradeContact/ram:TelephoneUniversalCommunication/ram:CompleteNumber |
BT-58 | Buyer contact email address | An e-mail address for the contact point. | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:ElectronicMail | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:DefinedTradeContact/ram:EmailURIUniversalCommunication/ram:URIID |
BT-59 | Payee name | The name of the Payee. | /Invoice/cac:PayeeParty/cac:PartyName/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:Name |
BT-60 | Payee identifier | An identifier for the Payee. | /Invoice/cac:PayeeParty/cac:PartyIdentification/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:ID |
BT-61 | Payee legal registration identifier | An identifier issued by an official registrar that identifies the Payee as a legal entity or person. | /Invoice/cac:PayeeParty/cac:PartyLegalEntity/cbc:CompanyID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:PayeeTradeParty/ram:SpecifiedLegalOrganization/ram:ID |
BT-62 | Seller tax representative name | The full name of the Seller’s tax representative party. | /Invoice/cac:TaxRepresentativeParty/cac:PartyName/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:Name |
BT-63 | Seller tax representative VAT identifier | The VAT identifier of the Seller’s tax representative party. | /Invoice/cac:TaxRepresentativeParty/cac:PartyTaxScheme/cbc:CompanyID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:SpecifiedTaxRegistration/ram:ID |
BT-64 | Tax representative address line 1 | The main address line in an address. | /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cbc:StreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:PostalTradeAddress/ram:LineOne |
BT-65 | Tax representative address line 2 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cbc:AdditionalStreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:PostalTradeAddress/ram:LineTwo |
BT-164 | Tax representative address line 3 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cac:AddressLine/cbc:Line | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:PostalTradeAddress/ram:LineThree |
BT-66 | Tax representative city | The common name of the city, town or village, where the tax representative address is located. | /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cbc:CityName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:PostalTradeAddress/ram:CityName |
BT-67 | Tax representative post code | The identifier for an addressable group of properties according to the relevant postal service. | /Invoice/cac:TaxRepresentativeParty/cac:PostalAddress/cbc:PostalZone | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTaxRepresentativeTradeParty/ram:PostalTradeAddress/ram:PostcodeCode |
BT-70 | Deliver to party name | The name of the party to which the goods and services are delivered. | /Invoice/cac:Delivery/cac:DeliveryParty/cac:PartyName/cbc:Name/ | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:Name |
BT-71 | Deliver to location identifier | An identifier for the location at which the goods and services are delivered. | /Invoice/cac:Delivery/cac:DeliveryLocation/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:ID |
BT-75 | Deliver to address line 1 | The main address line in an address. | /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:StreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:PostalTradeAddress/ram:LineOne |
BT-76 | Deliver to address line 2 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:AdditionalStreetName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:PostalTradeAddress/ram:LineTwo |
BT-165 | Deliver to address line 3 | An additional address line in an address that can be used to give further details supplementing the main line. | /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cac:AddressLine/cbc:Line | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:PostalTradeAddress/ram:LineThree |
BT-77 | Deliver to city | The common name of the city, town or village, where the deliver to address is located. | /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:CityName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:PostalTradeAddress/ram:CityName |
BT-78 | Deliver to post code | The identifier for an addressable group of properties according to the relevant postal service. | /Invoice/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:PostalZone | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeDelivery/ram:ShipToTradeParty/ram:PostalTradeAddress/ram:PostcodeCode |
BT-84 | Payment account identifier | A unique identifier of the financial payment account, at a payment service provider, to which payment should be made. | /Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeePartyCreditorFinancialAccount/ram:IBANID |
BT-85 | Payment account name | The name of the payment account, at a payment service provider, to which payment should be made. | /Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeePartyCreditorFinancialAccount/ram:AccountName |
BT-86 | Payment service provider identifier | An identifier for the payment service provider where a payment account is located. | /Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount/cac:FinancialInstitutionBranch/cbc:ID | rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayeeSpecifiedCreditorFinancialInstitution/ram:BICID |
BT-87 | Payment card primary account number | The Primary Account Number (PAN) of the card used for payment. | /Invoice/cac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:ApplicableTradeSettlementFinancialCard/ram:ID |
BT-88 | Payment card holder name | The name of the payment card holder. | /Invoice/cac:PaymentMeans/cac:CardAccount/cbc:HolderName | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:ApplicableTradeSettlementFinancialCard/ram:CardholderName |
BT-89 | Mandate reference identifier | Unique identifier assigned by the Payee for referencing the direct debit mandate. | /Invoice/cac:PaymentMeans/cac:PaymentMandate/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:DirectDebitMandateID |
BT-90 | Bank assigned creditor identifier | Unique banking reference identifier of the Payee or Seller assigned by the Payee or Seller bank. | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:CreditorReferenceID |
BT-91 | Debited account identifier | The account to be debited by the direct debit. | /Invoice/cac:PaymentMeans/cac:PaymentMandate/cac:PayerFinancialAccount/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:PayerPartyDebtorFinancialAccount/ram:IBANID |
BT-128 | Invoice line object identifier | An identifier for an object on which the invoice line is based, given by the Seller. | /Invoice/cac:InvoiceLine/cac:DocumentReference/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeSettlement/ram:AdditionalReferencedDocument/ram:IssuerAssignedID |
BT-153 | Item name | A name for an item. | /Invoice/cac:InvoiceLine/cac:Item/cbc:Name | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:Name |
BT-154 | Item description | A description for an item. | /Invoice/cac:InvoiceLine/cac:Item/cbc:Description | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:Description |
BT-155 | Item Seller’s identifier | An identifier, assigned by the Seller, for the item. | /Invoice/cac:InvoiceLine/cac:Item/cac:SellersItemIdentification/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:SellerAssignedID |
BT-156 | Item Buyer’s identifier | An identifier, assigned by the Buyer, for the item. | /Invoice/cac:InvoiceLine/cac:Item/cac:BuyersItemIdentification/cbc:ID | /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedTradeProduct/ram:BuyerAssignedID |
Is there any news regarding a JS viewer/ component?
If a XRechnung has embedded files, like this one quba will show a open-link and the attachment but then the close icon is missing in the popup->there is no possibility to close the attachment view
In FX extended one line may have multiple charges like in the example "warenrechnung". Loading one of these files result in an error.
if no doc is open and only the "startpage" with the link to the examples displayed dropping a file onto the quba window wont open it
Importing a xml File with:
EN16931-ID: BT-72 Actual delivery date
The part of the xml Code:
<ram:ApplicableHeaderTradeDelivery>
<ram:ActualDeliverySupplyChainEvent>
<ram:OccurrenceDateTime>
<udt:DateTimeString format="102">20240607</udt:DateTimeString>
</ram:OccurrenceDateTime>
</ram:ActualDeliverySupplyChainEvent>
</ram:ApplicableHeaderTradeDelivery>
But QUBA Viewer is not displaying the actual delivery date.
currently thats ignored
I am using the Mac version 1.0.0.
If I am opening an new xRechnung document in quba viewer, the app still shows the old data / invoice.
The only way to prevent this from happing is closing the app and restarting it for every new document.
When a file is loaded, then changed externally, and loaded again, the old, already displayed version will show twice
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.