ERP Requirements Consultant, Singapore

How a Singapore ERP specification is laid out

The specification sits between the business analysis and the contract. It does not argue for a process; it states, line by line, what the chosen system must do. For a Singapore company with regional operations, I lay it out as follows:

• Control page: version, author, reviewers, approvers and a running change log.
• Entity matrix: each company in scope, its functional currency, its accountant and the chapters that apply to it.
• Process chapters: quote-to-cash, procure-to-pay, inventory or trading, projects and services, intercompany, and record-to-report including consolidation in Singapore dollars.
• Statutory register for Singapore and, where needed, separate registers drafted with each subsidiary's own advisor.
• Non-functional chapter, interfaces, data migration and reporting.

Every line carries an ID, a statement, an owner, an entity flag, a priority and trace references. That structure lets an implementer quote the Singapore entity first and the regions later without anyone losing track of what was promised. The workshops that produce the content are described on my ERP business analyst page for Singapore; the general method is on ERP requirements gathering.

Statutory lines for GST, InvoiceNow, filings and retention

Singapore rules in this area have been evolving, so the register treats every statement as something your tax advisor or accountant confirms, not something I decide. What I contribute is the wording, which must be specific enough to test. Examples of the style:

• A credit note issued against an InvoiceNow invoice is sent through the same channel and references the original document.
• A billing user can see, for each outbound e-invoice, whether it was delivered, without asking IT.
• Each GST code your advisor approves maps to the correct box in the return, and the return figures can be drilled back to source transactions per entity.
• Where your advisor confirms a reverse charge or import treatment, the system records it with its own tax code rather than a manual journal.
• Year-end figures can be exported in a structure your accountant can use when preparing annual filings.
• Ledgers, source documents and e-invoice files can still be retrieved, in readable form, for as long as your advisor says they must be kept.

Lines such as these usually carry a must tag. When InvoiceNow is delivered through an access point provider rather than inside the ERP, the register says so, and the interface chapter states who owns that connection.

Hosting, PDPA and access requirements written to be answered

Non-functional requirements are where Singapore specifications are often thinnest, and where weak answers cost most after signing. I write them as direct questions with a required response:

• Hosting: where production data and backups are stored, whether a Singapore or regional location is offered, and whether any customer contract or sector expectation, for example in financial services or healthcare, affects that choice. Your advisor confirms what applies.
• Personal data: roles that limit who sees employee and customer personal data, masking of identification numbers in screens and exports, and the ability to delete or anonymize records when retention ends, in line with how your advisor reads the PDPA.
• Access: single sign-on, role design that separates entities, and approval controls for supplier bank detail changes.
• Audit trail: who changed a master or a posted document, when and from what value.
• Availability and support: service windows that suit users across regional time zones, and support response during Singapore business hours.
• Performance: month-end close and consolidation behavior across entities, with targets set by your team.

Each bidder answers every line as met, partly met or not met, with an explanation that becomes part of the record.

Priority, traceability and use in RFPs and contracts

A specification without priorities invites implementers to quote everything and promise everything. I use four tags. Must means the Singapore entity cannot go live without it. Should means a short-term workaround exists. Could marks a genuine improvement. Later records an idea for a future phase. Regional subsidiaries can carry different tags on the same line, which keeps a rollout plan honest.

Trace columns link each line to the demo script step that tested it, the implementer's response, the design note, the scripted test and its UAT outcome. If a disagreement arises during build, the trail shows what was asked, what was promised and what was proven.

In an ERP RFP, bidders classify each line as standard, configuration, customization, third-party product or not supported. Where a proposal comes bundled with a grant-supported package, the package scope is compared against your specification rather than replacing it. Once the decision is made, the baseline version and the winning response are attached to the contract, and every later change goes through a numbered change request with its impact noted. My ERP selection consultant page for Singapore shows how those responses feed scoring.

Gaps that put Singapore specifications at risk

Some omissions turn up repeatedly in Singapore requirement documents, and each one tends to become a change request or a compliance problem later. When I review a document, these are the first things I look for:

• InvoiceNow written as sending only, with nothing about receiving supplier e-invoices into purchasing.
• Intercompany charges and eliminations left out because the sponsor sits in the Singapore entity.
• Foreign currency revaluation and consolidation currency assumed rather than stated.
• The payroll journal interface missing, because CPF and payroll run in a separate product.
• No PDPA-related retention or deletion requirement, so personal data is kept indefinitely by default.
• Reports described by title only, with no fields, filters or entity breakdown.
• No line on how statutory updates are delivered and charged under support.

Each is cheap to fix on paper and costly once configuration has started. If a project is already under way and these gaps are surfacing, an ERP gap analysis may come first. For the wider view of my remote work in this market, see the Singapore hub or the Singapore ERP consulting page.