Xilnex-AutoCount - Master Data Sync (Creditors & Debtors)
Master data synchronization ensures your vendor (creditor) and customer (debtor) information flows seamlessly from AutoCount to Xilnex, creating a single source of truth across both systems.
What Is Master Data Sync?
Master data refers to core information that doesn't change frequently:
- Creditors (Vendors/Suppliers) – Company name, vendor code, contact details, payment terms, address
- Debtors (Customers) – Company name, customer code, registration, contact details, credit terms, address
By synchronizing this data, you ensure:
- Vendors are consistent across purchasing and GRN processes
- Customers are consistent across sales and POS transactions
- Changes in AutoCount automatically reflect in Xilnex
Creditor Sync (AutoCount → Xilnex)
What Gets Synchronized
When a creditor is created or updated in AutoCount, the following fields sync to Xilnex:
Field | |
Vendor Identifier Code | Unique vendor code (e.g., "400-T001") |
Company Name | |
Business Registration Number | |
Email | |
Phone / Mobile | |
Address | |
Payment Terms | Credit terms (e.g., "C.O.D.", "Net 30") |
Why This Matters
- Purchasing: When you select a vendor in Xilnex PO/GRN, all details are pre-populated from AutoCount
- Invoice Matching: Supplier information matches automatically, reducing manual entry
- Compliance: A single version of vendor information across systems
Step-by-Step: Posting Creditors
Step 1: Create a New Creditor in AutoCount
- Open AutoCount
- Go to A/P > Creditor > New
- Fill in creditor details:
- Creditor Account: 400-1001
- Company Name: ABC TRADING
- Business Reg. No.: 12983829374
- Email: abc@email.com
- Mobile: 0123456789
- Address: 123, JALAN BESAR
- Terms: C.O.D. or Net 30
- Save
Step 2: Access Xilnex Autocount Integration Program
- Open Xilnex Application (ClassicPOS)
- Go to Main Menu > Xilnex AutoCount Integration
- Log in with Xilnex credentials
- Log in to AutoCount when prompted
- Select the account book
Step 3: Post the Creditor
In the integration interface:
Document: Select Creditor
- Date From: 05-11-2025 (creditor creation date)
- Date To: 05-11-2025
- Include Flagged Data: Leave unchecked (for new data)
- Click "Generate"
- Review the creditor(s) listed
- Click "Post"
- Status shows "Completed outbound data posting"
Step 4: Verify in Xilnex
- In Xilnex, go to Vendor > Search
- Search by vendor code 400-1001
- Confirm all details match AutoCount:
- Vendor name, code, email, mobile, address, terms
Result:
The vendor is now available in Xilnex for purchase orders and GRN processing.
Debtor Sync (AutoCount → Xilnex)
What Gets Synchronized
When a debtor is created or updated in AutoCount, the following fields sync to Xilnex:
Field | Purpose |
Client Identifier Code | Unique customer code (e.g., "300-S001") |
Company Name | |
Registration Code | Tax ID or business registration |
Email | |
Mobile | |
Address | |
Credit Terms | Payment terms (e.g., "C.O.D.", "Net 30") |
Why This Matters
- Sales Invoicing: When you select a customer in Xilnex sales, all details pre-populate
- Invoice Accuracy: Customer information matches, reducing errors
- Consistency: Single source of truth for customer data across accounting and POS
Step-by-Step: Posting Debtors
Step 1: Create a New Debtor in AutoCount
- Open AutoCount
- Go to A/R > Debtor > New
- Fill in debtor details:
- Debtor Account: 300-5001
- Company Name: WONDERS SDN BHD
- Business Reg. No.: 129839487449
- Email: wondersdemoxxx@gmail.com
- Mobile: 0123456789
- Address: 1, JALAN BESAR
- Terms: C.O.D. or Net 30
- Save
Step 2: Access Xilnex Autocount Integration Program
- Open Xilnex Application (Classic POS)
- Go to Main Menu > Xilnex AutoCount Integration
- Log in with Xilnex credentials
- Log in to AutoCount when prompted
- Select the account book
Step 3: Post the Debtor
- In the integration interface:
- Document: Select Debtor
- Date From: 05-11-2025 (debtor creation date)
- Date To: 05-11-2025
- Include Flagged Data: Leave unchecked
- Click "Generate"
- Review the debtor(s) listed
- Click "Post"
- Status shows "Completed outbound data posting"
Step 4: Verify in Xilnex
- In Xilnex, go to Client > Search
- Search by client code 300-S001
- Confirm all details match AutoCount:
- Company name, code, email, mobile, address, terms
Result:
The customer is now available in Xilnex for sales invoicing.
Best Practices
- Sync regularly: After adding vendors or customers in AutoCount, post them immediately to Xilnex
- Verify terms: Ensure payment terms are identical in both systems
- Use unique codes: Keep vendor and customer codes consistent
- Update existing records: If you update a vendor/customer in AutoCount, re-post with "Include Flagged Data" enabled
Related Articles
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 - 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 - 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 - 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: Open your web browser and ...
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. ...