01 / DIRECT ANSWER
How do you reverse a transfer in FC 26 Live Editor?
Load the intended Career, open the current Transfer History, identify the exact current-season row, protect the save, then use only the undo control presented by the live interface. Confirm the player’s club and both squads before and after a Career reload.
The README says they can be viewed and quickly undone.
OFFICIAL CONTRACTMatch identity, origin and destination; a similar name is not enough.
OUR SAFETY PROTOCOLLoan, release, finances and prior-season behavior remain undefined.
NO GUESSES02 / OFFICIAL CONTRACT
What Transfer History actually promises
The public product description contains one compact sentence: view all transfers done in the current season and quickly undo them if needed. The changelog shows the feature arrived in v26.1.8.
README / FEATURE CONTRACTView all transfers done in current season and quickly undo them if needed.
Official FC 26 Live Editor README
Added in v26.1.8.
The only explicit time range.
Read these from the compatible live UI.
03 / INTERACTIVE EVIDENCE LAB
Build a transfer-review receipt before touching the save
This local simulator classifies season, transaction type and row evidence. It cannot see FC 26 and deliberately cannot execute an undo.
Transfer Review Ledger
Plans evidence only · never reads FC 26
Classify the candidate row
Confirm the exact direction
Decision questionDoes the live row identify this same player and this same A → B move?
NOT A LIVE ACTION This ticket deliberately has no Undo button. Read the actual current interface and its confirmation before changing the Career.
Close the review receipt
The candidate fits the narrow documented scope, but the recovery and proof receipt is incomplete.
REALISM REVIEW · CURRENT · PERMANENT04 / AUDIENCE JOB
The real job is saving the story, not winning a menu
Career players describe implausible AI destinations, positional hoarding and distorted squads as immersion breakers. A reviewable undo matters because it can preserve years of context without restarting the whole save.
A star moves somewhere that breaks the save’s football logic.
The correct player was sent to the wrong club.
A club’s squad construction makes a league or Europe less believable.
Keep a written realism rule so the editor does not become a result generator.
05 / EXACT ROW
Identify the transaction, not just the player
A safe candidate has three matching coordinates: the player identity, the origin club and the destination club. Capture the row before making a decision.
Use the ID when names collide, change or truncate.
Where the player was registered before the move.
Where the current row says the player moved.
06 / TRANSACTION BOUNDARIES
A transfer is not automatically a loan, release or list edit
The README does not enumerate Transfer History subtypes. Elsewhere, the editor treats permanent transfer, loan, terminate loan and release as distinct actions, while listing and clauses change state without moving the player.
07 / TIME BOUNDARY
Current season is a hard evidence boundary
The official wording does not promise an archive after the Career rolls into a new season. Discovering an old bad move is not evidence that Transfer History can still reverse it.
Exact current-season transfer row → inspect live undo.
Use recovery evidence or label a manual repair as a different operation.
08 / RECOVERY SLOT
Protect the Career before the reversal
The official Editing Player Wiki tells users to make a backup by saving the Career in another slot. Keep that recovery point until the post-reload state is proven.
- 01Save to another slot
Name it with the in-game date and disputed player.
- 02Capture the original row
Record player, origin, destination and current season.
- 03Change one row only
Do not combine the review with unrelated player edits.
- 04Verify before overwrite
Keep recovery until squads survive a Career reload.
09 / OPERATION MODEL
Undo is not the same as transferring the player back
A counter-transfer is another forward movement. Transfer History is the documented quick-undo route; public sources do not prove that a manual return restores the same financial, contract or narrative state.
Use the current row and the live control attached to it.
DOCUMENTED INTENT: UNDOUseful only as an explicitly labeled workaround with separate proof.
NOT EQUIVALENT BY DEFAULT10 / ORIGIN QUESTION
Does it cover AI, user and editor-created transfers?
The README says “all transfers” in the current season but does not publish an origin taxonomy. The honest test is whether the exact row exists in the loaded Career—not an assumption about who initiated it.
Motivation is strong; origin-specific coverage remains unpublished.
Do not infer inclusion from base-game Transfer Hub history.
A separate tool action; confirm whether the row actually appears.
11 / ANALYTICS ≠ ACTION
Transfers In and Transfer History Balance are not Undo
Version v26.3.5 added five Teams List columns: Transfers Out, Transfers In, Transfer Income, Transfer Expenditure and Transfer History Balance. The changelog calls them columns, not reversal controls.
12 / SURFACE SEPARATION
Do not confuse three different histories
Search results mix the Live Editor feature with FC 26 Transfer Hub and Office budget transactions. They answer different questions and do not share an undo contract.
Current-season transfer review and quick undo.
THIS ARTICLEScouting and negotiation context.
NO LE UNDO PROOFOffice-level income and expense review.
FINANCE SURFACE13 / POST-ACTION PROOF
Verify the rollback on four surfaces
Because the public docs do not list every reversed field, prove the observable state yourself. A changed overlay row alone is not enough.
Exact ID remains the intended player.
Player is present where expected.
Player is absent where expected.
Save, exit the screen, reload and repeat checks.
Confidence limit: this proves club registration persistence. It does not prove unpublished financial, contract, statistical or news-feed rollback semantics.
14 / ROW MISSING
What if the transfer does not appear?
Stop before editing. A missing row can mean the wrong save, a prior season, a different transaction class or an identity mismatch; public sources do not define a hidden-history repair.
Is this the slot where the move happened?
Did the Career already roll over?
Are two similar names being conflated?
Was it a loan, release or state edit?
Document the unknown instead of manufacturing certainty.
15 / EDGE CASES
Wrong club, duplicate name and late discovery
These cases need different evidence. The presence of a familiar name is never sufficient to reverse a Career transaction.
Prove A → B from the row; do not “correct” it to a guessed Club C in the same operation.
Use a stable player ID and both squads before selecting any row.
If the row belongs to a prior season, the documented quick-undo scope has ended.
16 / VERSION GATE
Verify the game/editor pair before diagnosing history
At this research freeze, the official manifest maps FC 26 v1.6.6 build 1.0.139.20381 to Live Editor v26.3.5–v26.3.6. Recheck the live manifest after any game update.
Build 1.0.139.20381
Public / Silver at freeze
17 / REALISM POLICY
Use surgical correction, not invisible authorship
The most durable rule is one that can be stated before the transfer occurs. Correct only moves that violate that rule, and preserve a log of every intervention.
EXAMPLE HOUSE RULE“I reverse only a current-season AI move that leaves an elite club without a viable starter, duplicates a position irrationally or contradicts an explicit no-transfer setup rule.”
- TriggerWrite the football reason.
- EvidenceCapture the exact row.
- InterventionOne transaction only.
- ReceiptRecord the reloaded result.
18 / VIDEO EVIDENCE
What current videos prove—and what they do not
Four searches produced 48 result slots and 35 unique videos. None supplied a current caption-backed demonstration of the full Live Editor history-undo contract, so videos are used only for audience intent and surface separation.
Explains why bad transfer logic can distort clubs and competition.
01:41 / PLAYER CAREERMy Pro transfer routeA different mode and flow; excluded from Live Editor instructions.
00:35 / BASE GAMEBudget transactionsOffice finance history, not the Live Editor undo surface.
Official text remains the authority for scope and feature intent.
19 / FAQ
Transfer History and undo questions, answered precisely
01How do I undo a transfer in FC 26 Live Editor?+
Load the intended Career and use Transfer History to find the exact current-season transfer. Inspect the player and both clubs, protect the save, then use only the undo control shown by the current interface. Public documentation does not publish a more detailed click path.
02Does Transfer History include only the current season?+
That is the only scope the official README promises: transfers done in the current season. It does not promise an archive or undo after season rollover.
03Can I undo an AI transfer?+
The README says all transfers in the current season but does not divide rows by AI, user or editor origin. Treat the exact visible row as the evidence and do not promise origin-specific coverage before inspecting it.
04Can I undo my own transfer?+
The public documentation does not distinguish user and AI transactions. If the exact current-season row is present, inspect the live undo option; if it is absent, do not manufacture a guarantee.
05Can Transfer History reverse a loan?+
Loan coverage is not publicly enumerated. Loan and terminate-loan are separate operations elsewhere in the editor, so classify the row in the current UI instead of treating the word transfer as proof.
06Can it reverse a player release?+
Not on published evidence. Release to Free Agents is a separate Player Editor operation and the Transfer History sentence does not name releases.
07Can I undo a transfer from a previous season?+
No public source promises it. The official wording limits the feature to the current season, so use a recovery save or another documented correction plan rather than claiming a historical undo.
08What if the transfer is missing from Transfer History?+
Confirm the loaded save, current season, exact player identity and transaction class. If no exact row appears, stop; a new counter-transfer is not evidence that the original transaction was undone.
09Are Transfers In and Transfer History Balance the same feature?+
No. Those are Teams List analytics columns added in v26.3.5. The changelog does not say they provide an undo action.
10Does undo delete the player or move them to Free Agents?+
The public documentation does not define its internal reversal fields. Verify the player’s club, both squads and the Career after reload; never describe deletion or Free Agents behavior without live evidence.
11Should I save before reversing a transfer?+
Yes. The official Editing Player Wiki tells users to keep a backup in another save slot before edits. Preserve that recovery point until the player, clubs and reloaded Career all pass verification.
12Why not just transfer the player back manually?+
A counter-transfer creates another forward operation and may not restore every state changed by the original deal. Transfer History is the documented quick-undo route; if no exact row exists, label any manual repair as a separate workaround.
20 / EVIDENCE LEDGER
Sources, role and confidence boundary
Creator sources control product behavior and version facts. EA, community and video sources explain the realism problem or distinguish adjacent surfaces; they never fill gaps in the Live Editor contract.
The complete public contract: view all transfers done in the current season and quickly undo them if needed.
Transfer History added in v26.1.8; separate Teams List transfer analytics added in v26.3.5.
Current game-build and Live Editor compatibility snapshot at the research freeze.
Recovery-slot guidance plus Save, re-enter-screen and Career-save verification pattern.
Direct Player Editor transfer and loan are different operations from history review.
Direct-transfer form boundary; it is not presented as the Transfer History undo surface.
Direct-transfer route and form context; no Transfer History undo contract.
No public issue matched exact “transfer history” or transfer + undo searches at the freeze.
Official context for current AI squad evaluation and transfer-logic changes.
Current audience report that CPU moves can continue despite a setup toggle.
Different Player Career transfer-request flow; useful for mode separation only.
Current examples of implausible destinations and fees that break Career immersion.
Users describe abandoning saves after implausible transfers and simulation outcomes.
Direct demand for undoing transfers that make no sense.
Long-running save-slot/reload workaround and realism pain.
Base-game negotiation context, explicitly not Live Editor undo evidence.
Adjacent prevention/logic product; not evidence for Transfer History behavior.
Current squad-balance and realism motive; locally normalized captions.
My Pro/Agent/Path flow, retained to prevent route conflation.
Office/Budget Overview/Transactions surface, separate from Live Editor history.