A certificate naming the wrong entity or ABN
In short
- A certificate has to name the entity that signed the contract or is doing the work. A related company, a trading name, or a former entity name is not the same thing.
- Confirm the name against a business register lookup, not the letterhead — trading names and registered entity names are often different.
- A wrong-entity certificate is a real gap, not a typo to wave through, because the policy responds to the entity insured, not to whoever is standing on site.
A certificate arrives, everything on it looks correct, and then a closer read shows the insured name is not quite the business being engaged. Sometimes it is a related entity, sometimes an old trading name, sometimes a director’s personal name. Whatever the cause, the certificate does not evidence cover for the business actually doing the work.
This is one of the more consequential defects a certificate can carry, because it is easy to miss and expensive to discover after something has gone wrong.
Why the exact entity matters
A policy insures a specific legal entity, not a brand or a person by reputation. If the certificate names a different company, a trust, or an individual rather than the entity that actually signed the contract, that entity has no evidenced cover — regardless of who is physically doing the work.
This comes up constantly with group structures, where a holding company, an operating company and a trust can share a trading name and letterhead but be entirely separate for insurance purposes.
How to check it properly
Check the certificate’s insured name and ABN against a business register lookup, not against the letterhead or the trading name on a sign or invoice. The register shows the current registered entity name, its ABN, and its status.
Compare that against the entity actually named on the contract — the party that signed it, not the party whose logo appears on correspondence. Where the two do not match exactly, that is the defect to raise, before work starts if possible.
Getting it fixed
The fix depends on the cause. If the certificate simply has a typo or an old trading name printed on it, the issuer can usually correct and reissue it quickly, because the underlying policy already covers the right entity.
If the policy itself is genuinely in a different entity’s name — say, a director’s personal policy rather than the company’s — there is no certificate to fix, because there is no cover for the entity that needs it. That has to be raised as a contracting issue, not chased as a documentation error.
Questions
- The certificate shows our trading name, not our registered company name. Is that a problem?
- It can be. A trading name is not the entity the policy insures. Check the certificate against the registered entity name and ABN, and if they do not match what is on the contract, ask for it to be corrected.
- What if the certificate is in a director’s personal name instead of the company’s?
- That usually means the policy itself covers the director personally, not the company. It is not a typo, and reissuing the certificate will not fix it — the company would need its own cover.
- How do I confirm which entity actually signed the contract?
- Read the contract’s parties clause, not the letterhead or email signature. That clause names the legal entity bound by the agreement, and it is the name the certificate has to match.
Sources
- Australian Business Register (ABN Lookup) — Free public tool to confirm a business’s registered entity name, ABN and status against the name printed on a certificate.
- ASIC — Regulator of the AFS licensees and authorised representatives — including brokers — who issue certificates of currency.