Custom Form Style EZ Mapping tags bugs

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:

1. Click on Help at the top menu bar.
2. Hit on the Contact Us button.
3. Enter a brief description of the issue in the What can we help you with? box.
4. Press on Let's talk.
5. Select on Get a callback.
6. Key in your contact details, then tap on Confirm my call.

I'm also adding here a link about mapping the imported sales template in QuickBooks Online for reference: Import custom form styles for invoices or estimates

I'm just a few clicks away if there's anything else you need. Just let me know by leaving a reply below. Have a great day!

Thanks BettyJane.

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.

Tim

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.

Tim

.

I have had similar issues. I ended up basically putting everything into tables that don't allow overlap, and then QuickBooks will keep them from overlapping. Even then some stuff still gets messed up if too many lines are added to the invoice. I have also noticed that I can't map the Account summary description field without the pdf creation failing. QuickBooks needs to get their act together on this.