MatrixBy Khaled Hawari

The Defect Log We Build in the First Two Weeks

A diagnostic that produces a narrative gets read once, and a diagnostic that produces a ranked log gets worked through.

Two weeks into a new engagement you owe the owner a document. The version most firms produce is a memo: an assessment of the state of the books, written in paragraphs, ending with recommendations. It gets read once, on the day it arrives, and then it sits in an email thread while the actual work happens according to whatever seemed urgent that week.

Produce a log instead. One row per defect, six columns, ranked, with a verdict from a closed set of three. It is a worse read and a much better instrument, and the difference shows up around week six when somebody asks what is left.

The claim underneath that, stated early because it changes what goes in the log: the most common defect found in a first diagnostic is not that a number is wrong. It is that nobody can evidence the number. Those are different findings with different fixes, and a memo tends to blur them because both come out as concern. A log cannot blur them, because the evidence column is empty or it is not.

The six columns

Column What goes in it What does not
Defect One sentence describing the condition that exists now, in the present tense, specific enough that somebody could verify it independently A recommendation. “Reconcile the clearing account monthly” is a fix. The defect is that the clearing account has not been reconciled since a stated period
Evidence Where it was seen. The account, the report, the export, the date of the file it was read from. Enough that the finding can be reproduced by somebody else, including next year “Observed during process walkthrough” on its own. If nobody can find it again, it will be argued about later and the argument will be won by whoever is more confident
Consequence if left Who finds out, and when. Stated as an event rather than as an adjective “High risk”, “significant exposure”. A severity word is a placeholder for the sentence somebody did not want to write
Effort to fix A band, and the constraint. Hours or days, and whether the work depends on something else finishing first A precise estimate. Anything expressed to the hour in week two is invented, and it will be quoted back at you in month three
Owner One named person, and often not finance. Many defects are fixed by operations, by the person who signs contracts, or by the owner A department. A defect owned by “the team” is a defect owned by nobody
Verdict One of exactly three: fix now, fix at year end, live with it A fourth value

The consequence column does most of the work in the whole document, and it is the one that takes the longest to write. “Who finds out, and when” forces the finding into the world where decisions get made. Compare two versions of the same defect. High risk of misstatement in deferred revenue. Against: the external accountant will raise an adjusting entry at year end, the monthly results everyone has been reading will move, and the covenant calculation filed on those results was computed on the wrong figure. The second one gets fixed.

Why the verdict set is closed at three, and why there is no fourth

The fourth value everybody wants is “investigate further”. It is reasonable, it is often honest, and it destroys the log.

A log with an investigate column becomes a log where the hard items live in the investigate column. Nothing forces them out, because moving an item out requires a decision and leaving it there requires nothing. Six weeks later the log has thirty rows, eleven of them under investigation, and the document has quietly become the memo it was supposed to replace.

If a defect genuinely cannot be assessed in two weeks, it gets a verdict of fix now where the fix is the investigation itself, scoped, with a name and a date. That is a real commitment and it appears in the same list as everything else, competing for the same attention.

The three verdicts mean specific things:

Fix now. Started within the current engagement period, ahead of new work. Everything on this list should be short enough that all of it is done before the next quarter starts. If the fix-now list has fifteen items, the ranking has not been done, or the file needs remediation as its own engagement before a recurring calendar can go in at all.

Fix at year end. Deferred deliberately, because year end is when the work is being done anyway, or because the fix requires a clean cutover that only a period end provides. This verdict has a date attached to it, and the item stays on the log until that date passes.

Live with it. Accepted, in writing, with the reason. The item stays on the log permanently with this verdict so that next year’s reader knows it was seen and decided rather than missed.

That last verdict is the one that gets objected to, and the objection is worth answering directly. A diagnostic that finds twenty-six defects and recommends fixing twenty-six of them has not been ranked. It has been listed. Most companies at this size can absorb three or four real changes in a quarter alongside running the business, and the value of the exercise is in deciding which three, honestly, in front of the owner. A long list of accepted defects is not laziness. It is the only mechanism that makes the short list credible.

How the ranking is done

Consequence first, effort second, and never the reverse.

Sorting by effort produces a log that starts with everything easy, which feels productive and leaves the expensive defect at the bottom for a year. Consequence sets the order. Effort breaks ties inside a consequence band and it decides sequencing within a week, not priority.

The consequence bands, in order:

  1. Cash can leave the company without authority. Anything in this band is fix now, regardless of effort or of how long it has been that way without incident.
  2. A reported figure is wrong and somebody has relied on it. A covenant certificate, a bonus calculation, a distribution, a figure given to a lender, a decision priced off a management account.
  3. The close cannot be completed or cannot be evidenced. Reliability, rather than a known error.
  4. The year end will cost more than it should. Real money, spent later, in somebody else’s engagement.
  5. Internal irritation only. Untidy reporting, awkward workflow, a chart of accounts nobody likes.

Band five is where most of the live-with-it verdicts sit, and band four is where most of the fix-at-year-end verdicts sit. That is not a coincidence, it is the bands doing their job.

Four rows, so the shape is unambiguous

The rows below are invented. They are the kinds of finding a first diagnostic produces and none of them is drawn from a real engagement.

Defect Evidence Consequence if left Effort Owner Verdict
One person can add a supplier to the vendor master and release a payment to it, with no second approval at either step User role export from the accounting and banking systems, taken in week one. Confirmed in the walkthrough with the person holding both permissions Cash can leave to a bank account nobody else has seen. Nothing detects it until a reconciliation is read carefully, and nobody is currently reading them carefully Low. A permission change and a written approval threshold. Half a day, plus the owner’s agreement on the threshold Owner, with finance drafting Fix now
Deferred revenue has no supporting schedule. The balance has been carried forward unchanged for several periods while the company has been billing annual plans up front Trial balance at the last three locks, showing an identical balance. No schedule in the close binder. Confirmed with the bookkeeper The external accountant raises an adjusting entry at year end. Every monthly result issued this year moves, and the reported figures used in the last two lender submissions were computed on the wrong revenue Medium. Rebuilding from contracts and invoices, then a monthly schedule going forward. Depends on the contract file being complete, which is not yet established Finance lead Fix now
The fixed asset register does not agree to the capital assets balance, and additions for two prior years were posted without invoices attached Continuity schedule against the trial balance, and a sample of eight additions of which three had no document in the file The year end file takes longer and costs more, and a depreciation error may be sitting in prior years. Nobody outside the company is currently relying on the asset balance High. Reconstruction from purchase records and bank detail Finance lead, with the operations manager for the equipment history Fix at year end
Duplicate and near-duplicate expense accounts across the chart, so similar costs land in different places depending on who coded them Chart of accounts export, with the duplicates listed. Twelve months of ledger detail showing the split Reporting is untidy and comparisons take longer to explain. No external consequence, and no reported figure is wrong Medium, and it cannot be done mid-year without breaking comparatives Finance lead Live with it, revisit at the next year end

Read the fourth row against the second. Both are medium effort. One is fixed this month and one is accepted for a year, and the only thing separating them is the consequence column. That is the entire argument for building the log this way.

What this document is not

It is not an audit, a review or a compilation, and nothing in it is an opinion on whether the financial statements are fairly stated. That work is an assurance engagement, it is performed by a licensed public accounting firm under professional standards, and this is not that. If a lender, an investor or a board wants assurance, they need a different firm and a different engagement, and we will say so rather than letting a management document be presented as something it is not. The full boundary, including what stays with your external accountant, is set out here.

What the log is, is a management assessment of whether the finance function can be relied on to produce a number and evidence it. That question is answerable in two weeks. Whether a given balance is correct usually is not.

Which leads to the honest limit of the exercise. In two weeks you can establish what is evidenced, what is not, who can do what in which system, and where the process breaks. You cannot establish that the numbers are right. Where a balance is unsupported, the log records that it is unsupported. It does not record that it is wrong, because that has not been determined, and a diagnostic that asserts more than it tested is a diagnostic somebody will eventually check.

Working the log after week two

The document is only worth building if it stays alive, and staying alive is mostly mechanical.

  • Nothing is deleted, ever. Items are closed, with the date and a sentence on what changed. A deleted row is indistinguishable from a row that was never found.
  • Closed items keep their evidence. The proof of the fix goes in the same row: the permission export after the change, the new schedule, the reconciliation that now exists.
  • It is reviewed on a fixed cadence with the owner, at the same meeting each month, with the fix-now list read first and the accepted list read once a quarter.
  • New defects are added as they are found, in the same format, and they compete with what is already there rather than jumping ahead of it because they are recent.
  • The verdict can change, and the change is recorded. A live-with-it item that becomes a fix-now item because the company took on debt is a normal event. An item that quietly moves without a reason is not.

A log worked this way is also the handover document. When the function moves to an in-house hire or to another provider, the log with a year of closures on it says more about the state of the file than any summary written for the occasion.

What we do not do

We do not fix anything in the first two weeks. Repairing an account before the diagnostic is complete destroys the evidence of what went wrong, and the evidence is most of the value.

We do not present the log as assurance, and we do not let it be forwarded to a lender as though it were.

We do not write a severity word where a sentence belongs.

And we do not hand over a log with twenty-six items marked fix now. If everything is first, the ranking has not been done, and the ranking is the part the owner is actually paying for.

MoreOther working documents

If this keeps failing in the same place.

A document that has to be re-explained every period is a process problem rather than a documentation problem. That is the point at which handing the function over is cheaper than fixing it again.