Automated StoreHub E-Invoice Tracking
Every morning, WebRun opens StoreHub, lists the e-invoices raised yesterday, checks each one's validation status on the LHDN MyInvois portal, and posts a Slack summary of anything rejected, cancelled, or still pending so your team can fix it before the deadline.
How do I track which StoreHub e-invoices were accepted by LHDN?
Every morning WebRun opens StoreHub, lists yesterday's e-invoices, and checks each one's status on the LHDN MyInvois portal. It posts a Slack summary of anything rejected, cancelled, or still pending, with the reason, so your finance team can correct and re-submit before the validation window closes. WebRun never files anything itself.
- Rejected e-invoices are caught inside the validation window
- Compliance exceptions surface daily, not at audit time
- Every submission's LHDN status checked without manual lookups
Built for Malaysian retailers · F&B operators · finance teams · multi-outlet businesses
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
backoffice.storehub.comin a real browser with your saved login - no setup, no API keys. -
1
StoreHub - list yesterday's e-invoices
storehub.com
WebRun opens StoreHub to list yesterday's e-invoices. - Open StoreHub BackOffice and go to the e-Invoicing section
- List the e-invoices and consolidated e-invoices raised yesterday
- Capture each invoice number, buyer, amount, and submission reference
Done when Yesterday's e-invoices are listed with their submission references.
-
2
MyInvois - check validation status
- Open the LHDN MyInvois portal and look up each submission reference
- Read the validation status: valid, invalid, rejected, cancelled, or pending
- Note the reason for any that failed validation
Done when Every e-invoice has a confirmed status from MyInvois.
-
3
Slack - flag exceptions for review
slack.com
WebRun opens Slack to flag exceptions for review. - Post a summary of any rejected, cancelled, or still-pending e-invoices
- Include the invoice number, buyer, amount, and the failure reason
- Leave the list for your finance team. WebRun never re-submits or files anything to LHDN on its own
Done when Your finance team has today's e-invoice exception list in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it submit or re-file e-invoices to LHDN for me?
No. WebRun only reads submission status and flags exceptions for your team. Filing, re-submitting, or cancelling an e-invoice stays a human decision, so nothing goes to LHDN without approval.
What counts as an exception?
Any e-invoice that MyInvois marks rejected, cancelled, or still pending validation. WebRun lists each one with its reason, so your team can correct and re-submit it before the deadline.
How often does it check?
Every morning WebRun reviews the previous day's e-invoices, which gives your team the full validation window to fix and re-submit anything MyInvois rejected.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.