Sales Pack - XInvoice

[yuri]

Here's the tutorial on how to add custom fields: https://forum.espocrm.com/forum/deve...-in-sales-pack

[Nina]

Hey,

We delivered the first XRechnung invoices yesterday!
Thanks to the tutorial!

Now we've received the first feedback - we need to add more fields. The feedback came from several customers :/

We were asked for BT-19 (Buyer accounting reference) - ‘Cost centre’ - "Kostenstelle"

Also options for the following fields:

- Specialised service (specialist service) "Fachdienst"
- Product (I don't know what is meant here, I got a numerical value)
- Order number (I think BT-13)
- Is there a free field? e.g. for remarks?

Are these still provided or is there a copy template to implement them?

Thank you very much!

Nina

[yuri]

Hi Nina,

Buyer References is already there. You might need to add it to the Invoice's Detail layout.




BT-13 is not available out of the box. You can use a custom field to store the Purchase Order Reference. The library has "setPurchaseOrderReference" method.

> Is there a free field? e.g. for remarks?

Not yet. I think you can use a custom field and the "addNote" method.

> Product (I don't know what is meant here, I got a numerical value)

I don't know what it is.

[Nina]

Hey,

Thanks for your reply.
I have swapped the Electronic Address Identifier with the Buyer Reference :/....... sorry...

That's the standard from hell :/

Thank you very much! I'll have a look at the other fields.
Hopefully you'll understand it all at some point

[yuri]

In v2.6.6 added Purchase Order Reference and Note fields. These fields are mapped to E-Invoice.

[Nina]

Hey,

I would like to know how to change the invoice type

There are the following types ( <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>:

TypeCode: 326 - Partial invoice (actually: Partial final invoice)
TypeCode: 380 - Invoice (current standard)
TypeCode: 381 - Credit note
TypeCode: 384 - Invoice correction

Is there a possibility?

We have many “partial invoices” - we previously split the order.
In the same way as our cancellation now has to work differently.

How could this be set up?

Thank you!

[yuri]

Hi Nina,

Use the tutorial to create a custom preparator. Then, in your custom preparator class you can call $eInvoice->setType(381); Where 381 is an example code.

[yuri]

I have already worked out the data design for payment means. The way it will be coherent with an extensible providers feature. Will be available in a future version.

[hom]

Hello Yuri,

the eInvoice in Espo works quite well with some custom adjustments. Thanks for that!

However, it turns out that a small adjustment would be necessary, which cannot be solved sensibly with a custom field. It concerns the description of an invoice item (BT-154). This is not included in the eInvoice, but already exists as a standard field in the invoice.

Would it be possible to include the existing item description field as an item in the eInvoice?
The field would have the following assignment:
BT-154 Item description - Item description

This field is not a mandatory field, but the item description is almost always necessary for customers to be able to check the invoice.

Please let me know if it's possible?

HOM

[yuri]

Hi, I'll look into.

[hom]

Hi Yuri, thanks for adding the notes to the eInvoice. That helps a lot!

[yuri]

In the future version there will be E-Invoice support for:

• payment Credit Transfer
• SEPA Direct Debit mandates
• taxable shipping charges

[yuri]

Hi everyone,

I was thinking about integrating with some PEPPOL access point service. If anybody has some thoughts on this subject, please share.

[Provata]

Yuri,

have a look when it becomes mandatory for which size of company - and check against your customer base.

We are a small SME - "end of 2027" for us.