Finance and Treasury Centre: map network companies and funding sources

A Finance and Treasury Centre incentive case should show a real Singapore treasury function, not a list of group loans assembled for a tax rate. The current EDB description focuses on growing treasury-management capabilities and using Singapore as a base for strategic finance and treasury activities. Management needs a controlled map of the network companies, services, funding sources and income that make up the proposed operating model.

Define the Finance and Treasury Centre mandate

Describe the decisions made in Singapore, the people making them, systems used, risk limits, funding responsibilities and services provided to the group. Separate existing activity from proposed expansion. Use the current EDB FTC page and the EDB incentive directory for the programme context, then obtain current professional and authority guidance for the specific structure.

Record expected skilled employment, business spending and governance without treating them as generic targets. The case should explain why Singapore performs genuine regional functions and how those functions are supervised. A booking entry or local bank account alone does not establish the operating substance.

Build the network-company and funding-source matrix

List each group counterparty, jurisdiction, ownership link, service received, facility, currency, tenor and responsible relationship owner. Identify which companies are expected to be approved network companies and which remain outside the proposed scope. Keep legal agreements and transfer-pricing analysis linked to the matrix.

For each borrowing or funding source, record lender type, location, use of funds, interest terms, hedging and payment flows. Separate ordinary withholding-tax treatment from any incentive assumption. The final approved terms, legislation and actual use of funds control the outcome, not a planning label.

Reconcile activity, income and compliance

Map each income stream to the service, counterparty, people, system and supporting agreement. Maintain a normal-tax and incentive view so finance can identify amounts outside the approved boundary. Include foreign-exchange, interest, guarantee, advisory and other treasury components only where the legal and approved conditions are satisfied.

Set review triggers for new network companies, restructurings, refinancing, new instruments and functional changes. A treasury model can change quickly after an award. The control file should detect a boundary change before tax filing or payment rather than reconstructing it later.

Turn the decision into a controlled file

Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.

Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.

Review before commitment and again before closeout

Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.

Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.

Handle exceptions without rewriting history

Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.

If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.

Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.

Verify the final outcome independently

Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.

Use the FTC substance guide for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.

Practical review checklist

• Singapore mandate documented
• Network companies listed
• Funding sources traced
• Income mapped
• Change triggers assigned

The map is decision-ready when the proposed Singapore treasury function, network companies, funding sources, income and compliance owners can be traced without assuming that every group flow qualifies.