Enforce Buyer Details for E-Invoicing

Enforce Buyer Details for E-Invoicing

Idea
Individual E-Invoice for Specific Classification Codes
When certain Classification Codes are assigned to an item or service, buyer details become mandatory during setup. In this case, the engine will prevent consolidation and issue an individual E-Invoice instead of a Consolidated E-Invoice.

Info
InfoLocation in X3 Portal: Integration >Malaysia LHDN E-Invoice > E-Invoice Settings > Maintainence
This setting defines which Classification Codes require buyer details before submission. When enabled, the the system (such as Classic POS) performs a validation on each transaction:
  • If the Classification Code matches the configured list and buyer details are provided, the transaction proceeds and an individual E-Invoice is issued.
  • If the Classification Code matches the configured list but buyer details are missing, the transaction is blocked and cannot be committed.
  • If the Classification Code does not match the configured list, the transaction follows the standard process and may be included in a Consolidated E-Invoice.
Alert
Important Note: This feature may require an application version update in order to be supported. Please reach out to Xilnex Support for further clarification.
    • Related Articles

    • How to Resolve Invalid E-Invoices in E-Invoicing Dashboard

      E-Invoices are validated directly by the LHDN Malaysia server. When a submission is marked as invalid, the server will return an error message (also known as the “Invalid Reason”). Taxpayers are expected to review this message and take corrective ...
    • Enforcing Individual E-Invoice for Classification Code

      Under LHDN E-Invoice requirements, certain activities and transactions must be issued as Individual E-Invoices for each transaction, where consolidated E-Invoice submission is not permitted. For these activities, taxpayers are required to obtain full ...
    • Enforcing Individual E-Invoice Submission for Sales Above RM10,000

      Effective 1 January 2026, all single sales transactions with a total value exceeding RM10,000 must be submitted as an Individual e-Invoice. This enforcement is implemented to ensure compliance with LHDN e-Invoice regulatory requirements. Compliance ...
    • Getting Started with Xilnex E-Invoicing

      Read Me First Before we begin, please review the following important points: Xilnex product is directly integrated with IRBM's API. Upon complete setup, your document may be submitted to IRBM via the API. All testing should be conducted in the ...
    • Enable E-Invoicing via Xilnex Portal

      Xilnex Portal is the central platform where all configurations and settings for your system can be managed. Designed for flexibility and ease of use, the portal allows you to set up, monitor, and maintain various aspects of your business operations ...
    • Recent Articles

    • Managing Lark User Email Mapping in Xilnex for Lark

      Overview The Users card matches each Xilnex user to their Lark account by email. This is what lets features like Permission Approvals and Document Approvals deliver Lark cards to the right person. This article covers how to review the mapping and fix ...
    • E-Wallet and Credit Card Payment - Recheck Status & Force Complete

      This guide walks you through what to do when a payment goes through on the terminal or e-wallet, but Classic POS fails to commit sales. When Does This Happen? During payment, Classic POS will show a "Connecting to Ewallet party..." or processing ...
    • E-Journal for BIR Compliance (Philippines)

      Overview The E-Journal feature generates a .txt file that complies with BIR (Bureau of Internal Revenue) requirements in the Philippines. This feature is available only for the Philippines COM. Users from other countries' COMs will not be able to ...
    • Disconnecting or Reconnecting Xilnex for Lark

      This article covers how to disable a template, fully disconnect the integration from Lark, and reconnect it again. Disable a Template Turning a base off only stops that one base, everything else keeps syncing, and none of your existing data in Lark ...
    • Creating a Base in Xilnex for Lark

      Overview This article walks you through creating a base for a template, giving end users access to it in Lark, and verifying data is syncing correctly. Xilnex for Lark must already be connected before you start. If the Templates card isn't accessible ...
    • Popular Articles

    • Basic - How to create a voucher-coupon

      Voucher and coupon definition Voucher can be generated in bulk and can be used once Coupon can only be created one at a time (reusable code) and can be use multiple times Pre-voucher / coupon setup There are 2 things need to be prepared before we can ...
    • Understanding DuitNow QR Payment in ClassicPOS

      Introduction This document introduces the DuitNow QR payment feature available in the Xilnex Retail POS, enabling merchants to accept payments conveniently through Malaysia's national QR payment standard. The integration of DuitNowQR simplifies the ...
    • Intermediate - How to Configure and Use Approval Settings in Purchase Orders (PO)

      1.0 What is approval setting In general, "approval setting" refers to the configuration or process by which a request, action, or change must be reviewed and approved before it proceeds. The term is often used in business, software applications, and ...
    • Buy 2 for Special Price Promotion

      Use Case: Stock clearance, seasonal offers, or spotlight products. From the sample screenshot above, this promotion requires 2 items to trigger. If only 1 Milk Tea is added to the sales list, no discount will apply since the condition of 2 items is ...
    • Creating Delivery Type for Sales in Classic POS

      How to Create Delivery Type 1. Access to the [System Configuration] 2. Select the [Sales] section 3. In the [All Outlets] tab, look for the 'Delivery Type' 4. Click on the [Configure] In the Delivery Type Setup form: 1. Enter the Delivery Type. 2. ...