
Most of the e-Invoice conversation in Malaysia has been about the invoices you send. The quieter cost sits on the other side of the desk: the supplier invoices you receive. They still arrive as PDFs in an inbox, photos on WhatsApp, paper in a delivery box, and, increasingly, as validated e-Invoices. Someone in your accounts team then types each one into SQL Account or AutoCount, line by line.
That retyping is the part worth fixing. This article explains how Document AI handles it, what a sensible workflow looks like, and where a person should stay in the loop.
Why e-Invoicing has not removed the retyping
LHDN's e-Invoice rollout is phased by business size, and the current rules, timelines and exemptions are set out in this 2026 guide to the LHDN e-Invoice guideline. Read it for the dates that apply to your company; we will not restate them here.
What matters for this article is simple. Your suppliers will not all move at the same pace. In a typical month an SME receives a mix of:
- validated e-Invoices from larger suppliers
- PDF invoices from smaller suppliers not yet in scope
- scanned or photographed paper invoices and delivery orders
- credit notes, debit notes and statements that need matching
Each of these still has to end up as a purchase invoice in your accounting system, posted to the right supplier, the right account and the right tax code. A mixed inbox is harder to process than a single format, so the paperwork can grow before it shrinks. We covered this gap in more detail in e-Invoicing is live, and the hard part is the invoices you receive.
What Document AI actually does
Document AI is software that reads a document the way a trained clerk would. It finds the supplier, invoice number, date, line items, quantities, unit prices, tax and totals, whatever the layout. It does not need a template for each supplier.
For incoming invoices, a working setup does four things.
1. Collects documents from where they arrive
Invoices come in through a shared accounts mailbox, a WhatsApp number, a scanner, or the MyInvois portal. The first job is to pull them all into one queue, so nothing sits unread in someone's personal inbox.
2. Reads and structures each document
The system extracts the header fields and every line. For a validated e-Invoice the data is already structured, so this step is quick and reliable. For a PDF or a phone photo, the model reads the image and gives each field a confidence score.
3. Checks the figures before anything is posted
This is where most of the value lies. Before posting, the system checks that:
- the supplier exists in your accounting system and the details match
- the invoice number has not been posted before (duplicate check)
- line totals add up to the invoice total, including tax
- quantities and prices match the purchase order or delivery order, where you use them
- the tax treatment is consistent with how that supplier is usually billed
4. Posts clean invoices and routes the rest
Invoices that pass every check are posted to SQL Account or AutoCount as purchase invoices, with the original document attached. Anything that fails a check, or that the model read with low confidence, goes to a review screen. Your staff see the document beside the extracted fields, correct what is wrong, and approve.
The outcome is that people stop keying routine invoices and start dealing only with the exceptions.

A worked example (illustrative figures)
The figures below are an example to show the shape of the change. They are assumptions, not a client result, and your numbers will differ.
Picture a Klang Valley distributor with two accounts staff. It receives around 600 supplier invoices a month from about 80 suppliers.
Before (example):
- Each invoice takes around 4 minutes to open, read, key in and file.
- That is roughly 40 hours a month of data entry.
- Errors are found at month-end, when supplier statements do not reconcile.
After (example):
- Suppose most of those invoices, say 480 of the 600, pass every check and post without anyone touching them.
- The remaining 120 or so go to review and take about 2 minutes each to confirm or correct.
- That is roughly 4 hours a month of review, plus time to deal with genuine disputes.
Again, these are example figures. The share of invoices that post cleanly depends on how consistent your suppliers are, how tidy your supplier and item master data is, and whether you match against purchase orders.
Where people should stay in the loop
Automation is not a reason to stop checking. We recommend keeping a person responsible for:
- New suppliers. The first invoice from a new supplier should always be reviewed, and the supplier record created by a person.
- Price or quantity variances. If an invoice does not match the purchase order beyond a tolerance you set, someone decides.
- Credit notes and disputes. These need judgement about which invoice they relate to.
- Period-end. A short review of what was posted automatically, especially near the closing date.
A good system also keeps an audit trail: who approved what, when, and against which original document. That matters for your auditor and for any LHDN query.
What you need in place first
You do not need a large IT team. You do need a few basics.
Clean master data
Supplier names, registration numbers and default accounts should be tidy in SQL Account or AutoCount. Duplicated or inconsistent supplier records are the most common reason invoices land in the review queue.
Agreed rules
Decide your tolerances. How much price variance is acceptable before review? Which expense accounts can be posted automatically, and which always need a person? These are business decisions, not technical ones.
A connection to your accounting system
SQL Account and AutoCount can both receive purchase invoices from outside systems. The details depend on your version and set-up; our integrations page lists what we connect to.
A sensible starting scope
Start with your highest-volume suppliers, or one branch, and widen once the review rate settles. A narrow start makes problems easy to see.
What it does not do
To be clear about limits:

- It will not make a supplier's wrong invoice right. It flags mismatches; people resolve them.
- It does not replace your accountant or your tax adviser on e-Invoice compliance questions.
- Accuracy on poor photos and handwritten documents is lower. Those will reach the review queue more often.
Beyond data entry
Once supplier invoices are posted the same day they arrive, your purchase data is current rather than a month behind. That opens up simple questions you can answer at any time: which suppliers have raised prices this quarter, what you owe this week, which deliveries are still unbilled. We wrote about getting those answers without the monthly Excel export in business insights from SQL Account or AutoCount.
If you run a distribution business, the volume of supplier paperwork makes this especially relevant.
Next step
Codech Solutions builds AI agents, document automation and business insights for SMEs in Malaysia and Hong Kong.
If your accounts team spends a good part of each week keying supplier invoices, it is worth a short look at where the time goes. Our AI audit maps your current invoice flow, estimates the review rate you could expect, and tells you plainly whether automation is worth it for your volume. You can also read more about our Document AI work.
Frequently asked questions
Does Document AI work with both SQL Account and AutoCount?
Yes. Both systems can accept purchase invoices from outside software. The exact connection depends on your version and set-up, so we confirm it during the audit before any build work starts.
Do we still need staff to check invoices?
Yes. Invoices that pass every check post automatically, but new suppliers, price or quantity variances, credit notes and low-confidence reads go to a person for review. The aim is to remove routine typing, not judgement.
Can it read invoices that arrive on WhatsApp or as phone photos?
Yes, it can read PDFs, scans and photos as well as validated e-Invoices. Clear photos read well; blurred or handwritten documents are more likely to be sent to the review queue.
How much time will we save?
It depends on your invoice volume, how consistent your suppliers are and how clean your supplier records are. The figures in this article are an example only. An audit of your own invoice flow gives a realistic estimate.
Does this make us e-Invoice compliant?
No. It handles the invoices you receive and posts them to your books. Your obligations for issuing e-Invoices are a separate matter, and you should confirm them with your accountant or tax adviser.