Bwat

Finance work

Spend the review on exceptions, not rows

Bwat helps turn messy files into traceable analysis and a usable first draft

Give Bwat the workbook, ledger export, invoice folder, agreement, or board pack behind the question. It can clean and compare the material, show how it reached a figure, produce a working file, and draft the explanation around it.

Bwat is an analysis assistant, not an accounting system, auditor, or approver.

Bring the real source material

  • Workbooks and CSV exports
  • Invoices, statements, and receipts
  • Budgets, forecasts, and board papers
  • Contracts, facilities, and lease documents

Reconciliation should end in an exception list

The useful output is not a paragraph saying that two files differ. Ask Bwat to normalise the data, define the matching logic, produce the matched and unmatched populations, and return a workbook another person can inspect.

  • State the match keys and tolerances before comparing
  • Keep timing differences separate from unexplained differences
  • Preserve source rows and identifiers in the output
  • Summarise the value and cause of the exceptions, not only their count

Common comparisons

  • Bank statement against ledger
  • Invoices against receipts and payments
  • Payroll against prior month and approved changes
  • Budget against actuals and revised forecast

Across the reporting cycle

Interrogate a workbook

Understand sheets, formulas, assumptions, and anomalies without manually hunting through every tab.

Build the working

Turn stated assumptions into a model or calculation with formulas another analyst can inspect and change.

Explain a variance

Separate price, volume, timing, mix, and data-quality effects before drafting the management explanation.

Find the exception

Check a large file or folder for duplicates, gaps, unusual movements, and records that break the expected rule.

Draft the pack

Create the memo, board narrative, chart, or slide deck from reviewed figures and the supporting context.

Read the obligation

Extract payment terms, covenants, dates, fees, and conditions from the agreements behind the numbers.

Make the working explicit

Attach the relevant files, replace the brackets, and keep the output reviewable.

Reconcile two exports

Reconcile the bank export and ledger I attach for [period]. Before matching, inspect both files and propose the match keys, date tolerance, and amount tolerance. Then produce an Excel workbook with matched items, timing differences, and unexplained exceptions on separate sheets, preserving the original row identifiers and formulas used.

Explain budget variance

Compare actuals with budget and the latest forecast for [period]. Quantify the largest favourable and adverse variances, separate likely price, volume, timing, and classification effects where the data supports it, and cite the exact sheet and cells. Draft a concise management commentary, but flag explanations that need confirmation.

Audit a model

Review this financial model without changing it first. Map the input, calculation, and output sheets; find hard-coded values in formulas, broken references, inconsistent periods, circular logic, and assumptions that are not documented. Rank findings by possible effect on the result and cite each cell.

Read a finance agreement

Extract every financial obligation, fee, covenant, reporting deadline, default trigger, and remedy from this agreement. Build a table with the obligation, responsible party, amount or formula, due date or frequency, condition, and clause reference. Do not infer a value the agreement does not state.

Review remains part of the workflow

A spreadsheet can be internally consistent and still answer the wrong question. AI can also choose the wrong matching rule, misread a period, or explain a variance with a plausible story the data does not prove.

Bwat is most useful when it produces inspectable working, preserves the source references, and labels assumptions for a finance professional to confirm. It prepares and accelerates the analysis; it does not sign it off.

Try it on a completed month

Use a period your team has already closed. Known answers and known exceptions are the fastest test of whether the workflow deserves trust.