Home/AI for Accounting/Accounts payable

Accounts Payable Invoice Automation for Malaysian Businesses

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
  • Azure AI Document Intelligence
  • LHDN MyInvois
  • Microsoft 365
  • SQL Accounting

iGain Invoice Automation

AP automation that finance and IT can both trust

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.

  • Capture from SharePoint, shared mailbox or upload
  • AI extraction with field-level confidence scores
  • MyInvois, TIN and SST validation warnings
  • Approve exceptions without leaving Microsoft 365
  • Export to SQL Accounting, AutoCount or CSV

Or WhatsApp +60 12-672 1050.

Product

See the AP register and review screen

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.

iGain Accounts Payable invoice register showing pending review status, AI confidence and RM totals
Invoice register: search by invoice number, supplier, TIN or UUID. Status tabs and open payable value in Ringgit.
iGain SPFx invoice review screen with PDF preview, extracted fields, AI confidence and LHDN SST validation warnings
Review screen: PDF on the left, extracted fields on the right, Malaysian validation alerts at the top.

How it works

From AP inbox to accounting export

Capture runs in Azure so it can watch folders overnight. SharePoint is the review and approval layer - not the OCR engine.

StepWhat happensRuns in
1. LandingInvoices arrive in an AP Inbox library, shared mailbox (for example ap@company) or upload page.SharePoint / Exchange
2. DetectSharePoint notifies the Function when a file is added; a timer job every 15 minutes catches anything missed.Azure Function + Queue
3. ClaimStatus set to Processing with a lock so two workers never take the same file. Stalled jobs restart automatically.Function + Graph
4. ExtractDocument Intelligence (prebuilt-invoice) maps fields, then LHDN/SST checks, duplicate check and confidence scores run.Azure Function
5. OutputOne register row, file columns filled, JSON saved for audit. Status becomes Needs review or Ready.Function + Graph
6. FileMove to Processed/yyyy/mm or keep one library with Inbox / Processed / Exceptions views (configurable).Function
7. ReviewSPFx screen for exceptions: PDF preview, editable fields, Approve or Reject.SharePoint SPFx
8. ExportPush approved invoices to SQL Accounting, AutoCount, Business Central, Xero or CSV.Function

Why Malaysia

Built for LHDN, SST and local ledgers

Generic OCR is everywhere. What wins AP projects in Malaysia is validation, security and the connector to the ledger you already use.

LHDN e-Invoice and MyInvois

Check MyInvois UUID and QR, TIN and SST registration numbers. Catch mapping mistakes before finance posts the invoice.

Duplicate and fraud checks

Same supplier and invoice number, bank details that suddenly change, and amounts that do not add up are flagged for review.

Malaysian accounting connectors

SQL Accounting and AutoCount first, then Business Central and Xero. Crest already works with SQL Accounting customers such as Terra Group-style rollouts.

Stays in your Microsoft 365

Invoices never leave your tenant and Azure region. Sites.Selected + managed identity + Key Vault means IT can sign off without opening the whole tenant.

Human-in-the-loop for the 5%

Automated AP is judged on failures. Retries, a dead-letter queue, Reprocess, Application Insights and a clear review UI keep exceptions under control.

Copilot over the AP register

Ask questions such as what you owe a supplier or which invoices are due this week - fitting the Copilot work Crest already delivers.

Security

Designed so customer IT can approve it

  • Sites.Selected: the Function reaches only the customer''s AP site, not every SharePoint site in the tenant
  • Managed identity and Key Vault: no secrets in the SPFx web part or browser
  • Customer Azure first: deploy into each customer''s subscription; they pay Azure usage and keep PDPA control
  • Audit trail: JSON extract plus register history for every processed invoice
  • Monitoring: Application Insights on queues, retries and stalled claims

Engagement

How Crest delivers iGain

Start with deployment into your Azure. Faster to build, easier for PDPA, and aligned with Crest''s implementation and support model.

Setup

One-off packaging: Bicep and PowerShell installer, AP Inbox, Function, Document Intelligence and SPFx review app in your tenant.

Subscription

Monthly tier by invoice volume (for example up to 300, 1,500 or unlimited). Margin sits in support and product, not OCR page fees.

Pilot

Ideal pilots: high invoice volume and already on SQL Accounting or AutoCount. We run the same flow on Crest''s own AP first.

Roadmap

Multi-tenant SaaS and a Microsoft Marketplace listing later - without changing how we sell the first customer deployments.

FAQ

Accounts payable invoice automation - common questions

What is iGain Invoice Automation?

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.

Does invoice data leave our Microsoft 365 tenant?

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.

Does it support LHDN e-Invoice and MyInvois?

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.

Which accounting systems can it export to?

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.

How is this different from Power Automate AI Builder or generic OCR?

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.

Who reviews low-confidence invoices?

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.

How is iGain priced?

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.

How long does a pilot take?

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.

Ready to stop re-keying supplier invoices?

Tell Crest your monthly volume and accounting system. We will map an iGain pilot inside your Microsoft 365 and Azure tenant.