LHDN e-Invoice and MyInvois
Check MyInvois UUID and QR, TIN and SST registration numbers. Catch mapping mistakes before finance posts the invoice.
Home/AI for Accounting/Accounts payable
Stop re-keying supplier invoices. iGain lands invoices from SharePoint, email or upload, extracts the fields with Azure AI, flags LHDN and SST issues, and routes exceptions for approval - all inside your Microsoft 365 tenant.
iGain Invoice Automation
Crest packages Azure Functions, Document Intelligence and a SharePoint review app into a sellable accounts payable product for Malaysian companies - with local tax checks and connectors to the ledgers you already run.
Product
Finance sees every invoice in one register, then opens exceptions beside the original PDF - with confidence scores, SST and MyInvois warnings, and Approve or Reject.
How it works
Capture runs in Azure so it can watch folders overnight. SharePoint is the review and approval layer - not the OCR engine.
| Step | What happens | Runs in |
|---|---|---|
| 1. Landing | Invoices arrive in an AP Inbox library, shared mailbox (for example ap@company) or upload page. | SharePoint / Exchange |
| 2. Detect | SharePoint notifies the Function when a file is added; a timer job every 15 minutes catches anything missed. | Azure Function + Queue |
| 3. Claim | Status set to Processing with a lock so two workers never take the same file. Stalled jobs restart automatically. | Function + Graph |
| 4. Extract | Document Intelligence (prebuilt-invoice) maps fields, then LHDN/SST checks, duplicate check and confidence scores run. | Azure Function |
| 5. Output | One register row, file columns filled, JSON saved for audit. Status becomes Needs review or Ready. | Function + Graph |
| 6. File | Move to Processed/yyyy/mm or keep one library with Inbox / Processed / Exceptions views (configurable). | Function |
| 7. Review | SPFx screen for exceptions: PDF preview, editable fields, Approve or Reject. | SharePoint SPFx |
| 8. Export | Push approved invoices to SQL Accounting, AutoCount, Business Central, Xero or CSV. | Function |
Why Malaysia
Generic OCR is everywhere. What wins AP projects in Malaysia is validation, security and the connector to the ledger you already use.
Check MyInvois UUID and QR, TIN and SST registration numbers. Catch mapping mistakes before finance posts the invoice.
Same supplier and invoice number, bank details that suddenly change, and amounts that do not add up are flagged for review.
SQL Accounting and AutoCount first, then Business Central and Xero. Crest already works with SQL Accounting customers such as Terra Group-style rollouts.
Invoices never leave your tenant and Azure region. Sites.Selected + managed identity + Key Vault means IT can sign off without opening the whole tenant.
Automated AP is judged on failures. Retries, a dead-letter queue, Reprocess, Application Insights and a clear review UI keep exceptions under control.
Ask questions such as what you owe a supplier or which invoices are due this week - fitting the Copilot work Crest already delivers.
Security
Engagement
Start with deployment into your Azure. Faster to build, easier for PDPA, and aligned with Crest''s implementation and support model.
One-off packaging: Bicep and PowerShell installer, AP Inbox, Function, Document Intelligence and SPFx review app in your tenant.
Monthly tier by invoice volume (for example up to 300, 1,500 or unlimited). Margin sits in support and product, not OCR page fees.
Ideal pilots: high invoice volume and already on SQL Accounting or AutoCount. We run the same flow on Crest''s own AP first.
Multi-tenant SaaS and a Microsoft Marketplace listing later - without changing how we sell the first customer deployments.
Related
FAQ
iGain is Crest's accounts payable invoice automation product for Malaysian businesses. It captures supplier invoices from SharePoint, a shared mailbox or an upload page, extracts fields with Azure AI Document Intelligence, applies LHDN MyInvois and SST checks, and lets finance review and approve exceptions in a SharePoint (SPFx) screen before exporting to accounting software.
No. Processing runs in your own Azure and SharePoint environment. Invoices stay in your AP site, and Azure Document Intelligence is called from a Function App with Sites.Selected permissions - so the app cannot touch the rest of your tenant. That design supports PDPA and internal security reviews.
Yes. The Malaysia pack checks MyInvois UUID and QR data, TIN fields and SST registration numbers, and flags mismatches such as an SST number landing in the TIN field. Finance sees those warnings on the review screen before approval.
First connectors target SQL Accounting and AutoCount, with Business Central and Xero on the roadmap, plus CSV export for any other ledger. Crest already supports SQL Accounting customers and can scope the right connector for your stack.
Plain OCR is a commodity. iGain's edge is Malaysian validation (MyInvois, TIN, SST), duplicate and fraud checks, SharePoint review with confidence scores, Sites.Selected security, and connectors for local accounting packages - plus optional Copilot questions over the AP register.
Your AP team. High-confidence invoices can move straight to Ready; exceptions open in the SPFx review screen with the PDF beside editable fields, AI confidence per field, and Approve or Reject actions. A toggle shows only fields that need checking.
Typical structure is a one-off setup and deployment into your Azure, plus a monthly subscription tiered by invoice volume (for example up to 300, 1,500 or unlimited). Azure Document Intelligence usage is billed to your Azure subscription. Crest will quote based on monthly volume and connectors.
After the AP inbox and Azure Function are connected, most pilots start processing Crest-style volumes within weeks. Phase plans usually cover automatic processing first, then the Malaysia validation pack and accounting export.
Tell Crest your monthly volume and accounting system. We will map an iGain pilot inside your Microsoft 365 and Azure tenant.