Skip to content

Doc 1041/germany proof of company reg #293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

ntombing
Copy link
Contributor

Not ready for team review yet. Just generating a preview for Alexa to see the structure.

@ntombing ntombing requested a review from racene-swan April 25, 2025 14:23
Copy link

linear bot commented Apr 25, 2025

Copy link

netlify bot commented Apr 25, 2025

Deploy Preview for incomparable-tiramisu-91a96a ready!

Name Link
🔨 Latest commit 9265952
🔍 Latest deploy log https://app.netlify.com/sites/incomparable-tiramisu-91a96a/deploys/6814c97d50f4850008676657
😎 Deploy Preview https://deploy-preview-293--incomparable-tiramisu-91a96a.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

| Genossenschaft (N/A) | Cooperative Society |
| Gesellschaft bürgerlichen Rechts (eGbR) | Registered Civil Law Partnership |

### Accepted documents for German companies
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The headings need to be updated because they're not consistent - here we say "for German companies" next it's "Self-employed and freelancers". Should it be German self-employed and freelancers"? They need to be clear and distinguishable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The next section is an H2 heading, so it didn't need that detail. I've simplified all the H3 headings to avoid confusion.
Screenshot 2025-04-30 at 15 51 06

### Accepted documents for German companies
The following table lists the accepted proof of registration documents for German companies.
:::info Document request
*Documents marked with an asterisk are sourced by Swan.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do we mean by "sourced by Swan"? We use "Whenever possible, Swan retrieves required documents independently." in the Docs. Is this the same?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same thing, but here we highlight the documents we retrieve. I've changed the word from 'source' to 'retrieve'.

The following table lists the accepted proof of registration documents for German companies.
:::info Document request
*Documents marked with an asterisk are sourced by Swan.
All other documents may be requested from the user on a case-by-case basis.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we say user - we're talking about the User in the account onboarding process?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're talking about the partner's end user.


| Document Type | German term |
| :----------------------------------------- | :----------------------------------------------------------- |
| Proof of Company Registration* | Nachweis der Firmenregistrierung* |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the table above, the first column is German, and the next is English. We should make this consistent across all the tables.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I played around with both options. I felt that different audiences may search for the doc type in English first, but it could go either way. So I've swapped them back to German -> English.

| :----------------------------------------- | :----------------------------------------------------------- |
| Proof of Company Registration* | Nachweis der Firmenregistrierung* |
| Articles of Association* | Gesellschaftsvertrag/Satzungen* |
| Ultimate Beneficial Owners (UBO) certificate* | UBO-Zertifikat* |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason why UBO has been spelled out twice?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, removed.

| Ultimate Beneficial Owners (UBO) certificate* | UBO-Zertifikat* |
| Identity documents of Ultimate Beneficial Owners (UBOs) | Personalausweis der wirtschaftlich Berechtigten (UBOs) |
| Power of Attorney and legal representatives identity card | Vollmacht und Personalausweis |
| Politically Exposed Person (PEP) Form | Formular für politisch exponierte Personen (PEP) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason why Form is caplitalised? Certificate isn't so wondering what the logic is.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, removed it.

| Partnerschaft | Partnership | Articles of Association |
| Gesellschaft bürgerlichen Rechts (eGbR) | Civil law partnership | - Articles of Association <br/> - Business or trade license (if available) |

### Accepted documents for Self-Employed and Freelancers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self-employed and freelancers needs to be consistently capitalised. In the section above employed isn't capitalised in the heading - and self-employed and freelancers isn't capitalised in the intro text.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it actually shouldn't be capitalized at all. I've updated it across the page.

| Gesellschaft bürgerlichen Rechts (eGbR) | Civil law partnership | - Articles of Association <br/> - Business or trade license (if available) |

### Accepted documents for Self-Employed and Freelancers
The following table lists the accepted proof of registration documents for self-employed individuals and freelancers in Germany.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does the heading not say self-employed individuals and freelancers?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simplified these titles to just say "Accepted documents"


| Document Type | German Term |
| :----------------------------------------- | :-------------------------------------------- |
| Business or trade license | Gewerbeschein |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment - German should come first if that's the standard we're doing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this has been addressed.

@ntombing ntombing requested a review from racene-swan April 30, 2025 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants