OnSubmit Free and fast tools
EN
English English EN Français Français FR Español Spanish ES Deutsch German DE Italiano Italian IT
Search
Finance · free tool

Fake French company generator for B2B test data

Generate coherent synthetic French company data with SIREN, SIRET, VAT, address, contact, IBAN/BIC and UUID.

Your tool

Fake French Company Generator

The same seed and location filters reproduce the same dataset. Every value is synthetic; official and banking existence is not checked.

Good to know

A fake French company is a synthetic test record that combines coherent B2B identifiers and fields without checking whether a business, establishment or bank account exists.

fake french companycompany data generatorfake SIRET VAT IBANB2B test datafake french company generator

Understand

Understand Fake French Company Generator

What is Fake French Company Generator?

A fake French company is a synthetic test record that combines coherent B2B identifiers and fields without checking whether a business, establishment or bank account exists.

Main use case: Create repeatable French company fixtures for B2B onboarding, CRM demos, invoice mockups, API payloads, CSV imports and QA scenarios.

Common use cases

B2B onboarding
Fill legal name, company identifiers, VAT, contact and registered office fields.
CRM demos
Create repeatable account records without copying registered companies.
Invoice mockups
Combine company identity, French VAT and test IBAN/BIC details.
API fixtures
Export nested JSON with linked identifiers, address, contact, activity and UUID.
Import QA
Export flattened CSV to test mappings, required columns and validation rules.

How to use the tool

  1. Choose a region, department or city for the registered office.
  2. Set the number of companies and a dataset seed.
  3. Select JSON, CSV or readable text.
  4. Generate, copy or download the dataset.
  5. Keep the records in test, demo or documentation environments.

Best practices

  • Reuse the same seed for stable fixtures.
  • Mark every generated record as synthetic.
  • Store identifiers and banking values as strings.
  • Test local format checks separately from official existence checks.
  • Never present generated records as registered companies or real accounts.
  • Use Sirene, VIES or an appropriate banking source only when real existence matters.

Common mistakes

Confusing coherence with existence
Luhn, VAT and IBAN checksums can be mathematically coherent without proving official or banking registration.
Using fixtures in production
Generated companies are for QA, mockups, training and demos, not official processes.
Editing only one identifier
Changing the SIREN without recalculating SIRET and VAT breaks record consistency.

Related terms and searches

fake French companysynthetic datalegal namelegal formAPE codeNAF codeSIRENSIRETNICFrench VAT numberIBANBICFrench addressUUIDCRMB2B invoicefixtureQA

FAQ

Frequently asked questions

What data is included in a fake French company?

Each record includes a synthetic legal name, legal form, APE activity, address, contact, SIREN, SIRET, French VAT number, IBAN/BIC and UUID.

Are generated SIREN and SIRET numbers valid?

They match expected lengths and Luhn checksum rules for local tests. This does not prove registration in the INSEE Sirene directory.

Is the VAT number linked to the SIREN?

Yes. The numeric VAT key is calculated from the same SIREN used in the record and in the first nine digits of its SIRET.

Does the generated IBAN belong to a real bank account?

The IBAN matches French format and MOD-97 checksum rules for tests. The tool does not check account existence or usability.

Do the generated companies exist?

The tool does not query Sirene, VIES or a bank. Records are synthetic and official existence is not checked.

Can I reproduce the same dataset?

Yes. The same seed, record count and location filters produce the same dataset.

Can I export fake companies as JSON or CSV?

Yes. JSON preserves nested structure, while CSV flattens fields for imports and spreadsheets.

Can I use this data on a real invoice?

No. Generated records must not be used for invoices, contracts, declarations or official procedures.

Are my inputs sent to a server?

OnSubmit tools run in the browser whenever the task can be processed locally. Avoid pasting production secrets, real banking details or personal data into public tools.