Registry entry
Cyprus Application for Registration of a Business Name by an Individual (Form EE1)
Register a business (trade) name under which a sole individual trades, filed with the Department of Registrar of Companies and Intellectual Property (Τμήμα Εφόρου Εταιρειών και Διανοητικής Ιδιοκτησίας, part of the Ministry of Energy, Commerce and Industry) under Article 52 of the Partnerships and Business Names Law, Cap. 116 (Ο περί Ομορρύθμων και Ετερορρύθμων Συνεταιρισμών και Εμπορικών Επωνυμιών Νόμος). Form EE1's own "Details of the Owner or of the Owning Company" section covers both an individual owner and a body-corporate owner on the same page; this document is scoped to the individual-owner path only (the applicant is a natural person trading in their own name/right), mirroring how this registry already scopes ie/cro/business-name-registration-individual to the individual-applicant variant of Ireland's structurally similar business-name-registration form. A body-corporate owner (company name plus its own registration number, printed on the same form) is out of scope — see VERIFICATION.md. It does not submit the registration; the live companies.gov.cy source is always authoritative. GovSchema is independent and is not affiliated with, endorsed by, or operated by Cyprus or the Department of Registrar of Companies and Intellectual Property.
Registry entry
cy/drcor/business-name-registration-individual
Authoritative source Form EE1 — "Αίτηση για εγγραφή εμπορικής επωνυμίας" (Application for registration of a business name), native flat PDF, 1 page
Machine access
- Schema document
registry/cy/drcor/business-name-registration-individual/1.0.0/schema.jsonapplication/schema+json- Verification record
registry/cy/drcor/business-name-registration-individual/1.0.0/VERIFICATION.mdtext/markdown- Registry catalog
registry/index.jsonone record per schema id
Field reference
40 fields across 5 steps, read from the published schema.json, with names, types, requiredness, and validation as the document states them. The live government form remains the authoritative source.
Business name, nature of business, and place of business
-
businessNamestring requiredThe trade name being registered under Article 52 of Cap. 116.
length: 1–160 -
natureOfBusinessDescriptionstring requiredA description of the business activity carried on under the registered name.
length: 1–500 -
nameApprovalApplicationNumberstring optionalThe reference number of a prior application to the Registrar for approval of the business name, where one was filed and obtained before this registration application. Not explained by any footnote on the source form (which carries none), so modelled as optional rather than assuming it is always obtained beforehand.
length: 0–60 -
natureOfBusinessCodestring optionalA business-activity classification code corresponding to natureOfBusinessDescription. The source form gives no key or list of valid codes, so this is modelled as an unconstrained optional string rather than a fabricated enum.
length: 0–30 -
placeOfBusinessStreetOrAvenuestring requiredPlace of business — street/avenue
length: 1–160 -
placeOfBusinessStreetNumberstring requiredPlace of business — number
length: 1–20 -
placeOfBusinessBuildingstring optionalPlace of business — building (optional)
length: 0–100 -
placeOfBusinessFloorstring optionalPlace of business — floor (optional)
length: 0–20 -
placeOfBusinessApartmentstring optionalPlace of business — flat/apartment (optional)
length: 0–20 -
placeOfBusinessParishTownVillagestring requiredPlace of business — parish/town/village
length: 1–100 -
placeOfBusinessDistrictstring requiredPlace of business — district
length: 1–60 -
placeOfBusinessPostalCodestring requiredPlace of business — postal code
length: 1–20
Owner's particulars
-
ownerGivenNamestring requiredPrinted on the same row as "Αρ.Εγγραφής" (Registration No.), which applies only to a body-corporate owner and is out of scope here — see VERIFICATION.md.
length: 1–100classification: pii -
ownerSurnamestring requiredOwner — surname
length: 1–100classification: pii -
ownerGivenNameLatinstring requiredOwner — given name in Latin characters
length: 1–100classification: pii -
ownerSurnameLatinstring requiredOwner — surname in Latin characters
length: 1–100classification: pii -
ownerPreviousGivenNamestring optionalOwner — previous given name (optional)
length: 0–100classification: pii -
ownerPreviousSurnamestring optionalOwner — previous surname (optional)
length: 0–100classification: pii -
ownerIdCardNumberstring optionalThe source form provides this alongside ownerPassportNumber with no printed note stating which nationality of owner uses which; disclosed here as an either/or rather than encoded as a brittle cross-field requirement (see VERIFICATION.md).
length: 0–30classification: pii -
ownerPassportNumberstring optionalSee ownerIdCardNumber — the source discloses no rule for which of the two identity-document fields a given owner must complete.
length: 0–30classification: pii -
ownerDateOfBirthdate requiredOwner — date of birth
classification: pii -
ownerNationalityCountrystring requiredOwner — country of nationality
length: 1–100classification: pii -
ownerOccupationstring requiredOwner — occupation
length: 1–160classification: pii -
ownerStreetOrAvenuestring requiredOwner — residential street/avenue
length: 1–160classification: pii -
ownerStreetNumberstring requiredOwner — residential number
length: 1–20classification: pii -
ownerBuildingstring optionalOwner — residential building (optional)
length: 0–100classification: pii -
ownerFloorstring optionalOwner — residential floor (optional)
length: 0–20classification: pii -
ownerApartmentstring optionalOwner — residential flat/apartment (optional)
length: 0–20classification: pii -
ownerParishTownVillagestring requiredOwner — residential parish/town/village
length: 1–100classification: pii -
ownerDistrictstring requiredOwner — residential district
length: 1–60classification: pii -
ownerPostalCodestring requiredOwner — residential postal code
length: 1–20classification: pii -
ownerCountrystring requiredOwner — country of residence
length: 1–100classification: pii
Commencement of business and other trade names
-
dateOfCommencementOfBusinessdate requiredDate of commencement of business
-
otherBusinessNamesstring optionalOther business names under which the business is conducted (optional)
length: 0–300
Signature
-
ownerSignatureConfirmedboolean requiredRecords the fact of the owner's wet signature on the printed declaration, not the signature image itself, consistent with this registry's convention for wet-signature declarations.
-
signatureDatedate requiredDate of signature
Correspondence details
-
correspondenceNamestring requiredThe name of the person or firm to whom the Registrar should address correspondence about this application (may differ from the owner, e.g. a representing advocate or accountant).
length: 1–160classification: pii -
correspondenceAddressstring requiredPrinted as a single free-text writing area, unlike the place-of-business and owner address blocks above which are printed as separately labelled street/building/floor/etc. boxes.
length: 1–300classification: pii -
correspondencePostalCodestring requiredCorrespondence — postal code
length: 1–20 -
correspondenceTelephonestring optionalCorrespondence — telephone (optional)
length: 0–30
Verification record
Candidate selection
GOV-4208 ("GovSchema Standard Research"). A fresh scan of CATALOG.md's own "Known Gaps & Opportunities" section (item 0b, banked GOV-4169, 2026-07-21) found Cyprus's Form EE1 (business-name registration by an individual) as the strongest genuinely-open, well-sourced candidate: an unauthenticated, non-Cloudflare-gated, single-page official PDF at companies.gov.cy, left unauthored only because that cycle's own scouting pass reported the Greek text as "glyph-index-encoded (no ToUnicode CMap), needing embedded-font glyph-mapping or a pixel-scan extraction pass beyond what that cycle's scouting attempted." This cycle re-examined that specific blocker before treating it as still valid, per this routine's own standing procedure of treating prior "confirmed" findings with some skepticism rather than accepting them at face value.
Reaching the live source
Re-fetched https://www.companies.gov.cy/assets/modules/wgp/articles/201801/53/docs/ee1.pdf directly with curl using a standard desktop Chrome User-Agent.
- HTTP 200,
Content-Type: application/pdf,Content-Length: 87675,Last-Modified: Tue, 07 May 2019 12:38:56 GMT— byte-identical to the GOV-4169-era fetch (same content-length recorded in CATALOG.md). - No login, CAPTCHA, or WAF gate on the asset itself.
The glyph-encoding concern did not reproduce
Loaded the PDF with pdfjs-dist's legacy Node build (legacy/build/pdf.js, from a pre-existing /tmp/node_modules/pdfjs-dist install used by many prior cycles) and called page.getTextContent() directly — no manual glyph-to-Unicode mapping pass, no pixel-scan render step. The returned item.str values are clean, directly readable Modern Greek Unicode text end to end (e.g. "Αίτηση για εγγραφή εμπορικής επωνυμίας", "Ο ΠΕΡΙ ΟΜΟΡΡΥΘΜΩΝ ΚΑΙ ΕΤΕΡΟΡΡΥΘΜΩΝ ΣΥΝΕΤΑΙΡΙΣΜΩΝ ΚΑΙ ΕΜΠΟΡΙΚΩΝ ΕΠΩΝΥΜΙΩΝ ΝΟΜΟΣ"). Whatever font-encoding property the prior cycle's own tooling observed either does not affect pdfjs-dist's text-extraction path or was mischaracterized; either way, no glyph-mapping or pixel-scan groundwork was actually needed to extract this form's text faithfully. This is disclosed as a genuine correction of a prior cycle's own recorded finding, not a silent overwrite of it.
Structure of the source
One page, 265 text items, page size 595×842pt (A4). No AcroForm fields — this is a flat, label-only printed form (confirmed by pdfjs-dist finding no annotation/field objects), consistent with cy/crmd/passport-application and most of this registry's other flat-PDF sources. Every text item's transform[4]/transform[5] (x/y) was extracted and items were grouped by rounded y-coordinate into printed rows, then ordered by x within each row — this recovers the form's genuine multi-column layout (e.g. the y=419 row prints "Αρ.Ταυτότητας" at x=137 and "Αρ. Διαβατηρίου" at x=351 side by side, and the y=366 row prints three columns — "Κτίριο"/"Όροφος"/"Διαμ." — on one line), which a single left-to-right text dump would not disclose.
Unlike ie/cro/business-name-registration-individual's RBN1 (8 numbered explanatory notes), this form carries no footnotes or explanatory notes at all — every field is a plain labelled box with no note to cross-reference. Every field description in this schema is therefore derived directly from the label text and general knowledge of Cyprus's business-name registration process (Cap. 116, Article 52), not from a footnote citation.
Disclosed source-fidelity findings and scoping decisions
- The owner-details section serves both an individual and a body-corporate owner on the same page. The section header itself, "Στοιχεία Ιδιοκτήτη ή Ιδιοκτήτριας Εταιρείας," literally reads "Details of the Owner or of the Owning Company." The first row of that section pairs "Όνομα" (Name) with "Αρ.Εγγραφής" (Registration No.) — the latter only meaningful for a registered body corporate — while the immediately following row, "Επώνυμο" (Surname), applies only to a natural person. This document is scoped to the individual-owner path only, mirroring how this registry already scopes Ireland's structurally similar business-name-registration form into
ie/cro/business-name-registration-individualspecifically. The body-corporate-owner path (ownerCompanyRegistrationNumberand a company name distinct fromownerGivenName) is not modelled; a future companion document could cover it the same wayie/cro/company-incorporationandie/cro/business-name-registration-individualare separate documents in this registry, rather than one document with a discriminated owner-type union. ownerIdCardNumberandownerPassportNumberare both optional, with no encoded either/or rule. The source form prints both boxes with no note stating which applies to which owner. This registry's own standing pitfall list (anotEquals-empty-string check against an absent optional field silently evaluates as if the field were present) specifically warns against encoding this kind of either/or as a brittlecrossFieldValidationrule, so the relationship is disclosed in each field's owndescriptioninstead.nameApprovalApplicationNumberandnatureOfBusinessCodehave no explanatory note distinguishing applicant-supplied from registrar-assigned values. Both are modelled as optional, unconstrained strings rather than asserting either interpretation as certain.- Two distinct address blocks, both split into the source's own separate boxes rather than collapsed to free text. Unlike RBN1 (whose address fields print as single ruled writing areas and are modelled as single free-text strings), EE1 prints the place-of-business address and the owner's residential address each as separate street/building/floor/ flat/parish-town-village/district/postal-code boxes (the owner's address additionally has its own country box; the place-of-business address does not, since a Cyprus-registered business's premises are necessarily domestic). This document follows the source's own granularity and splits each into its own leaf field, consistent with this registry's convention for other forms with genuinely separate printed boxes (e.g.
lv/ur/sole-trader-registration-kr2). - The correspondence address is the one exception, printed as a single free-text box ("Όνομα και Διεύθυνση για Αλληλογραφία" — Name and Address for Correspondence), unlike the two structured address blocks above — modelled as a single
correspondenceAddressstring accordingly. - No numbered-district checkbox grid. Cyprus government forms sometimes render the six historic districts as a checkbox row; this form instead prints a single blank "Επαρχία" (District) box in both address blocks, so
placeOfBusinessDistrict/ownerDistrictare modelled as free-text strings rather than a fabricated enum. ownerSignatureConfirmedrecords the fact of signature, not a signature image, consistent with this registry's convention for other wet-signature declarations (e.g.ie/cro/business-name-registration-individual's owncertificationDeclarationConfirmed).
Conformance
2 valid mock scenarios (valid-complete-individual-application.json, a Cypriot-national owner using an ID card number and only the statically-required fields; valid-foreign-national-passport-owner.json, a UK-national owner using a passport number, a company-presented correspondence address, and every optional field populated) plus 6 mutation-control fixtures (five missing- required-field cases, one from each of the five steps — businessName, ownerGivenName, dateOfCommencementOfBusiness, ownerSignatureConfirmed, correspondenceName — and one unknown-field rejection) are committed under conformance/cy/drcor/business-name-registration-individual/1.0.0/.
An ephemeral, from-scratch mock validator (deriving required-field and unknown-field rules directly from this schema's own fields[], not committed) ran all 8 fixtures: both valid scenarios at 0 errors, all 6 mutation controls each raising exactly 1 error.
node tools/validate.mjs and node tools/validate-ajv.mjs both pass for the full registry with this document included.
Scope boundaries
This document models only the individual-owner path of Form EE1 (see finding 1 above). It does not submit anything on an applicant's behalf; the live companies.gov.cy source is always authoritative. GovSchema is independent and is not affiliated with, endorsed by, or operated by Cyprus, the Ministry of Energy, Commerce and Industry, or the Department of Registrar of Companies and Intellectual Property.
View the raw record (VERIFICATION.md)
Version history
-
1.0.0draftlatestthis pagehas verification recordschema.json
Independent and non-affiliated
GovSchema is an independent, open-source project. This reference is not produced, reviewed, or endorsed by Department of Registrar of Companies and Intellectual Property or any government. The authoritative source is always the live government form and its official instructions.