Settings and activity
26 results found
-
22 votes
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment 
Daniel Minnick
commented
A major reason these specific fields aren’t available or consistent is the archaic state of the DOCX rendering engine. It can’t handle modern XML mapping or advanced conditional logic (like SKIPIF) reliably because it's running on nearly 20-year-old libraries. Modernizing the parser to OOXML v16 would allow for the robust field mapping we actually need. I've detailed the specific mapping failures and the path to a fix here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
Daniel Minnick
supported this idea
·
-
24 votes
Hi community we appreciate your feedback on the limitations of branding within Xero right now. While we are looking into improvements to branding and simplifying how customers customise their invoices, we don't have any plans at this stage to increase the # of branding templates that can be set up in the short term.
In consideration of those in the discussion who's workflow consists of creation of recipient created tax invoice, Xero does not currently have a feature to directly support these transaction types, however we have an idea specifically for this that you may be interested in adding your support to. This is not something we have plans for right now, but we are watching the feedback for this and will share if there's any updates, there.
An error occurred while saving the comment Daniel Minnick
commented
We keep asking for DOCX support in more modules (PO/Receipts/Remittance), but unless Xero fixes the core rendering engine first, those new templates will still suffer from blurry logos and stripped fonts. The current v12 engine is a bottleneck for the entire platform. We need a modernized document stack that respects modern security and branding standards. Join the push for an engineering fix here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
-
14 votes
We're grateful for your engagement and letting us know the changes that matter to you.
Our Community have reviewed your idea and now it can gain support from other community members.
Along with votes, others can now comment to share additional detail about how your idea could improve their experience with Xero.
Daniel Minnick
supported this idea
·
An error occurred while saving the comment Daniel Minnick
commented
A major reason these specific fields aren’t available or consistent is the archaic state of the DOCX rendering engine. It can’t handle modern XML mapping or advanced conditional logic (like SKIPIF) reliably because it's running on nearly 20-year-old libraries. Modernizing the parser to OOXML v16 would allow for the robust field mapping we actually need. I've detailed the specific mapping failures and the path to a fix here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
-
2 votes
Hi 👋 your idea is being looked into by our Community team. We'll be in touch soon to update you once your idea has been reviewed.
Did you know you can join our Xero Research panel to be involved in early testing and research? Find out more and sign up through our website 🙂
An error occurred while saving the comment Daniel Minnick
commented
The reason we’re fighting for every pixel at the top of our invoices is that Xero’s Advanced Template parser is locked into OOXML AppVersion 12 (Office 2007). Modern Word spacing and margin logic are literally ignored by Xero's legacy engine. If Xero updated the parser to modern v16 standards, these layout issues would disappear. I’ve posted a full technical audit on how to fix the underlying engine here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
Daniel Minnick
supported this idea
·
-
673 votes
Hi everyone, we’ve taken time to review the suggestion to include custom fields for both invoices and contacts, and recognise the value it'd bring in helping users capture more detailed information and avoid manual processes.
However, with other focuses drawing the teams attention such as multiple addresses this idea is not on our current development roadmap.
As we continue to plan future roadmaps, being highly supported this idea will continue to be considered, however we want to be open about it's current position with you all here. We appreciate you sharing your feedback and for your ongoing participation in the Xero community. Any changes to this status will be shared with everyone on this idea.
Daniel Minnick
supported this idea
·
.jpg){kind=link}
A major reason these specific fields aren’t available or consistent is the archaic state of the DOCX rendering engine. It can’t handle modern XML mapping or advanced conditional logic (like SKIPIF) reliably because it's running on nearly 20-year-old libraries. Modernizing the parser to OOXML v16 would allow for the robust field mapping we actually need. I've detailed the specific mapping failures and the path to a fix here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod