Settings and activity
26 results found
-
83 votes
An error occurred while saving the comment -
27 votes
An error occurred while saving the comment 
Daniel Minnick
commented
To show 'Total Before Discount,' the template needs to support 'Calculated Fields' (Total + Discount). Modern Word supports these math nodes easily, but Xero’s archaic v12 engine simply can't process them. Modernizing the parser to OOXML v16 would solve this math failure across all templates. See the breakdown here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
-
10 votes
An error occurred while saving the comment Daniel Minnick
commented
Word’s native date switches (YYYY MM) are incredibly powerful, but Xero’s 2007-era parser often ignores or strips this formatting during the repeat cycle. We need a modernized document stack that respects modern Word logic so we can stop being forced into 'December 2024' formats. Check out the technical audit here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
-
9 votes
An error occurred while saving the comment Daniel Minnick
commented
Customizing terms like due dates and currency at the template level is a standard feature in modern document processing, but Xero’s legacy v12 engine lacks the support for 'Calculated Fields' and logic overrides needed to make this seamless. Updating the parser would unlock these dynamic fields. Join the push for a modern document engine here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
-
4 votes
An error occurred while saving the comment Daniel Minnick
commented
FYI, you can add a calculated field in the DOCX advanced template - I have not tested this yet, but that was available even in the archaic OOXML library Xero is using.
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
-
46 votes
An error occurred while saving the comment Daniel Minnick
commented
That is somewhat available in the DOCX advanced template, but unless Xero fixes the core rendering engine first, there are not many options. 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
-
26 votes
Thanks for submitting your idea on Xero Product Ideas. We appreciate you taking time to let us know how we could improve Xero for you.
Your feedback will soon be reviewed by our Community team, and in the meantime this can begin to build support with votes from other community members.
If you're interested to see recent releases or get a pulse on what's coming soon see The Long and Short of it. 🙂
An error occurred while saving the comment Daniel Minnick
commented
@Phil Hunter - no promises, that is up to Xero, I just see so many ideas circling around the same concept, indicating that what we have is broken! We are asking Xero to add functionality into something that is built on 20+ year old standards. That is ancient in the technology world! Let's band together and ask for a newer model car and get all the modern features that come with it at the same time!
An error occurred while saving the comment Daniel Minnick
commented
The Brighton Studio - thank you! After burning down about a week of my spare time trying to get this right (I am a 25-year veteran of the Information Technology field and hold multiple Microsoft certifications), I am at my wits end. There is no reason Xero should be using multiple standards that literally predate the release of their platform almost 20 years ago!
Daniel Minnick
shared this idea
·
-
4 votes
Hi Choonke thanks for raising this here. We understand the need for having Sales person's fields both on the invoice itself as well as the custom template. We have opened this idea up for the community so they can add their votes and comments on this idea. In the meantime, we'll monitor this space for more traction.
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
·
-
17 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
-
76 votes
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
-
7 votes
An error occurred while saving the comment Daniel Minnick
commented
We keep asking for better DOCX support, 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
Daniel Minnick
supported this idea
·
-
311 votes
Hi community, we appreciate the on-going interest this idea is receiving and the growing needs in the ability to customise documents that you send from Xero.
Right now, our position for this idea remains the same - we do have future plans to improve the branding experience across Xero, starting with invoicing which you can read more about.
As this experience continues to build out we'll make sure to share any updates for customising Remittance for everyone here.
Daniel Minnick
supported this idea
·
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
-
8 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 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
-
4 votesDaniel Minnick
supported this idea
·
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
-
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 🙂
Daniel Minnick
supported this idea
·
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
-
7 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
Many of us are forced to use DOCX just to get a clean layout, but then Xero ‘obliterates’ our branding by stripping fonts and flattening high-res logos into blurry bitmaps. This happens because the server-side parser is stuck in 2007 and only supports the 1996 'Core Web Font' set (Arial/Verdana). Let’s push Xero to support modern font-embedding and SVG fidelity by updating the document engine. See the technical breakdown and vote for the fix here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod
-
3 votes
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
-
4 votes
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
-
7 votesDaniel 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
-
76 votes
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
Tracking categories are a core part of Xero now, but because the Advanced Template parser hasn't seen a significant update sincethey were added, these fields were never mapped into the schema. It’s a textbook case of technical debt holding back a great feature. I've detailed the mapping failures and the fix here: https://productideas.xero.com/forums/967115-invoices-quotes/suggestions/51245914-modernize-advanced-templates-full-support-for-mod