To detect shell companies and synthetic business identities, compare independent layers of evidence instead of trusting any single check: formation date against claimed history, registered address against operating address, business credit file against stated age, domain and phone records against the application, and bank deposits against revenue evidence. Fabricated businesses usually pass each layer alone. They rarely stay consistent across all of them.

This guide is for underwriting, risk and onboarding teams at alternative lenders, merchant cash advance funders, fintechs and payment processors. It defines the three terms people mix up, walks through how synthetic business identities are built, gives a detection method for each evidence layer, covers controls for digital onboarding, lists the operational signals worth requiring, and ends with a review checklist that uses no score and a documentation standard. For the data sources themselves, see our companion guide to KYB verification software; this article is about how to read those sources against each other.

What is the difference between a shell company, a shelf company and a synthetic business identity?

A shell company is a real entity with little or no operating activity, a shelf company is a real entity formed earlier and left dormant so it can be sold with apparent age, and a synthetic business identity is a business profile assembled from real and fabricated pieces to pass verification. Only the last one is fraud by definition.

Shell company

A shell company is a legally registered entity with no meaningful operations, staff or physical presence. FinCEN's advisory FIN-2006-G014 on shell companies describes them as typically having no physical presence beyond a mailing address and notes that most are formed for legitimate purposes, such as holding assets or facilitating a merger. In lending, the problem is a shell presented as an operating business.

Shelf company

A shelf company, sometimes called an aged corporation, is an entity formed and then kept inactive so a buyer can later acquire it with an older formation date. The lending risk is that formation age gets presented as years of trading history, which it is not. A shelf company has an old registry record and no operating record to match it.

Synthetic business identity

A synthetic business identity combines real and fabricated elements into a business profile built to pass validation. FinCEN's deepfake media alert FIN-2024-Alert004 uses the same idea, defining synthetic identity as a mix of real and fake identifying information used to fabricate a person or entity. A typical example is a real LLC and EIN paired with manufactured revenue and an altered owner ID.

The distinction matters for how you respond. A shell or shelf entity is not evidence of fraud, so the question is whether a real operating business stands behind the application. A synthetic identity is a deliberate construction, so the question is whether its arranged evidence holds across sources the applicant does not control.

How are synthetic business identities built?

Synthetic business identities are usually assembled in a recognizable order: register an entity, add contact points, build a thin web footprint, seed a business credit file, simulate revenue through a bank account, and then apply with documents that tie it all together. Each step uses a real service, so each step leaves a real record.

An illustrative construction pattern. Real schemes skip, reorder or repeat steps; the point is that every step leaves a record you can compare with the others.

Formation. Online formation takes minutes in many states, and a registered agent service supplies the in-state address the filing requires. The entity, its filing number and its EIN are all genuine. Some schemes buy a shelf company instead.

Contact points. A VoIP number and a virtual office or mail-forwarding address give the business a phone and a street address that look ordinary on an application. FinCEN's 2006 advisory already described agents selling service packages that create an appearance of local presence; the same products are cheaper and faster to buy today.

Web footprint. A domain, a template site and a few free directory listings make the business searchable without proving it operates.

Credit file. Some suppliers report small trade accounts to business credit bureaus, and these are openly marketed as a way to establish business credit quickly. A few such accounts paid on time produce a file with a payment history, which then looks like a reference.

Simulated revenue. Money moves into the business account from accounts the operator controls, sometimes labeled to look like customer payments, and often leaves again quickly. The account is real and the deposits really happened. They are just not revenue. This is the step most closely tied to bust-out fraud, where a business builds an attractive profile, borrows from several funders at once and disappears.

Application documents. Finally, statements, tax returns or IDs are edited or generated to close any gaps. This is where synthetic-document detection and fabricated document detection come in: checking file structure, fonts, arithmetic and metadata on each document, covered step by step in how to detect fake bank statements and edited PDFs and in our broader guide to document fraud detection in underwriting. FinCEN's 2024 alert reports criminals using generative AI to alter or create identity documents. A well-made fake still has to agree with every record the applicant did not make.

Why do shell companies and synthetic identities pass single checks?

They pass because most verification checks ask whether something exists, and in a synthetic identity almost everything exists. The entity is registered, the EIN is real, the account is open and the website loads. Detection depends on asking whether the pieces agree with each other and with a plausible operating business.

Each check answers one of three questions. Existence: is there a registered entity with this name? Ownership: does the applicant control it and the bank account? Operation: is a real business generating the revenue claimed? Shells and synthetic identities are designed to pass the first two, so operation is where review time should go.

The other reason is organizational. When verification, bank statement analysis and fraud review happen in separate tools, the person who sees a five-month-old formation date may never see the deposits that claim four years of revenue. The layer method below reads every finding against the others in one file.

How do you detect shell companies and synthetic business identities, layer by layer?

Work through seven layers, from the entity record to the money, and for each one write down what the layer says about age, location, ownership and activity. Then compare the answers across layers. One odd finding is a question; several findings that point the same way are a pattern.

Seven layers read against each other on one illustrative file. No single row is a reason to decline; the alignment of all seven is what calls for a person.

Registry, formation and identity inconsistencies

Pull the Secretary of State record and compare it field by field with the application: exact legal name, entity type, formation date, status, registered agent, principal office address and listed officers or managers. Inconsistencies that matter most are an officer list that does not include the applicant, a principal office in a different state than the claimed operations without a foreign registration where one would be expected, an entity that was administratively dissolved and reinstated just before the application, and a recent change of officers or registered agent. That last pattern can indicate a purchased shelf or a recently acquired shell. Our KYB for lenders guide covers the registry lookup itself.

Formation age against claimed history

A business registered weeks or months before applying, showing financials that would be strong even for an established company, warrants closer verification. It does not warrant automatic rejection: legitimate businesses re-form as new entities, convert from sole proprietorships or change states, and some do grow fast. Ask for the predecessor entity or prior trade name and check that it existed. The reverse case also matters. An old formation date with no matching credit, web or banking history is the signature of a shelf company being presented as an established one.

Registered-agent and virtual-office addresses

FinCEN's 2006 advisory lists businesses that share an address, or that provide only a registered agent's address, among its shell company red flags. Using a registered agent is normal and often required, so the agent address on the registry is not a concern on its own. The concern is when it is the only address anywhere: on the application, the bank account, the website and the credit file. Check whether the operating address resolves to a commercial mail receiving agency, a virtual office, a coworking membership or a residence, and whether many unrelated businesses list the same suite. A residential address is fine if it fits the business claimed.

Web presence, domain age and digital footprint

Look up the domain's registration record, now served through RDAP, which ICANN describes as the replacement for the WHOIS protocol, and compare the registration date it returns, where available, with the claimed years in business. A four-year-old business whose only domain was registered last month needs an explanation. Then check whether the site names the legal entity, shows the address and phone on the application, and describes products consistent with the stated industry. A missing website is not suspicious for many trades. A brand-new, generic website for a business claiming substantial revenue is more informative than no website.

Phone and address intelligence

For the phone, note the line type (landline, mobile or VoIP), the carrier and, where your data provider supplies it, how long the number has been active. VoIP is ordinary for small businesses, so treat it as context. The stronger signal is reuse: the same phone, email domain, address or bank account appearing on applications for businesses that claim to be unrelated. That check needs only your own application history, and it is one of the most effective tools against synthetic rings, because operators reuse infrastructure across identities.

Bank account ownership and deposit behavior

First confirm that the account holder name matches the legal entity and that the account has existed for the period the statements claim. A direct connection to the bank through a data aggregator, where the applicant agrees to one, is stronger evidence than an uploaded PDF. Then read the deposits for source, not just volume. Signals of manufactured history include deposits from a small number of related accounts, round-number transfers that dominate revenue, money that leaves within a day or two of arriving, deposits labeled as customer payments that come from the owner's personal account, and a pattern that does not match the industry. A restaurant should show card settlements across most days; a contractor should show checks or ACH from identifiable customers.

Just as telling is the expense side. A real operating business pays for things: payroll or contractors, rent, inventory, utilities, software, insurance, taxes. A shell with simulated revenue often shows strong inflows and almost no ordinary operating outflows, because nothing is being produced. Our explainer on how bank statement analysis software works covers transfer detection and categorization, and the guide to stacking covers recurring debits from other funders, which a bust-out profile often shows shortly before default.

Revenue evidence cross-checks

Revenue claims appear in several places, and a synthetic identity has to fake all of them consistently: the stated revenue on the application, bank deposits net of transfers and loan proceeds, card processor statements, marketplace payout reports, tax returns and, where provided, accounting exports. Reconcile them. Processor statements should match settlement deposits in the bank account within normal timing; a tax return should not report a small fraction of what the bank statements show without an explanation; marketplace payouts should arrive from the marketplace, not from an individual. See bank statements vs accounting data.

How can lenders detect shell companies through business credit report inconsistencies?

Read the business credit report as a history and check whether that history matches the application: the file's age against the claimed years in business, the trade lines against the stated industry and size, and the names, addresses and phones on file against everything else. Shells show thin, young or mismatched files. Synthetic identities show files built quickly from a few small accounts.

Specific inconsistencies worth checking:

  • File age against claimed history. A business claiming four years of trading whose credit file was opened six months ago, or whose oldest trade line is recent, has a history gap that needs an explanation.
  • Trade mix against size. A file made only of small accounts with suppliers that are known for reporting quickly, and no trade lines from industry suppliers, landlords or equipment lessors, does not look like a business with the revenue claimed.
  • Trade volume against revenue. If the application implies hundreds of thousands in annual revenue, the file usually shows supplier relationships of some scale. Tiny balances against large claimed sales are a mismatch.
  • Identity fields on file. Compare the names, officer names, addresses, phone numbers and industry codes recorded on the file with the registry and the application. Several different addresses or phones in a short time, or an industry code for a different trade, deserve a question.
  • Linked businesses. Some reports show other businesses at the same address or with the same principals. A cluster of young businesses sharing an address or owner is a stronger signal than any single file.
  • Inquiry pattern. A burst of recent inquiries from lenders can indicate an applicant shopping several funders at once, the setup for stacking or a bust-out.

Two cautions. A thin file is common for young or cash-based small businesses, so thinness alone should lead to a request for other evidence rather than a decline. And business credit coverage varies by bureau and by business type, which our KYB verification software guide discusses. The value of the file in shell detection is less its score than whether its history agrees with the other layers.

What are the best methods for fintechs to detect shell companies and synthetic business identities during digital onboarding?

The best onboarding methods collect structured identity data up front, verify it automatically against independent sources, check it against your own past applications for reuse, ask for stronger evidence only when layers disagree, and send disagreements to a person instead of declining automatically. That keeps friction low for real businesses and raises the cost for fabricated ones.

An onboarding flow that adds friction only where layers disagree. The lender's underwriter makes the decision at the end.

Collect structured identity at the start

Ask for the exact legal name, formation state, entity number where available, EIN, operating address, registered address if different, business phone, website, industry, years in business, and every owner and control person. Structured fields can be checked automatically. Free text and uploaded documents have to be read, which is slower and easier to fake around.

Verify against sources the applicant does not control

Run the registry lookup, address type check, phone line check, domain lookup, business credit pull and sanctions screen automatically, and store each result with its source and timestamp. Link each owner's KYC to the entity: the person should appear in the registry, on the bank account or in some other record tying them to the business. The KYB vs KYC guide explains where the two checks meet.

Check for reuse across your own applications

Compare each new application's phone, email domain, operating address, bank routing and account number, owner identifiers and uploaded file hashes with your history. Reuse across businesses that claim no relationship is one of the clearest synthetic signals available, because it comes from your own data and does not depend on a third party's coverage. Note that related businesses with a common owner legitimately share details, so the finding to record is undisclosed reuse.

Prefer direct data to uploaded documents

Where the applicant agrees, a direct bank connection or processor data feed removes most of the room for edited statements. When documents are uploaded, run synthetic-document detection on every one: file metadata, producer software, font and layout consistency, running balance arithmetic, and comparison against known templates. FinCEN's 2024 alert notes that institutions often found synthetic content by re-reviewing account opening documents, which is a reason to keep the originals and the checks run on them.

Step up instead of declining, and route by risk

When layers disagree, ask for evidence that is costly to fake: a signed lease or utility bill for the operating address, processor statements, a state license for regulated trades, supplier invoices, or a short video call at the premises. Use your own portfolio outcomes by industry, channel and geography to decide which applications get deeper review by default. Industries that are hard to verify externally, and channels or regions where your own losses have clustered, can route to deeper review without declining anyone automatically.

Which business identity data should risk teams require to review business legitimacy alongside operational signals?

Require two sets of evidence and compare them: identity records that prove the entity exists and who controls it, and operational signals that prove it does business. Identity records alone confirm that a company exists. Operational signals show whether it trades, and their absence is what separates a shell from an operating company.

This applies to payment processors onboarding merchants as much as to lenders. Our guide to merchant underwriting explains how the two contexts differ, and its section on services that surface merchant operational signals covers the data categories. For shell detection, a practical minimum looks like this:

  • Identity records: legal name, entity number, formation state and date, status, registered agent, EIN evidence, officers or managers from the registry, beneficial owners and control persons with KYC, sanctions screening results.
  • Location signals: operating address with its type (commercial, residential, mail receiving agency, virtual office), whether it matches the registry, bank and website, and whether other unrelated businesses share it.
  • Contact signals: phone line type and history, email domain and whether it matches the website, domain registration date.
  • Activity signals: bank deposits by source with transfers removed, ordinary operating outflows, card processing or marketplace payout history, refunds and chargebacks where relevant.
  • Industry signals: state or professional licenses for regulated trades, industry codes consistent across registry and credit file, a website or listings describing goods or services that match the stated industry and the merchant category.
  • Third-party traces: customer reviews with real history, supplier relationships on the credit file, mentions in trade or local directories that predate the application.

A useful written rule is that every claim of operation, such as years trading, monthly revenue or number of locations, should have at least one source the applicant did not create. If none exists, the file goes to step-up or human review. This replaces a score with a question a reviewer can answer and an auditor can follow.

Note what is no longer available. According to FinCEN's beneficial ownership information page, an interim final rule published March 26, 2025 exempted entities formed in the United States from beneficial ownership reporting under the Corporate Transparency Act, and a final rule effective August 14, 2026 made that exemption permanent. Lenders cannot check a domestic applicant's owners against a federal filing, so ownership has to be established from registry records, bank account ownership and the owners' own KYC. This area has changed several times, so check the current FinCEN guidance before relying on it.

What do FinCEN's shell company red flags mean for lenders?

FinCEN's 2006 shell company advisory was written for banks' anti-money laundering programs, but its red flags read almost directly as underwriting checks: activity that does not fit the customer's profile, payments with no clear purpose, shared or agent-only addresses, and transfers between related companies with no apparent business reason.

In an underwriting file, activity exceeding the projected profile becomes deposits that do not fit the stated industry or size; payments with no stated purpose become generic deposits from individuals rather than customers or processors; agent-only addresses are the address layer above; and high-value transfers between related companies are circular deposit activity. The advisory also describes nominee arrangements, where nominee officers, shareholders or signatories act for owners who are not disclosed, which is why the person applying should be traced to the entity through more than their own statement.

The advisory's due diligence approach is risk-based rather than a fixed checklist, with ongoing monitoring. Whether a particular lender has suspicious activity reporting obligations depends on its institution type and structure, which is a question for counsel.

How should underwriting leaders compare platforms that verify business revenue evidence?

Compare platforms on whether they reconcile revenue across sources with links to the evidence, not on whether they produce a number, because a platform that totals deposits will total manufactured ones too. The useful ones separate transfers and loan proceeds from revenue, identify counterparties, compare bank data with processor and tax evidence, and show the source for every flag.

Questions to put to every vendor, using your own anonymized files:

  1. Counterparty extraction. Does it identify who each deposit came from, and group deposits by source so you can see concentration?
  2. Transfer and related-party detection. Does it detect transfers between the applicant's own accounts and from owners, including across multiple statements and banks, and remove them from revenue?
  3. Cross-document reconciliation. Can it compare bank deposits with processor statements, marketplace payouts and tax returns, and show the differences rather than averaging them away?
  4. Expense profile. Does it show operating outflows by category, so a reviewer can see when a business has inflows but no costs?
  5. Document authenticity. Does it run synthetic-document detection on uploaded statements and explain what it checked, and does it accept direct bank data where available?
  6. Source links. Does every figure and every flag link to the page and line it came from? If not, your underwriters will re-check by hand.
  7. Explanations, not verdicts. Does it describe what was found and why it matters, leaving the decision to your team, or does it return an opaque score?
  8. Reviewer workflow and audit trail. Can reviewers record notes, overrides and the evidence they requested, and is that history kept with the file?

Test with files whose outcomes you already know. Our vendor due diligence questions cover security, data handling and model governance, and the comparison of bank statement analysis software vs underwriting platforms explains why reconciliation across documents usually needs more than a statement parser.

A review checklist for suspected shell or synthetic businesses

Use a checklist that records findings rather than points: for each question, mark corroborated, not found or contradicted, and cite the source. Not found is different from contradicted, and a scoring system tends to blur the two. The decision then rests on the pattern a reviewer can explain.

  1. Does the registry record match the legal name, entity type, status and officers on the application?
  2. Does the formation date fit the claimed years in business, or is there a documented predecessor entity?
  3. Is there an operating address other than a registered agent, and does its type fit the business?
  4. Do the registry, bank account, website, credit file and application agree on address and phone?
  5. Does the business credit file's age, trade mix and identity data fit the claimed history and size?
  6. Was the domain registered before the claimed start of trading, and does the site name the legal entity?
  7. Does the phone, email domain, address, bank account or owner appear on other applications you hold for unrelated businesses?
  8. Does the bank account holder name match the legal entity, and is the account as old as the statements suggest?
  9. After removing transfers, owner deposits and loan proceeds, what share of deposits comes from identifiable customers, processors or marketplaces?
  10. Does the account show ordinary operating expenses for this industry?
  11. Do processor, marketplace, tax and accounting figures reconcile with bank deposits within explainable differences?
  12. Did the uploaded documents pass authenticity checks, and do they agree with each other?
  13. Where layers disagreed, what step-up evidence was requested, and what did it show?

One contradicted item with a reasonable explanation describes many normal small businesses; contradictions across formation, address, credit history and deposits are the pattern this guide describes. If your policy has hard stops for certain findings, such as a confirmed altered document, keep them explicit and separate from this review, as described in our guide to underwriting rules, hard stops and knockout criteria.

How should shell company and synthetic identity reviews be documented?

Document each check with its source, the date it was retrieved, the result, and the reviewer's note, then record the decision and the specific findings it rests on. Someone reading the file a year later should be able to see what was known, where it came from, and why the lender decided as it did.

  • Keep the evidence, not just the conclusion. Save the registry extract, credit report, domain record, address and phone results, and the original uploaded documents with their file hashes.
  • Separate not found from contradicted. A missing website and a website naming a different company are different findings and should be recorded differently.
  • Record step-up requests and responses. What was asked for, when, what came back, and whether it resolved the question.
  • Write the reasoning in plain language, naming the specific findings and the evidence that could not be produced.
  • Log overrides with a reason and an approver. If a reviewer proceeds despite a contradiction, the file should say why and who agreed. See policy exceptions, overrides and the audit trail.
  • Follow your reporting obligations. Where an institution files suspicious activity reports, FinCEN's 2006 advisory asks filers to use the term shell in the narrative and include details such as the entities involved and any registered agent. Whether that applies to you depends on your institution type.

Files later confirmed as fabricated also show which layers caught them and which missed, which is how routing rules improve. Our pieces on underwriting audit trails and evidence-backed underwriting reports go further into file structure.

From here, this article is about Cevrynt

How Cevrynt supports fraud-aware verification

Illustrative exception view: a verification mismatch and an out-of-policy reading kept visible until a reviewer resolves them.
Illustrative view of Fraud Signals · synthetic dataSee Fraud Signals

Cevrynt is AI-assisted underwriting infrastructure for alternative lenders and MCA funders. Its Business Verification and Fraud Signals modules work from the same connected file as Bank Statement Analysis, so inconsistencies between registration records, deposit activity and application details are surfaced together rather than left for an underwriter to cross-reference across separate reports. Every flagged inconsistency links back to its source document or record.

Cevrynt surfaces these findings for human judgment. It does not render a fraud verdict, decline applicants automatically or make funding decisions; the lender's underwriters keep final authority, and their notes and overrides stay in the file's audit history. A walkthrough can show how this connected review works on representative files, or you can talk to our team.