Settings and activity
2 results found
-
132 votes
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…
Dan Garrick supported this idea ·
An error occurred while saving the comment -
94 votes
Dan Garrick supported this idea ·
As another commenter mentioned, we would expect 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.