Weekly business report from your till and accounts

Reading the week means exporting from the till, exporting from the accounts and merging them by hand. A scheduled agent does the merge each week and drafts one report: revenue, top movers, costs and anomalies. Its department head reviews the report, then you approve.

How it runs

One agent does the work. Its department head reviews it, then you approve.

  1. 1Business analyst agent

    Runs every Monday at 08:00 and prepares the report from your connected sources.

  2. 2COO agent · Review

    The department head reviews the report before it reaches you.

  3. 3You

    You approve before anything goes out.

What you get

Weekly business report (Sample, not live data)Sample, not live data

Sample, not live data. The shop, products and figures are invented.

Week 3 (12 to 18 January)

This weekLast weekSame week last year
Sales (till)$18,400$17,100$16,900
Costs (accounts)$11,200$10,900$10,300

Top movers vs last week: Oat latte +38% · Gift cards -45% Top movers vs same week last year: Pastries +52% · Filter coffee -21%

Anomalies:

Tuesday till sales were $0 from 14:00 to 16:00; check whether the till was offline.

A $2,400 supplier bill is in the accounts but unpaid.

Two systems, one question

Most shops, cafes and service businesses keep sales in the till or POS and costs in the accounting package. Each answers half the question of how the week went. Record-keeping guidance treats both as core records: the IRS lists cash register tapes and deposit information among the documents for gross receipts, and HMRC lists bank statements, sales invoices, till rolls and bank slips as types of proof. The owner who wants a weekly view ends up exporting both and merging them in a spreadsheet, which is tedious and easy to let slip.

How the scheduled job works

You add the job and give it read access to your till or POS and to your accounting package. Organ builds both connections with read access; until they are in place the job waits, paused. A scheduled business analyst agent then runs every week. It totals sales from the till and costs from the accounts and sets both beside last week and the same week last year where the data exists. It ranks the products or services that moved most against each of those weeks, and notes anomalies such as a gap in till sales, an unpaid supplier bill or a cost line far above its usual level. Its department head reviews the report before it reaches you, and you approve, edit or skip it.

A worked example

Imagine a cafe that connects its POS and its accounting package. The report shows sales up on last week and on the same week last year, costs broadly level, oat lattes as the top riser against last week and pastries as the top riser against last year. It also points out two hours of zero sales on Tuesday afternoon. The owner checks and finds the card reader had dropped offline, something that is easy to miss when nobody looks at the week as a whole. This cafe and all figures here are illustrative.

Getting a useful report

Keep the report short and the same shape each week, so changes stand out. Name the extra metrics you care about, such as average sale or staff cost as a share of sales, and leave the rest out. If last year's data lives in an older system, say so when you add the job, so the year-on-year column has something to read. For related weekly jobs, see the inventory low stock alert job for reordering and the overdue invoice follow-up job for late payers, both linked below.

Questions

Any with an API or an MCP server: Organ can work with any API or MCP server, built for you, using read access you provide. The job waits, paused, until both connections are in place. It does not take uploaded exports.

Start with one report

You approve every report · Free to start