Skip to content
Hypamoon

For teams that run on Standard Books

Standard Books monthly report by email

Standard Books has many reports on screen, but the overview a manager asks for often ends up in a spreadsheet. Excellent’s own help explains running the invoice rows report to Excel and doing the analysis there. Partners sell dashboards on Standard Books data, and Excellent runs sessions on pulling data out for analysis, for the same reason.

How it goes today

  1. Run the profit and loss report for last month in Standard Books.
  2. Run it again for each object or project the managers ask about, or export the rows to Excel.
  3. Paste the results into one spreadsheet and add last year’s figures.
  4. Check that the totals agree with Standard Books and mail the file to each manager.

How it can go

The monthly figures per object or project, in your inbox on the first working day.

On the first working day of each month you get an email with revenue, costs and result per object or project for last month, next to the same month last year, built from the bookings in Standard Books. Each department head can get just the part for their own object. If you keep budgets in Standard Books, the budget sits in a column next to it. Per quarter works the same way.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Standard Books first switches on access for your company when you ask them, which can take a few business days. After that you create the key yourself and paste it in the portal, never in the chat.

Your request

With Hypamoon, on the first working day of each month, email me revenue, costs and result per object and per project from Standard Books for last month, next to the same month last year and the budget where we have one. Send each department head just their own part.

You ask Excellent to switch on the API module for your company; in the cloud version their administrator also sets up the secure web address. You then create a separate API user with a validated email address in a user group with the Rest API right and access to the registers it needs. Its sign-in details are the key, and they stay yours.