Million accounting is a fixture in Singapore SMB finance. Many manufacturers have been running Million for years — it handles their GST, payroll, and basic accounts payable/receivable cleanly. The question is not whether Million is good software; it is whether it was designed to handle manufacturing operations. It was not.
This distinction matters because many Singapore manufacturers using Million assume they need to replace it entirely when they outgrow their operational workflow. Often the better path is to keep Million for finance and build a purpose-built operational system alongside it.
What Million does well
- Double-entry accounting — GL, AP, AR, bank reconciliation
- GST compliance — GST F5/F7 preparation, IRB-ready reporting
- Payroll — Singapore payroll, CPF contributions, IR8A/IR21 generation
- Basic inventory — stock balances, goods receipt, goods issue
- Purchase and sales orders — basic PO and SO with invoice generation
- Local support — Multisoft Singapore support, established user community
Where Million hits limits for manufacturers
Custom pricing and quoting
Million handles standard pricing with price lists. It does not support formula-based pricing, customer-specific pricing rules, dimension-variable quotes, or structured quoting workflows with approval steps. Manufacturers who quote on custom jobs typically maintain a separate Excel quoting system and manually transfer confirmed orders into Million for invoicing.
Production job tracking
Million does not have a production module. There is no concept of a production job, a work order, WIP status, or shop-floor tracking. Manufacturers track production in Excel, WhatsApp, or on a whiteboard. This gap is the most common reason Singapore manufacturers on Million seek a new system — not because the accounting is wrong, but because they have no operational visibility.
Multi-level BOM
Million supports a basic item master with a simple BOM for material requirement calculation. It does not support multi-level BOMs (sub-assemblies within assemblies), dimension-variable BOMs, or BOM versioning for engineering change management. Manufacturers with complex product structures maintain their BOMs outside Million.
InvoiceNow / PEPPOL e-invoicing
Million does not natively generate PEPPOL BIS 3.0 XML for Singapore's InvoiceNow network. For manufacturers in the government supply chain or supplying large contractors who mandate InvoiceNow, this is a gap that must be filled by a third-party solution or by upgrading the system.
The split-stack approach
The most practical path for a manufacturer on Million is often to keep Million for finance and build a custom operational system alongside it. The operational system handles quoting, order management, production tracking, inventory, document generation, and InvoiceNow. It posts completed invoices to Million via a scheduled export or API for GL entry. Finance sees what they need in Million; operations runs in the purpose-built system.
This approach avoids a disruptive full system replacement. The finance team continues using software they know. The operational team gets the workflow they need. The integration is simple — a one-way invoice sync — and can be built as part of the custom system project.
When to replace Million entirely
Replace Million entirely when: (1) the business has grown to a point where multi-entity consolidation, multi-currency complexity, or advanced financial reporting is needed beyond what Million provides; (2) the business is moving to a comprehensive mid-market ERP (Sage 300, Synergix) that includes accounting; (3) a new system is being built from scratch and there is no legacy accounting data worth preserving.
Cost comparison
Million licences cost S$1,000–S$3,000 one-time with annual maintenance. A custom operational system built alongside Million costs S$15,000–S$25,000 (fixed price, one-time). Total investment: S$16,000–S$28,000 versus replacing both with a comprehensive ERP at S$30,000–S$80,000+ implementation plus ongoing fees. For most Singapore SMB manufacturers, the split-stack approach is the better value.