Treasury with IT, Legal, Audit and Tax

5 minutes 5 Questions

Within the CTP body of knowledge, treasury does not operate in isolation; its effectiveness depends on strong internal relationships with IT, Legal, Audit, and Tax. Each function supports treasury's core objectives of liquidity management, risk mitigation, and control. Treasury and IT: Treasury relies heavily on technology, including treasury management systems (TMS), ERP integration, bank connectivity (SWIFT, host-to-host, APIs), and payment platforms. IT provides infrastructure, system security, data integrity, and business continuity planning. Treasury must collaborate with IT on cybersecurity controls, user access management, straight-through processing, and system selection or upgrades to ensure secure, efficient cash and payment operations. Treasury and Legal: Legal counsel supports treasury in negotiating and reviewing bank agreements, credit facilities, loan covenants, ISDA master agreements for derivatives, and bank account documentation. Legal also advises on regulatory compliance (e.g., Dodd-Frank, anti-money laundering, sanctions/OFAC), corporate governance, signatory authority, and board resolutions. A close partnership ensures contracts protect the organization and that treasury activities remain within legal and regulatory boundaries. Treasury and Audit: Internal audit independently evaluates treasury's controls, including segregation of duties, payment authorization, bank reconciliations, investment policy compliance, and fraud prevention. External auditors review treasury-related balances and disclosures (cash, debt, derivatives, hedge accounting). Treasury must maintain documented policies, audit trails, and transparent processes to support Sarbanes-Oxley compliance and reduce control deficiencies. Treasury and Tax: Tax and treasury coordinate on cash repatriation, intercompany lending, transfer pricing, withholding taxes, and the tax implications of financing structures and hedging strategies. Decisions about where to hold cash, how to fund subsidiaries, and how to structure debt or in-house banks have significant tax consequences. Alignment helps optimize global liquidity while minimizing tax leakage. Overall, these relationships enable treasury to operate securely, legally, with strong controls, and in a tax-efficient manner, which is essential for protecting enterprise value.

Treasury with IT, Legal, Audit and Tax: A Complete CTP Study Guide to Treasury's Key Internal Relationships

Overview
Within the AFP Certified Treasury Professional (CTP) body of knowledge, the topic Treasury with IT, Legal, Audit and Tax sits inside the broader area of Internal and External Relationships. It examines how the treasury function interacts with four support partners inside the organization: Information Technology (IT), Legal, Internal and External Audit, and Tax. Treasury cannot execute its mission of liquidity management, risk management, capital structure, and banking relationship management in isolation. It depends on IT for systems and security, on Legal for enforceable agreements and regulatory compliance, on Audit for independent assurance over controls, and on Tax for structuring decisions that preserve after-tax cash. This guide explains why the topic matters, what each relationship involves, how the relationships work in practice, and how to answer exam questions on it confidently.

Why This Topic Is Important
1. Treasury is a hub, not an island. Nearly every treasury activity touches another department. A cash forecast depends on tax payment timing; a cross-border cash pool depends on legal entity documentation and tax rulings; a treasury management system (TMS) depends on IT for implementation, interfaces, and security. The CTP exam tests whether you understand these dependencies.
2. Control and governance. Treasury moves large sums of money. Weak coordination with IT (access controls), Audit (independent testing), and Legal (signatory authority) creates fraud and compliance risk. Regulators and boards expect a well-controlled treasury.
3. Value creation. Poor coordination with Tax can trap cash offshore or trigger withholding and deemed-dividend taxes. Poor coordination with Legal can leave a company exposed in a derivative default or covenant breach. Strong relationships convert treasury from a cost center into a strategic partner.
4. Exam weighting. The Role of Treasury and its relationships appear in the early domain of the Essentials of Treasury Management text. Questions are frequently scenario-based and ask which function treasury should consult or which function is responsible for a specific task. These are achievable points if you learn the responsibility boundaries.

What It Is: The Four Relationships Defined

1. Treasury and Information Technology (IT)
IT provides the technology infrastructure and security framework on which treasury operates. Key touchpoints include:
• Treasury Management Systems (TMS) and Enterprise Resource Planning (ERP) systems: selection, implementation, upgrades, and integration. Treasury defines functional requirements (cash positioning, forecasting, debt and investment tracking, FX exposure, bank account management); IT evaluates technical fit, hosting (on-premise versus cloud/SaaS), vendor stability, and integration.
• Bank connectivity: host-to-host file transfers, SWIFT (including SWIFT for Corporates and service bureaus), APIs, and bank web portals. IT manages secure communication protocols, encryption, and file formats (ISO 20022 XML, BAI2, EDI).
• Straight-through processing (STP): automating the flow from forecast to payment to reconciliation to general ledger posting with minimal manual intervention.
• Information security and cybersecurity: user authentication, multi-factor authentication, tokens, role-based access, payment file encryption, protection against business email compromise (BEC), malware, and payment fraud.
• Segregation of duties enforced through systems: IT configures user profiles so that the person who initiates a payment cannot also approve or release it.
• Business continuity and disaster recovery (BC/DR): backup sites, redundant connectivity, documented procedures so treasury can make critical payments even if primary systems fail.
• Data governance: data integrity, audit trails, retention, and reporting.

2. Treasury and Legal
Legal ensures that treasury's agreements are enforceable, that the company is compliant with laws and regulations, and that authority to act is properly documented. Key touchpoints include:
• Bank account documentation: account opening resolutions, signature cards, authorized signatory lists, and corporate resolutions approved by the board.
• Credit agreements and loan documentation: term sheets, covenants (affirmative, negative, financial), representations and warranties, events of default, and security/collateral documents.
• Derivative documentation: the ISDA Master Agreement, Schedule, Credit Support Annex (CSA), and trade confirmations. Legal reviews netting provisions, termination events, and collateral terms.
• Capital markets documentation: indentures for bonds, commercial paper dealer agreements, underwriting agreements, registration statements, and disclosure obligations.
• Trade finance instruments: letters of credit, guarantees, and standby letters of credit, which are governed by rules such as UCP 600 and ISP98.
• Regulatory compliance: Know Your Customer (KYC) and anti-money laundering (AML) requirements, OFAC sanctions screening, Dodd-Frank derivative reporting and end-user exemptions, FBAR foreign account reporting, escheatment (unclaimed property), and the Uniform Commercial Code (UCC) Articles 3, 4, 4A, and 9 covering negotiable instruments, bank deposits, funds transfers, and secured transactions.
• Intercompany agreements: loan agreements, cash pooling agreements, and guarantees between legal entities.
• Mergers, acquisitions, and divestitures: due diligence on debt, bank accounts, hedges, and change-of-control provisions.
• Treasury policy: Legal helps draft and approve the investment policy, FX hedging policy, debt policy, and delegation of authority.

3. Treasury and Audit (Internal and External)
Audit provides independent assurance that treasury activities are properly controlled, recorded, and reported.
• Internal Audit reports to the audit committee of the board (for independence) and periodically reviews treasury operations: compliance with treasury policies, segregation of duties, bank account controls, payment authorization, bank reconciliations, investment compliance with the investment policy, derivative usage limits, and fraud prevention. Internal Audit does not perform treasury functions; it evaluates them. Treasury must remain operationally separate from Internal Audit to preserve independence.
• External Audit issues an opinion on the financial statements. Treasury supports the external auditors by providing bank confirmations (often through confirmation services), debt confirmations, investment statements, derivative valuations and hedge documentation, letters of credit and guarantee listings, and support for disclosures about liquidity, debt maturities, and risk.
• Sarbanes-Oxley (SOX) Section 404: management must assess internal control over financial reporting; treasury controls over cash, debt, investments, and hedging are typically key controls that are documented and tested.
• Hedge accounting under ASC 815 (US GAAP) or IFRS 9: auditors examine formal hedge designation documentation, effectiveness testing, and fair value measurement. Treasury must prepare contemporaneous documentation at hedge inception.
• Bank account rationalization and signatory audits: confirming that only current authorized employees have access and signing authority.

4. Treasury and Tax
Tax affects almost every treasury structuring decision because treasury manages after-tax cash flows.
• Cash forecasting: Tax provides timing and amounts of estimated tax payments, refunds, and payroll tax deposits, which are major cash flows.
• Intercompany funding: choosing debt versus equity to fund subsidiaries, setting arm's-length interest rates (transfer pricing), and respecting thin capitalization and interest deductibility limits.
• Cash repatriation: dividends, intercompany loans, royalties, and management fees each have different withholding tax and foreign tax credit consequences. In the US, Section 956 (deemed dividends from certain intercompany loans or guarantees), and post-TCJA provisions such as GILTI and BEAT, shape how treasury moves cash.
• Cash pooling and in-house banking: physical (zero-balance) pooling creates intercompany loans with tax implications; notional pooling may raise deemed-loan and withholding questions. Tax must approve pool structures and locations.
• Investments: tax-exempt versus taxable yields (taxable equivalent yield calculations), tax lot accounting, and treatment of gains and losses.
• Hedging: tax treatment of derivatives may differ from accounting treatment; tax may require hedge identification for tax purposes.
• Leasing and capital structure: tax deductibility of interest versus lease payments influences the lease-versus-buy and debt-versus-equity analysis, and the after-tax cost of debt (Kd × (1 − t)) used in WACC.
• Entity location decisions: treasury centers, in-house banks, and holding companies are often placed in tax-efficient jurisdictions with favorable treaty networks, subject to substance requirements.

How It Works in Practice
Scenario A: Implementing a new TMS. Treasury defines requirements and selects functionality; IT runs the technical evaluation, security review, data migration, and bank interface build; Legal reviews the vendor contract, service level agreements, data privacy clauses, and liability limits; Internal Audit reviews the control design (user roles, approval workflows, audit logs) before go-live; Tax may be consulted if the system will manage intercompany loans and interest calculations.

Scenario B: Establishing a multi-currency cash pool in Europe. Treasury designs the pool and selects the bank; Tax evaluates withholding taxes, transfer pricing on intercompany balances, and deemed-dividend risks; Legal drafts the pooling agreement, intercompany loan agreements, and board resolutions for each participating entity; IT builds the connectivity for daily sweeps and reporting; Audit reviews that intercompany balances are reconciled and interest is properly accrued.

Scenario C: Hedging a forecasted foreign currency sale. Treasury identifies the exposure and executes a forward; Legal has previously negotiated the ISDA with the counterparty; Treasury prepares hedge designation documentation at inception; External Audit tests effectiveness and fair value at period-end; Tax determines whether the hedge receives integrated tax treatment; IT ensures the trade is captured in the TMS with proper valuation feeds.

Scenario D: Detecting a payment fraud attempt. A business email compromise attempt requests an urgent wire. Controls designed with IT (multi-factor authentication, dual approval, call-back verification) and reviewed by Audit stop the payment. Legal is engaged on notification obligations and potential recovery; IT investigates the intrusion.

Key Principles to Remember
• Treasury owns the business requirements and policy; IT owns technical delivery and security architecture; Legal owns enforceability and compliance; Audit owns independent assurance; Tax owns after-tax optimization and compliance.
• Segregation of duties is a shared responsibility: Treasury designs the workflow, IT enforces it in systems, Audit tests it.
• Independence matters: Internal Audit should not report to the treasurer, and treasury staff should not perform their own audit.
• Documentation is the bridge: hedge designation memos, board resolutions, signatory lists, intercompany agreements, and transfer pricing studies are what Legal, Audit, and Tax rely on.
• Timing: involve partners early. Tax and Legal consulted after a structure is implemented often cannot undo adverse consequences.

Exam Tips: Answering Questions on Treasury with IT, Legal, Audit and Tax

Tip 1: Map the keyword to the function. Exam questions often describe a task and ask which department treasury should work with. Build a mental dictionary:
• Systems, interfaces, SWIFT, connectivity, encryption, access rights, disaster recovery, STP, cybersecurity → IT.
• Contracts, ISDA, covenants, resolutions, signatories, indentures, UCC, letters of credit, regulatory filings, KYC/AML, sanctions → Legal.
• Controls, segregation of duties, policy compliance review, bank confirmations, SOX 404, hedge documentation testing, independent assurance → Audit.
• Repatriation, withholding, transfer pricing, intercompany interest rates, thin capitalization, deemed dividends, taxable equivalent yield, after-tax cost of debt, estimated tax payments → Tax.

Tip 2: Watch for the independence trap. If an answer choice has Internal Audit executing payments, setting policy, or reporting to the treasurer, it is wrong. Internal Audit evaluates; it does not operate. Similarly, treasury should not approve its own controls assessment.

Tip 3: Distinguish internal audit from external audit. Internal Audit focuses on operational compliance and control effectiveness and reports to the audit committee. External Audit focuses on the fairness of financial statements and obtains independent confirmations from banks and counterparties. A question about bank confirmations or an audit opinion points to external auditors; a question about periodic review of treasury policy compliance points to internal audit.

Tip 4: Recognize cash pooling and intercompany questions as multi-function. When a question involves cross-border pooling, in-house banks, or intercompany loans, the best answer usually involves Tax (withholding and transfer pricing) and Legal (agreements and resolutions) together. If only one is offered, Tax is most often the tested answer for cross-border cash movement consequences.

Tip 5: Remember that treasury defines requirements, IT delivers technology. A common distractor suggests IT should select the TMS based on technical features alone. The correct view is that treasury leads the functional requirements and business case while IT handles technical evaluation, security, and integration. Vendor contracts still go to Legal.

Tip 6: Hedge accounting questions blend treasury, audit, and documentation. Know that formal designation documentation must exist at inception of the hedge, and that auditors test effectiveness and fair value. If a question asks why a hedge failed to qualify for hedge accounting, late or missing documentation is a frequent cause.

Tip 7: Use after-tax thinking for quantitative items. If a calculation involves cost of debt, taxable versus tax-exempt yields, or lease-versus-buy, apply the tax rate. After-tax cost of debt = pre-tax rate × (1 − tax rate). Taxable equivalent yield = tax-exempt yield ÷ (1 − tax rate). These formulas link treasury decisions to the Tax relationship.

Tip 8: Favor answers that involve partners early and emphasize documentation and controls. The CTP exam rewards best-practice governance. When in doubt between an answer that is fast and informal and one that is documented, approved, and reviewed, choose the latter.

Tip 9: Eliminate answers that put responsibility in the wrong place. For example, Treasury does not file tax returns (Tax does), does not issue audit opinions (External Audit does), does not write code or manage firewalls (IT does), and does not draft indentures (Legal and outside counsel do). Treasury coordinates, provides inputs, and consumes outputs.

Tip 10: Practice with scenario questions. Read the stem for the problem being solved (connectivity, enforceability, assurance, or after-tax outcome). Identify the problem type first, then select the function. Most questions become straightforward once you classify the underlying issue.

Sample Question Walkthrough
A company plans to centralize its European subsidiaries' cash in a single header account with daily physical sweeps. Before implementation, which two functions should the treasurer consult to avoid adverse consequences?
Reasoning: Physical sweeps create intercompany loans. Intercompany loans raise transfer pricing, withholding tax, and deemed-dividend issues (Tax) and require intercompany loan agreements and board approvals (Legal). IT and Audit are relevant later for connectivity and control testing but are not the primary pre-implementation risk. Correct answer: Tax and Legal.

Which function is responsible for verifying that treasury's payment approval workflow actually prevents the same employee from initiating and releasing a wire?
Reasoning: Designing the workflow is treasury; configuring it is IT; independently verifying that it operates effectively is Internal Audit.

Summary
Treasury's effectiveness depends on four internal partnerships. IT supplies secure, integrated systems and bank connectivity. Legal supplies enforceable documentation and regulatory compliance. Audit supplies independent assurance over controls and financial reporting. Tax supplies after-tax optimization and compliance for funding, pooling, repatriation, and investment decisions. For the CTP exam, master the responsibility boundaries, memorize the keyword-to-function map, respect audit independence, and remember that the best treasury practice is to involve these partners early, document thoroughly, and build controls that can be independently tested.
Test mode:

CTP - Treasury with IT, Legal, Audit and Tax Example Questions

Test your knowledge of Treasury with IT, Legal, Audit and Tax

Question 1

Within a company, which function gives the board independent, objective assurance that treasury's internal controls are properly designed and operating effectively?

Question 2

A U.S. parent company plans to fund its German subsidiary with an intercompany loan booked through the parent's in-house bank. The treasury analyst has drafted the loan terms and must review them with the corporate tax department before the funds are advanced. Which matter is the tax department's primary concern in this review?

Question 3

A company is moving its payment and cash positioning activity to a vendor-hosted treasury management system. The external auditor plans to rely on the vendor's controls over financial reporting for the full fiscal year. Working with IT and internal audit, which report should the treasury analyst request from the vendor?

More Treasury with IT, Legal, Audit and Tax questions
21 questions (total)