A spoken method for briefing, building, and reconciling financial summaries.

Dictating a Prompt for Financial summaries starts with four facts that remove most ambiguity: the period, the currency, the basis, and the reader. Say the exact date range, whether figures are in whole units or thousands, and which basis the statement follows. Then name the reader and the decision they face: a budget owner comparing spend, a board reviewing the quarter, or a client checking an invoice total. Without these four facts, the summary may be accurate and still answer the wrong question. Speak them in the same order every time and keep them at the top of the prompt.
Name the source files and the scope before you ask for prose. Say which export, which sheet, and which date the figures come from, using the exact file names. State what is included and excluded, such as one business unit, two cost centers, or a single project. If a figure is provisional, say so and ask for it to be marked. When a source is missing, require the summary to list the gap rather than estimate. This scoping step is what separates a summary that can be audited from one that merely looks complete. Keep this scope line in the brief so the same boundary applies every month.
State the comparison the reader cares about. A monthly summary usually compares actual to budget, current period to prior period, or both. Say which comparison matters, and ask for the variance in absolute terms and as a percentage. Name the threshold that makes a variance worth explaining; below it, a note may be enough. Without a threshold, every line gets a paragraph and the significant items disappear in the volume. Ask for the threshold to appear in the prompt and in the summary header, so the reader knows why some lines are discussed and others are not. Ask for the threshold to be applied consistently to every line.
Define the level of detail and the rounding rule. Say whether the reader wants line items, categories, or a single total per area. Round consistently, and say where the unrounded figures live so a reader can check. Ask for one decimal convention and apply it to every table. When a total is rounded separately from its components, the parts may not add up visibly, so ask for a note explaining the difference. These small instructions prevent the most common review comment on a financial summary, which is that the numbers do not tie. State the rounding rule once and repeat it in the assumptions block.
Fix the structure before the numbers arrive. A workable order is: headline result, three drivers, variance table, risks, and questions for the reader. Say how many drivers you want, because three forces prioritization and ten invites a list. Ask for the headline to name the result and the main cause in one sentence. Put the variance table after the drivers so the reader sees the story before the detail. Keep the structure in the prompt, not in your head, so every monthly summary is comparable and a reader can find the same section in the same place. Number the sections so a reader can refer to them in a review comment.
Ask for the drivers to be stated as causes, not as line items. A driver says why the number moved: higher volume in one region, a timing shift in a payment, or a rate change. A line item says only that a category changed. Require each driver to name the evidence and the amount it explains. If a driver cannot be quantified, ask for it to be labeled qualitative. This rule keeps the summary from becoming a restatement of the table with adjectives. Three quantified drivers are more useful to a reader than twelve categories described as strong or soft.
Separate facts from interpretation in the structure. Ask for a facts section with figures and sources, then an interpretation section with causes and implications, then a decision section with what the reader must do. This separation lets a reviewer check the facts without arguing about the interpretation. It also makes it easy to update the summary when a number changes: only the facts section and the affected interpretation need revision. State the separation in the prompt and check that each section stays in its lane. Mixed sections are where unsupported opinions hide among correct figures. Ask for every interpretation sentence to point to a fact above it.
Set the length by the reader, not by the amount of material. A one-page summary for a budget owner, two pages for a board pack, and an appendix for anyone who wants the detail. Ask for the appendix to be optional and clearly separated. When the summary must fit one page, say what must be included: headline, drivers, variance table, and open questions. Everything else moves to the appendix. A summary that respects a page limit forces the writer to decide what matters, which is the actual work the reader is paying for. Review the page limit before the close, not after the draft is written.
Require every figure to trace to a source. Ask for a source column in the variance table naming the file and the line or cell. When a figure is calculated, ask for the calculation to be written out. When a figure is estimated, require the label estimated and the method in one line. This rule turns review into a checking exercise rather than a trust exercise. It also stops a plausible number from entering the summary through a guess. Say explicitly that a figure without a source should be flagged rather than printed as fact. Add the source column to the review checklist so it is never skipped under time pressure.
Check the arithmetic on the totals before you read the prose. Ask for a totals row and a note on how subtotals were combined. Add every column yourself once, or ask for a separate check pass with the same inputs. Look for double counting when categories overlap, and for missing items when a filter excluded a cost center. Record the check in the review notes with the date. Arithmetic errors damage trust more than any wording issue, because a reader who finds one assumes the rest are wrong and stops reading the analysis. Keep the arithmetic check separate from the narrative review so both happen.
Handle changes in the source carefully. When a re-export replaces a file, say which version the summary uses and why. Ask for the superseded figure to be shown beside the new one when the change is material. Keep the previous summary until the new one is approved, so a reader can compare. If a source is revised after the summary is sent, issue a short correction with the affected lines rather than a full resend. A clear version trail is what makes a monthly summary usable across a quarter, when readers compare one month with another. Note the version in the summary header so the reader knows which figures are in use.
Ask for a short assumptions block at the end. List the period, the currency, the basis, the rounding, the entities included, and any provisional figure. Keep it to six lines. A reader who picks up the summary later can then interpret every number without asking. When an assumption changes from the prior period, highlight it, because a change in basis can explain a variance that looks like performance. The assumptions block is the cheapest way to keep a financial summary reusable and to prevent comparisons across periods from misleading a reader. Update the block whenever a policy or reporting boundary changes during the year.
Voiskey keeps the summary work inside the document where it will be read. Press the shortcut, speak the period, currency, basis, reader, and structure, and the polished text lands at the insertion point. Then dictate the reconciliation questions in the same field: which lines changed, and by how much. Because filler words and false starts are removed, a prompt with several conditions survives dictation intact. The workflow of speak, polish, type, and edit means the brief, the table notes, and the review comments stay in one document instead of scattered across messages. Keep the review notes in the same document so the trail is easy to follow.
Reconcile the summary against the source before you send it. Pick the three largest variances and trace each one to a document. Confirm the sign, the period, and the entity. Ask for the variance table to show the prior figure, the current figure, and the difference, so a reader can recompute without a calculator. When a total does not tie, do not send the summary with a note that it is close; find the missing line. Rounding explains small differences, not large ones. Record each reconciled variance in the review notes with the source reference. Save the reconciliation note as part of the month file for the next preparer.
Ask for each material variance to be explained in one sentence with a cause and a consequence. The cause is why the number moved; the consequence is what it means for the reader. Keep the explanation next to the figure rather than in a separate narrative, so the reader does not have to match paragraphs to lines. When the cause is unknown, say unknown and name who will investigate. A summary that says unknown in the right place is more trustworthy than one that supplies a confident cause for every line. Review the unknown list before sending. Assign each unknown to a name and a date, not to a group.
Walk the summary with the budget owner before distribution, even briefly. Ask them to point to the one number they would question first, and check that the summary answers the question. Use their language for the drivers; a summary written in the reader vocabulary is easier to act on. Note any figure they cannot confirm and resolve it before sending. This conversation often reveals a scope difference, such as a cost center that moved between periods. Ten minutes with the owner prevents a correction later in front of a wider audience. Record the owner comments beside the summary and carry them into the next brief.
Turn the prompt into a monthly summary brief with fixed blocks: period and currency, sources, scope, comparison, structure, thresholds, assumptions, and review steps. Save the blocks in the order you speak them. Each month, change only the period, the file names, and the known exceptions. A stable brief makes summaries comparable across months and lets a colleague prepare the draft when you are away. Review the brief quarterly and remove blocks that no longer match how the team reports results. Keep the blocks short enough to speak without notes, print the order above the desk, and read it once before the close.
Share the brief with the finance and business partners and agree on the variance threshold and the structure. The team plan offers shared vocabulary and workflows, so account names and driver labels stay consistent across preparers. Store one approved summary as an example beside the brief. When two summaries differ, compare the briefs before comparing the numbers. Keep a change log with the date and the reason for each adjustment, because a threshold change can make a month look different from the one before it even when performance is unchanged. Ask each preparer to note the brief version on the summary header.
Voiskey supports more than one hundred languages and translation, so a preparer can dictate the brief in one language and ask for a summary in the language of the reader. Keep account codes, entity names, and currency labels unchanged. Ask for the assumptions block to state which language version is authoritative. Review the translated summary with a fluent speaker who knows the reporting conventions, because a translated term can shift the meaning of a variance. Store the approval with the brief so the next month uses the same wording. Note the language of each artifact in the month file for the reviewer.
Download Voiskey for Mac and Windows and dictate one monthly summary from the brief before the next close. Speak the period, the sources, and the structure, then reconcile the three largest variances as you review the draft. Keep the assumptions block and the review notes with the summary. After the close, add one line to the brief about what the reader asked for that was missing. Within two cycles you will have a brief that matches how your readers actually review numbers, which is more valuable than a longer template nobody follows. Keep the brief where the closing files live, not in a separate drive.
Voiskey is an AI voice typing app. Press a shortcut, speak the period, currency, sources, and structure, and the text appears at the insertion point in the app you are using. Filler words, stutters, and false starts are removed, and formatting is adapted, so the brief arrives as clean instructions for the summary.
Yes. Voiskey turns spoken requests into AI-ready prompts, including file names, paths, and commands. Say the export name and the sheet slowly, then check them in the polished text. Clear references help the summary point back to the exact source of each figure.
Voiskey learns names, jargon, acronyms, and spelling preferences. Account names, cost center labels, and finance terms stay consistent as you dictate, which matters when a small spelling difference changes the line being discussed. Say the terms once in the monthly brief and reuse it across periods.
Voiskey supports more than one hundred languages and translation. You can dictate the brief in one language and ask for the summary in another, keeping account codes and currency labels unchanged. Have a fluent reviewer check the translated variance explanations, because a shifted term can change what a figure appears to mean.

Download Voiskey for Mac and Windows and dictate your next financial summary.
Use it across macOS, Windows, iOS, and Android