Procurement Software | Vendor Compliance at PO
Vendor compliance verified at PO save. Not at FY-end.
UEN status against ACRA, GST registration against IRAS, insurance and licence expiry, and dispute history checked live at vendor onboarding and again at every PO save. An entity that has been struck off blocks the PO. A supplier who is not GST-registered is flagged before anyone claims input tax on their invoice.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| UEN check at PO | Vendor UEN + ACRA register | Live / struck off / wound up status |
| GST registration check | Vendor UEN + IRAS register | Registered / not registered, with effective date |
| Document expiry | Insurance and licence certificates on file | Warning where a certificate has lapsed or expires inside the PO term |
| Dispute history | Open + resolved disputes | Soft warning at PO |
| Block on critical | Struck-off or wound-up entity | PO save blocked |
| Audit trail | Every check | Timestamp + status preserved |
-
UEN check at PO
- Input
- Vendor UEN + ACRA register
- Output
- Live / struck off / wound up status
-
GST registration check
- Input
- Vendor UEN + IRAS register
- Output
- Registered / not registered, with effective date
-
Document expiry
- Input
- Insurance and licence certificates on file
- Output
- Warning where a certificate has lapsed or expires inside the PO term
-
Dispute history
- Input
- Open + resolved disputes
- Output
- Soft warning at PO
-
Block on critical
- Input
- Struck-off or wound-up entity
- Output
- PO save blocked
-
Audit trail
- Input
- Every check
- Output
- Timestamp + status preserved
Compliance + integrations
Compliance check at the source, not at the audit.
Vendor compliance checked at PO is the cleanest pattern. The PO carries the verified state forward to the bill, to the payment, to the input tax claim on the GST return.
Regulations we work within
-
GST Act
Input tax is claimable only on a tax invoice from a GST-registered supplier, so registration is confirmed at the PO.
-
Companies Act 1967
Entity status and registered particulars come from the ACRA register, not from the vendor record.
Connects to
- ACRA Entity status and business profile
- IRAS GST-registered business search
Vendor Compliance at PO FAQ
What buyers ask.
A vendor is struck off. Does the PO block immediately?
Yes. A struck-off or wound-up entity at PO save triggers a hard block with a clear message. The vendor record updates with the status, AP and procurement are alerted, and the vendor is locked from new POs until the entity is restored or the record is repointed at the successor entity.
The vendor is not GST-registered. Block or warn?
Warn, not block. Suppliers below the registration threshold are perfectly legitimate, so the PO goes through. What the warning prevents is the downstream error: an invoice from that vendor that charges GST, or an input tax claim against one that should never have been made.
How does the document expiry check work?
Insurance certificates, licences and any other document you require of a vendor are held with an expiry date. The PO check warns where one has lapsed, or where it expires before the PO is due to be delivered, which is the case teams usually miss.
How often is the UEN re-checked?
At every PO save. Results are cached for up to 24 hours for read-heavy operations, but the check behind a blocking decision is always live.
More in Procurement Software
Related features
Run your top 50 vendors through the PO compliance check.
Connect your vendor master, free. The PO compliance check runs across every vendor, and the struck-off entities, the suppliers who are not GST-registered and the lapsed certificates all surface tonight.