Writing Technical Accounting Memos

How a financial accountant writes technical accounting memos that stand up to audit: what memos are for, a sound structure and template, rigorous analysis, a worked revenue example, how auditors use them and the faults to avoid.

  • Founded by Adrian Lawrence FCA, ICAEW
  • Permanent, interim and fractional finance hires
  • Offices in London and the West Midlands
Finance team reviewing cash flow

The technical accounting memo is one of the financial accountant’s most important written outputs, and its quality says a great deal about the person who wrote it. When a business faces a significant or unusual accounting question — how to account for a new type of transaction, how to apply a standard to a particular situation, how to justify a judgement — the memo is the document that sets out the issue, analyses it against the relevant standards, and reaches and supports a conclusion. A well-written memo gives a clear, defensible basis for the treatment. A poor one leaves the business exposed when the treatment is questioned. Writing memos well combines technical knowledge with clear analytical writing, and it distinguishes a strong financial accountant.

This guide is for financial accountants who want to write technical memos well. It covers what a memo is for, a sound structure and template, rigorous analysis, a worked example, clear writing, the common weaknesses, when a memo is needed and how auditors use one.

What a Technical Memo Is For

A technical accounting memo exists to analyse a significant accounting question and provide a documented, reasoned basis for its treatment. It has three purposes. It establishes the correct treatment, by analysing the question against the standards so the answer is sound rather than arbitrary. It documents the basis for the treatment, leaving a clear record of why the accounting was done as it was — valuable for the audit, for future years and for showing that the judgement was made properly. And it defends the treatment when it is questioned, whether by the auditor, a regulator or a buyer’s due diligence team, because a treatment supported by a sound memo is far more defensible than one supported only by assertion.

So a memo must do more than state a conclusion. It must analyse the question and support the conclusion with reasoning grounded in the standards and the facts. A memo that simply asserts a treatment neither shows that it is correct nor supports it against challenge.

The Structure of a Sound Memo

A sound memo takes the reader from the question to a supported conclusion. It begins with the issue — the accounting question, stated clearly and specifically so the reader knows exactly what is being analysed. It then sets out the relevant facts: the specific circumstances of the transaction that bear on the accounting. The right treatment depends on the specifics, so a memo that does not establish the facts cannot analyse the question soundly.

The memo then identifies the relevant standards and requirements — the authoritative guidance that governs the question — and analyses the question against them, applying the requirements to the facts. The analysis is the heart of the memo. Finally it reaches a conclusion, stated explicitly so there is no doubt what treatment the analysis supports. Issue, facts, standards, analysis, conclusion: that sequence is what makes a memo clear and rigorous. Omit an element — leave the facts unestablished, skip the analysis, keep the conclusion vague — and the memo becomes weaker and less defensible.

A memo template you can adapt

In practice, most finance teams add two elements to the core sequence: what the accounts will say about the matter, and who reviewed and approved it. A template keeps memos consistent across the team and across years.

Section What it contains
Header Entity, period, title, author, date, version, materiality of the amounts involved
1. Issue The question in one or two sentences, e.g. “Should the set-up fee be recognised on invoicing or over the contract term?”
2. Background and facts The transaction, key contract terms with clause references, amounts and dates, and the source documents relied on
3. Relevant standards The framework (FRS 102, FRS 101 or UK-adopted IFRS), the specific sections or paragraphs, the version in force for the period, and any interpretive guidance
4. Analysis Each requirement applied to the facts in turn; alternative treatments considered and why they were rejected; the numbers
5. Conclusion The treatment, the journal entries or effect on the accounts, and any conditions that would change the answer
6. Disclosure Accounting policy wording, critical judgement or estimation uncertainty note, and other note disclosures required
7. Sign-off Prepared by, reviewed by (usually the Financial Controller), approved by (Finance Director or audit committee where significant), with dates

Analysing the Accounting Issue Rigorously

The analysis is where the memo’s value is created. Rigorous analysis means identifying the correct, applicable standards — not a half-remembered version, but the actual guidance in force for the period — and applying them carefully to the specific facts. It means working through each requirement, considering how it applies, and addressing the genuine difficulty or judgement the question involves rather than glossing over it. A rigorous analysis engages with the points that are not straightforward rather than asserting a comfortable answer.

It also means considering the alternatives where the treatment is not obvious. Where more than one treatment might be argued, or where the application of a standard to the facts is uncertain, a sound analysis sets out the alternatives, explains why the chosen treatment is preferred and why the others are rejected. That shows the conclusion was reached through genuine analysis rather than assumption, and it makes the memo far more defensible: a treatment chosen after weighing the alternatives stands up better than one asserted as if no other were possible. The framework choice itself is often part of the context, and our guide to IFRS vs UK GAAP in practice covers where the frameworks diverge.

Worked Example: A Set-Up Fee Under the Five-Step Revenue Model

Revenue is one of the most common memo topics, and it has become more so for UK GAAP preparers. The FRC’s periodic review amendments to FRS 102, effective for periods beginning on or after 1 January 2026, replace the old revenue section with a five-step model based on IFRS 15. Many companies are writing their first five-step memos now. The extract below shows the shape of a good one; our guide to revenue recognition under IFRS 15 covers the model in full.

Issue and facts

Issue: should a non-refundable set-up fee charged to a new software customer be recognised as revenue when the set-up work is completed, or over the contract term?

Facts: on 1 October the company signs a three-year contract to provide hosted software. It charges a one-off set-up fee of £30,000, invoiced on signing, and a subscription of £60,000 a year, invoiced annually in advance. The set-up work involves configuring the customer’s account, migrating its data and creating user profiles; it takes about three weeks. The customer cannot use the configured account without the subscription, and no other supplier could use it. The year-end is 31 December. The contract can be renewed without a further set-up fee.

Relevant standards

IFRS 15, particularly paragraphs 22–30 on identifying performance obligations and the application guidance on non-refundable upfront fees (paragraphs B48–B51) and customer options (B39–B43). For an FRS 102 preparer, the equivalent requirements in the amended revenue section apply, and the memo should cite those paragraphs and note any FRS 102 simplifications the company relies on.

Analysis

  • Step 1 – contract: a signed, enforceable contract with commercial substance and collectable consideration exists.
  • Step 2 – performance obligations: the key judgement. The set-up activities are tasks the company must perform to deliver the service; they do not transfer a good or service to the customer that it can benefit from on its own or with readily available resources. They are therefore not a distinct performance obligation. The only performance obligation is the hosted service, provided evenly over the term.
  • Step 3 – transaction price: £30,000 plus £180,000 = £210,000, with no variable consideration or significant financing component (the advance timing reflects normal commercial terms).
  • Step 4 – allocation: with one performance obligation, the whole price is allocated to the service.
  • Step 5 – recognition: the customer receives and consumes the benefit as the service is provided, so revenue is recognised over time on a straight-line basis: £210,000 ÷ 36 months = £5,833 a month.

Alternatives considered: recognising the £30,000 on completion of set-up was rejected because the set-up is not distinct. The memo also considers whether the right to renew without a further fee is a material right that would extend the recognition period; it concludes that it is not, because the renewal subscription is priced at the stand-alone selling price and the set-up fee is small relative to the total contract value. That conclusion should be revisited if renewal pricing changes.

Conclusion, disclosure and sign-off

For the three months to 31 December, revenue is £17,500. Of the £90,000 invoiced, £72,500 is a contract liability (deferred income), split between amounts due within and after one year. Recognising the set-up fee upfront would have overstated revenue by £27,500. The accounting policy note describes recognition of subscription revenue over time and the treatment of set-up fees; if the amounts are material, the identification of performance obligations is disclosed as a critical judgement. The memo is prepared by the financial accountant, reviewed by the Financial Controller and approved by the Finance Director, with dates.

The same template works for other common topics: whether an arrangement contains a lease (see lease accounting under IFRS 16, and note that the amended FRS 102 now brings most leases onto the lessee’s balance sheet too), recognition of a deferred tax asset, capitalisation of development costs, or the debt-or-equity classification of a new instrument.

Hiring a Financial Accountant Who Can Document Technical Judgements? — 0204 553 8893

Accountancy Capital places qualified financial accountants at £50,000 and above across the UK — permanent, interim and fractional. We respond the same working day; interim and fractional shortlists usually follow within days.

Tell us about your hire →Register as a candidate →

Writing the Analysis Clearly

A rigorous analysis must also be written clearly. A memo that is technically sound but badly written fails to communicate its reasoning and is harder to rely on. Clear writing means setting out the analysis in a logical sequence, explaining the reasoning step by step rather than leaping to conclusions, and expressing technical content in plain language rather than dense prose. The reader — the auditor, a colleague, or the author a year later — should be able to follow how the conclusion was reached.

Clear technical writing is also precise: say exactly what is meant, reference the specific paragraphs accurately, and state the facts and conclusion without ambiguity, because small distinctions can change the treatment. It is concise, covering the analysis thoroughly without padding. And it is well organised, with numbered sections and headings so the reader can find their way. Quote the key words of a standard where the analysis turns on them, but do not paste in pages of text. Write the memo as the issue arises, not after the year-end: the facts are fresher, and a contemporaneous memo carries more weight than one written to justify a treatment already booked.

The Common Weaknesses to Avoid

Technical memos have recognisable weaknesses. The most common is the memo that asserts a conclusion without the analysis to support it — stating the treatment without demonstrating why it is correct. The remedy is rigorous analysis that grounds the conclusion in the standards and the facts. The second is the memo that fails to establish the facts, so the analysis floats free of the circumstances it should rest on. The remedy is setting out the relevant facts, with document references, before analysing.

The third weakness is the analysis that glosses over the genuine difficulty, asserting a comfortable answer without engaging with what makes the question hard. The remedy is honest engagement with the complexity and the alternatives. The fourth is poor writing that obscures the reasoning even where the analysis is sound; the remedy is clear, logical, precise writing. The fifth is reliance on out-of-date or wrongly identified standards, which undermines the analysis at its foundation. Standards are amended periodically, and the 2026 changes to FRS 102 make this a live risk: a memo that still applies the old risks-and-rewards revenue approach to a period beginning on or after 1 January 2026 is wrong from the first page.

Common faults: a quick review checklist

  • The issue is vague (“revenue recognition”) rather than a specific question.
  • Facts are taken from a sales summary, not checked against the signed contract.
  • The standard cited is the wrong version, or the wrong framework for the entity.
  • No numbers: the memo never quantifies the effect or compares it with materiality.
  • Alternatives are not mentioned, so the conclusion looks pre-determined.
  • The conclusion is hedged (“it may be appropriate to…”) rather than stated.
  • No disclosure section, so the note wording does not match the analysis.
  • Unsigned, undated or never reviewed — and so not obviously the company’s own position.

When a Technical Memo Is Needed

Not every accounting question warrants a formal memo, while some clearly do. A memo is warranted where the question is significant — material to the accounts — and involves genuine judgement, complexity or unusual circumstances, so the treatment must be analysed and documented rather than simply applied. A new type of transaction, a significant judgement that affects the accounts materially, an area where the correct treatment is not straightforward, a matter the auditor is likely to scrutinise, a change of accounting policy or a first-time adoption — these are the situations that call for one.

Recognising them is itself a sign of good technical judgement. Documenting the significant judgements and complex treatments, without over-documenting the routine, applies the discipline where it adds value. A financial accountant who fails to document a significant judgement may find, when it is questioned, that no clear basis was ever recorded — a weak position. Memos sit naturally alongside the year-end work described in our guide to preparing statutory accounts, and a short register of open memos is a useful item on the year-end plan.

How Auditors Use Technical Memos

Auditors are among the most demanding readers of a memo. Under the International Standards on Auditing (UK), issued by the Financial Reporting Council, the audit team must identify and respond to significant risks and evaluate management’s judgements and estimates. Complex revenue, leases, provisions and impairment are frequently in that category. A good memo gives the auditor management’s position in one place: what the issue is, which facts were relied on and why the treatment is right.

What the auditor does with it:

  • Tests the facts. The audit team will check the memo’s description against contracts, board minutes and correspondence. Facts that turn out to be wrong undermine the whole analysis.
  • Challenges the analysis. Expect questions on the alternatives you rejected, and on the judgements the analysis turns on. Technical reviewers or the firm’s technical department may also read significant memos.
  • Checks consistency. The conclusion should match the ledger, the accounting policy note and the critical judgements disclosure, and the same approach should apply to similar contracts.
  • Files it. The memo, or the auditor’s own summary of it, often becomes part of the audit file and the starting point for next year.

Share significant memos before fieldwork starts, ideally at the planning stage, so disagreements surface while there is time to resolve them. And remember that the memo must be the company’s own work: ethical standards prevent the auditor from taking management decisions, so the audit firm can discuss a treatment but cannot write the memo that justifies it. Our guides to the financial accountant’s role in the audit and managing the year-end audit relationship cover the wider process. The ICAEW’s financial reporting resources and the IFRS Foundation’s IFRS 15 page are useful starting points for the authoritative text.

The Memo as a Demonstration of Competence

Beyond supporting an accounting treatment, a technical memo demonstrates the competence of the person who wrote it. A memo that frames the issue clearly, establishes the facts, identifies the right standards, analyses rigorously and reaches a supported conclusion, all in clear writing, shows technical knowledge, analytical capability and communication skill at once.

So a memo is worth writing well not only for its immediate purpose but as a reflection of professional standards. A financial accountant who consistently produces sound, clear memos builds a reputation for technical rigour; weak memos signal the opposite. Strong memo-writing is also something to evidence when you move roles: describe the judgements you documented in your financial accountant CV, and be ready to talk through one at interview. For employers, it is one of the hardest skills to fake, which is why it features in many financial accountant recruitment briefs, particularly for businesses with complex transactions or a framework change ahead.

Frequently Asked Questions

How long should a technical accounting memo be?

As long as the issue needs and no longer. Two to three pages covers most single judgements; a complex transaction with several alternatives may need more, with appendices for contract extracts and calculations.

Who should sign off a memo?

Typically the preparer, a reviewer such as the Financial Controller, and the Finance Director for significant matters. In larger companies, significant judgements are often taken to the audit committee.

Can our auditors write the memo for us?

No. The memo records management’s judgement, and ethical standards restrict auditors from taking management decisions. They can discuss the issue and tell you whether they agree, but the analysis must be yours.

Do memos need updating every year?

Review them each year-end. If the facts and the standard are unchanged, a short note confirming the conclusion still holds is enough. A change in contracts, the business or the framework — such as the FRS 102 amendments from 1 January 2026 — means a fresh analysis.

Can AI tools help draft technical memos?

They can help with structure and first drafts, but every reference to a standard must be checked against the authoritative text, and the judgement must be the author’s. Auditors increasingly ask how such tools are used; see what auditors ask about AI.

Adrian Lawrence FCA — Founder, Accountancy Capital

Fellow of the ICAEW | Chartered Accountant holding an ICAEW practising certificate | Part of FD Capital Group

Adrian is a former listed-company Finance Director with a BSc from Queen Mary College, University of London. Accountancy Capital, one of the five specialist firms of FD Capital Group, places financial accountants and Financial Controllers who can take a difficult accounting question, analyse it against the standards and document a conclusion that stands up to audit.

View Adrian’s ICAEW profile

Related Pages and Resources

Technical Standards

The standards technical memos most often analyse.

→ Revenue recognition under IFRS 15

→ Lease accounting under IFRS 16

→ IFRS vs UK GAAP in practice

Audit and Year-End

Where memos support the judgements auditors scrutinise.

→ The financial accountant’s role in the audit

→ Audit preparation

→ Year-end statutory accounts timetable

Financial Accountant Careers

The role, pay and progression for technical accountants.

→ Financial accountant job description

→ Financial accountant salary guide

→ Financial accountant career path

Need technical accounting capability on your team? — 0204 553 8893

Whether it is a permanent financial accountant, interim cover for a framework transition or a fractional technical resource, our recruitment team can help. Call us or email recruitment@accountancycapital.co.uk; permanent shortlists typically follow within one to two weeks.

Tell us about your hire →Register as a candidate →

Start a search

Tell us about your finance hire

Share a few details about the role and your timetable. A consultant will review your brief and come back to you the same working day.

  • Same-day response from a consultant who works on finance searches every day
  • Confidential from the first conversation, with no obligation to proceed
  • Permanent, interim and fractional finance roles across the UK
Please enable JavaScript in your browser to complete this form.

Your details are used only to respond to your enquiry.