Xilnex-AutoCount - Portal Configurations

Xilnex-AutoCount - Portal Configurations

All integration rules and configurations are managed through the Xilnex Web Portal. This guide walks you through accessing the portal and introduces the three core configuration areas.


Accessing the Xilnex Web Portal:

  1. Open your web browser and navigate to: https://portal.xilnex.com/Integration.
  2. Log in with your Xilnex account credentials (email and password)
  3. From the main menu, navigate to: Integration > AutoCount.

  4. You are now in the AutoCount integration configuration area.


The 3 Core Configuration Areas

Configuration Sequence

Always Configure in this order:
  1. Document Type: Enable modules and documents.
  2. Account Code: Link GL accounts and payment methods.
  3. Document Fields: Map and customize field formats.
Ready for Posting!


All integration setup revolves around three key sections. Each controls a different aspect of how Xilnex data is translated into AutoCount documents:

1. Document Type

Purpose: Define which Xilnex modules are integrated and how each document behaves during posting.
  1. Select which modules to activate (Sales, Purchase)
  2. Enable or disable specific document types within each module
  3. Configure posting options (e.g., multi-currency support, GRN verification, date handling)
When You Use It: First step in setup – you enable the modules and documents you need before posting.

2. Account Code Mapping

Purpose: Map Xilnex transaction components to AutoCount GL (General Ledger) accounts and payment methods.
  1. Link sales types, item categories, and ownership to GL accounts (e.g., "Food Sales" → GL 500-5000)
  2. Map payment methods (Cash, Card, E-Wallet) to AutoCount payment codes
  3. Configure variance and discount accounts for handling differences and adjustments
When You Use It: Second step – set up the GL account assignments so transactions post to the correct ledgers.

3. Document Fields

Purpose: Specify how each Xilnex field corresponds to AutoCount document fields during posting.
  1. Map header-level fields (e.g., Document No., Customer Code, Description)
  2. Map detail-level fields (e.g., Item Description, Project Code, Department)
  3. Create custom document numbering by combining fixed values and variables (e.g., CS-PG-20251001)
  4. Use auto-generated default templates as a starting point
When You Use It: Third step – customize how data appears in AutoCount documents.
    • Related Articles

    • Xilnex-AutoCount - Installation & System Requirements

      This section explains how to integrate the Xilnex Retail Management System with the external AutoCount Accounting System to automate data posting from operations to accounting. System Requirements Before you begin integrating Xilnex with AutoCount, ...
    • Xilnex-AutoCount - What Gets Synchronized?

      The Xilnex–AutoCount integration establishes a seamless, automated data exchange between your Xilnex Retail Management System and AutoCount Accounting System, so your operational transactions are automatically reflected in your financial records. 1. ...
    • Xilnex-AutoCount - Document Type Mapping

      This guide explains how to activate and configure Document Types—which modules and documents are integrated and how they behave during posting. 1. What Is Document Type Configuration? Document Type defines: Which Xilnex modules (Sales, Purchase) are ...
    • Xilnex-AutoCount - Account Code Mapping

      Account Code Mapping connects Xilnex transaction components (sales types, item categories, payment methods) to AutoCount GL accounts and payment codes. This ensures transactions post to the correct financial accounts. What Is Account Code Mapping? ...
    • Xilnex-AutoCount - Posting Cash Sales

      Cash Sales posting consolidates daily retail POS transactions and posts them to AutoCount Cash Book Entry, providing accurate cash-flow visibility and daily revenue tracking. What Is Cash Sales Posting? Cash Sales posting: Consolidates all retail ...
    • 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. ...