Sales Pack - XInvoice

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • yuri
    replied
    In the future version there will be E-Invoice support for:
    • payment Credit Transfer
    • SEPA Direct Debit mandates
    • taxable shipping charges

    Leave a comment:


  • yuri
    commented on 's reply
    Hi, I'll look into.

  • hom
    replied
    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

    Leave a comment:


  • yuri
    replied
    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.

    Leave a comment:


  • yuri
    commented on 's reply
    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
    replied
    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!

    Leave a comment:


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

    Leave a comment:


  • Nina
    replied
    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

    Leave a comment:


  • yuri
    replied
    Hi Nina,

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

    Click image for larger version  Name:	image.png Views:	0 Size:	9.8 KB ID:	113654


    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.

    Leave a comment:


  • Nina
    replied
    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

    Leave a comment:


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

    Leave a comment:


  • hom
    replied
    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.​

    Leave a comment:


  • Nina
    replied
    Thank you Yuri!

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

    Leave a comment:


  • yuri
    replied
    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.

    Click image for larger version

Name:	image.png
Views:	398
Size:	19.2 KB
ID:	111954

    Leave a comment:


  • yuri
    commented on 's reply
    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.
Working...