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.

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.
Reduce retyping
Use an appropriate import method to transfer supported data rather than repeatedly entering the same records.
Map the correct fields
Confirm customer codes, item references, dates, quantities and transaction types before importing.
Test before scale
Use representative sample files and reconcile the results before processing a full batch.
Confirm compatibility
Supported source formats, document types, permissions and licensing depend on the chosen AutoCount solution.
AutoCount import methods compared
| Import method | Typical source | When to consider it |
|---|---|---|
| Universal Import Plugin | Excel / CSV / TXT files with configured mapping | Repeatable file imports where column mapping is required |
| AutoCount Import Plugin | Supplier or third-party document layouts | Incoming documents requiring format or document-specific configuration |
| Integrator Plugin | Scheduled local or FTP folder imports | Repeat files arriving on an agreed schedule |
| Third-Party XML Module | Compatible XML source files | External systems that export supported XML documents |
| API integration | Custom system-to-system data exchange | Projects needing scoped data transfer and field validation |
Explore each import workflow
These original AutoCount screenshots are retained from the existing article. Select a screenshot to open its full-size version.
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.
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.
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.
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.
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.

Three checks before importing live data
Review the source
Identify required document types, file formats, field definitions, frequency and sample records.
Map and test
Confirm the plugin or integration scope. Test representative files and resolve validation errors.
Verify the results
Check imported counts, amounts, duplicates and rejected records before wider rollout.
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.
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.
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 requirementsWhat to prepare
Bring file samples, target transaction types, required import frequency, expected volumes and the checks needed after importing.









