Make the monthly accountant meeting produce decisions

A useful accountant meeting starts with questions the participants can resolve. Identify the decision, the facts already available, the uncertainty, and the person authorized to act. Routine status can be read in advance; reserve conversation for interpretation, tradeoffs, and unresolved responsibilities.

An agenda item such as discuss reporting is difficult to prepare for. A better item might ask whether the company needs customer-segment reporting, which decisions it would support, and who will maintain the underlying classification. That gives the accountant a defined question and management a decision to make.

Atlassian's decision-documentation template distinguishes the person driving a decision, its approver, and contributors. You can use that role distinction without adopting a particular software product or a formal acronym. The important point is that attending a meeting does not automatically confer approval authority.

For each decision, provide the current position, relevant evidence, options where known, and the date an answer is needed. Identify which facts are confirmed and which remain assumptions. Keep the packet focused so participants can prepare without searching through a large folder.

Ask the accountant to flag questions that need separate research or a specialist before the meeting. A casual answer to an unfamiliar issue should not become an authoritative conclusion merely because everyone was present when it was said.

Check that the necessary company owner will attend or has delegated a clear decision. If only coordinators are present, the meeting may still clarify facts, but it should end with an explicit route to approval. Do not record agreement where participants only agreed to ask someone else.

Record the question and outcome in plain language. Include the reason for the choice, material assumptions, action owner, approval, and completion evidence. A list of discussion topics is a useful memory aid but is not a decision record.

The following illustrative record shows how a reporting conversation can become an owned implementation task. It is an operational example, not a recommendation that every company add customer-segment reporting.

The accountant may explain an accounting consequence while management chooses a business action. Record both accurately. A note that the accountant approved can obscure whether the professional advised on treatment, accepted an assignment, or actually had authority to make the business decision.

If the discussion creates new work, confirm its scope, price where relevant, input requirements, and delivery date through the appropriate process. A meeting action should not silently expand a recurring engagement into an open-ended project.

The Journal of Accountancy's documentation guidance discusses recording recommendations, client follow-up, judgments, and relevant dates. Apply that discipline to the final meeting record. The record should reflect what was actually concluded and preserve important limitations.

Send the draft decisions and actions to the relevant participants promptly enough that they can correct misunderstandings. Ask for specific corrections, especially to authority, assumptions, dates, and the meaning of an action. Silence should not be treated as authorization where explicit approval is required.

If a recording or automated transcript is used, follow the applicable consent and information-handling arrangements and review the output. A transcript can omit a negation or confuse speakers. It is supporting material, not a substitute for a concise reviewed statement of the decision.

When participants disagree about the outcome, keep the item open and identify the unresolved point. It is better to record that no final decision was made than to preserve an apparently tidy agreement that the company cannot implement.

Review overdue or consequential actions by their completion evidence. An email was sent may be a step, while the intended result remains unfinished. Ask whether the approved report, corrected schedule, signed instruction, or other expected output exists.

Remove completed actions from the active agenda while retaining the decision history. Revisit a previous choice when facts or assumptions change, and explain why it is being reopened. Repeatedly debating the same issue without new information often indicates that the original authority or outcome was unclear.

Cancel or shorten a meeting when no useful decisions require discussion. The value comes from a well-supported conclusion and completed follow-up, not the duration of a recurring appointment. A compact record should let an authorized colleague understand the decision even if they were unable to attend.