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.