HelpWiki Highnix - Recent changes [en]

Gross Margin Scheme

Khkoh — Sun, 13 Sep 2026 13:45:15 GMT

Create a GST Tax Type

← Older revision		Revision as of 21:45, 13 September 2026
Line 25:		Line 25:
	\|-		\|-
	\|Tax Type		\|Tax Type
	\|'''NA-~~GSM~~'''		\|'''NA-GMS'''
	\|-		\|-
	\|GST Rate		\|GST Rate

Late Payment Interest

Khkoh — Sat, 12 Sep 2026 09:05:02 GMT

Preparation

← Older revision		Revision as of 17:05, 12 September 2026
(2 intermediate revisions by the same user not shown)
Line 309:		Line 309:
	=== Preparation ===		=== Preparation ===

	Before generating recurring LPI invoices, the ~~recurring~~ LPI setup must first be configured.		Before generating recurring LPI invoices, the '''Recurring LPI''' setup must first be configured.

	# Navigate to '''Sales > Maintenance > Recurrent LPI'''.		# Navigate to '''Sales > Maintenance > Recurrent LPI'''.
	# Set up the recurring LPI by ~~filling in~~ the required information. This defines the rules and parameters that the system will use when generating the LPI invoices.		# Set up the recurring LPI by completing the required information. This defines the rules and parameters that the system will use when generating the LPI invoices. For '''MCSTs or property management companies''', users can select a '''Sales Group''' instead of selecting individual customers. A Sales Group allows customers with common characteristics to be grouped together for billing purposes. For example, customers may be grouped according to:
			## Number of bedrooms, such as '''2-bedroom''' or '''3-bedroom''' units; or
			## Share value, such as '''100 share-values''' or '''130 share-values'''.
			# Once a Sales Group is selected, all customers belonging to that group will be included and billed according to the recurring LPI setup when the recurring LPI invoice is generated.
	# Review the information entered and click '''Save'''.		# Review the information entered and click '''Save'''.

	Once the recurring LPI setup has been saved, the system is ready to generate the LPI invoices.		Once the recurring LPI setup has been saved, the system is ready to generate the recurring LPI invoices.

	=== Create Recurring LPI Invoices ===		=== Create Recurring LPI Invoices ===

Error codes explain dolution

Khkoh — Mon, 07 Sep 2026 06:00:14 GMT

The entered transaction does not exist or cannot be voided.

← Older revision		Revision as of 14:00, 7 September 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__

	===<span id="err message 1"><span style="color:~~RED~~">This document cannot be processed because there is insufficient quantity for items marked.</span>===		== <span id="err message 1"><span style="color:black">This document cannot be processed because there is insufficient quantity for items marked.</span> ==
	[[#err message 1\|Tag:#err message 1]]		[[#err message 1\|Tag:#err message 1]]

Line 10:		Line 10:
	----		----

	===<span id="err message 1"><span style="color:~~red~~">The customer could not be added Tutorial, error code : 1062 error message : Duplicate entry for key ...</span>===		== <span id="err message 1"><span style="color:black">The customer could not be added Tutorial, error code : 1062 error message : Duplicate entry for key ...</span> ==
	[[#err message 2\|Tag:#err message 2]]		[[#err message 2\|Tag:#err message 2]]

Line 21:		Line 21:
	----		----

	===<span id="Unable to find xref table"><span style="color:~~red~~">TCPDF error: Unable to find xref table.</span>===		== <span id="Unable to find xref table"><span style="color:black">TCPDF error: Unable to find xref table.</span> ==
	[[#Unable to find xref table\|Tag:#Unable to find xref table]]		[[#Unable to find xref table\|Tag:#Unable to find xref table]]

Line 38:		Line 38:

	----		----

			== The entered transaction does not exist or cannot be voided. ==
			This message appears when the selected transaction cannot be voided.

			The most common reasons are:

			# '''The transaction has downstream transactions'''The transaction has already been used to create or process one or more subsequent transactions. In this case, the downstream transactions must be voided '''first''', before the original transaction can be voided.
			# '''The transaction has already been fully voided'''The transaction may have been voided previously and therefore cannot be voided again.

			=== What should I do? ===

			# Please check the transaction and its related transactions to determine whether any downstream transactions exist or whether the transaction has already been voided.
			# If downstream transactions exist, '''void them first and then try to void the original transaction again'''.

			[[#Top\|<u>Go to Top</u>]]

HelpWiki Highnix:General disclaimer

Khkoh — Mon, 07 Sep 2026 02:30:52 GMT

← Older revision		Revision as of 10:30, 7 September 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__

			= Disclaimer =

			The information provided on '''Highnix Online Help''' is intended to assist users in understanding and using Highnix software, including its features, functions, configuration, and related procedures.

			While we make reasonable efforts to ensure that the information provided is accurate, complete, and up to date, '''Highnix does not warrant or guarantee that all information is error-free, complete, or current at all times'''. Software features, functionality, procedures, screenshots, and system requirements may change from time to time as a result of software updates, enhancements, changes in technology, or changes in applicable requirements.

			== Use of Information ==

			The information provided in this Help site should be used as a general reference and guide. Users are responsible for ensuring that any instructions or procedures are appropriate for their particular system configuration and business requirements.

			Highnix shall not be responsible for any loss, damage, interruption, or other consequences arising from the use of, or reliance upon, information provided on this Help site, to the extent permitted by applicable law.

			== Accounting, Tax and Regulatory Information ==

			Where this Help site contains information relating to '''accounting, taxation, GST, InvoiceNow, e-invoicing, or other regulatory requirements''', such information is provided for general guidance only and should not be regarded as professional accounting, tax, legal, or regulatory advice.

			Users should verify the applicable requirements with the relevant government authority, regulatory body, or their own qualified professional adviser before making decisions or submitting information based on such guidance.

			== Third-Party Information and Links ==

			This Help site may contain references or links to third-party websites, services, software, or documentation. Such references are provided for convenience only.

			Highnix does not control and is not responsible for the content, accuracy, availability, security, or privacy practices of third-party websites or services. The inclusion of any third-party reference or link does not necessarily constitute an endorsement or recommendation by Highnix.

			== Software and System Changes ==

			Highnix software is continually being improved and updated. As a result, the appearance, functionality, menus, procedures, and behaviour described in this Help site may differ from the version currently used by a customer.

			Where there is a difference between information published on this Help site and the actual behaviour of the software, the '''latest applicable software version, system configuration, or official communication from Highnix shall take precedence'''.

			== No Guarantee of Availability ==

			Although reasonable efforts are made to maintain the availability of Highnix Online Help, Highnix does not guarantee that the Help site or any particular article will always be available, uninterrupted, or free from errors.

			Highnix reserves the right to modify, update, replace, or remove any content on this Help site at any time without prior notice.

			== Acceptance ==

			By using Highnix Online Help, you acknowledge and agree that the information provided is intended as a general reference and that you are responsible for determining its suitability for your particular circumstances.

			If you require assistance with a specific issue or are uncertain about the appropriate procedure, please contact '''Highnix Support''' for further assistance.

			'''© Highnix. All rights reserved.'''
			```

HelpWiki Highnix:General disclaimer

Khkoh — Mon, 07 Sep 2026 02:29:05 GMT

Created page with "__FORCETOC__"

New page

__FORCETOC__

MediaWiki:Common.css

Khkoh — Mon, 07 Sep 2026 02:23:23 GMT

← Older revision		Revision as of 10:23, 7 September 2026
Line 115:		Line 115:
	text-decoration: underline !important;		text-decoration: underline !important;
	color: #3399ff !important;		color: #3399ff !important;
			}

			/* Koh: R0907: Hide "This page was last edited..." */
			#footer-info-lastmod {
			display: none;
	}		}

Invoice Data Submission through APs

Khkoh — Sun, 06 Sep 2026 04:50:38 GMT

Invoice Preparation

← Older revision		Revision as of 12:50, 6 September 2026
(One intermediate revision by the same user not shown)
Line 6:		Line 6:
	# Invoices (sales or purchase) are prepared in the Highnix system using a user-friendly interface.		# Invoices (sales or purchase) are prepared in the Highnix system using a user-friendly interface.
	# Once an invoice is prepared, the user will be directed to a processing page (See Fig 1), where multiple options are available for handling the invoice.		# Once an invoice is prepared, the user will be directed to a processing page (See Fig 1), where multiple options are available for handling the invoice.
			# NOTE: For supplier invoice and supplier credit note and the supplier is a InvoiceNow participant, user must copy the supplier invoice reference and UUID as shown in the modal (pop-up small window) and paste to the supplier reference and supplier reference UUID fields respectively. If user is not a InvoiceNow participant, then enter "NA" (must be in capital letters) at the UUID reference field.

	=== Submission Process ===		=== Submission Process ===

GL Closing

Khkoh — Fri, 04 Sep 2026 07:08:42 GMT

GL Closing

← Older revision		Revision as of 15:08, 4 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
			==GL Closing==
			The '''GL Closing''' function is used to close the General Ledger up to a specified date. Once the GL is closed, transactions dated on or before the closing date are treated as '''Closed''' and can no longer be edited or deleted through the normal system interface.

			GL closing is an important accounting control and should be performed carefully. Users should ensure that all necessary accounting entries, adjustments and reconciliations for the period have been completed before closing the GL.
			===Accessing GL Closing===

			# To access the GL Closing function:
			## Navigate to '''Finance Mgt > Maintenance > GL Closing'''.
			## The GL Closing screen will be displayed.

			===Closing the GL===

			# Select the desired '''Closing Date''' using the calendar.
			# Review the selected date carefully to ensure that it is the intended accounting closing date.
			# Click the '''Close GL''' button.
			# The system will close the GL up to the selected date.
			# Once the GL has been closed, transactions within the closed period will be marked as '''Closed''' and cannot be edited or deleted through the normal transaction screens.
			# Important: Re-opening the GL

			=== Re-Open the GL ===

			# Highnix allows users to re-open the GL if further accounting entries need to be posted for a previously closed period. This can be done by removing or changing the closing date and using the '''Close GL''' function again.
			# However, users must understand that '''re-opening the GL does not re-open transactions that were previously closed'''.
			# For example, if an invoice or journal entry was already marked as '''Closed''' when the GL was closed, re-opening the GL will allow new transactions to be entered, but the previously closed transaction will remain closed. It will not automatically become available for editing or deletion.
			# Therefore, '''GL closing should be treated as a serious accounting control and should not be used casually or repeatedly to facilitate changes to previously closed transactions.'''
			===Accounting Best Practice===

			# It is not recommended to manually intervene in the database to change the status of closed transactions simply to make them editable.
			# Directly modifying accounting data in the database can affect the integrity and audit trail of the accounting records. Any correction to a closed transaction should, wherever possible, be handled using the appropriate accounting procedure, such as entering an adjustment, reversal or void transaction.
			# If a situation arises where a previously closed transaction genuinely needs to be modified and there is no appropriate standard system procedure to do so, '''Highnix Support can assist with the database intervention as a chargeable service'''. Such changes should only be carried out after the customer has confirmed and accepted the required adjustment.
			===Important Reminder===

			# '''Before closing the GL, always ensure that:'''
			## All transactions for the period have been entered.
			## Required adjustments and corrections have been completed.
			## The relevant accounts have been reviewed and reconciled.
			## The closing date is correct.
			## The GL does not need to remain open for any further changes to existing transactions.
			# '''Remember:'''
			## '''Re-opening the GL allows new entries to be posted. It does not re-open previously closed transactions for editing or deletion.'''

GL Closing

Khkoh — Fri, 04 Sep 2026 06:56:00 GMT

Created page with "__FORCETOC__"

New page

__FORCETOC__

Home (Click on Highnix Logo)

Khkoh — Fri, 04 Sep 2026 06:55:31 GMT

Online Manual Table of Content:

← Older revision		Revision as of 14:55, 4 September 2026
Line 235:		Line 235:
	\|''Maintenance:''		\|''Maintenance:''
	\|[[Add and Edit Bank Accounts]]		\|[[Add and Edit Bank Accounts]]
			\|-
			\|
			\|
			\|
			\|[[GL Closing]]
	\|-		\|-
	\|■		\|■

Late Payment Interest

Khkoh — Sun, 30 Aug 2026 03:53:41 GMT

Changing the LPI Item

← Older revision		Revision as of 11:53, 30 August 2026
Line 139:		Line 139:
	Navigate to:		Navigate to:

	'''System Setup → ~~Forms~~ and ~~Docs Reference Number~~'''		'''System Setup → System and General GL'''

	Select the desired item code from the available list and save the setting.		Select the desired item code from the available list and save the setting.

Home (Click on Highnix Logo)

Khkoh — Sun, 30 Aug 2026 03:23:14 GMT

Online Manual Table of Content:

← Older revision		Revision as of 11:23, 30 August 2026
Line 164:		Line 164:
	\|		\|
	\|		\|
	\|[[Late Payment Interest\|Late Payment Interest Module]]		\|[[Late Payment Interest\|Late Payment Interest Module (LPI)]]
	\|-		\|-
	\|■		\|■

Late Payment Interest

Khkoh — Sat, 29 Aug 2026 13:41:18 GMT

Grace Period

← Older revision		Revision as of 21:41, 29 August 2026
(9 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__

	= Late Payment Interest (LPI) Module User Guide =		== Late Payment Interest (LPI) Module User Guide Introduction ==

	== Introduction ==
	The Late Payment Interest (LPI) Module is designed to help organizations automatically calculate and bill interest on overdue customer balances.		The Late Payment Interest (LPI) Module is designed to help organizations automatically calculate and bill interest on overdue customer balances.

Line 17:		Line 15:
	----		----

	= Understanding Late Payment Interest =		== Understanding Late Payment Interest ==

	== What is Late Payment Interest (LPI)? ==		=== What is Late Payment Interest (LPI)? ===
	Late Payment Interest (LPI) is an interest charge imposed on overdue amounts when payment is not received within the specified grace period.		Late Payment Interest (LPI) is an interest charge imposed on overdue amounts when payment is not received within the specified grace period.

	LPI may arise from:		LPI may arise from:

	=== Statutory or By-Law Provisions ===		==== Statutory or By-Law Provisions ====
	Certain legislation and by-laws permit organizations to charge interest on overdue payments.		Certain legislation and by-laws permit organizations to charge interest on overdue payments.

Line 34:		Line 32:
	These organizations are generally permitted to impose interest on overdue maintenance fees, sinking fund contributions, and other charges when payment remains outstanding after the prescribed grace period.		These organizations are generally permitted to impose interest on overdue maintenance fees, sinking fund contributions, and other charges when payment remains outstanding after the prescribed grace period.

	=== Contractual Agreements ===		==== Contractual Agreements ====
	Businesses may also impose interest on overdue invoices when such charges are expressly stated in a contract, service agreement, sales agreement, or terms and conditions accepted by the customer.		Businesses may also impose interest on overdue invoices when such charges are expressly stated in a contract, service agreement, sales agreement, or terms and conditions accepted by the customer.

Line 81:		Line 79:
	The Highnix LPI Module supports both non-compounded and compounded interest calculations.		The Highnix LPI Module supports both non-compounded and compounded interest calculations.
	# '''Note:''' When '''LPI on LPI''' is enabled, '''new''' Late Payment Interest (LPI) invoices generated thereafter are flagged as eligible for future LPI calculations. If such an LPI invoice remains unpaid after the applicable grace period, its outstanding amount will be included in subsequent LPI calculations, resulting in compounded interest. LPI invoices generated before '''LPI on LPI''' was enabled remain non-compounded and are not retrospectively included in future LPI calculations.		# '''Note:''' When '''LPI on LPI''' is enabled, '''new''' Late Payment Interest (LPI) invoices generated thereafter are flagged as eligible for future LPI calculations. If such an LPI invoice remains unpaid after the applicable grace period, its outstanding amount will be included in subsequent LPI calculations, resulting in compounded interest. LPI invoices generated before '''LPI on LPI''' was enabled remain non-compounded and are not retrospectively included in future LPI calculations.
	= Configuring Late Payment Interest Terms =
			== Configuring Late Payment Interest Terms ==
	Before generating Late Payment Interest transactions, the interest terms must be configured.		Before generating Late Payment Interest transactions, the interest terms must be configured.

Line 103:		Line 102:
	Example:		Example:

	If the grace period is 30 days, interest begins only after the invoice remains unpaid for more than 30 days.		If the grace period is 30 days, interest begins only after the invoice remains unpaid for more than 30 days. That means, the interest will start from the next day after the grace period (30 days).

	=== Additional Grace Period ===		=== Additional Grace Period ===
	An optional additional period before interest calculations commence.		An optional additional period before interest calculations commence.

	This allows organizations to provide further flexibility to customers before interest charges are applied.		This allows organizations to provide further flexibility to customers before interest charges are applied. If there is any outstanding payment (even with after partial payment), after this additional grace period, the interest will start 1 day '''<u>after the Grace Period</u>''', not after the Additional Grace Period.

	=== Interest Calculation Basis ===		=== Interest Calculation Basis ===
Line 119:		Line 118:
	----		----

	= Defining the Late Payment Interest Item =		== Defining the Late Payment Interest Item ==
	Late Payment Interest is billed using a dedicated service item.		Late Payment Interest is billed using a dedicated service item.

	== Default Item ==		=== Default Item ===
	Highnix provides a predefined service item:		Highnix provides a predefined service item:

Line 135:		Line 134:
	This item is automatically available after installation.		This item is automatically available after installation.

	== Changing the LPI Item ==		=== Changing the LPI Item ===
	If a different item code or description is preferred, users may create a new service item and designate it as the official Late Payment Interest item.		If a different item code or description is preferred, users may create a new service item and designate it as the official Late Payment Interest item.

Line 147:		Line 146:
	----		----

	= Configuring Compounded Interest for a Customer =		== Configuring Compounded Interest for a Customer ==
	The system supports customer-specific control over compounded interest calculations.		The system supports customer-specific control over compounded interest calculations.

Line 172:		Line 171:
	----		----

	= Mixing LPI with Normal Invoice Items =		== Mixing LPI with Normal Invoice Items ==
	Late Payment Interest transactions are treated differently from normal sales transactions.		Late Payment Interest transactions are treated differently from normal sales transactions.

Line 302:		Line 301:
	----		----

	= Recommended Practice =		== Recurring LPI Invoice Generation ==

			The Recurring LPI Invoice feature allows users to automatically generate Late Payment Interest (LPI) invoices on a regular basis without having to create each invoice individually. This can save a significant amount of time, particularly for MCSTs, Management Corporations and property management companies that manage a large number of property units and need to apply late payment interest to overdue payments.

			Once the recurring LPI setup has been configured, the system can generate the applicable LPI invoices based on the selected date. This helps to simplify the LPI billing process and reduces the amount of manual work required.

			=== Preparation ===

			Before generating recurring LPI invoices, the recurring LPI setup must first be configured.

			# Navigate to '''Sales > Maintenance > Recurrent LPI'''.
			# Set up the recurring LPI by filling in the required information. This defines the rules and parameters that the system will use when generating the LPI invoices.
			# Review the information entered and click '''Save'''.

			Once the recurring LPI setup has been saved, the system is ready to generate the LPI invoices.

			=== Create Recurring LPI Invoices ===

			To generate the recurring LPI invoices:

			# Navigate to '''Sales > Transactions > Create and Print LPI Recurrent Invoices'''.
			# Select the required '''date'''. This is an important step because the system will calculate and generate the LPI based on the selected date. The selected date determines which outstanding amounts are subject to LPI according to the recurring LPI settings.
			# Click the '''Create LPI Invoice''' icon on the right to generate the applicable LPI invoices.
			# The system will generate the LPI invoices based on the recurring LPI configuration and the selected date.
			# Once the invoices have been generated, users can either '''print the invoices''' for distribution or '''email the invoices directly to the customers'''.

			The recurring LPI process eliminates the need to create LPI invoices individually and is particularly useful for property management operations where LPI invoices need to be generated regularly for multiple property units.

			== Recommended Practice ==
	To ensure accurate and compliant interest calculations:		To ensure accurate and compliant interest calculations:

System Setup

Khkoh — Tue, 25 Aug 2026 05:07:20 GMT

Manufacturing Defaults:

← Older revision		Revision as of 13:07, 25 August 2026
(One intermediate revision by the same user not shown)
Line 166:		Line 166:
	==== Dimension Defaults: ====		==== Dimension Defaults: ====

	# '''Dimension Required By After''': ~~Number~~ of days ~~before~~ a ~~Dimension expires~~.		# '''Dimension Required By After''': Dimensions Required By is a configuration setting that defines the number of days after which a dimension (such as a project, department, or cost center) is considered overdue or past its target date.

	==== Suppliers and Purchasing: ====		==== Suppliers and Purchasing: ====
Line 191:		Line 191:
	==== Manufacturing Defaults: ====		==== Manufacturing Defaults: ====

	# '''Work Order Required By After''': (Default is 20 days). If the Manufacturing Module is not implemented, leave the setting as default.		# '''Work Order Required By After''': (Default is 20 days).
			#* When you create a new work order, the system automatically calculates the default "Required By" date by adding this number of days to the current date.
			#* Purpose: It establishes an expected production lead time, letting the shop floor know when the finished goods need to be ready.
			#* Flexibility: This is just a baseline default. You can easily override the date manually whenever you create a specific work order. If the Manufacturing Module is not implemented, leave the setting as default.

	[[#Top\|<u>Go to Top</u>]]		[[#Top\|<u>Go to Top</u>]]