AutoCount data importing / Malaysia

AutoCount Import Data: Find the Right Method

Move business data into AutoCount with an approach that fits your file structure and source system. Compare spreadsheet imports, scheduled workflows, XML and custom API connections.

Malaysian business team preparing sales, purchase and stock records for AutoCount data import
A practical starting point

Choose a data import method based on your source

Data can arrive as a spreadsheet, supplier document, XML export or a recurring feed from another system. The best approach depends on which records must reach AutoCount, how often they arrive and what validation is required.

LESS REPETITION

Reduce retyping

Use an appropriate import method to transfer supported data rather than repeatedly entering the same records.

BETTER MATCHING

Map the correct fields

Confirm customer codes, item references, dates, quantities and transaction types before importing.

CONTROLLED ROLLOUT

Test before scale

Use representative sample files and reconcile the results before processing a full batch.

VERSION CHECK

Confirm compatibility

Supported source formats, document types, permissions and licensing depend on the chosen AutoCount solution.

Five ways to evaluate

AutoCount import methods compared

Import methodTypical sourceWhen to consider it
Universal Import PluginExcel / CSV / TXT files with configured mappingRepeatable file imports where column mapping is required
AutoCount Import PluginSupplier or third-party document layoutsIncoming documents requiring format or document-specific configuration
Integrator PluginScheduled local or FTP folder importsRepeat files arriving on an agreed schedule
Third-Party XML ModuleCompatible XML source filesExternal systems that export supported XML documents
API integrationCustom system-to-system data exchangeProjects needing scoped data transfer and field validation
Important: These are different tools and workflows, not interchangeable features. Actual document coverage depends on plugin version and setup. Importing data also does not automatically validate or submit an e-Invoice to LHDN.
Genuine AutoCount screenshots

Explore each import workflow

These original AutoCount screenshots are retained from the existing article. Select a screenshot to open its full-size version.

01 / SPREADSHEET MAPPING

Universal Import Plugin

Bring supported Excel, CSV or TXT data into a configured import process. Map source columns to AutoCount fields and review the outcome.

Suitable when: You receive repeatable spreadsheets with consistent headers.

View related AutoCount guide

Universal Import plugin source-to-destination field mapping
Universal Import plugin source-to-destination field mapping — click to enlarge
Excel data formatted for AutoCount Universal Import
Excel data formatted for AutoCount Universal Import — click to enlarge
AutoCount Universal Import configuration example
AutoCount Universal Import configuration example — click to enlarge
02 / DOCUMENT IMPORT

AutoCount Import Plugin

Assess data received from suppliers, customers or external systems. Review document layout and mapping requirements before implementation.

Suitable when: Incoming documents need a dedicated import configuration.

View related AutoCount guide

AutoCount Import Plugin example screen
AutoCount Import Plugin example screen — click to enlarge
AutoCount third-party import data interface
AutoCount third-party import data interface — click to enlarge
03 / SCHEDULED PROCESSING

Integrator Plugin

Assess scheduled imports using configured local or FTP folders and the relevant supported data types.

Suitable when: Repeat files arrive regularly and staff want a more predictable processing workflow.

AutoCount file import from local or FTP source
AutoCount file import from local or FTP source — click to enlarge
AutoCount Integrator Plugin interface
AutoCount Integrator Plugin interface — click to enlarge
04 / XML EXCHANGE

Third-Party XML Module

Review compatible XML exports and the document types that AutoCount can accept for the chosen configuration.

Suitable when: An external business system already produces suitable XML records.

AutoCount Third-Party XML Module settings
AutoCount Third-Party XML Module settings — click to enlarge
AutoCount Third-Party XML data import screen
AutoCount Third-Party XML data import screen — click to enlarge
AutoCount Third-Party XML document processing
AutoCount Third-Party XML document processing — click to enlarge
Custom integration projects

Need a direct system connection instead?

When a file-based import is not suitable, an AutoCount API integration may be worth assessing. Define the source system, records, field mapping, error handling and required frequency before selecting an architecture.

Read the AutoCount API integration overview for related requirements.

Not every source system or document type will support direct real-time updates. Confirm feasibility during technical scoping.

Malaysian IT consultant and finance team discussing AutoCount API integration requirements
Implementation workflow

Three checks before importing live data

01 / PREPARE

Review the source

Identify required document types, file formats, field definitions, frequency and sample records.

02 / CONFIGURE

Map and test

Confirm the plugin or integration scope. Test representative files and resolve validation errors.

03 / RECONCILE

Verify the results

Check imported counts, amounts, duplicates and rejected records before wider rollout.

Safety check: Back up live data and agree on duplicate prevention, failure handling and reprocessing procedures before running any high-volume import.

For larger system transitions, review our AutoCount data migration service. For a step-by-step spreadsheet procedure, see theAutoCount Excel import user guide. For a product comparison, read AutoCount Excel vs Universal Import Plugin.

Frequently asked questions

AutoCount data import FAQs

What file formats can AutoCount import?

Supported formats depend on the selected tool and document type. File-based options may support Excel, CSV or TXT, while XML and API workflows require their own compatible setup.

Can I import Excel data without the Universal Import Plugin?

AutoCount also documents an Excel import workflow for supported data. The choice depends on the destination module and whether configurable mapping is needed.

Can imports run on a schedule?

Scheduled processing can be assessed through an Integrator Plugin setup using supported local or FTP folders. Confirm the actual schedule and supported document types.

Does imported invoice data mean it is already validated by LHDN?

No. Data import and e-Invoice submission/validation are separate. Review the relevant e-Invoice workflow and MyInvois status.

What if an import contains errors or duplicates?

Review the error details and source data, then confirm the mapping and duplicate-handling rules before retrying. Do not re-import blindly.

SL Software Solutions

Plan the right AutoCount import workflow

Share the AutoCount version, source-system details, document types and a sample file with personal information removed. We can discuss which supported approach fits the required workflow.

Discuss your import requirements

What to prepare

Bring file samples, target transaction types, required import frequency, expected volumes and the checks needed after importing.