Xilnex-AutoCount - Posting Cash Sales

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:
  1. Consolidates all retail cash-and-carry transactions from Xilnex for a given period
  2. Aggregates by store and date into a single Cash Book Entry document
  3. Posts to AutoCount for cash-flow reporting and revenue recognition
  4. Excludes credit-term sales (which are handled separately as invoices)
Info
Result:
Your daily POS transactions are reflected in AutoCount's financial records immediately.

Supported Document Types

The Cash Sales module supports:
  1. Cash sales (Retail) – Standard POS cash sales
  2. Optional: Return sales (if enabled in Document Type configuration)
  3. Optional: Multi-currency sales (if enabled)

Prerequisites

Before posting cash sales, ensure:
  1. Cash Sales document type is Active in Document Type configuration
  2. All GL accounts are mapped in Account Code configuration (sales account, rounding, discounts)
  3. All payment methods are mapped (Cash, Card, E-Wallet, etc.)
  4. Document Field mapping is complete (voucher number format, description, etc.)
  5. At least one day of POS transactions exists in Xilnex

Step-by-Step: Posting Cash Sales

Step 1: Open the Integration Program
  1. Open Xilnex Application (Classic POS)
  2. Go to Main Menu > Xilnex AutoCount Integration
  3. Log in with Xilnex credentials
  4. Log in to AutoCount when prompted
  5. Select the account book
  6. The integration interface appears
Step 2: Select Cash Sales Document
  1. In the integration interface:
    1. Document: Select Cash Sales (dropdown)
    2. Doc Type: Select Cash Sales (Retail) (or other applicable type)
    3. Ownership: Select ownership (or All ownerships)
    4. Outlet: Select the store/outlet (or All stores)
Step 3: Set Date Range
  1. Date From: Enter the start date of transactions to post (e.g., 23-10-2025)
  2. Date To: Enter the end date (e.g., 23-10-2025)
Idea
Tip:
To post a single day, set both dates the same. To post multiple days, use a range.
Step 4: Choose Include Flagged Data
  1. Unchecked (recommended for first post) – Generates only new, never-posted data
  2. Checked – Includes data that was posted before (for re-posting or corrections)
Step 5: Generate Data
  1. Click "Generate"
  2. System loads all transactions matching your criteria
  3. Status bar shows: "Data population complete"
  4. A list appears showing:
    1. Voucher No. (e.g., CS-PG20251023)
    2. Voucher Date
    3. Amount
    4. Currency
    5. Description
Step 6: Review Generated Data
Verify that:
  1. All expected sales are listed
  2. Amounts and dates are correct
  3. No duplicates are present
Step 7: Post to AutoCount
  1. Click "Post"
  2. System creates Cash Book Entry document(s) in AutoCount
  3. Status bar shows: "Completed outbound data posting"
  4. Results appear with status for each posting:
    1. ✓ Success – Posted successfully
    2. ✗ Error – Check error message
Step 8: Verify in AutoCount
  1. Open AutoCount
  2. Go to General > Cash Book Entry (or Bank > Receipt Voucher)
  3. Search for voucher number (e.g., CS-PG20251023)
  4. Confirm:
    1. Voucher amount matches Xilnex
    2. Payment breakdown is correct
    3. Description and fields match mapping
Info
Result:
Daily sales are now posted to AutoCount, updating cash position and revenue accounts.

Example Posting

Xilnex Cash Sales for Oct 23, 2025:
  1. Store: PG (Project Group – store code)
  2. Total Sales: 1,200 MYR
  3. Breakdown:
    1. Food sales: 700 MYR
    2. Beverage sales: 300 MYR
    3. Discount given: -100 MYR
    4. Payments: Cash 1,200 MYR
AutoCount Result:
Cash Book Entry created:
  1. Voucher No.: CS-PG-20251023
  2. Date: 23-10-2025
  3. Description: (from Document Field mapping)
  4. GL Postings:
    1. DR 500-5000 (Food Sales) – 700
    2. DR 500-6000 (Beverage Sales) – 300
    3. CR 520-0000 (Discount) – 100
    4. CR 320-0000 (Cash Account) – 1,200
Notes
Encounter an errors?
Click here to troubleshoot the common posting errors

    • Related Articles

    • Xilnex-AutoCount - Troubleshooting Common Posting Errors

      Cash Sales Error Cause Solution "Missing mapping" A GL account or payment method wasn't mapped Go to Account Code, add the missing mapping, re-post "No data generated" No transactions in the date range Verify date range is correct and POS has ...

    • 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 - 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 - 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? ...

    • 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. ...