Section 19B IP acquisition: build the valuation file

A Section 19B IP acquisition claim depends on the right acquired, legal and economic ownership, qualifying capital cost and an appropriate valuation where required. The purchase agreement, valuation and tax election should describe the same intellectual property. A transaction price alone does not establish the amount eligible for writing-down allowances.

Identify the acquired right

List each patent, copyright, trademark, registered design, geographical indication, integrated-circuit layout design, trade secret, commercial information right or plant variety included in the transaction. Record registration numbers, territories, remaining life, restrictions and uses in the Singapore trade. Separate rights from services, customer data and ordinary process documentation.

The IRAS Section 19B page explains the qualifying categories and exclusions. It says the transferee generally must acquire both legal and economic ownership unless EDB has approved a waiver of legal ownership. The agreements, accounting and operational control should support that conclusion.

Reconcile qualifying capital expenditure

Build a purchase-price schedule for each right and exclude legal fees, registration fees, stamp duty and other acquisition-related costs from Section 19B capital expenditure as IRAS states. Keep those excluded costs visible for their separate tax and accounting review rather than deleting them from the transaction record.

For a bundle containing businesses, services, software, data and intellectual property, preserve the allocation method and evidence. A residual number from negotiations may not be an open-market value. Related-party and cross-border transactions also require transfer-pricing and withholding-tax review on their own facts.

Decide whether a valuation is required

IRAS may require an independent valuation report when capital expenditure exceeds prescribed thresholds and can request another valuation or restrict allowances where the purchase price exceeds open-market price. Check the current threshold and filing requirements for the acquisition date instead of relying on an old transaction checklist.

The IRAS valuation-report guide describes the appropriate valuer’s independence and experience and the expected business, right, method, assumption and value information. Engage the valuer early enough to inspect the real rights and forecasts, but keep management responsible for the underlying records.

Control forecasts and assumptions

Reconcile valuation revenue, margins, useful life, obsolescence, development cost and discount rate to the board-approved plan. Separate existing intellectual property at acquisition from future technology expected to be developed later. Run sensitivities and record which party approved the commercial assumptions.

Avoid counting synergies or economic benefits that do not accrue to the Singapore acquiring company. Compare the valuation date, completion date and point at which ownership passes. If the deal terms change, assess whether the report and allocation need revision before filing.

Make and preserve the WDA election

For acquisitions from YA 2017, the IRAS page permits an irrevocable straight-line election over five, 10 or 15 years, made with the declaration at the first corporate-tax filing for the claim. Compare the periods with expected taxable income and ownership plans. Do not choose a shorter period merely for the largest headline deduction.

Link the file to the EIS conversion guide and the IP Development Incentive guide. Use the tax cornerstone for the annual related-party and documentation controls.

Use a controlled implementation file

Keep one dated file that links the decision, approved scope, source evidence, responsible owner, milestones, costs and final acceptance. A status label should distinguish proposed, approved, completed, claimed and paid items. This prevents an application acknowledgement or a vendor invoice from being mistaken for a completed outcome.

Review the file when ownership, scope, eligibility or timing changes. Preserve the earlier version and the reason for the change. Where a formal adviser, auditor or authority is required, record that dependency rather than replacing it with an internal assumption. Management remains responsible for accurate declarations and the commercial decision.

Stage the decision before commitment

Use four review points: fit, application or authority engagement, implementation and closeout. At the fit review, confirm the applicant, activity and business need. At the application review, freeze the requested scope and preserve the submission. During implementation, compare actual work with the approved terms. At closeout, reconcile deliverables, cost, payment, evidence and continuing obligations.

Name the person who may approve each review point and the evidence that person must see. Procurement should not treat a draft application as approval to contract. The project team should not treat a vendor completion notice as company acceptance. Finance should not treat claim submission as payment. These distinctions protect both operating quality and the integrity of any support request.

Plan for changes and exceptions

Maintain an exception log for delayed milestones, substituted staff, changed suppliers, cost movements, technical limitations and missing evidence. State the effect on scope, business benefit, eligibility and timing. Where authority approval is needed, submit the change through the official route before relying on it. Silence or a portal upload should not be read as consent.

For a material defect, pause the affected acceptance or claim item, preserve the original evidence and assign corrective action. Do not rewrite a baseline after seeing the result, backdate a document or move a cost between categories to improve the appearance of compliance. A transparent exception with a resolution is stronger than a clean file that cannot explain the actual project.

Close the project with independent readback

Have a person who did not prepare the final pack compare the approved terms, latest deliverables, invoices, full-payment evidence and operating result. Recalculate totals and test several source records. Confirm that public, employee or customer claims remain accurate. Record unresolved items separately, with owners and dates, instead of hiding them in a completion statement.

After submission, retain the acknowledgement and reconcile any questions, adjustments and final receipt to the project ledger. Continue conditions that survive closeout, including record retention, asset use, reporting or outcome commitments. The project is finished only when management can explain what was approved, what was delivered, what was paid and what must still be maintained.

Practical review checklist

• Rights and exclusions inventoried
• Ownership evidenced
• Qualifying cost reconciled
• Valuation requirement checked
• WDA election approved

A Section 19B file is defensible when the acquired right, ownership, qualifying cost, valuation and election reconcile. Build it during the transaction, approve the assumptions and preserve the evidence for every Year of Assessment in which allowances are claimed.