1.1. Operator View: Company > System Settings a. The System Settings is now separated into 3 sections: 1. General Settings

2. Season Pass Settings

3. E-Invoice Settings a. Introduced Auto Submission option. This option indicates that the system will submit E-Invoice to LHDN on behalf of the operator.

a. This new format is to ensure that each invoice / receipt number is unique and includes relevant information for tracking and processing purposes. b. Format: [yyMMdd][OperatorID][ReservedValue1][PaymentChannel][ReservedValue2][LastId] yyMMdd: Description: Represents the date of the invoice. Format: 'yy' is the last two digits of the year, 'MM' is the month (01-12), and 'dd' is the day of the month (01-31). Example: '240725' for July 25, 2024. OperatorID: Description: A unique identifier for the operator issuing the invoice. Format: A 4-digit numeric code. Example: '1234'. ReservedValue1: Description: A reserved field for future use. Format: A single digit (0-9). Example: '0'. PaymentChannel: Description: A code representing the payment channel used for the transaction. Format: A 2-digit numeric code. Example: '05' ReservedValue2: Description: Another reserved field for future use. Format: A single digit (0-9). Example: '0'. LastId: Description: The last inserted ID for the invoice, based on the payment channel. Format: A 4-digit numeric code. Example: '1234'. c. Sample: Invoice for casual & valet entries. Invoice Reference No.: 240722015100100052 Breakdown of the example Date: 240722 OperatorID: 0151 ReservedValue1: 0 PaymentChannel: 01 ReservedValue2: 0 LastId: 0052

d. Sample: Invoice for season pass purchase or renewal before payment 'INVOICE NO.' Description: This is the invoice number given to the customer before they make a payment.

e. Sample: Receipt for season pass purchase or renew after payment 'REF NO.' Description: This is the invoice number given to the customer before they make a payment. Usage: It is used to reference the invoice during the payment process. 'RECEIPT NO.': Description: This is the receipt number generated by the system after the customer has completed the payment for the invoice. Format: The receipt number follows the new format introduced, which includes specific components to ensure uniqueness and traceability.

3.1. Operator View: Company > Company Profile > E-Invoice a. The supplier profile is required to submit an E-Invoice to LHDN on the operator's behalf.

a. This applies to Record Portal LPR QR Payment Company Admin: Purchase & Renew Season Pass User View: Season Pass > Billing User View: Profile > E-Invoice b. Users must agree to the E-Invoice Consent to proceed further.

c. If the user clicks the disagree button, the system will display a message box informing them that they cannot proceed with the E-Invoice request.

d. Users can request an E-Invoice using either their personal or company profiles.

5.1. Operator View: Parking Rule > Parking Lot > Building a. Introduced a new QR code for E-Invoice Request Portal b. Operators can click to download or copy the QR code.

5.2. User View: E-Invoice Request Portal a. The E-Invoice Request Portal is designed for casual and valet users to request E-Invoice. b. The transaction can be traced by using the car plate number.

c. If a parking record is found, users can fill in the information to request an E-Invoice. The E-Invoice Request Workflow will apply here.

d. The system will display the requested date if it is determined that the user has already requested an E-Invoice.

e. The system will inform users that they can no longer request an E-Invoice if the parking record has exceeded the allowable request period.

a. Revamp UI: Search Page.

b. User can request a Receipt or an E-Invoice.

c. Revamp UI: Payment Review Page.

d. For Receipt option: UI for payment success record.

e. For E-Invoice option: UI for payment success record. The E-Invoice Request Workflow will apply here.

f. For Receipt option: UI for search after paid but yet to exit record.

g. For E-Invoice option: UI for search after paid but yet to exit record. The E-Invoice Request Workflow will apply here.

h. If the user has requested an E-Invoice in the E-Invoice Request Portal, the system will display the date and time when the user submitted their E-Invoice request.

7.1. User View: Account > Season Pass > Season Pass Application When a company admin purchases or renews a company pass, they can request an E-Invoice after the payment is made. The E-Invoice Request Workflow will apply here. Additionally, company admins have the option to skip the E-Invoice request process to complete the payment process.

8.1. Operator View: Record > Payment > Entry Basis & Valet a. The E-Invoice Status "Requested" indicates that the buyer has already submitted the necessary information for this transaction to be generated as an E-Invoice.

b. Introducing "E-Invoice Status" filter: operator can choose to view records that are marked as requested.

a. Auto Submission to LHDN on behalf of the operator. Consolidated submissions will be processed after the period for requesting an E-Invoice has expired. User-requested submission will be processed within 5 to 10 minutes after the user submits the request.

a. The default maximum value has been adjusted from MYR 9999.99 to MYR 999999.99.

a. Added e-Invoice consent.

b. Company admins can now request e-invoices for Company Group Pass purchases

Added a search function for easier parking site lookups.

Receipts now include an e-invoice QR Code, allowing users to scan for easy e-invoice requests. Invoice numbers and user payment details have also been added to the receipts.