Draft stores details with a delay. Competing changes are seen by the revision.
Organisations
Application step by step
This page explains the application in the existing app. The organisation overview with real public data stays under Organisations. We invent no successful end and no worldwide tax recognition.
Information phase · Translations and operational release under reviewWho can apply
Charitable legal persons with an authorised contact person can apply.
You keep your existing account. The organisation is selectable as a large account type from the start.
Umbrella bodies and independent country branches are reviewed separately.
Registration does not activate donation receiving and not payout.
Phone and computer use the same wizard. Camera and file pick are available in the proof step.
States stay separate
Submit requires the server required fields, proofs, a bank account and released agreements.
Profile publish, donation receive, bank review and payout are independent admin decisions.
Released agreement texts are missing on purpose. Submit stays blocked.
A platform review is not state recognition and not a worldwide tax certificate. Shared limits stay 10 %, 5 %, 2,9 %, 15 %, 14 days, 2500, 10 MB and 5 MB.
Create an account and confirm email
Choose the account type Organisation. The public username is already checked for availability while you type.
Email and password stay private. After send the confirmation link arrives.
Account type, name and form data are stored before the confirmation screen and taken over after login.
Without a confirmed email there is no organisation access.
Profile photos are optional, JPG JPEG PNG or WebP up to 5 MB.
| Field | Required | Help |
|---|---|---|
| Account type | Required | Buyer, seller or organisation. Organisations do not buy. |
| Username | Required | 3 to 30 characters, public, unique. Period not at the start or end. |
| Email address | Required | For sign in and confirmation. Not public automatically. |
| Password | Required | At least 8 characters. |
| Repeat password | Required | Must match the password. |
| Profile photo | Optional | JPG, JPEG, PNG or WebP, at most 5 MB. Also possible later. |
| App language | Conditional | Required only on the seller path. Organisations use the app language. |
| Residence country | Conditional | Seller path only. 249 ISO countries. |
| Ship from country | Conditional | Only if the ship from place does not match the residence country. |
| Ship from city (optional) | Optional | Helps with shipping and pickup. Stays private. |
Create an organisation or continue a draft
After confirmation you open the organisation area and continue the draft.
Registration does not activate receiving.
Missing proofs can be added later. Submit stays blocked without them.
Save and continue later keeps the draft. Submit is a separate step.
There is one application per founder account. Memberships in further organisations remain possible.
| Field | Required | Help |
|---|---|---|
| Save and resume later | Optional | Save draft without submit. |
| Organisation workspace | Required | Entry after a confirmed account. |
Step 1 Identity
Here it is stated who should legally receive donations.
The server requires name, display name, form, country, founding, authority, status and receiving legal person.
Number or reason must be set. Both empty blocks submit.
An umbrella body does not create receive rights for other members.
These details are not a tax recognition.
Long step. The view shows the upper part. The table names all fields.
| Field | Required | Help |
|---|---|---|
| Registered legal name | Required | Server required. Full registered name. |
| Public display name | Required | Server required. Public display name. |
| Short name | Optional | Optional short name. |
| Legal form | Required | Server required. Reference list such as association or foundation. |
| Registration country | Required | Server required. ISO country of registration. |
| Founding year or date | Required | Server required. Year or date. |
| Register and responsible authority | Required | Server required. Register and authority. |
| Registration number | Conditional | Required if there is no reason for its absence. |
| Official register URL | Optional | Optional official register link. Do not type an HTTPS prefix. |
| Reason a register is unavailable | Conditional | Required if the number is missing. |
| Charitable status claimed | Required | Server required. Claimed status, not a world certification. |
| Tax / charity number | Optional | Optional. Country specific. |
| Parent organisation | Optional | Optional. Umbrella bodies are reviewed separately. |
| Relationship to parent organisation | Optional | Optional for the umbrella body. |
| Legal entity receiving donations | Required | Server required. Legal person that receives donations. |
Step 2 Contacts
Main contact with name, function, email, phone and language is required.
The contact mail must match a confirmed member mail. Otherwise verified_contact_email blocks.
Further contacts are repeatable. Per entry name, role and email are required, phone optional.
Legal representation, finance contact and partnership contact are optional.
These data stay internal unless you later set them public.
| Field | Required | Help |
|---|---|---|
| Contact full name | Required | Server required. First and last name. |
| Contact function | Required | Server required. Function. |
| Verified business email | Required | Must match the confirmed member mail. |
| Phone with country code | Required | Server required, with country code. |
| Preferred / original language | Required | Server required. Preferred source language. |
| Legal representative | Optional | Optional, in addition to the main contact. |
| Finance contact | Optional | Optional. |
| Partnership contact | Optional | Optional. |
| Name | Required | Repeatable further contacts. Name required per entry. |
| Role | Required | Role required per further contact. |
| Required | Email required per further contact. | |
| Phone | Optional | Phone optional per further contact. |
Step 3 Locations and countries
Headquarters and public email are server required.
Countries or a confidential reason must be set.
Scope is required: local, national, several countries or worldwide.
Locations are repeatable. Visibility private keeps protected places internal.
ISO countries come from the central list with 249 entries.
Repeatable locations. The view shows headquarters and the first location.
| Field | Required | Help |
|---|---|---|
| Registered headquarters address | Required | Server required. Registered headquarters, internal. |
| Different postal address | Optional | Optional if different. |
| Public contact address | Optional | Optional public. |
| Public email | Required | Server required, public. |
| Public phone | Optional | Optional public. |
| Actual operating / target countries | Conditional | Required if there is no confidential reason. |
| Confidential country information and justification | Conditional | Required if no public countries are set. |
| Geographic scope | Required | Server required: local, national, several countries or worldwide. |
| Name | Required | Repeatable locations. Name required. |
| Country | Required | Country required per location. |
| Visibility | Optional | private or public. Private protected places stay internal. |
Step 4 Public profile
Short text, description, mission and website are server required.
Fields of work, target groups, donation page, video and social links are optional.
Per social entry the URL is required, platform and visibility complete it.
Public texts can be translated later. 25 translations are not required for submit.
Changed source texts do not keep an old translation release.
| Field | Required | Help |
|---|---|---|
| Short description | Required | Server required. Short description. |
| Detailed description | Required | Server required. Long text. |
| Mission and objectives | Required | Server required. Mission and goals. |
| Areas of activity | Optional | Optional. Fields of work. |
| Supported target groups | Optional | Optional. |
| Website (HTTPS) | Required | Server required. Official website, without a forced https typing prefix. |
| Official donation page (HTTPS) | Optional | Optional. |
| Introduction video (HTTPS) | Optional | Optional. |
| URL (HTTPS) | Required | URL required per set social entry. |
Step 5 Logo and images
Images are JPEG, PNG or WebP. The hint names 5 MiB. The server accepts up to 10 MB and rejects PDF and SVG here.
Formats: square logo, mobile title image 4 to 5, desktop banner 3 to 1, optional light and dark, gallery.
Alternative text, credit and rights confirmation are required per upload.
Images are recoded. Public visibility needs a separate release.
Without images you can save the draft. Submit does not hang on a logo, but it does hang on the other server duties.
| Field | Required | Help |
|---|---|---|
| Square logo | Optional | JPEG, PNG or WebP. Hint 5 MiB. Server up to 10 MB. No SVG. Recoded. |
| Mobile cover (4:5) | Optional | Mobile title image 4 to 5. Same image rules. |
| Desktop banner (3:1) | Optional | Desktop banner 3 to 1. Same image rules. |
| Alternative text | Required | Required for every image upload. |
| Copyright / image credit | Required | Required for every image upload. |
| I hold the required media rights | Required | Rights must be confirmed with yes, otherwise no upload. |
Step 6 Proofs
For submit the server needs registration, statutes, representation, charitable status and partnership, each not refused and not expired.
At first registration proofs may be added later. Donation receiving stays blocked anyway.
PDF, JPG, JPEG, PNG or WebP up to 10 MB. Signatures are checked, PDFs are cleaned.
Type, title and language are required metadata. Issuer and dates are optional.
Public redacted versions are a separate process.
| Field | Required | Help |
|---|---|---|
| Registration evidence | Required | PDF or image up to 10 MB. Needed for submit, can be added later at account creation. |
| Statutes | Required | Statutes. Needed for submit. |
| Authority to represent checked | Required | Representation proof. Needed for submit. |
| Charitable status claimed | Required | Charitable status proof. Needed for submit. |
| Partnership agreement | Required | Partnership. Needed for submit. Texts are still missing. |
| Type | Required | Document type from the reference list. |
| Title | Required | Title required. |
| Preferred / original language | Required | Server required. Preferred source language. |
Step 7 Bank
At least one unblocked account is needed for submit.
SEPA requires euro and a valid IBAN. BIC is not forced for SEPA.
International needs IBAN or a local number plus required master data.
Ownership proof is required. No PIN or TAN.
New accounts start unreviewed. Confirmation is a later admin step.
SEPA fields in the upper part. International fields stand in the table.
| Field | Required | Help |
|---|---|---|
| Account holder | Required | Account holder required. |
| Account holder legal entity | Required | Must match the receiving legal person. |
| Bank name | Required | Bank name required. |
| Bank country | Required | Bank country required. |
| Currency (ISO 4217) | Required | ISO 4217. SEPA only euro. |
| Payment route | Required | SEPA or international. |
| IBAN (where applicable) | Conditional | Required and checked for SEPA. Otherwise one of IBAN or account number. |
| Local account number | Conditional | On the international path if there is no IBAN. |
| BIC / SWIFT (if required) | Optional | Optional, not forced for SEPA. |
| Account ownership evidence | Required | Ownership proof required. |
Step 8 Agreements and submit
Only versioned, released texts can be accepted.
The stored drafts are not released. The surface names missing texts and blocks submit.
Acceptances would store person, time, version and text state. That is not reachable now.
Marketing consent is separate and off by default.
We show no successful finish.
| Field | Required | Help |
|---|---|---|
| I am authorised to represent the organisation and accept these versions | Required | Only versioned released texts. Currently blocked. |
| Optional marketing consent | Optional | Separate, off by default. |
Review, questions and resubmit
Admins review existence, representation, contacts, charitable status, ownership, provider path, countries, purpose, media and agreements.
Resubmissions can carry field, deadline and message.
Internal notes stay internal.
Refusal is not a certification. A new state stays versioned.
Nobody releases their own organisation.
| Field | Required | Help |
|---|---|---|
| Review all information before submitting | Required | Check all details before submit. |
| Message to organisation / reason | Optional | On resubmit with field reference and deadline. |
Members
Owner, editorial, finance and read access are separate.
Invites hang on the confirmed email and can be revoked.
Read members see no bank details and no donor addresses.
Revoke blocks new downloads. Short links expire after 60 seconds.
Several organisations per person are possible through membership.
| Field | Required | Help |
|---|---|---|
| Required | Confirmed email of the invited person. | |
| Role | Required | Owner, editorial, finance or read access. |
Dashboard
Organisation accounts start with dashboard, appeals, inbox and profile.
If the workspace is missing, the surface leads back to the application.
Documents can be added later through the dashboard in the wizard.
Several organisations appear as a choice, not as a silent switch.
The dashboard does not claim a booked donation.
| Field | Required | Help |
|---|---|---|
| Organisation | Conditional | Choice when several organisations exist. |
| Refresh | Optional | Reload the state. |
Donation appeal
Appeals use purpose, photo and countries or worldwide.
General support without a purpose can be activated separately.
Without a purpose a later assignment goes to the organisation once receiving is allowed.
An appeal is not a payment and not a tax certificate.
Releases for image and receiving stay their own states.
| Field | Required | Help |
|---|---|---|
| Specific use of donations | Optional | Without purpose general support, if activated. |
| Actual operating / target countries | Optional | Single available countries or worldwide. |
| General organisational support | Optional | Can be activated separately. |
Project and earmarking
Projects need title, short text, description, language, cause category, countries, binding, purpose, start, currency, reviewed account and completion rule.
Binding can be one country, shared countries or separate pots.
Shared funds do not fulfil an exclusive lock to only one country.
Event, region, goal, target amount and reports are optional or complementary.
Project photos follow JPEG PNG WebP, client check up to 10 MB.
Long form. The view shows title and binding. The table names all required fields.
| Field | Required | Help |
|---|---|---|
| Title | Required | Title required. |
| Short description | Required | Server required. Short description. |
| Detailed description | Required | Server required. Long text. |
| Purpose category | Required | Cause category required. |
| Actual operating / target countries | Required | Required if there is no confidential reason. |
| Donation restriction | Required | One country, shared countries or separate pots. |
| Specific use of donations | Required | Concrete use of funds required. |
| Start date | Required | Start date required, format YYYY MM DD in the help. |
| Currency (ISO 4217) | Required | ISO 4217. SEPA only euro. |
| Verified payout account | Required | Reviewed payout account required. |
| Completion, overfunding and cancellation rule | Required | Rule for completion and non performance required. |
Contacts per country
Owner and editorial maintain several contact persons per country.
Function, address, email and phone stay internal.
Changes check the version against concurrent edits.
These contacts are not automatically the public profile.
They do not replace the required contact of the application.
| Field | Required | Help |
|---|---|---|
| Country | Required | ISO country. |
| Name | Required | Name of the contact person. |
| Role | Required | Function of the contact person. |
| Address | Optional | Internal, not public. |
| Optional | Internal email of the contact person. | |
| Phone | Optional | Internal phone of the contact person. |
Messages and attachments
New message opens the recipient choice. Only parties of booked donations or LuxCharity.
Send delivers text and an optional attachment. PDF JPG PNG WebP up to 10 MB.
Admins in the messenger have no access to donor conversations through the support right.
The review channel in the application stays separate.
Hide conversation removes only the own inbox view.
| Field | Required | Help |
|---|---|---|
| Message to organisation / reason | Required | Text is delivered only after send. |
| Attachment | Optional | PDF, JPG, PNG, WebP up to 10 MB. Optional. |
Donation overview and receipts
The overview is based on booked assignments after refunds, split by currency and environment.
Duplicate older entries do not raise sums.
Receipts belong to the assignment. That is not tax recognition.
Only owner and finance of the receiving organisation and the donating person see the planned address data.
Downloads are private, valid 60 seconds. An upload changes neither capture nor bank status.
| Field | Required | Help |
|---|---|---|
| Assignment | Required | Belongs to a finance assignment after refund. |
| Receipt file | Optional | PDF or image up to 10 MB. No tax recognition. |
Set up payout
Receive and payout are separate switches in the admin file.
Confirmed account, valid proof and a later provider state are preconditions.
Without a provider connection the status stays pending. That must not be set as success.
Organisation shares additionally need a manual release.
Bank times start only after release of the transfer, not with the buyer payment.
| Field | Required | Help |
|---|---|---|
| Donation reception | Required | Admin decision, separate from the profile. |
| Authorize payouts | Required | Admin decision, separate from receiving. |
| Payment provider verification | Conditional | Without a payment connection not settable as reviewed. |
What is possible after a release
After a profile release, reviewed public details can become visible. That is not receiving.
After receive release the organisation may be chosen as a donation recipient if proofs stay valid.
After bank confirmation and a later provider state a payout can be prepared. Bank times follow after that.
Members can use appeals, projects, country contacts and messages as far as their role allows.
We show no invented successful finish and no real payout.