Discovering missing or incorrect e-Invoice submissions can be worrying, but the best first step is practical: reconcile the source sales records with what was actually submitted.
Malaysia’s special voluntary disclosure programme for e-Invoice—PKPS—runs from 7 July 2026 to 31 December 2027 under HASiL’s programme announcement. It provides a route for specified omissions and inaccuracies, subject to the programme conditions.
It isn’t a general income-tax amnesty or a promise that every historical mistake will receive protection.
What kind of problem did you find?
Start by describing the gap accurately:
- no e-Invoices were submitted for a period;
- some transactions were omitted;
- information in submitted documents was incorrect;
- consolidated submissions were missing; or
- the issue was found during a compliance-review situation covered by the guidance.
Different errors may require different documents or steps. Don’t choose a correction method until the issue and affected periods are clear.
Also confirm that the business was required to submit for those periods. A change in current exemption status may affect the next step, but it doesn’t rewrite the facts of an earlier period automatically.
Reconcile before correcting
Compare source records with submission records month by month. Useful sources may include:
- sales invoices and receipts;
- point-of-sale and marketplace exports;
- bank and payment-platform settlements;
- refund and credit-note records;
- accounting sales reports; and
- MyInvois submission identifiers and statuses.
Agree the total sales and identify each missing or incorrect item. A correction made from incomplete books can create a second problem instead of resolving the first.
Keep a correction register
Give each missing or incorrect item an entry showing its transaction month, source evidence, amount, original submission reference if any, proposed correction, reviewer and final outcome. Where no original submission exists, say so.
Keep the detailed document references in the workpaper and a short progress table for the team. The case below shows a completed structure without squeezing every field into one wide table.
Keep missing consolidated months separate
Section 17 of the Specific Guideline, version 4.9 addresses omitted and incorrect submissions. Missing consolidated submissions must be separated by transaction month rather than combined across several months.
One combined entry shouldn’t be used to hide which transactions belong to which period.
Section 17.5 designates PKPS 1.2 for submissions without a digital signature and PKPS 1.3 for submissions with one. These programme versions are for PKPS disclosures, not ordinary submissions. Confirm the applicable technical route before sending the documents.
Fictional case study: three missing months
Assume a retailer’s mandatory implementation date has been confirmed as 1 January 2026. In September 2026, it discovers omitted consolidated submissions for April, May and June 2026. All transactions in this example are eligible for consolidation, no buyer requested an individual e-Invoice, and none of these transactions was already submitted separately.
After checking sales, refunds and the accounting records, the reviewer establishes the following amounts. Assume there are no further tax or adjustment components in this simplified table:
| Transaction month | Reconciled amount | Source evidence | PKPS submission to prepare |
|---|---|---|---|
| April 2026 | RM45,000 | April sales and reconciliation pack | One consolidated e-Invoice for April |
| May 2026 | RM60,000 | May sales and reconciliation pack | One consolidated e-Invoice for May |
| June 2026 | RM55,000 | June sales and reconciliation pack | One consolidated e-Invoice for June |
| Total checked | RM160,000 | Three monthly packs | Three submissions, not one quarterly submission |
The retailer uses the appropriate PKPS version, saves each actual validation reference and checks that the three accepted amounts total RM160,000. Any rejected item remains open until corrected and validated. The team also checks for duplicate submissions before closing the register.
The result is a month-by-month correction trail that agrees with the books. It illustrates the submission structure in section 17.6; acceptance by the system is not, by itself, proof of entitlement to every programme protection. The conditions below still apply.
Conditions still matter
The programme requires good-faith accuracy. The guideline excludes fraud, deliberate default and negligence from the stated protection.
That means a business shouldn’t backdate false evidence, estimate figures carelessly or use a consolidated correction to obscure the underlying periods. Keep the source records, calculation and reviewer’s sign-off.
If a compliance review, notice or other formal process is already involved, have the position assessed against the exact programme conditions before acting.
A practical correction process
- Confirm the business’s obligation and affected periods.
- Preserve sales, accounting and MyInvois records.
- Reconcile source sales with submitted data by month.
- Classify each omission or error.
- Prepare the correction register and supporting evidence.
- Have the proposed treatment reviewed.
- Follow the current official submission instructions.
- Save acknowledgements and reconcile the final outcome.
The programme deadline is 31 December 2027, but waiting until the end can make records harder to recover and leaves less time to resolve rejected submissions.
Prevent the same gap from returning
After the correction, compare accounting sales with e-Invoice submissions on a recurring basis. Assign someone to review rejected documents, consolidated submissions, refunds and credit notes.
If the underlying bookkeeping is behind, use the catch-up accounting plan to rebuild it. PKPS corrects specified e-Invoice issues; it doesn’t replace complete accounting records or other tax obligations. If the original obligation is uncertain, start with the e-Invoice applicability guide.
Approach the problem calmly and keep the evidence honest. A month-by-month reconciliation and clear correction register are more useful than rushing to submit a number that hasn’t been checked.
Sources checked on 24 September 2026 against the July 2026 announcement and Specific Guideline version 4.9. Recheck section 17 and the current technical instructions immediately before submission.
Sources referred to in this guide (2)
We’ve taken reasonable steps to verify the cited sources and check this information as at the source-check date. We can’t guarantee 100% accuracy, completeness or that it remains up to date. This is general information and does not replace professional accounting, tax or legal advice tailored to your circumstances. How these guides were prepared.