Treasury controls

Keep an intercompany transfer note with both entity approvals

An intercompany transfer guide that names the evidence, the approver, and the close condition Revisit the rule with one current example before the next cycle.

Keep an intercompany transfer note with both entity approvals workflow illustration

Keep an intercompany transfer note with both entity approvals

Name the decision and the queue owner

Before work begins on intercompany transfer, confirm which entity, period, and queue the case belongs to and who accepts the outcome. The record should show the source, the decision, and the surviving value in one place. A clean-looking status is not evidence that the underlying work is correct. Confirm that the request belongs in this queue before assigning an owner. The intercompany transfer reviewer records the ledger entries, the owner, and the next action in one place.

Name the trigger that brought the case into the queue. Use the same definition across the queue and the review so the counts agree. Record the requester and the promised response time. A short written rule is easier to test than an unwritten habit. An intercompany transfer exception keeps the ledger entries attached and routes the question to the treasury manager.

Note the observation window; a case without a period cannot be compared later. Record the queue and the entity so the case cannot drift into another team's work. Separate the request from the decision, because a complete request is not an approval. Do not let a deadline expand a role beyond its written limit. In this intercompany transfer case, the record points to the general ledger and names the treasury manager as the decision owner.

Map the source and the evidence trail

A reviewer should be able to rebuild intercompany transfer from the destination entity approval, the ledger entries, and the general ledger record without asking for a private screenshot. Record who supplied each document and when it arrived. The next reviewer should not have to ask which document is authoritative. Do not let a deadline expand a role beyond its written limit. A sample intercompany transfer review checks the transfer request, the source entity approval, and the surviving value in the general ledger.

Use the same case key in the queue and in the evidence extract. Record who supplied each document and when it arrived. Do not treat a screenshot as a substitute for the system record. Preserve a conflicting value instead of overwriting the first one. Apply the same intercompany transfer test to the destination entity approval and to the value that survives in the general ledger.

Do not let a deadline expand a role beyond its written limit. Preserve a conflicting value instead of overwriting the first one. The next reviewer should not have to ask which document is authoritative. The record should show the source, the decision, and the surviving value in one place. The intercompany transfer record should let a second reviewer rebuild the decision from the source entity approval and the destination entity approval.

Set the authority boundary

Write the intercompany transfer authority limit into the case template, including the amount, scope, and end date of any delegation. Keep the original request so a later correction does not erase the reason for the work. Name the owner for every open item, including items waiting on someone else. A role change should trigger a review of queue access. For intercompany transfer, compare the transfer request with the destination value rather than relying on a status label.

The record should show the source, the decision, and the surviving value in one place. A clean-looking status is not evidence that the underlying work is correct. Preparation, comparison, and follow-up may sit with the assistant. Do not let a deadline expand a role beyond its written limit. The intercompany transfer close note cites the general ledger, the approver, and the time of the final check.

Record rejected and deferred requests as well as approvals. A role change should trigger a review of queue access. Write the authority limit into the case template. Keep the original request so a later correction does not erase the reason for the work. The intercompany transfer case note should show what the general ledger held at the time and who reviewed it.

Run the daily handoff

The daily intercompany transfer pass starts with the oldest item, the unassigned handoff, and the case paused for more than two business days. The next reviewer should not have to ask which document is authoritative. Record one next action and one due time per open item. If the team cannot reproduce the result from the record, the control is not finished. For intercompany transfer, the working file keeps the transfer request and the source entity approval beside the decision note.

Keep the queue view readable on one screen. Open the day with a queue pass by age, owner, and missing evidence. Record one next action and one due time per open item. A case that moves between owners should keep both owner periods visible. Every intercompany transfer handoff names the treasury manager and the field in the general ledger that will confirm the change.

Check that the owner is actually available before assigning. The next reviewer should not have to ask which document is authoritative. If the team cannot reproduce the result from the record, the control is not finished. Leave the next shift a queue that needs no chat history. In the intercompany transfer queue, an item without a next action is treated as an exception.

Handle exceptions without rewriting history

A repeated intercompany transfer exception becomes a reason code in the queue, not a story retold in each thread. If the exception repeats, give it a reason code. Record the stop reason and the release decision together. A short written rule is easier to test than an unwritten habit. An intercompany transfer exception keeps the ledger entries attached and routes the question to the treasury manager.

When access blocks the work, name the system, role, and approver. Do not let a deadline expand a role beyond its written limit. An escalation that ends in silence remains open. If the team cannot reproduce the result from the record, the control is not finished. In this intercompany transfer case, the record points to the general ledger and names the treasury manager as the decision owner.

The next reviewer should not have to ask which document is authoritative. An escalation that ends in silence remains open. Route one bounded question to the owner instead of negotiating in the queue. Keep the failed attempt and the correction in the same history. The intercompany transfer reviewer records the ledger entries, the owner, and the next action in one place.

Close with a verified destination value

If intercompany transfer hands work to another team, keep it open until that team acknowledges receipt and the surviving record is confirmed. Note the next review date before closing. Verify that the surviving record is the one downstream teams will use. Keep the original request so a later correction does not erase the reason for the work. Apply the same intercompany transfer test to the destination entity approval and to the value that survives in the general ledger.

Do not mark complete until the check is repeatable by another reviewer. A closed status is not proof that the destination changed. Record the close reason with the same codes used in the exception queue. Keep the original request so a later correction does not erase the reason for the work. The intercompany transfer record should let a second reviewer rebuild the decision from the source entity approval and the destination entity approval.

Use the same definition across the queue and the review so the counts agree. Reopen the case when the destination value is disputed. Record the close reason with the same codes used in the exception queue. Tie the close note to the original request and the final evidence. A sample intercompany transfer review checks the transfer request, the source entity approval, and the surviving value in the general ledger.

Review the pattern, not only the case

The intercompany transfer review should separate the ordinary case, the reopened case, the missing-evidence case, and the cross-owner handoff. The next reviewer should not have to ask which document is authoritative. If the team cannot reproduce the result from the record, the control is not finished. The record should show the source, the decision, and the surviving value in one place. The intercompany transfer close note cites the general ledger, the approver, and the time of the final check.

Use the same definition across the queue and the review so the counts agree. Report age and dependency, not only the total count. Choose the sample from the export before the meeting. Keep the prior procedure available for comparison. The intercompany transfer case note should show what the general ledger held at the time and who reviewed it.

The next reviewer should not have to ask which document is authoritative. Use the same definition across the queue and the review so the counts agree. Use case-level review to explain an outlier before calling it a trend. Check whether the definition changed during the period. For intercompany transfer, compare the transfer request with the destination value rather than relying on a status label.

Keep the record ready for the next reviewer

Keep the intercompany transfer record short enough to read during the day and specific enough to survive a later audit. Record event time separately from entry time. Use the approved repository for sensitive content. Label the version of every file that can change. Every intercompany transfer handoff names the treasury manager and the field in the general ledger that will confirm the change.

A case that moves between owners should keep both owner periods visible. A clean-looking status is not evidence that the underlying work is correct. Write the note so a reviewer can reconstruct the decision without a meeting. A short written rule is easier to test than an unwritten habit. In the intercompany transfer queue, an item without a next action is treated as an exception.

The record should show the source, the decision, and the surviving value in one place. Link the evidence to the exact field it supports. Avoid a private second version in a personal document. Record event time separately from entry time. For intercompany transfer, the working file keeps the transfer request and the source entity approval beside the decision note.

This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.