Events/Invoice Delivery Events - Revision history

Scarpenter at 01:37, 31 October 2018

2018-10-31T01:37:21Z

Scarpenter: /* See Also */

2018-10-26T06:49:41Z

‎See Also

Dcowan: added postal invoice stuff

2017-08-17T08:42:56Z

added postal invoice stuff

Scarpenter: Scarpenter moved page InvoiceEmailTemplate to Events/Invoice Delivery Events

2017-02-27T05:48:51Z

Scarpenter moved page InvoiceEmailTemplate to Events/Invoice Delivery Events

Scarpenter: /* See Also */

2017-02-27T05:39:43Z

‎See Also

Scarpenter: /* Invoice Due/Overdue */

2017-02-27T05:38:37Z

‎Invoice Due/Overdue

Scarpenter: /* Invoice Delivery Events */

2017-02-27T05:32:56Z

‎Invoice Delivery Events

Scarpenter at 05:20, 27 February 2017

2017-02-27T05:20:56Z

Dcowan: added clarity to the use of inline CSS

2016-09-14T05:09:48Z

added clarity to the use of inline CSS

Dcowan: clarified using comma as email address separator

2016-05-23T00:06:01Z

clarified using comma as email address separator

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:Invoice Delivery Events}}
+=This Content Has Moved House=
-== Invoice Delivery Events ==
+This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
-;Invoice Post (id 23)
+We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to our new home.
-== Invoice Due/Overdue ==
+[https://resources.emersion.com/display/EKB/Invoicing Take me to the Emersion Knowledge Base article]
-* Invoice Due (id: 13)
+[[file:new_home_sm.jpg|900px]]

← Older revision		Revision as of 06:49, 26 October 2018
Line 16:		Line 16:
	* Invoice Due (id: 13)		* Invoice Due (id: 13)
	* Invoice Overdue (id: 7)		* Invoice Overdue (id: 7)
−
−	~~= See Also =~~
−	* [[InvoiceDeliveryApproval\|Configuring your Invoice Delivery and Invoice Approval Settings]]

@@ Line 4: / Line 4: @@
 == Invoice Delivery Events ==
-;Invoice Delivery (id 23)
+;Invoice Delivery (id 22)
 This is the event that delivers the invoice via email. It is used when the customer's invoice delivery method is set to 'Email' or 'Email and Post'.
-;Invoice Post (id 22)
+;Invoice Post (id 23)
-This is the event that delivers the invoice via post. It is used when the customer's invoice delivery method is set to 'Post' or 'Email and Post'.
+This is the event that delivers the invoice via post. It is used when the customer's invoice delivery method is set to 'Post' or 'Email and Post'. <br />
 == Invoice Due/Overdue ==

← Older revision		Revision as of 05:39, 27 February 2017
Line 17:		Line 17:

	= See Also =		= See Also =
		+	* [[InvoiceDeliveryApproval\|Configuring your Invoice Delivery and Invoice Approval Settings]]

@@ Line 11: / Line 11: @@
 == Invoice Due/Overdue ==
-You may also want to consider the importance of setting up the two invoice reminder notifications. but these are not essential for invoices.
+You may also want to consider setting up the two invoice reminder notifications, however these are not critical from a systems point of view.
 * Invoice Due (id: 13)
 * Invoice Overdue (id: 7)
+= See Also =

← Older revision	Revision as of 05:48, 27 February 2017
(No difference)

← Older revision		Revision as of 05:20, 27 February 2017
Line 1:		Line 1:
−	==Invoice ~~Email Template~~==	+	{{DISPLAYTITLE:Invoice Delivery Events}}
		+	= Overview =
		+	There are two [[Events\|System Events]] whose sole purpose is to physically deliver PDF invoice to your customers via their preferred delivery method. Arguably, these two events are the most important in the system. If these events are not configured and enabled, your customers will not receive their invoices after they have been approved.

−	~~The~~ Invoice email ~~template defines~~ the ~~content~~ and ~~layout of~~ the ~~email~~ that ~~is sent to your customer containing~~ the ~~.PDF~~ invoice ~~attachment~~. ~~A number of variables are available to include in~~ the ~~email, such as~~ customer ~~number, customer name,~~ invoice ~~number, invoice amount,~~ and invoice ~~due date~~.	+	== Invoice Delivery Events ==
		+	;Invoice Delivery (id: 23)
		+	This is the event that delivers the invoice via email. It is used when the customer's invoice delivery method is set to 'Email' or 'Email and Post'.
		+
		+	;Invoice Post (id: 22)
		+	This is the event that delivers the invoice via post. It is used when the customer's invoice delivery method is set to 'Post' or 'Email and Post'.
		+
		+	== Invoice Due/Overdue ==
		+	You may also want to consider the importance of setting up the two invoice reminder notifications. but these are not essential for invoices.
		+
		+	* Invoice Due (id: 13)
		+	* Invoice Overdue (id: 7)

@@ Line 2: / Line 2: @@
 The Invoice email template defines the content and layout of the email that is sent to your customer containing the .PDF invoice attachment. A number of variables are available to include in the email, such as customer number, customer name, invoice number, invoice amount, and invoice due date.
@@ Line 9: / Line 10: @@
 # Locate the ''Invoice Delivery'' template in the ''Event'' column, and click the template number or name in the ''ID'' or ''Name'' column. The invoice email template will be displayed.
 # Click the '''Return to list''' button to exit.
@@ Line 49: / Line 51: @@
 # Select the invoice template to associate with the event from the ''Invoice Template Selection'' drop list.
 # Enter the message text in the ''Content'' box. The ''Content'' box is a basic HTML editor (i.e. tinyMCE). Some standard text formatting options are available. <br/>
-#:To add graphics to the message, such as an image or logo, the image file needs to be hosted externally. This is the preferred way of handling images in a message, rather than as attachments. This is done by editing the HTML directly, using the ''Edit HTML Source'' function, and including the image in the HTML code directly.
+#:To add graphics to the message, such as an image or logo, the image file needs to be hosted externally. This is the preferred way of handling images in a message, rather than as attachments. This is also the method to define custom inline CSS on individual HTML tags. This is done by editing the HTML directly, using the ''Edit HTML Source'' function, and including the image in the HTML code directly.
 # Insert the required account and invoice ''Variables'' into the message. These are shown beside the ''Content'' box, per step 11 above. Click the variable name in the list. The variable ''code'' will be added to the subject field. Position it within the text as required.
 # Use the ''Preview'' function to see how the invoice email will appear to the customer.
 # Click the '''Save''' button. The ''Invoice Email Template'' details will display.
 # Click the '''Return to list''' button to exit.
@@ Line 64: / Line 67: @@
 # Click the '''Save''' button. The updated template details will display, with an information box showing the template has been saved successfully.
 # Click the '''Return to list''' button to exit.
@@ Line 70: / Line 74: @@
 # Select '''Events''' &gt; '''Templates '''&gt;''' '''from the '''Menu.''' A list of existing templates will be shown.
 # Click the '''Delete Template''' link beside the required template in the ''Delete Mapping''''' '''column. An information box will display showing that the template has been deleted.
@@ Line 89: / Line 113: @@
 * '''Attachment''' will only appear for invoice based event types and can be only None or Invoice.
 * '''Content''' is a HTML editor which also allows template variables.

@@ Line 82: / Line 82: @@
 ** '''Secondary Contact''' will use the Secondary Contact's Email Address
 ** '''Billing Contact''' will use the Billing Contact's Email Address.
-** '''Custom ...''' which allows the user to enter a semi-colon delimited list of email addresses.
+** '''Custom ...''' which allows the user to enter a comma delimited list of email addresses. [eg. test@test1.com,test@test2.com]
-* '''CC''' is the carbon copy field.
+* '''CC''' is the carbon copy field. Also accepts comma delimited list of email addresses. [eg. test@test1.com,test@test2.com]
-* '''BCC''' is the blind carbon copy field.
+* '''BCC''' is the blind carbon copy field. Also accepts comma delimited list of email addresses. [eg. test@test1.com,test@test2.com]
 * '''Subject''' is the subject field. This field accepts variables, a list of variables will appear next to the field when in focus to assist the user as to what is available.
 * '''Priority''' is the message priority.
 * '''Attachment''' will only appear for invoice based event types and can be only None or Invoice.
 * '''Content''' is a HTML editor which also allows template variables.