Sales Pack - XInvoice

[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.

[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.

[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]

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

[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]

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,

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]

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

[hom]

Hello Yuri,

if a global solution for payment processing is not possible, instructions for creating and customizing custom fields would be very helpful.
Many thanks in advance.

[Nina]

Thank you Yuri!

You can't see the wood for the trees...
... it was very obvious.

[yuri]

Hi Nina,

We have a built-in Due Date field in the Invoice entity type. You need to use it instead of the custom field. You may need to add it to the Detail layout.

[yuri]

I think I'll write a tutorial how to add use custom fields in e-invoices.

After some research and analysis I came to a conclusion that the payment terms design we have discussed above will not suit well if we add the Payments feature to Sales Pack in the future.

[Nina]

HI!

As we should already be sending out the first e-invoices... :/
I wanted to take care of the settings in ESPO today.


Maybe I don't have a good overview yet, but I still get the following error messages and can't find where I can currently make the entries.


Invalid invoice.

Failed rule ID: BR-CO-25

In case the Amount due for payment (BT-115) is positive, either the Payment due date (BT-9) or the Payment terms (BT-20) shall be present.


When we started using the sales pack, we actually created fields for ‘Payment due date’. But it doesn't know how to use them now.

Unfortunately, this is the first time I've dealt with e-invoicing. Unfortunately, I haven't found anything in the documentation at the moment.

Or has this not yet been implemented?
I can't quite make heads or tails of the thread here ;D

Maybe you can give me a hint where I can find the settings

[hom]

Hi Yuri,

I share your view that stability should come before rapid implementation. My question was more about whether implementation can be expected before the end of the year? Because this is the only way to meet the obligation to use e- invoicing, which comes into force at the beginning of next year.

[yuri]

I don't know yet. It's risky to hurry with implementation