Does AutoCount import from Excel directly?

Yes. The Purchases module accepts Excel/CSV/TXT imports with column mapping, and the Universal Import Plugin handles larger structured files with error-record export. Exact menus vary by version — your AutoCount dealer can confirm what your installation includes.

Why does my AutoCount import keep failing?

The four causes we see most: the supplier (creditor) does not exist yet, the document date falls outside the book’s fiscal year, columns are mismapped or date formats are inconsistent, and duplicate document numbers from re-running a partially imported file.

Do I still have to key in the data before importing?

That is the catch — an Excel import only saves time if the Excel already exists. If your starting point is a pile of PDFs, photos and handwritten bills, someone still keys every line into the spreadsheet first. That step is what BalanceNow removes: AI reads the documents and produces the entries, your accountant approves, and the result posts to AutoCount directly or exports as an import-ready file.

Is there a way to skip the import file entirely?

Yes — for AutoCount Cloud, approved entries post through the official API; for on-premise AutoCount, they post with one click, no export-import. The import-file route stays available whenever you want full manual control.

Guide

How to Import Purchase Invoices into AutoCount from Excel.

Two routes exist: the built-in Excel import and the Universal Import Plugin. Both work — when the file is clean and the traps below are avoided. Written by a team that integrates with AutoCount every day.

Book a Demo WhatsApp us

The Process

The import, in five steps

Prepare your Excel/CSV file: first row = column names, one invoice line per row (supplier code, invoice number, date, amounts, account).
In AutoCount, open the Purchases module and choose Import (or install the Universal Import Plugin via Tools → Plug-In Manager for bulk imports).
Map each file column to the matching AutoCount field — invoice number, date, creditor, amounts.
Run the import, then review the error records AutoCount reports (the plugin lets you export them for correction).
Verify a sample in A/P Invoice Entry: supplier, invoice number, date, amount, account.

Menus and options vary slightly by AutoCount version and installed plugins — your AutoCount dealer can confirm the specifics of your installation.

Field Experience

Why AutoCount imports fail

The four causes behind most rejected files and silent data damage — the same rules our own integration has to respect.

The creditor does not exist yet

AutoCount will not attach an invoice to a supplier it has never met. Create the creditor record first — every missing supplier fails its rows.

Date outside the fiscal year

Document dates must fall inside the book's fiscal year. A January invoice imported into a book whose year has not been opened (or was closed) gets rejected.

Column mapping and date formats

Mismapped columns and inconsistent date formats (dd/mm vs mm/dd, text vs date cells) are the most common silent corrupters — the import "works" but the data is wrong.

Duplicate document numbers

Re-running a file after a partial failure creates duplicates unless you strip the rows that already went in. Track what actually imported before retrying.

The Honest Part

The import file is not the hard part

An Excel import only saves time if the Excel already exists. For most firms, the real cost is upstream: someone keys a month of PDFs, photos and handwritten bills into that spreadsheet, line by line. That step is what BalanceNow’s AutoCount integration removes — AI reads the documents, your accountant approves, and entries post to AutoCount directly or come out as an import-ready file in the AutoCount schema. The creditor-exists and fiscal-year rules above? Handled before you ever see them.

FAQ

Import questions, answered straight

Does AutoCount import from Excel directly?: Yes. The Purchases module accepts Excel/CSV/TXT imports with column mapping, and the Universal Import Plugin handles larger structured files with error-record export. Exact menus vary by version — your AutoCount dealer can confirm what your installation includes.
Why does my AutoCount import keep failing?: The four causes we see most: the supplier (creditor) does not exist yet, the document date falls outside the book’s fiscal year, columns are mismapped or date formats are inconsistent, and duplicate document numbers from re-running a partially imported file.
Do I still have to key in the data before importing?: That is the catch — an Excel import only saves time if the Excel already exists. If your starting point is a pile of PDFs, photos and handwritten bills, someone still keys every line into the spreadsheet first. That step is what BalanceNow removes: AI reads the documents and produces the entries, your accountant approves, and the result posts to AutoCount directly or exports as an import-ready file.
Is there a way to skip the import file entirely?: Yes — for AutoCount Cloud, approved entries post through the official API; for on-premise AutoCount, they post with one click, no export-import. The import-file route stays available whenever you want full manual control.

Compliance context: LHDN raised the e-Invoice exemption threshold to RM3 million on 1 September 2026 — it changes who issues e-Invoices, not how purchase documents reach the ledger.

Get Started

Bring the Pile, Skip the Spreadsheet.

20 minutes on your real documents — watch them become AutoCount entries without anyone touching Excel.

Book a Demo WhatsApp us

Last reviewed 3 August 2026 · BalanceNow team · Questions? hello@balancenow.com.my