Lapasar
Procurement committee of a government-linked company reviewing documents in a formal meeting room

GLC & Government

GLC & Government Procurement Platform for Malaysia

Lapasar Procurement OS is a full procure-to-pay suite for GLCs and government agencies: requisitions, budgets, multi-level approvals, purchase orders, goods receipt and three-way invoice matching through to payment readiness. AI-assisted controls, Bumiputera vendor records and scoped ERP PunchOut connect to a live B2B marketplace from an MOF-registered supplier.

Last updated:

Registered supplier
MOF
ERP punchout
cXML · OCI
Verifiable with SSM
1198228-D

Lapasar Procurement OS is a full procure-to-pay suite for GLCs: requisitions, budgets, multi-level approvals, purchase orders, goods receipt, three-way invoice matching and payment readiness with an audit trail. It connects to the Lapasar B2B Marketplace, with AI-assisted reviews and scoped ERP PunchOut. Lapasar is a Ministry of Finance (MOF)-registered supplier. Approval thresholds are configured to each organisation's own Treasury, board and delegation-of-authority rules. Payment execution remains subject to the customer's finance process.

Key takeaways

  • Lapasar is a Ministry of Finance (MOF)-registered supplier offering procurement software connected to a B2B marketplace.
  • Approvals route by value, category and site using thresholds each organisation configures to its own policy.
  • Requester, approver and receiver stay separate, and self-approval is blocked.
  • Each vendor's Bumiputera status is recorded, so purchases can be reported by vendor status and category.
  • cXML and OCI punchout connect the catalogue to SAP, Oracle and Dynamics 365 where supported.

What you get with Lapasar

Threshold-based approvals

Requests route by value, category and site to the right approver.

Bumiputera vendor records

Vendor status recorded so participation can be reported.

Audit-ready trail

Every request, approval, PO and receipt timestamped.

Multi-entity control

One set of rules across sites, subsidiaries and cost centres.

How Lapasar helps

01

Bring the long tail onto one catalogue

Recurring operational buying moves from many small vendors to one governed catalogue.

02

Apply your rules to every purchase

Thresholds, approvers and budgets you configure are checked before an order is placed.

03

Keep the record for audit

Requests, approvals, receipts and vendor status are kept in one searchable trail.

Start browsing on mall.lapasar.com

What a GLC procurement platform must do

Six checks to run on any platform before a GLC or agency puts operational spend through it. Read the guide on how government buying works in the procurement guide for government agencies and GLCs.

Capabilities a GLC procurement platform needs, and how Lapasar provides each
CapabilityWhy GLCs need itHow Lapasar does it
01MOF-registered supplyAgencies, statutory bodies and many GLCs can only buy from vendors registered with the Ministry of Finance.Lapasar is an MOF-registered supplier. Lapasar Sdn Bhd (1198228-D) can be checked with SSM.
02Treasury value-threshold routingEach purchase has to follow the route its value requires: direct purchase, quotation or tender.Requests route by value, category and site against thresholds your team configures to its own circulars and policy.
03Delegation of authority and segregation of dutiesRequester, approver and receiver must be different people, each acting within a set limit.Approver limits follow your delegation-of-authority matrix, and self-approval is blocked.
04MACC s17A adequate-procedures controlsUnder Section 17A, organisations need documented procedures to prevent corruption in buying.Every request, approval, order and receipt is timestamped. Lapasar publishes its own anti-bribery and whistleblowing policies.
05Bumiputera vendor participation reportingMany GLCs and agencies report the share of spend that goes to Bumiputera vendors.Vendor Bumiputera status is recorded on supplier profiles, so spend can be reported from your transaction data.
06ERP integrationFinance needs requisitions and POs to stay inside the system it already controls.cXML or OCI punchout to SAP, Oracle and Dynamics 365, confirmed for each deployment.

Treasury value thresholds

Public financial procedures put each purchase into a value band, and the band decides whether it is bought directly, by quotation or by tender. The figures below are indicative only. Always check the current Treasury circular and your own agency or board policy, which take precedence. Lapasar applies the limits you configure; it does not set them.

Recommended procurement workflow

  1. Step 1

    Requisition

    Staff request items from an approved, priced catalogue instead of sourcing informally.

  2. Step 2

    Threshold routing

    The request value decides the route. Higher values go to quotation or tender outside the catalogue.

  3. Step 3

    Documented approval

    Each approver signs off digitally within their limit, and the decision is kept on record.

  4. Step 4

    Goods receipt

    A different person confirms delivery against the purchase order.

  5. Step 5

    Three-way match

    PO, goods receipt and invoice are matched before payment is released.

Recommended approval process

A starting point for value-based tiers. Calibrate each limit and approver to your delegation of authority before go-live.

Indicative value-based approval tiers for government and GLC procurement
TierIndicative valueApprover
Direct purchaseUp to RM50,000Head of department or procurement officer
QuotationRM50,000 to RM500,000Quotation committee
TenderAbove RM500,000Tender board or accounting officer
Major or multi-yearHigh value, strategicMinistry or board approval

Government and GLC ERP and finance systems

Where an agency or GLC already budgets and raises POs in an ERP, Lapasar runs as a cXML or OCI punchout catalogue. Requisitioners shop inside SAP, Oracle or Dynamics 365 and send an approved cart back into the existing requisition and PO flow, so finance keeps one record. Connector scope is confirmed per deployment.

How punchout works

Registered and documented for public-sector due diligence

Lapasar is a Ministry of Finance (MOF)-registered supplier, and Lapasar Sdn Bhd (1198228-D) can be checked with the Companies Commission of Malaysia (SSM).

Lapasar publishes its anti-bribery and anti-corruption policy, a board-approved whistleblowing policy, a personal data protection policy and vendor terms, each with a downloadable PDF. The anti-bribery framework is guided by the Guidelines on Adequate Procedures under Section 17A(5) of the MACC Act 2009. It is a published policy framework, not a certification.

  • Ministry of Finance (MOF)-registered supplier
  • Lapasar Sdn Bhd (1198228-D), verifiable with SSM
  • Published anti-bribery, whistleblowing, PDPA and vendor-conduct policies
  • Section 17A: a published policy framework, not a certification

Browse live stock & pricing on mall.lapasar.com

Bumiputera vendor participation, from your own data

Each supplier profile records the vendor's Bumiputera status. Because every purchase is tied to a vendor, participation can be reported by category and period from your transaction data, rather than compiled by hand. Report format and frequency are agreed with your team during setup.

See contract pricing on mall.lapasar.com

Common questions

What is a GLC procurement platform?
A GLC procurement platform is software that government-linked companies and agencies use to raise requisitions, route approvals by value and authority, issue purchase orders, record receipts and keep an audit trail. Lapasar combines that software with a B2B marketplace of verified suppliers, so GLC teams can buy recurring operational items under the same controls they apply to every other purchase.
Does Lapasar follow Treasury procurement thresholds?
Lapasar routes each request by value, category and site using approval thresholds that your organisation configures. Your team sets those thresholds to match the Treasury circulars, board policy and delegation of authority that apply to you. Lapasar does not decide which rules apply, and using it does not by itself guarantee public procurement compliance. High-value purchases should stay on your quotation or tender route.
How does Lapasar support MACC Section 17A adequate procedures?
Lapasar keeps a timestamped record of who requested, approved, ordered and received each purchase, and it blocks self-approval. Lapasar also publishes its own anti-bribery, whistleblowing and vendor-conduct policies, guided by the Guidelines on Adequate Procedures under Section 17A(5) of the MACC Act 2009. These records support your own adequate-procedures framework. They are not a certification or a legal defence on their own.
Can a GLC run Lapasar alongside ePerolehan or MyProcurement?
Yes, alongside them, not instead of them. Many organisations keep tenders and other processes on the government systems that apply to them, and use Lapasar for recurring, lower-value operational buying with approvals and audit records. Which purchases belong in which system depends on your agency or company policy, so confirm the split with your procurement and finance teams first.
Is Lapasar a Ministry of Finance (MOF)-registered supplier?
Yes. Lapasar is registered with the Ministry of Finance as a supplier, which government bodies and many GLCs require before they can buy from a vendor. Lapasar Sdn Bhd (1198228-D) can also be checked independently with the Companies Commission of Malaysia (SSM). Supporting documents are shared on request during your vendor onboarding and due-diligence process.
Does Lapasar support Bumiputera vendor participation reporting?
Lapasar records each vendor's Bumiputera status as part of its supplier profile, so purchases can be reported by vendor status, category and period from your transaction data. The exact report format and how often it is produced are agreed with your team during setup. Vendor status comes from supplier records, so your organisation should still review it against its own requirements.
Can Lapasar connect to our existing ERP?
Yes, where your system supports it. Lapasar works as a cXML or OCI punchout catalogue, so requisitioners shop the marketplace inside SAP, Oracle or Dynamics 365 and return an approved cart into the requisition and purchase-order workflow your finance team already controls. Connector availability and setup are confirmed for each deployment before go-live.
Can Lapasar pass our vendor due-diligence checks?
Lapasar publishes the documents due-diligence teams usually ask for: an anti-bribery and anti-corruption policy, a board-approved whistleblowing policy, a personal data protection policy and vendor terms and conditions, each in full text with downloadable PDFs. Registration documents are shared on request. Whether these meet your checks is for your compliance team to decide.

Didn't find your answer?

Ask us directly — WhatsApp or email, whichever suits you.

AI-first procurement software. Live marketplace. Human services.

See the GLC procurement platform with your own thresholds

Walk through requisition, threshold routing, approval, receipt and three-way match with our team, using your organisation's approval limits.

Prefer to talk to a real person?

Our team replies fast on WhatsApp and email — no forms, no waiting.

A reviewable procurement journey for GLC teams

Evaluate purchasing controls and AI against your own mandate, delegation matrix and evidence requirements. Product capability is not a government endorsement or compliance certification.

  1. 1

    Apply the purchasing rules

    Procurement OS applies the configured budget, policy and approval workflow. AI gives reviewers context; it does not approve or bypass a limit.

    Lapasar Procurement OS
  2. 2

    Find a comparable offer

    Use Marketplace search, photo or list matching and Co-Pilot. Check specification, pack, quantity and delivery eligibility before comparing prices.

    Lapasar B2B Marketplace
  3. 3

    Use evidence, not an AI verdict

    Quotation analysis explains recorded price, lead time and response gaps. AI insights inform an authorised reviewer; supplier selection, procurement rules and approval decisions remain with your organisation.

    AI solutions for procurement
  4. 4

    Keep system ownership clear

    For a configured PunchOut journey, return the cart to the originating procurement system. Confirm which system owns approval, PO, receipt and invoice data.

    PunchOut and ERP workflow

Availability depends on permissions, configuration, feature enablement and evidence. AI advice does not replace product suitability checks, approval authority or recorded outcomes.