ERP Requirements Consultant, Malaysia

Chapters of a Malaysian ERP requirements specification

The business analysis decides how processes should run; the specification records what the system must do so that a contract can depend on it. For a Malaysian company the document I prepare usually contains:

• Control section: version number, contributors, reviewers, approvers and change history.
• Footprint: each company, plant, warehouse and branch, with notes on any free zone or licensed warehouse arrangement that brings customs records into scope.
• Process chapters: order-to-cash, procure-to-pay, inventory, production and subcontract processing, service or projects where relevant, and record-to-report.
• Statutory register: MyInvois, SST, record retention and statutory reporting lines, each confirmed by your advisor.
• Non-functional chapter: hosting, data protection, access, audit trail, performance and availability.
• Interfaces, migration and reports, with reports defined by fields and filters, not titles.

Each line has an ID, a plain statement, an owner, a priority and room for trace links. Workshop and mapping work that feeds it is a separate service: ERP business analyst in Malaysia. For the BRD format that often precedes a specification, see ERP BRD consulting.

Acceptance lines for MyInvois, SST and retention

Because the e-invoicing rollout and SST scope have both been changing, the register holds statements your advisor has confirmed, not my interpretation of the law. My job is precise wording. Examples of the style I use:

• A document rejected during validation returns to a queue where the billing user sees the reason in plain text and can correct and resubmit it.
• Resubmitting a corrected document does not create a second invoice number or a duplicate receivable.
• Cancelling a validated e-invoice requires an approver and leaves a visible record of who cancelled it and why.
• Every SST code used on a sales or purchase line traces to a row of the advisor-approved treatment matrix.
• Figures for SST return preparation can be produced per period and drilled down to the source documents.
• Ringgit is the base currency, with foreign currency invoicing for exports and revaluation at period end.
• Records and e-invoice files stay retrievable for the period your advisor confirms they must be kept.

Most of these carry a must tag. If submission is handled by middleware outside the ERP, that fact is written down and a named party is made responsible for keeping the link working.

Non-functional requirements for plants, branches and data protection

Malaysian specifications often describe screens in detail and say little about how the system must behave. Those are the requirements that hurt most when they are discovered after signing. I write each one as a question every bidder must answer:

• Hosting: the data center and backup location for production, the choices on offer and whether any customer contract or group policy restricts that choice. Your advisor confirms whether data protection rules on transfers abroad affect you.
• Personal data: who can see employee and customer details, how identification numbers are masked in screens and exports, and how records are removed when they no longer need to be kept.
• Access: roles separated by company and site, approval for changes to supplier bank details, and separation between raising and approving payments.
• Audit trail: changes to masters and posted documents logged with user, time and previous value.
• Performance: month-end posting and e-invoice submission volumes, with targets your team sets.
• Availability: what plants or branches on unreliable connections must still be able to record, and how it catches up.

Each bidder's yes, no or partial answer is kept on file with its explanation.

Interfaces, migration, priorities and traceability

Interfaces are written as their own lines, not buried in process text. Typical Malaysian entries cover the e-invoicing route, journals from the payroll product that handles EPF, SOCSO, EIS and PCB deductions, bank payment files and statement imports, and marketplace or webstore orders. Each line states direction, frequency, data owner and the behavior when a transfer fails.

The migration chapter states what moves from the outgoing package: masters, open receivables and payables, stock by location and batch, and how much history. It also states who signs off the reconciliation. More detail is on ERP data migration.

Priority uses four plain tags. Must means go-live cannot happen without it. Should has a short-term workaround. Could is a worthwhile improvement. Later is parked for a future phase. A must needs a written reason, which stops every department marking everything as essential.

Trace columns then connect each line to the demo script step used in selection, the implementer's response, the design document, the test case and its UAT outcome. That chain is what lets a project manager answer, months later, whether a gap was in the requirement, the proposal or the build.

Using the specification with bidders, and common gaps

In an ERP RFP, each bidder states for every line whether it is handled out of the box, by setup, by custom development, through an add-on, or not at all. Proposals that arrive framed as an e-invoicing upgrade are compared against the full specification, not only the e-invoicing lines. After the decision, the signed version and the winning response become a contract annex, and changes follow a numbered request with impact noted. The ERP selection consultant page for Malaysia covers scoring.

Gaps that weaken Malaysian specifications, and that I check for when reviewing an existing document, include:

• MyInvois treated as outbound only, with nothing on self-billed or inbound documents your advisor says apply.
• Subcontractor stock and returns from outside processing missing.
• Customs record needs for free zone or licensed warehouse sites left to a later phase.
• East Malaysia branches or remote depots not named in scope.
• Print layouts in Malay or Chinese mentioned with no owner for the wording.
• No commitment on how statutory updates are delivered under support.

For a wider view of my remote work here, see the Malaysia hub and the Malaysia ERP consulting page.