Sales Pack - XInvoice

[yuri]

The question is not about payments but payment means. E.g. credit card, cash, etc.

[dodom2]

We often accept multiple payments per invoice. Its pretty common in the states.

[yuri]

If anybody have thoughts and ideas regarding payment means, how we could better implement it, please share.

As I understand, in Germany an invoice can have only one payment mean. Would we need multiple ones? As the standard allows multiple payment means per invoice. Maybe in some countries it's a common practice to have multiple payment means?

[yuri]

I don't have an example.

Bind implementation https://docs.espocrm.com/development/di/#binding

Interface:

Espo\Modules\Sales\Tools\Invoice\EInvoice\Preparator

To be bound to a custom implementation.

The default implementation:

Espo\Modules\Sales\Tools\Invoice\EInvoice\DefaultPreparator

To be called inside the custom implementation.

This should be trivial for programmers who have experience in OOP.

This is not an official guideline. No guarantee that the implementation will not change in the future.

[Bernhard]

Hi Yuri,

I was busy for a while and just saw yesterday how much you have implemented. Great job!

[hom]

Hello Yuri,

do you have an example or instructions on how and where the preparator interface can be addressed?

[hom]

Thank you very much, that sounds excellent!

[yuri]

Added a preparator interface. Developers can add additional items to an E-Invoice from custom fields and related entities.

[yuri]

Thanks for input.

I've added the standard ProfileID value for XRechnung in the new version.

The online validator for 3.0.1 does not catch when the ProfileID is missing for some reason.

Regarding Payment Instruction. There's no the Payments functionality in Sales Pack at the moment. It was planned for the future. Before we have it implemented, I'm not sure how we could make it possible for users to specify values for an E-Invoice.

[hom]

Hello Yuri,

Firstly, I would like to thank you for the great job you did implementing e-invoice!
It must have been a lot of work, especially as there are so many different standards.

I installed the latest sales pack 2.4.1 and made all possible adjustments so that I could create an e-invoice according to the XRechnung standard. The implemented validator does not show any errors either, but there are fields that are additionally required and I don't know whether I simply haven't found them or whether they are not (yet) implemented.

The following is missing for me:

1) With the XRechnung Standard 3.0.1/3.0.2 the following field is required: ProfileID. The field references the BT-23 requirement, where a static value is stored according to which rules or standards the invoice was created. For Germany (as an example), the value "urn:fdceppol.eu:2017oacc:billing:01:1.0" would be entered. As this may differ in other countries, it would certainly be helpful to store the ProfileID as an additional field in the ‘Seller Information’. If there is no general list, at least a free field would be useful.

2) It is also necessary to store the payment information. This is to be used as section ‘PAYMENT INSTRUCTIONS’ BG-16 and contains information on how the payment should be made. I am not quite sure where this information is to be stored in the ESPO or whether this setting has not already existed for a long time and I have just not found it.
The PAYMENT INSTRUCTIONS have the following attributes
- Payment means type code : Code [1]
- Payment means text : Text [0..1]
- Remittance information : Text [0..1]
- CREDIT TRANSFER : CREDIT TRANSFER [0..*]
- PAYMENT CARD INFORMATION : PAYMENT CARD INFORMATION [0..1]
- DIRECT DEBIT : DIRECT DEBIT [0..1]

Please let me know if I can make the settings myself or if they already exist.
I am happy to continue supporting the process and thank you again for the great work!

[yuri]

Yet another problem to solve is generating CII. Currently we only have UBL implementation.

[item]

i have "like" on github.. maybe the PR will be merged

[user_4711]

thank you! i'll keep an eye on it, too.

[ThomasB]

sounds great, but i only found this discussion about PDF/X PDF/A Support in dompdf https://github.com/dompdf/dompdf/discussions/3191

@user_4711 Look here: https://github.com/dompdf/dompdf/pull/3269

[user_4711]

sounds great, but i only found this discussion about PDF/X PDF/A Support in dompdf https://github.com/dompdf/dompdf/discussions/3191