BUG 1 - When using EZ Mapping tags in custom invoice templates on the Mac I have discovered that the <netamount> tag causes the PDF creation to fail. IE Create the invoice template in Word, import into QBO 'Import Form Styles', then check that the fields map ok. QBO claims that the template is a success. Then 'Preview and Confirm Style' and QBO just shows a blank window. This is ok but it should start up Adobe Acrobat and show the new preview there. If that works all is ok, if you don't get a preview in Acrobat the whole process has failed. After countless attempts I have found that using the <netamount> tag causes the Custom Style template to fail.
BUG 2 - It seems that the <CustomX> tag causes the mapping to fail. Despite using exact wording from the EZ tag guide the <Custom1> <Custom2> and <Custom3> tags do not map and cause QBO to throw an error.
But if you manually override the mapping by checking the tick box to map the fields and continue the PDF preview will actually show the <Custom1> etc data.
This is basic stuff Intuit. If you say a feature is available you must make it work otherwise this is called 'misrepresentation'. Please look into these coding errors. Thanks.
I appreciate you sharing this concern with us here in the Community, @Beancounter.
To verify why the custom template fails when imported to QuickBooks Online, I recommend contacting our Customer Care Team. They have advanced tools like the remote-viewing session that can help isolate the root cause of this issue. They'll also generate an investigation ticket if necessary.
To contact them:
Click on Help at the top menu bar.
Hit on the Contact Us button.
Enter a brief description of the issue in the What can we help you with? box.
Press on Let's talk.
Select on Geta callback.
Key in your contact details, then tap on Confirm my call.
What is odd is that I took the QBO Invoice template sample and modified that so the original document should be clean. But as soon as you modify it you can really screw it up pretty quickly in terms of layout. I also can't see why the <custom1> fields don't map and that QBO lies to you saying that the template is perfect when it isn't
Another big issue with generating a template outside of QBO is that upon import QBO ignores a lot of the formatting. Such as 'Bold' text, table positioning, margins etc. It seems to default to something else that you can't control. It is definitely not WISYWIG. When you create a template in Word/Pages in .docx what you actually see is not what you get in QBO. Close (ish) but not the same.
You have to be really careful with text runaround settings too otherwise the QBO fields can end up overlaid ontop of other info making a right mess.
I also found that the tag <invoiceno> fails. You have to use <refnumber> for the invoice number. Why is that?
To minimise errors I am uploading into the browser version of QBO, not the App or the psuedo client side App that can sit on your desktop.
Formatting bugs are a real pain. If you select Helvetica Bold in Word QBO substitutes that for a Helvetica regular. For fun if you use Helvetica light you get a random serif font!
Supposedly QBO supports:
Arial Unicode MS o Courier, Courier Bold, Courier Oblique, Courier Bold-Oblique o Helvetica, Helvetica Bold, Helvetica Oblique, Helvetica Bold-Oblique o Times Roman, Times Bold, Times Italic, Times Bold-Italic o Symbol o Zapf Dingbats
But in reality it creates substitutions so you don't quite get what you want. Arial Unicode is a proper pain as it restricts line spacing control and has no font weights available but is the only way to get a light sans serif text.
When QBO creates the PDF from the template it also introduces a lot of spacing changes/errors that are not in your original design. Eg. I want my logo at the very top of the design so I reduced the margins in Word/Pages, but QBO merrily ignores this and puts the table with the logo in it about 20mm down from the top edge of the page anyway. I think there are some coding errors from the QBO API that the PDF engine (leased from Adobe?) does not like and therefore Acrobat will not render properly.