Transfer hold
Describes how a transfer hold prevents recognized revenue schedules from posting to the general ledger while preserving reporting visibility and rolling blocked entries into the next open period.
The Transfer hold is to prevent recognized revenue schedules from being posted to the downstream General Ledger.
Aspect | Details |
|---|---|
System behaviors |
Allows schedules to be generated in the subledger but freezes the transfer accounting step. Transfer holds can target Revenue, Allocation, or both. |
Impact on unposted entries |
While the hold is active, the current period's accounting entries are blocked from posting. During the period-close process, any unposted entries that were blocked by a transfer hold are pushed (rolled forward) into the next open period after running Sweep Unposted Schedules Program. |
Reporting visibility impact |
The waterfall schedule is populated, allowing Finance and FP&A teams to retain full visibility into revenue for close planning. |
| Application example | Suppose a transaction has revenue scheduled for $100 per month over the next 12 months. If a transfer hold is applied in the current period, the $100 entry will not be posted to the GL via the transfer accounting process. At the time of period close, this unposted entry is pushed to the following period. If the transfer hold is then cleared in that next period, a total of $200 (the delayed $100 from the prior period + the $100 for the current period) will be posted to the GL. |