KYB Compliance for Australian Marketplaces: A Practical Guide

The marketplace KYB challenge

B2B marketplaces in Australia face a specific compliance challenge: they need to verify that every business selling on their platform is legitimately registered — but they also need to keep onboarding fast enough to remain competitive.

Manual ABN checks create friction and slow onboarding. Skipping verification entirely creates fraud risk and potential liability. Automated KYB is the path between these two failure modes.

Why marketplaces need KYB

• Fraud prevention: Deregistered entities can transact on your platform, collect payment, and disappear before disputes are resolved
• Reputation risk: A marketplace that hosts fraudulent or non-existent businesses loses buyer trust rapidly
• Contractual obligations: Many payment processors and financial partners require marketplaces to have seller verification processes in place
• AML exposure: Platforms that facilitate business transactions may have AML/CTF obligations that require seller due diligence

The seller verification workflow

For a marketplace, the optimal KYB workflow looks like this:

1. Seller applies to list on the platform
2. Platform sends a Osapher onboarding link to the seller
3. Seller enters their ABN — Osapher validates format before submission
4. Osapher queries the live ABR and returns a Fracture Score™
5. Score 0–20: Auto-approve — seller is listed immediately
6. Score 21–50: Route to manual review before listing approval
7. Score 51+: Flag for compliance team — do not approve until reviewed

Scaling seller verification

For marketplaces onboarding large numbers of sellers simultaneously, Osapher's bulk verification pipeline allows you to upload a CSV of ABNs and verify up to 500 entities in a single batch — useful for migrating existing seller bases or periodic re-verification.

Each entity in the batch receives a Fracture Score and a verification result, and the full batch is available as a downloadable report.

Ongoing monitoring — not just onboarding

Entity status can change after initial verification. A seller who was active at onboarding may have their ABN cancelled months later.

Best practice for marketplaces is periodic re-verification — running the seller's ABN through KYB again every 6–12 months to confirm continued compliance. Osapher certificates expire after 90 days, prompting natural re-verification cycles.

See Applicant Onboarding Portal for the link-based seller verification flow, or read about the KYB Verification Engine for API integration options.

Risk thresholds for marketplace decisions

Different marketplaces set different risk thresholds based on the nature of their transactions and their own risk appetite. A common pattern:

• Low-value transactions: Allow all entities scoring 0–50 to list, with enhanced monitoring for scores above 20
• High-value transactions: Restrict listing to entities scoring 0–20 only, with manual review required for 21–50
• Regulated categories: Require score 0–10 and additional documentation for any listing involving regulated goods or services

The Fracture Score™ gives marketplace compliance teams a consistent, objective basis for these decisions rather than relying on subjective case-by-case assessment.