M³ — Features

Every invoice is checked against its purchase order and goods receipt across 11 criteria you switch on or off independently — vendor name, PO number, GSTIN, per-line description, quantity-vs-received, rate, unit of measure, per-line GST rate, footer total, tax arithmetic. Duplicate-bill detection is the one check that's never optional.

Five separate numeric tolerances decide how close is close enough — quantity variance %, rate variance %, GST-rate tolerance, a rupee tolerance on the footer total, and a re-bill similarity tolerance. Want bit-perfect matching, or want to auto-clear small rounding differences? Both are one settings screen away, not a support ticket.

When something doesn't match, you get the specific reason — "Rate Mismatch," never a generic "Footer Total Mismatch." An invoice with no real purchase order is always routed to a human; it's never waved through against a fabricated stand-in.

Every invoice — a scanned PDF, a phone photo, a pasted email — is read automatically: header fields, GSTIN, HSN codes, CGST/SGST, every line item, no per-vendor template to configure.

Pick the engine from a Settings page, not a code change: Google Gemini, OpenAI GPT, Anthropic Claude, or any OpenAI-compatible endpoint — including a model you run yourself (Ollama, LM Studio, vLLM), so invoice data never has to leave your network. Switch providers anytime; nothing in the data model locks you to one AI vendor.

Three ways in: paste raw text from an email, upload a file, or point M³ at a watched Gmail label for fully unattended processing. Every extraction lands on a review screen before it's saved — an odd AI read is always catchable before it's final.

One connector active at a time, swapped from Settings, no migration.

No ERP yet, or one that's not listed? The Generic REST connector maps your own API's fields; Excel/CSV import needs no ERP at all.

Vendors get their own login, completely separate from your staff accounts — their own invoices, their own open POs, nothing else. Upload a GST certificate, PAN card, or cancelled cheque, and the same AI engine that reads invoices pre-fills the bank account, IFSC, PAN, and GSTIN — nothing is trusted until an admin verifies it against the document itself. Once approved, a vendor can't quietly retype a verified bank account; only an admin can reopen and change it, closing the single biggest vendor-impersonation risk in AP.

Six reports, every one exportable to Excel and PDF: Accounts Payable Aging (7 overdue bands), Vendor Spend & Concentration, Duplicate & Fraud Risk, Exception Reason Breakdown, Processing Efficiency, and an admin-only Audit Trail.

Google and Microsoft sign-in, each independently switchable, additive to local login — never a forced migration. A brand-new SSO login is auto-provisioned at Viewer, the lowest privilege, never silently granted admin.