Skip to content

Settings and activity

2 results found

  1. 50 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Cameron Kerr commented  · 

    I have one large client who is a parent to multiple subsidiaries. The invoices get sent out by the parent, and the client wants to be able to include the name of the subsidiary on the line-item as well as the salesperson (alternatively truck, driver) used.

    I can get part of the way there by having a different branding template for each subsidiary, and communicating this via the Invoice API (BrandingThemeID), and wedging additional information in the description, but it would be much preferable to have this as a proper template field.

    Alternatively, the ability to add additional fields that are visible as a column in the invoice editor and available to template (and don't have the limitations of Tracking Categories) would also be a great solution to this problem.

  2. 157 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for sharing and feeding back through this idea, community. While our team are reviewing the behaviours of date fields in new invoicing - It may help to clarify how due date works in conjunction with defaults to define how these are working in your organisation at present. Basically put, every time you change an Issue date this influences the Due date, which is a slight change to classic invoicing.

    Currently, there are two defaults that can be set in Xero, within Invoice Settings and within an individual Contact records.

    Invoice Settings due date is a blanket for any invoice raised in the org, if you set a Contact due date this will override the Invoice Settings due date when you select that Contact when invoicing.

    When you change the Due date of an invoice, and then edit it's Issue date this will trigger any defaults you have set up…

    An error occurred while saving the comment
    Cameron Kerr commented  · 

    To clarify, for us at least we expect that an Invoice that is submitted as a draft via the API and does not include any DueDate field, should populate the Due Date from the Customer-specific Sales Payment Terms, or the Organisation-specific Sales Payment Terms. That behaviour is missing in the New Invoicing, but was present and relied upon in the Classic Invoicing.

    Thanks,
    Cameron

    Cameron Kerr supported this idea  ·