Setting up and Configuring NEOSYS Generally - Revision history

Lance: /* Specifying Payment Terms on Invoices */

2026-04-07T08:29:23Z

Specifying Payment Terms on Invoices

← Older revision		Revision as of 08:29, 7 April 2026
Line 255:		Line 255:

	Entering a full stop (.) or the word NONE in Client or Company File payment terms suppresses any terms found in Company or Configuration File allowing you to suppress, per client or company, any default payment terms specified in the Company or Configuration Files.		Entering a full stop (.) or the word NONE in Client or Company File payment terms suppresses any terms found in Company or Configuration File allowing you to suppress, per client or company, any default payment terms specified in the Company or Configuration Files.

			Also refer to: [[Agency_FAQ#What_is_the_difference_between_terms_of_payment_and_payment_instructions.3F\|Difference between terms of payment and payment instructions]]

	===Payment Terms for UAE E-Invoicing===		===Payment Terms for UAE E-Invoicing===
Line 260:		Line 262:
	For UAE E-Invoicing the payment terms must contain the due date.		For UAE E-Invoicing the payment terms must contain the due date.
	Accepted formats are:		Accepted formats are:
	* "Due Date: <DATE>" E.g. Due Date: 01/01/2026		* Due Date: <DATE> (E.g. Due Date: 01/01/2026)
	* "<Number of Calendar Unit> <Calendar Unit>" E.g "15 days" OR "2 weeks" OR "3 months"		* <Number of Calendar Unit> <Calendar Unit> (E.g "15 days" OR "2 weeks" OR "3 months")

	~~Also refer to: [[Agency_FAQ#What_is_the_difference_between_terms_of_payment_and_payment_instructions.3F\|Difference between terms of payment and payment instructions]]~~

	==Creating Email Alerts in NEOSYS==		==Creating Email Alerts in NEOSYS==

Lance: /* Specifying Payment Terms on Invoices */

2026-04-07T08:27:23Z

Specifying Payment Terms on Invoices

← Older revision		Revision as of 08:27, 7 April 2026
Line 255:		Line 255:

	Entering a full stop (.) or the word NONE in Client or Company File payment terms suppresses any terms found in Company or Configuration File allowing you to suppress, per client or company, any default payment terms specified in the Company or Configuration Files.		Entering a full stop (.) or the word NONE in Client or Company File payment terms suppresses any terms found in Company or Configuration File allowing you to suppress, per client or company, any default payment terms specified in the Company or Configuration Files.

			===Payment Terms for UAE E-Invoicing===

			For UAE E-Invoicing the payment terms must contain the due date.
			Accepted formats are:
			* "Due Date: <DATE>" E.g. Due Date: 01/01/2026
			* "<Number of Calendar Unit> <Calendar Unit>" E.g "15 days" OR "2 weeks" OR "3 months"

	Also refer to: [[Agency_FAQ#What_is_the_difference_between_terms_of_payment_and_payment_instructions.3F\|Difference between terms of payment and payment instructions]]		Also refer to: [[Agency_FAQ#What_is_the_difference_between_terms_of_payment_and_payment_instructions.3F\|Difference between terms of payment and payment instructions]]

Saif: /* Targetuser(s) */

2025-11-03T08:00:53Z

Targetuser(s)

← Older revision		Revision as of 08:00, 3 November 2025
Line 321:		Line 321:
	===Targetuser(s)===		===Targetuser(s)===

	Optional commas separated list of user codes (no spaces!) to receive any output from the alert. Note that some s may not have any output and that some alerts may automatically direct their output to various users.		Optional commas separated list of user codes (no spaces!) to receive any output from the alert. Note that some alerts may not have any output and that some alerts may automatically direct their output to various users.

	===Test email===		===Test email===

Gregory: /* Creating Email Alerts in NEOSYS */ GB - minor update convert from AREV cmd to exodus

2024-08-22T08:23:51Z

Creating Email Alerts in NEOSYS: GB - minor update convert from AREV cmd to exodus

← Older revision		Revision as of 08:23, 22 August 2024
Line 266:		Line 266:
	To find existing alerts		To find existing alerts

	~~SORT DOCUMENTS ALERTS~~		EXO_DATA=<DBCODE> list documents alerts

	===Syntax===		===Syntax===

Gregory: /* Runhours */

2023-03-06T10:39:15Z

Runhours

← Older revision		Revision as of 10:39, 6 March 2023
Line 295:		Line 295:

	===Runhours===		===Runhours===

			Configure hours as per server timezone.

	Required.		Required.

Arvind: /* Configuring Client Security mark */

2021-08-05T13:50:44Z

Configuring Client Security mark

← Older revision		Revision as of 13:50, 5 August 2021
Line 38:		Line 38:
	Run below command to start a live process in debugger mode,		Run below command to start a live process in debugger mode,
	./run <database>		./run <database>
	Press 'x' to open the command line interface,		Press 'x' to open the command line interface, then type
	setmark * "<clientmark>"		setmark * "<clientmark>"

Line 51:		Line 51:

	./run <database>		./run <database>
	Press 'x',		Press 'x', then type
	setmark <companycode> "<clientmark>"		setmark <companycode> "<clientmark>"

Line 62:		Line 62:

	./run <database>		./run <database>
	Press 'x',		Press 'x', then type
	setmark <companycode>		setmark <companycode>

Joel: /* Configuring Client Security mark */

2021-08-05T13:12:08Z

Configuring Client Security mark

← Older revision		Revision as of 13:12, 5 August 2021
Line 15:		Line 15:
	A "client security mark" which represents the client's general public identity or trading name is printed on all documents generated out of NEOSYS. This client mark is a mandatory contractual feature and cannot be removed.		A "client security mark" which represents the client's general public identity or trading name is printed on all documents generated out of NEOSYS. This client mark is a mandatory contractual feature and cannot be removed.

	[[Image:~~clientsecuritymark~~.jpg]]		[[Image:clientmark.jpg]]

	The objective of the client mark is that anyone can easily identify the general source of a document or report produced by NEOSYS. It, therefore, MUST clearly indicate the public identity of the client and CANNOT be brief or anonymous.		The objective of the client mark is that anyone can easily identify the general source of a document or report produced by NEOSYS. It, therefore, MUST clearly indicate the public identity of the client and CANNOT be brief or anonymous.
Line 35:		Line 35:

	<b> Exodus </b>		<b> Exodus </b>

			Run below command to start a live process in debugger mode,
	./run <database>		./run <database>
			Press 'x' to open the command line interface,
	x setmark * "<clientmark>"		setmark * "<clientmark>"

	===Setting a security mark per company===		===Setting a security mark per company===
Line 48:		Line 50:
	<b> Exodus </b>		<b> Exodus </b>

	~~Run below commands to get into the command line interface,~~
	./run <database>		./run <database>
	Press 'x',		Press 'x',
Line 59:		Line 60:

	<b> Exodus </b>		<b> Exodus </b>

	./run <database>		./run <database>
			Press 'x',
	x setmark <companycode>		setmark <companycode>

	==Configuring fonts and colors for all users==		==Configuring fonts and colors for all users==

Joel: /* Setting a security mark per company */

2021-08-05T12:31:15Z

Setting a security mark per company

← Older revision		Revision as of 12:31, 5 August 2021
Line 48:		Line 48:
	<b> Exodus </b>		<b> Exodus </b>

	Run ~~cmd~~ below to ~~start debugging in Live~~,		Run below commands to get into the command line interface,
	./run <database>		./run <database>
	Press 'x' ~~to get the cmd line interface~~,		Press 'x',
	setmark <companycode> "<clientmark>"		setmark <companycode> "<clientmark>"

Joel: /* Setting a default security mark */

2021-08-05T12:23:12Z

Setting a default security mark

← Older revision		Revision as of 12:23, 5 August 2021
Line 47:		Line 47:

	<b> Exodus </b>		<b> Exodus </b>

			Run cmd below to start debugging in Live,
	./run <database>		./run <database>
			Press 'x' to get the cmd line interface,
			setmark <companycode> "<clientmark>"

	~~x setmark <companycode> "<clientmark>"~~		===Removing a security mark===

	=== Removing a security mark ===

	<b> AREV </b>		<b> AREV </b>

Joel: /* Configuring Client Security mark */

2021-08-05T12:13:58Z

Configuring Client Security mark

← Older revision		Revision as of 12:13, 5 August 2021
Line 31:		Line 31:
	For all companies that do not have a specific mark		For all companies that do not have a specific mark

	~~======~~ AREV ~~======~~		<b> AREV </b>
	SETMARK * "<clientmark>"		SETMARK * "<clientmark>"

	~~======~~ Exodus ~~======~~		<b> Exodus </b>
	./run <database>		./run <database>

Line 43:		Line 43:
	In addition to the above initial general default client mark per database, in case certain companies within the same NEOSYS database cannot use the same mark at all, for example due to different branding, additional client security marks can be assigned to specific companies. This will not be allowed where a simpler client mark could cater for all companies.		In addition to the above initial general default client mark per database, in case certain companies within the same NEOSYS database cannot use the same mark at all, for example due to different branding, additional client security marks can be assigned to specific companies. This will not be allowed where a simpler client mark could cater for all companies.

	~~======~~ AREV ~~======~~		<b> AREV </b>
	SETMARK <companycode> "<clientmark>"		SETMARK <companycode> "<clientmark>"

	~~======~~ Exodus ~~======~~		<b> Exodus </b>
	./run <database>		./run <database>

Line 53:		Line 53:
	=== Removing a security mark ===		=== Removing a security mark ===

	~~======~~ AREV ~~======~~		<b> AREV </b>
	SETMARK <companycode>		SETMARK <companycode>

	~~======~~ Exodus ~~======~~		<b> Exodus </b>
	./run <database>		./run <database>