Importing allows us to do more customization on our invoice templates, Karina.
For you to use the EZ Map Fields, you'll need to enclose the texts in angle brackets (<>). For example, <shipdate> and <shippingaddress>.
Once you upload the file, the system will look for the fields with angle brackets, and match them to the QuickBooks fields. Then, you can continue matching the other fields until you're done. You can also refer to this article for reference: Import Custom Form Styles for Invoices or Estimates.
I'll get back to you if you have more questions about this.
Thanks for the response. I have been able to use the EZ Maps Fields successfully for other fields but not for the "Terms" field as documented in the QuickBooks Online EZ Map Fields Catalogue here.
The "Terms" field does not appear in the drop down when doing the mapping.
Hello there, Karina2.
I've read your original post and downloaded an example estimate template from QuickBooks Online. The terms field is unavailable. An estimate is a quote or a proposal for the work you plan to do and this is a non-posting transaction. Having said that, the terms is only available once you convert the estimate to an invoice. Or, once you create an invoice.
You can still import your estimate template and use it. Then, if you want to send it to your customer, you can manually add the terms in the Message displayed on invoice field. I've attached screenshots to guide you.
Please let us know if you have other concerns, we're just around.
Thanks for trying it out for me. The documentation I linked clearly shows "terms" is a field also available in estimates/quotes as well as invoices. This makes sense since it is expected that terms are included in a quote.
Your work around is not feasible for me since this is being used for more generic message to the customers. Also the system should be able to pull out the terms from the customer data automatically so it does not rely on memory or manually checking.
Since it says its supported in the documentations will this be rolled out shortly in an update?
Hi Karina, thanks for a great question. I have personally been a big advocate for fleshing out this functionality, and extending the uses (like the one you are describing here). While I can't promise any immediate change, I have your back in wanting this same feature. If anything updates, you will be the first to know. Thanks!
I agree with Karina! Not only does it say you should be able to do so, it is also an available EZfield if you import a custom invoice. How ridiculous that a field that is available to map as an invoice is not for a estimate. They simply did not bother to make it a choice in the drop selection in the EZfield choices though it already though it is there if they added into their table of choices.
Ez Tag <estimateno> does not map either.... You must use <estimatenumber>.
This is just shoddy coding at Intuit. I guess a spotty coder kid has dropped the ball when it comes to checking the detail!
This is not what we want you to experience, Beancounter. Rest assured, I'll route you to the right support to address your concern properly.
The <estimateno> scalar field is used to match the Estimate no. field in QuickBooks Online (QBO) when importing the custom estimate. To investigate why the scalar field in the EZ Map Fields Catalog is not mapping correctly in QBO, I'd suggest contacting our Customer Support Team. They'll pull up your account in a secure environment and provide detailed information about this one.
Here's how to reach them:
I have articles here about managing estimates:
Visit the Community if you need a hand preparing your year-end reports or any QBO related. I'll be here to help.
The complete list is useful thank you. There seems to be very little information around about such things.
I have noted a couple of errors around the Estimates section that I've come across that might help others:
1. The stated field <estimateno> is incorrect. It is in fact <estimatenumber>
2. The field <terms> does not work with estimates. If you try to use it, their is no associated field to map it to.
To add on to this, I have found the following EZ map fields do not correlate to Quickbooks. I have had 2 lovely ladies at support try and help to no avail.
Quote number - Quickbooks says should be <refnumber> but in fact it is <quotenumber>
Date - Quickbooks says it should be <date> but doesn't work in quote but does for invoice
shipping - Quickbooks says it should be <shippingaddress> doesn't come up
Prices/rate - should be <rate> but prices sometimes work and sometimes don't in the preview
Deposit - should be <deposit> but doesn't work in quotes, does in invoice though
and custom fields 1, 2 and 3 do not come up.
I appreciate the details of your post, Bec73.
I can see that you've been through this a lot. In fact, you're very detailed with the field names.
You can actually use different field names (<fieldname>) as long as you map them accordingly. The fields on the EZ map is just a recommendation. However, there might be instances where QuickBooks couldn't capture the information during import or preview. This could be due to the placement of the fields on your form. For example, overlapping tables.
If you didn't modify the placement of the tables on the sample form, our Support should be able to check this further for you. Did they mention to investigate this further? If not, please contact them again and request to check this further. That way, you can successfully import your own style.
In the meantime, you can create your own form style based on the preset templates we have. This will be our workaround for now.
If you have other questions, please don't hesitate to go back to this thread.