Month-end reporting for a small business

Month-end reporting is the set of reports a business runs once a month closes. Here, one small company uses Oplema, a browser app for data flows and dashboards, to turn June's books into two answers: call Fern Home first, and hold the best-selling bottle.

The company and data are fictional.

Tarn & Tin's month-end, in order.

WhenWhat happens
July 1Ask two questions and read the books
July 2Build two flows
July 3Answer both on one dashboard
July 6Publish it and schedule next month
August 1Upload July's shop export
August 2The flows run on schedule

What does month-end reporting need to answer?

Tarn & Tin makes drinkware and sells it online and to trade accounts. June is over, and two people each have a question.

  1. Priya Nair, credit control: 23 invoices were overdue at June 30. Who do I call first?
  2. Tom Hale, founder: which product do we promote in July?

The answers sit in Xero, a Google Sheet of product costs and a shop export. Oplema reads Xero and Google Sheets through its connectors and never writes back to Xero. No connector covers the shop, so Tom uploads its export to Oplema's file storage in Cloud.

July 2: build two flows in Strata

Priya and Tom each build a flow in Strata by chaining blocks that each do one job. When a block needs drafting or fixing, they ask Oplema's AI assistant, Elara, and check what it changed.

Both flows on interactive sample rows: Priya's on top, Tom's below. Select a block to see its output.

Skip the interactive flow

Loading the interactive flow. The steps above don't depend on it.The interactive flow didn't load. The steps above don't depend on it.

July 3: answer both on one dashboard

They put both answers on one Vista dashboard with controls. Set Reporting date to 3 July and Harbour Tea's bar shrinks, because it paid an invoice on July 2. Set Fix the bottle to Halved, cost −25% (refunds halved and unit cost 25% lower), and only then does the bottle earn most.

Skip the interactive dashboard

Loading the interactive dashboard. The figures below don't depend on it.The interactive dashboard didn't load. The figures below don't depend on it.

What each owner decides. These are judgments, and the fixes are scenarios.

WhoDecisionFull case
PriyaCall Fern Home first. Ask Cedar Goods what's wrong with two invoices. Leave Iris Optics for now.Priya's list
TomHold the bottle promotion, since it keeps 8p in the pound. Try Cooler bag as the lead.Tom's product call

Priya saves a version of the project in Echo, Oplema's version history, before she tries another call order, so she can come back to this one.

July 6: publish and schedule next month

Tom publishes the dashboard from Cloud to one person, the team or anyone with the link. Viewers see current data through Tom's connections, plus its blocks and formulas, so he publishes only what they may see.

Priya schedules both flows for day 2 of each month, so they run with nobody at a desk. They run as hosted runs in your region and save their results to Cloud. The shop export stays manual: on day 1, Tom uploads the new file and points the flow at it.

Tom checks the usage in Console, where the team owner sees what hosted runs and Elara have used and what's left. Scheduled runs count even when they fail.

Where it stands

Priya has a call list and Tom has a product to try. July's reports run on August 2, and both open the same published dashboard.

How we built it

Invoices

69 rows. Xero's Invoices object would supply these.

Required columns: invoice_idcustomer_idcustomerinvoice_datedue_dateinvoice_total

Payment allocations

45 rows, each linked to one invoice. Each payment row must name one invoice.

Required columns: invoice_idpayment_dateamount

Order lines

96 lines from a shop export.

Required columns: order_idproduct_idquantitysalesrefunds

Orders

72 orders from a shop export.

Required columns: order_idstatusshipping_costpayment_fees

Product costs

8 products. A Google Sheets tab would supply these.

Required columns: product_idproductunit_cost

What real books would change

This project is the AR aging and contribution margin flows side by side, unchanged, and our checks confirm each gives the same answers as it does alone. The dashboard leaves out the margin case's product table.

  1. Swap the sample rows for Input blocks reading Xero, Google Sheets and the uploaded export. Column names need matching.
  2. Add an Output block that saves to Cloud, because a schedule refuses downloads and local files.
  3. Move the reporting date each month: the sample offers fixed dates. Hosted runs stop after 5 minutes.

AR and margin share a company in this story, but nothing here joins them: the data can't show which customers bought which products.

FAQ

What is month-end reporting?
The reports a business runs once a month has closed, to see what happened and decide what to do next. For a small company that often means who owes money, what sold and what each sale kept.
Is this a month-end close tool?
No. It reads your books and reports on them. It doesn't post journals, reconcile accounts or write back to Xero or QuickBooks, so the close itself stays in your accounting system.
Do I need Xero or QuickBooks?
No. You can upload exports to Cloud as files. Connectors also read sources such as Stripe, Google Sheets and PostgreSQL. There is no connector for shop platforms, so use your shop's export.
What won't it do?
It won't email the report, alert you when a run fails, export a dashboard to PDF or decide who to call. You open the dashboard and check Run history yourself.

Build yours from your exports

Start with one question. Local runs are free.