Step one I created custom fields to Billable time. This includes Project number, category (type of service ie in-house or external) and staff member (ie role type) all relating to the billable time and cost there of.
Step two I generated the invoice but can’t seem to call any of the custom fields from the billable time.
(I did manage to add a custom field to the invoice, but his doesn’t allow me to call the billable time custom field or fields.
I thought maybe one could call the billable time custom field from within the tax invoice custom field in a manner similar to an email auto responder by using %billable_time_custom_field_NAME%.
Your further input on this item would be greatly appreciated.
That is because custom fields created for billable time entries only show there. In general, if you want custom fields to show on sales invoices, you must create them for sales invoices. There are a few exceptions. One includes:
For both categories of items, if a custom field is created for the item and checked to show on printed documents, the field will be inserted into the main body of the transaction form as an additional column and the content (if any for that item) will be displayed.
Another exception includes transaction recipients:
These fields will display at the bottom of a transaction that includes the relevant recipient, if the box is checked to show on printed documents.
Definitely one for future development. The client wants to see more and more on the invoices and the custom fields appear to be the way forward. Just need a similar option to “show on printed documents” for carry the custom field through to the invoice.
Having used billable time extensively for 7 years, my recommendation is not to hope for custom fields that will carry forward to an invoice for information you want customers to see. I use custom fields for the Billable Time module for several purposes, such as service classification, staff member’s name, etc. These are very useful for internal purposes—searching, sorting, creating reports, and so forth.
But in many cases, you might not want some of that information going to a customer. And, of course, different customers request different information. But the option to show a custom field on a printed document would be universal. A given field would appear on every invoice. So you would lose control over this.
If you want information to show for the customer, my strong recommendation is to put it into the Description field for the billable time entry. It’s quite easy to adapt that content to the needs of any particular customer—even after an invoice is created, by editing. You can even format the Description field using HTML code, so it is very flexible.
To summarize my practices, most built-in fields are for the program, but descriptions are for the customer, and custom fields are for my business uses. That has worked extremely well over a wide range of customer and service types. If treatment of custom fields for billable time were ever to change, there would be serious issues of backwards compatibility.
Yes - thank you Tut. I have modified my descriptions to include the additional data required. As you state this is what the customer will see.
I recently came across the ability to use html. I will be exploring this more.
Our use case is very open with the client. We are supplying resumes of the staff working on projects to the client and as part of the project requirements we must list a range of information to break down costs to areas, staff role or type of service etc. It is the most detailed invoicing we have had requested.
It’s actually a good thing for our business and we will adopt this commonly moving our business forward (the drop down menus are very useful for this data but Manager does cope by remembering description entries)
As you suggest for the custom fields to work you would need to be able to turn each custom field on or off for each individual invoice …and by backwards compatibility I assume they would be default off for already generated invoices and then you would need to have a means to set all future invoices to use a standard template that has only specifics on. SO I do see the complexity unfolding.
This would rely on Form Defaults. But those are defined for transaction types, not for the custom fields themselves. You can specify default content for custom fields, but it then appears on all custom fields. So, for example, if you tailored your default sales invoice content to include a custom field related to billable time, the same content would appear on a sales invoice selling inventory items. All could be edited, but the potential to forget and the irritation of having to frequently delete unwanted content would be high. (More complexity unfolding, as you put it.)