International transfers
How an international transfer (ITC) request is submitted through the public four-step form, which documents and fee are required, and how the international federation and the two national associations approve, reject or reset it.
Looking for something else? The team roster (name list)
An international transfer is the process of moving a player from a club in one national association to a club in another national association, under the international federation that governs the sport. The international federation issues an International Transfer Certificate (ITC) once both associations have agreed and the administration fee has been paid.
In Profixio this is a self-service request form plus an administration screen:
- Anyone involved in the move — the player, the receiving club, or a national association — fills in a short International transfer form and submits it.
- Both national associations (the one the player is leaving and the one the player is joining) see the request and approve or reject their own side.
- The international federation confirms the administration fee, and can reject or reset the whole request.
- Everyone involved is kept informed by e-mail, and the two associations can exchange messages inside the request.
Profixio records and routes the request. It does not decide eligibility: whether a transfer is allowed at all, what deadlines apply and what the federation's transfer regulations require are federation policy, decided outside Profixio.
This is a separate feature from moving a player between two clubs inside the same national association — see the national transfers page for that.
You do not need a Profixio login to submit an international transfer request. The form is public, so a club official, a player, or an association employee can all use the same form.
Open the federation's page in Profixio and click the International transfer tab in the top menu. That tab is only present for federations that have the feature switched on; for those federations it replaces the Clubs and Districts tabs. If you cannot find it, ask the federation for a direct link to their transfer form.
The form is a four-step wizard: Step 1 Player → Step 2 Clubs → Step 3 Transfer type → Step 4 Confirmation. You cannot jump ahead — each Next button stays disabled until the current step has everything it needs, and skipping a step is blocked on the server too.
Because the form is open to anyone, there is a limit on how many searches and how many submissions can be sent in a short time. If you hit it you get "Too many searches. Please try again later." or "Too many submissions. Please try again later." — wait and try again.
Enter First name, Last name and Date of birth and click Search player. The help text under the fields says: "Enter first name, last name and date of birth. Only exact matches on all three fields are shown."
- Date of birth must be a real date in the format
yyyy-mm-dd. - The search only matches players who are already registered as members of that federation, and only when all three values match exactly. It is not a fuzzy or partial search — a middle name in the wrong field, a nickname, or a birth date that is a day out will give no hits.
- Clear empties the fields so you can search again.
If the player is found, the result appears under Search result with the player's name, birth date and nationality. Click the row to select it — it gets a Selected badge — and continue.
If the player is not found, you see No exact match found in the player database, a Manual verification needed badge, and a panel headed Player not found telling you to "Continue with passport upload in Step 1 validation." You then have to:
- leave the name and date of birth you typed in place (they become the player's details on the request), and
- upload a Passport copy — PDF, JPG or PNG, maximum 10 MB.
This is the normal route for a player who has never played in this federation before, and for foreign players who have no record in the federation's member register. The federation will match the passport to a person themselves before the request goes any further, so type the name exactly as it appears in the passport.
Step 2 is headed Transfer details — "Enter origin and destination associations and clubs."
- Former association and Former club — where the player is coming from. The association is picked from a list of the federation's member associations; the club is typed in as free text.
- New association and New club — where the player is going. Same again.
All four fields are required. The two associations must be different — if you pick the same one on both sides the request is refused when you submit it, with the error shown on New association.
Club names are free text, so spell them the way the club is officially known. There is no club register behind these fields, and the associations will read exactly what you type.
Step 3 is headed Applicant and transfer type — "Enter contact information, choose transfer type and provide supporting documents where needed."
Contact email (required). The note under the field says: "All communication regarding this transfer request will be sent to this email address." Use an address someone actually reads — it is the only channel the applicant gets.
Transfer type (required), one of two cards:
| Type | What the form says | Document |
|---|---|---|
| Amateur | "No contract required." | A Contract may still be attached, but is optional |
| Professional | "Signed contract attachment is mandatory." | A Contract must be attached before you can submit |
Contract upload: PDF, JPG or PNG, maximum 10 MB.
Additional comments is a free-text field — "Add any relevant information for [federation] or the associations involved", with the federation's short name filled in. Use it for anything the associations need to know that the form has no field for (loan period, previous transfer history, urgency).
Before the Submit transfer request button there is a Request summary card — "Review the entered information before submitting." — listing the player, the movement (From / To), the contact e-mail and the transfer type, with a Submission status box that says either "All required information is present." or "Missing required information." Read it before you submit; it is the last chance to catch a wrong association or a missing document.
As soon as the request is submitted, the confirmation screen shows a panel headed Administration fee payment required, with the amount, and the federation's IBAN, SWIFT, Bank name and Bank address. The same details are repeated in the confirmation e-mail, together with the payment reference to quote.
Points that catch people out:
- Payment is a plain bank transfer. There is no card payment, no invoice and no online checkout in this flow. You transfer the money yourself and quote the reference.
- The reference is the Transfer ID plus the player's surname (for example
FIB-2026-123456 Lund). Payments without it are hard to match and slow the request down. - There is nowhere to upload a receipt. The federation ticks the payment off manually once it lands in their account. If you have paid and the request still shows as awaiting payment after a few days, reply to the confirmation e-mail.
- The panel warns: "No International Transfer Certificate (ITC) will be issued until the payment is completed." The request can be approved by both associations and still not complete, because payment is a third approval in its own right.
The amount, currency and bank details are set by the federation, so what you see is whatever that federation has configured — do not reuse details from an older request.
The final step is headed Transfer request submitted and shows three things:
- Transfer ID — for example
FIB-2026-123456. Quote this in every e-mail and on the bank payment. Write it down; it is not e-mailed to you a second time if you lose it. - Player reference — the player's name as recorded on the request.
- Confirmation email — the address you entered, with the note "A confirmation has been sent to this email address."
A confirmation e-mail with the subject Transfer request … submitted goes to that address immediately, repeating the transfer ID, the player, the movement, the transfer type, the fee and the bank details.
There is no self-service tracking page. The applicant cannot log in and watch the request progress. Progress reaches the applicant only as e-mail: every time an association changes its decision, the payment is confirmed, or the request is approved, rejected or reset, an update e-mail is sent to the contact address (together with the associations and the federation). Rejections include the reason that was written.
Two things happen quietly behind the confirmation screen:
- If the player was matched in step 1, both national associations are notified straight away and can start reviewing.
- If the player was not matched, the associations are not notified yet. Only the federation is, with a "Player not found — action required" message. Review starts once federation staff have linked the request to the right person. This is the single most common reason for a request appearing to be stuck: nobody is waiting for the associations, the federation still has to identify the player.
Messages that the two associations exchange inside a request are between them and the federation. They are not shown to the applicant.
A request has one overall status, shown as a coloured badge:
| Status | What it means |
|---|---|
| Submitted | Received, but the player has not been identified yet. Only the federation can see it |
| Under review | The player is identified and the request is with the two associations and the federation |
| Approved | Both associations have accepted and the fee has been confirmed as paid |
| Rejected | Either association rejected it, or the federation rejected the whole request |
Underneath, three separate decisions have to line up, each of which is Pending approval, Accepted or Rejected:
- Former association — the association the player is leaving.
- New association — the association the player is joining.
- Payment — confirmed by the federation.
The request only reaches Approved when all three are accepted. A single rejection from either association makes the whole request Rejected, and a rejection by the federation overrides everything, even if both associations had already accepted.
If a request was decided wrongly, the federation can reset it, which puts all three decisions back to Pending approval and clears a federation rejection. A reset request goes back to Under review, not to Submitted, and everyone involved is told the transfer was reset.
- Moving a player between two clubs in the same national association — a different process with its own form and approvals. See National transfers.
- Player licences — having an approved transfer does not by itself give the player a licence for the new club. See Player licences.
- The player register — searching, merging and correcting person records, which is what federation staff use when linking a request to a player. See Person registry and search.
- Putting foreign clubs' players on a team sheet in an international tournament — a tournament team can register players as free text where the club is not in the register. That is a squad/roster feature and has nothing to do with transfer certificates. See Team roster.
Choose your federation to see rules that apply to you
Some of this page depends on your federation. Choose it at the top of the page to see the settings that apply to you.
International transfers is not a general Profixio feature. It is switched on per federation, and today it is in use by the International Bandy Federation (FIB) only. Other federations, including national federations, have no International transfer tab, no transfer form and no International transfers menu entry.
Two consequences worth knowing:
- On a federation that uses international transfers, the International transfer tab replaces the Clubs and Districts tabs in the public menu. That is deliberate: for an international federation the interesting units are the member associations, not individual clubs.
- What Profixio calls a "district" under an international federation is a member national association. That is why the form says Former association and New association while the rest of Profixio talks about districts.
Everything about eligibility — whether a player may transfer at all, transfer windows, age rules, sanctions, what the fee is and whether an ITC is issued — is the federation's own regulation. Profixio only records the decisions the federation and its associations make.
For other roles
Federation staff work the requests from International transfers in the admin menu. You reach it with a federation-level login that has user-administration rights, at a federation that has the feature switched on.
You see every request for your federation, including the ones where the player has not been identified yet.
Identify the player first. On a request with Player not linked, use Link player and search the federation's own player register. Only a player in that register can be selected — anything else is refused with "The selected player is not in this association's register." Linking is what releases the request to the two associations: they are notified at that moment, not at submission. Use Change linked player if the wrong person was picked; the associations are not notified a second time.
Check the documents. The Documents tab lists the Passport, the Contract and any Other attachment, each with a Download button. Missing attachments show as Not attached.
Confirm the payment. The Payment tab shows the Payment reference, the Amount, the current Payment approval and who last changed it. The checkbox — "Payment status — Toggle to mark payment as Approved or Pending" — is the only way payment is registered; it is a manual tick, not a link to a bank feed or the ledger. Only federation staff can use it.
Decide on behalf of an association if you have to: the pencil next to Former association or New association opens a Decision picker with Pending approval / Accepted / Rejected, and a Reason for rejection that becomes required when you pick Rejected.
Reject the whole request with Reject transfer. A written Reason for rejection is required, and the request is then marked as rejected by your federation regardless of what the associations decided.
There is no "approve" button for the request as a whole. A request becomes Approved by itself the moment both associations have accepted and you have ticked the payment.
Undo everything with Reset transfer (confirmation required). All three decisions go back to Pending approval and a federation rejection is cleared.
If you log in at association (district) level for a federation that uses international transfers, International transfers appears in your admin menu. You do not need user-administration rights — any association-level login can open it.
What you see is deliberately narrow:
- Only requests where your association is the former or the new association.
- Only requests where the player has already been identified by the federation. Requests still in Submitted are hidden from you completely — they are not in your list, they are not in the Status filter, and opening one by its address gives "not found".
What you can do:
- Decide your own side. The pencil next to Former association or New association is only shown for the side that is yours. Pick Accepted or Rejected in the Decision field; Reason for rejection appears and is required if you reject. Your decision is e-mailed to the applicant, both associations — including your own — and the federation.
- Ask a question in the Messages tab.
- Read the documents in the Documents tab.
What you cannot do: confirm payment, reject the request on the federation's behalf, reset a request, or link a player. Those are the federation's, and the buttons are not just hidden — the actions are refused if attempted.
Each request has a Messages tab. It is the discussion thread for that transfer between the two national associations and the international federation.
- Anyone who can open the request can post. The message box shows "Write a message as …" with the name you are posting under — your association's name, or the federation's short name if you are federation staff. You cannot post under anyone else's name.
- Messages are attributed on screen as the federation, or as the association with (Former association) / (New association) after the name, so it is always clear which side wrote what.
- Posting sends an e-mail to the other association and to the federation. If the applicant needs to know something, e-mail the contact address directly.
- Unread messages show as a red count on the Messages tab. Opening the tab marks them read for you only.
- A maximum of 5000 characters per message. Messages cannot be edited or deleted afterwards.
The list shows, per request: ID, Created, Approved date, Birth date, First name, Last name, Transfer type, From, To and Status. Newest first, 25 per page.
Above the list are four stat cards — Total transfers, Under review, Approved and Awaiting payment — counting the requests you are allowed to see. "Awaiting payment" means nobody has rejected it and the fee has not been confirmed yet.
Filters, applied when you press the filter button:
- Status — All transfers by default, then Submitted / Under review / Approved / Rejected. Association logins do not get the Submitted option, because they never see those requests.
- Created from and Created to — the date the request was submitted.
- Search — matches the transfer ID, first name, last name, the former club, the new club and the transfer type. It does not search comments or messages.
Export produces an Excel file of exactly what is on screen: the same ten columns, the filters and sorting you have applied, and nothing more. Documents, comments, messages, rejection reasons and payment details are not included — if you need those, open the request.
Contact Profixio support to turn the feature on for a federation. When it is off, the public form gives "page not found", the admin menu entry does not exist, and the settings below are not shown at all.
Once it is on, these settings are edited on the federation in the admin area, all prefixed International transfer:
| Setting | What it does | Where | Also means |
|---|---|---|---|
| International transfer: Fee amount | The administration fee shown to the applicant | Federation edit page | Free text, shown exactly as typed on the confirmation screen and in the confirmation e-mail |
| International transfer: Fee currency | Currency shown in front of the amount | Federation edit page | Free text. Currency and amount are simply joined together |
| International transfer: IBAN | Account number in the payment panel | Federation edit page | Shown publicly to every applicant |
| International transfer: SWIFT | BIC/SWIFT in the payment panel | Federation edit page | Shown publicly to every applicant |
| International transfer: Bank name | Bank name in the payment panel | Federation edit page | Shown publicly to every applicant |
| International transfer: Bank address | Bank address in the payment panel | Federation edit page | Shown publicly to every applicant |
| International transfer: Notification email | Where the federation's own notifications go — "player not found", decisions, messages | Federation edit page | "Separate multiple addresses with a comma or semicolon." Every address is validated. If it is left empty, the federation is not e-mailed about anything — not new requests, not decisions, not payments, and not the alert that a request needs a player to be linked |
Behaviour that is fixed and not configurable:
| Behaviour | Rule |
|---|---|
| Uploads | PDF, JPG or PNG, maximum 10 MB each |
| Passport | Required only when no player was matched in step 1 |
| Contract | Required for Professional, optional for Amateur |
| Association list | The federation's own member associations, active ones only. A district named "National Teams" is never offered |
| Same association both sides | Refused |
| Transfer ID | Federation short name, year and a unique number |
| Payment reference | Transfer ID plus the player's surname |
| Payment | Manual bank transfer, ticked off by hand. No invoice, no ledger entry, no card payment |
| Applicant tracking | E-mail only; there is no page the applicant can open |
| Document storage | Private cloud storage, reachable only through the Download button on the request |
The applicant cannot find the transfer form / gets "page not found"
- Does that federation have international transfers switched on? If not, the form does not exist for them and the International transfer tab is not in the menu. Contact Profixio support to switch it on.
- Are they on the right federation's page? The form belongs to one federation; a link for another federation will not work.
A federation administrator does not see International transfers in the menu
- Is the login at federation level, and does it have user-administration rights? Both are required.
- Is the login attached to the federation that has the feature, not to a club or a district?
An association says a request is missing
- Is the request still Submitted? Associations never see requests where the federation has not identified the player yet — this is intentional. Check the Status column at federation level.
- Is that association actually one of the two on the request? A typo on the former or new association hides it from the association that expected it and shows it to another one. Federation staff can see it and put it right.
The applicant has heard nothing
- Check the Contact email on the request for a typo — it is the only address anything is sent to.
- Was the player linked? If not, the associations were never notified and the request has not started.
- Check the federation's International transfer: Notification email setting — if it is empty, the federation gets no e-mail about this request at all, including the "player not found" alert.
The transfer is approved by both associations but not complete
Payment is the third approval. Check the Payment tab: Payment approval must be Accepted.
See also
Not covered here
Was this page helpful?