Delivery can look real. The competition was not.

What looked normal

Three vendors bid. One won. Invoices matched the award. Goods or services arrived. On the surface, procurement worked.

Then someone joined vendor master to bank details. All three suppliers paid into the same account. That is not three competitors. That is one economic party wearing three badges— classic cover for bid rigging.

Why people should care

If work is delivered, why does it matter? Because you did not get a market price—you got a managed one.

Fake bidders rotate wins, submit cover bids, and keep prices high. The tender looks competitive. It never was. Shared bank accounts, addresses, tax IDs, or contacts are how that collusion shows up in data.

Seven analytics that catch fake competition

These tests use vendor master, bid/award history, and payment data— fields most ERPs and e-procurement systems already hold.

  1. Competing vendors sharing a bank account

    Vendors that bid against each other but remit to the same account or IBAN.

    Business impact: Strong signal that “competitors” are not independent.

  2. Shared tax ID, address, or phone across bidders

    Match master fields across vendors that appear on the same tender.

    Business impact: Exposes related parties posing as separate suppliers.

  3. Same contact email or phone on multiple bidders

    Flag identical buyer-facing contacts across supposedly independent vendors.

    Business impact: Operational proof of common control.

  4. Rotating wins among a closed vendor set

    The same small group of vendors repeatedly win against each other over time.

    Business impact: Classic bid-rotation pattern in award history.

  5. Persistent cover-bid / runner-up pattern

    One vendor always finishes a narrow second; prices cluster just above the winner.

    Business impact: Suggests bids designed to lose, not compete.

  6. Vendor created shortly before winning

    Short gap between vendor create date and first awarded tender.

    Business impact: Rushed entities used to shape a tender outcome.

  7. Unusually close bid amounts across “competitors”

    Bid prices land in a tight band with little real spread for the same scope.

    Business impact: Price collusion signal when paired with shared identity.

Why tender reviews miss this

Traditional

Lowest compliant bid

Check completeness, thresholds, and who won. Assumes bidders are independent.

What risk needs

Identity + award joins

Bank accounts, tax IDs, contacts, and win patterns across tenders— not one award file in isolation.

Key takeaway

Bid rigging hides behind paperwork that looks complete. Join vendor identity to tender history—and fake competition stops looking competitive.

How foretale.ai helps

foretale.ai runs procurement risk analytics across vendor master, award, and payment data— shared bank accounts among bidders, related-party identity matches, rotating wins, cover-bid patterns, and price clustering—with explainable evidence for every finding.

Procurement and audit teams review prioritized collusion risks across tenders—not only the winning bid.

Was your last tender really competitive?

Shared supplier identities and award patterns often sit in data you already have. Continuous AI analytics can surface fake competition before the next award locks in inflated cost.

Request a demo