Transfers and custodians

A transfer retains the previous and proposed custodian, cost center, location and effective date. Staff can explain where an asset was assigned when a count or period-end charge was recorded. Future assignments remain proposals until their effective date; historical movement records stay available after the current register changes.

A transfer approved today for next month remains a future assignment until that date arrives. Updating the current register immediately would make a physical count or historical report show the wrong responsible person. The effective action applies once at the agreed date, and the movement history retains who requested and approved it.

Asset Custodian or Fixed Asset Accountant prepares the request. Manager reviews within-department movements according to the configured scope; cross-cost-center decisions go to Controller / CFO. The decision maker must not be the preparer, and the target custodian must belong to the correct entity.

Within-department movements can follow the configured manager authority. A cross-cost-center change requires the financial review described by the process. In either case the approver must be different from the material preparer, and the proposed employee must be active and within the authorized entity before the assignment is applied.

A stale request cannot overwrite a newer approved assignment. Reject cross-entity references unless a separately reviewed inter-entity transfer process handles them. Changing current location must not rewrite earlier depreciation allocations or physical-count snapshots; preserve the movement and its effective timing.

Two open requests may propose different destinations for the same asset. The later action must recheck the current assignment and revision instead of overwriting a move already approved. A returned or rejected request retains its reason so the requester can correct the intended destination without creating an unexplained movement.

The transfer inbox shows proposed locations, custodians and effective dates before the reviewer acts. An employee departure may create a return or transfer request; it does not justify deleting the employee or asset history. A count taken before the handoff should continue to show the assignment expected at that time.

Configure manager scope, cost-center authority and employee identities using actual organizational assignments. Review a future-dated transfer and a conflicting second request during setup. The expected result is one clear current custodian plus a dated movement trail, with prior depreciation allocations and count snapshots preserved for the periods they describe.

The recorded handoff date should reflect when the receiving employee takes responsibility.

• Pending Transfer Approvals — Review the work and supporting records for this module.