AutoCount scripting

AutoCount Scripting — Custom Validation, Business Rules & Automation for AutoCount

AutoCount scripting is a customisation service for Malaysian SMEs that adds custom validation rules, business logic enforcement, and workflow automation directly into AutoCount's document screens — without developing or installing a separate plugin. Scripts are written inside AutoCount's built-in Scripting module and execute on document events: before a document saves, after it saves, when an item is selected, when a field value changes, or when a button is clicked. The script checks conditions, enforces rules, auto-populates fields, blocks incorrect entries, calculates values, or triggers actions — all in real time as your staff work in AutoCount. Lightweight, fast, no external dependencies. From RM300 per script.

Why AutoCount Scripting?

Not every customisation needs a full plugin. Many business requirements are simple rules that need to be enforced at the document level — "don't allow this invoice to save unless a salesman is assigned," "auto-fill the delivery address when the customer is selected," "block a sales order if the item is on hold," "calculate a handling fee based on item weight." These are validation and automation rules, not new modules. Building a plugin for a single rule is overkill — expensive and slow. AutoCount scripting handles these requirements directly inside the document screen using the built-in scripting engine. Write the rule once, attach it to the document event, and it runs every time. No plugin installation, no separate files, no system overhead.

What Scripting Can Do

Extra Validation Before Save

Add custom validation checks that run before a document is saved. AutoCount's standard validation checks for required fields and basic data integrity — but your business may need more. Block a Sales Invoice from saving if the credit term exceeds 90 days for a new customer. Prevent a Purchase Order from saving if the total exceeds the department's monthly budget. Reject a Delivery Order if the delivery date is earlier than the production date. Display a clear error message telling the user exactly what needs to be corrected. The document cannot be saved until the validation passes — enforced at the system level, not by staff discipline.

Extra Business Rules

Enforce business rules that AutoCount doesn't have built in. A minimum order quantity per item — block the document if any line item falls below the MOQ. A maximum discount percentage per salesman level — junior salesmen cannot exceed 10%, senior salesmen cannot exceed 20%. A mandatory project code for all purchase documents above RM5,000. A rule that prevents selling certain items to certain customer categories. These are your business policies — scripting turns them from verbal instructions into system-enforced rules that cannot be bypassed.

Auto-Fill & Auto-Calculate

Automatically populate fields when a trigger event occurs. When a debtor is selected, auto-fill the delivery address, contact person, and payment terms from the debtor master. When an item is selected, auto-fill a custom description, a recommended selling price, or a promotional note from UDF fields. When a quantity is entered, auto-calculate a volume discount, a weight-based surcharge, or a tiered pricing adjustment. Staff don't need to look up or calculate these values manually — the script fills them in instantly.

Field Change Triggers

Execute logic when a specific field value changes. When the salesman field changes, recalculate commission estimates on the document. When the warehouse location changes, update available stock display. When the payment method changes, apply or remove a card surcharge. When a date field changes, validate against business calendar rules (no delivery on public holidays). These triggers react to user input in real time — providing instant feedback and automation as the document is being filled in.

Conditional Alerts & Warnings

Display warning messages or alerts based on conditions without blocking the document. Show a warning when a customer's outstanding balance is approaching their credit limit — but still allow the save. Alert the user when an item hasn't been sold in 90 days — suggesting a stock clearance price. Notify the user when a supplier's last purchase was over 6 months ago — prompting them to verify pricing. Warnings inform without obstructing — the user sees the alert and decides how to proceed.

Cross-Field Validation

Validate relationships between multiple fields on the same document. Ensure the delivery date is after the order date. Ensure the discount percentage doesn't result in a selling price below cost. Ensure the quantity ordered doesn't exceed the available stock for that location. Ensure the project code matches the department code. Cross-field validation catches logical errors that single-field validation misses — preventing documents that are technically complete but logically wrong.

Automate Repetitive Tasks

Automate small tasks that staff perform manually on every document. Auto-generate a reference number based on a custom format. Auto-set the document date to the last working day of the month for month-end entries. Auto-copy remarks from the sales order to the delivery order during transfer. Auto-stamp the user's name and timestamp into a UDF field every time the document is modified. Each automation saves seconds per document — but across hundreds of documents per month, the cumulative time saving is significant.

Scripting vs Plugin — When to Use Which

Use scripting when:

The requirement is a validation rule, a business logic check, an auto-fill, or a small automation attached to an existing AutoCount screen. No new screens needed. No new database tables needed. No new menus needed. The logic runs on a document event (before save, after save, field change) and affects the current document only.
Use plugin development when:

The requirement needs a new screen, a new workflow, new database tables, cross-account book processing, multi-database operations, or functionality that goes beyond what document-level scripting can handle.
Scripting is lighter, faster, and cheaper — from RM300. Plugin development is more powerful but starts from RM1,600. Many businesses use both — scripting for validation rules and auto-fill, plugins for new modules and workflows.

Common Scripting Examples for Malaysian Businesses

Wholesale & Distribution

Enforce minimum order quantity per item. Auto-apply tiered pricing based on order volume. Block sales to customers with overdue invoices exceeding a custom threshold. Auto-fill delivery zone and freight charges based on customer postcode.

Retail

Validate discount limits per cashier level. Auto-calculate loyalty points based on transaction amount. Block selling items below cost price. Display stock availability alert when quantity entered exceeds current balance.

Manufacturing

Enforce mandatory batch number entry on stock documents. Validate that raw material items cannot be sold directly (production use only). Auto-calculate wastage allowance based on item type. Block purchase orders for items with existing stock above maximum level.

Service Businesses

Enforce mandatory project code on all invoices. Auto-fill service description from item master UDF fields. Validate that billing amounts match approved quotation amounts. Block invoicing for projects marked as "on hold."

How It Works

1. Describe the Rule

Tell us the rule, validation, or automation you need — in plain business language. "Don't allow saving if X." "Auto-fill Y when Z is selected." "Calculate A based on B and C." We translate your business requirement into scripting logic.

2. We Write & Test the Script

We write the script using AutoCount's built-in scripting engine, attach it to the correct document event, and test it against your data and scenarios. The script is validated to ensure it handles edge cases — empty fields, zero quantities, new customers without history.

3. We Deploy to Your System

The script is deployed into your AutoCount system — attached to the relevant document type. We demonstrate the script in action, verify it works in your production environment, and confirm your team understands what it does and when it triggers.

Pricing

From RM300 per script. Each script addresses one rule, validation, or automation task. Simple single-field validations and auto-fills are at the base rate. Complex multi-field cross-validations, conditional calculations, and multi-step automation may be quoted based on complexity.

Requirements

AutoCount Scripting requires AutoCount Pro Edition or AutoCount Premium Edition — the Scripting module is included in these editions. AutoCount Basic, Express Plus, and Account Plus editions do not include the Scripting module.

What's Included

✅ Custom Validation Rules (Before Save, After Save)

✅ Business Logic Enforcement (Block, Warn, Alert)

✅ Auto-Fill & Auto-Calculate on Field Events

✅ Field Change Triggers (Real-Time Reaction)

✅ Conditional Alerts & Warnings

✅ Cross-Field Validation

✅ Repetitive Task Automation

✅ Script Development, Testing & Deployment

✅ Requires AutoCount Pro or Premium Edition (Scripting Module)

✅ From RM300 Per Script

✅ Compatible with AutoCount Accounting 2.2