add own company fields for eRechnung

thgagel

Some fields in eRechnung are specific for my own company. These fields should exist in My Company, so no guesswork is needed to extract this information (which doesnt work at all).

SubTotal version: 1.5.62
Operating system: macOS
Device model: iMac Pro

timo

I don't understand this feature request. For example, I don't know what "fields" you are referring to and what exactly "doesn't work at all". Please explain in more detail.

thgagel

"Dieser Bildschirm ist mit Informationen vorausgefüllt, die aus der Rechnung entnommen wurden, wie z. B. die Adresse des Kunden, sowie mit den Daten, die in den Freitextfeldern auf der Seite 'Mein Unternehmen' eingegeben wurden."
This is not working even if e.g. my IBAN and UStID is on a single line by itself.
My feature request: give all data needed in eRechnung their own entry fields in My Company.

timo

thgagel This is not working even if e.g. my IBAN and UStID is on a single line by itself.

Please give an example (you can send it via mail if it's personal info). It is working for me. Perhaps your data is in a wrong format

thgagel My feature request: give all data needed in eRechnung their own entry fields in My Company.

I am hesitant to do that for multiple reasons. For example, e-invoicing is specific for the EU and most importantly Germany. I don't want SubTotal to be an invoicing app tailored for German companies - it should be useful for companies around the world. I want to keep input fields to a minimum as increasing them makes the PDF layouts more complex and the UI potentially more confusing and overloaded

thgagel

an example is on the way.

these fields do not need to be placed on pdf layouts. they are only needed for e-invoicing. if a user does not need them, they remain empty.
maybe showing them is an option in program settings. if not activated, these fields dont show up at all.

timo

thgagel Thanks for your example via mail. The VAT ID was in a wrong format (contained spaces) and was therefore not recognized correctly. IBAN contained a "non-breaking" space instead of a normal space - with the next version, the detection will be adjusted so that IBANs with non-breaking spaces will also recognized. I also was able to improve the phone number recognition thanks to your help.