Guided tour

Watch it do the thing, then do it yourself

A film of just over a minute, eight routes through twenty-eight of the real screens, and a longer film that walks the whole thing through end to end. Nothing here is a mock-up: these are captures of the application running on demonstration figures.

Eight routes, twenty-eight screens

Pick the one that matches your question

Each route is a few screens in the order the work actually happens. Use the numbered marker, the buttons, or the left and right arrow keys. This is a sample rather than the whole product: there are twenty-three modules, and the full map is here.

What the firm is carrying today

Everything a practice owes somebody, in one place, built from the client records rather than from a list a person maintains.

The practice dashboard, showing overdue work, clients, open jobs, work in progress by stage and the deadlines in the next thirty days
What is overdue, and whose it is The firm's own screen: what is past a statutory date, what is due this week, what is sitting with a client, and who owns each one. The deadlines come from each company's own year end and VAT stagger, so nobody types a date in twice.
The records inbox, with what has arrived by email, what is waiting to be placed against a client, and what has recently been filed
Records arrive and file themselves Clients send their papers to a mailbox the firm already has. Murgese reads what is unread, works out whose it is, and files it against that client's open period. What it cannot place with certainty it does not guess at: those wait at the top of the screen for somebody to say.
The job board with every client job grouped by stage, each showing its owner and due date
Every job, by where it has got to Not started, in progress, review, waiting on the client. Each card carries the client, the owner, the due date and how many steps are done. Next quarter's jobs exist because the deadline exists, not because somebody remembered to create them.
The Q2 VAT return job checklist with its completed steps, owner, reviewer and due date
And what is left to do on it The steps done, the owner, the reviewer and the date. Every tick goes to the audit trail with who made it. File with HMRC is a step somebody ticks once they have filed, not a claim that Murgese has filed anything.

Code a payment, and then trace it

A statement line arrives with no account on it. Give it one, post it, and find out a year later who did that and when.

A company dashboard showing cash at bank, what is owed, profit over twelve months and the items needing attention
One company, and what needs attention Cash, what is owed to the business and by it, profit over twelve months, and the handful of things that actually need somebody. Down the left is the whole of the software for this company: sales, purchases, accounting, reports, tax and the year end.
The bank screen with imported statement lines awaiting an account, and a note saying no bank feed is connected
The statement, read as it came Seven UK bank layouts read directly, so a statement does not have to have its columns rearranged first. The screen says plainly that no bank feed is connected and what would be needed, rather than leaving somebody to find out. Coding runs from the keyboard: a code, enter, and the next line.
The bank line with 5420 Printing, Postage and Stationery selected
The account, chosen rather than guessed 5420 Printing, Postage and Stationery, picked from the chart this company actually has. A rule can suggest an account, and a suggestion is not a posting: nothing reaches the ledger until it is told to.
The bank line showing its assigned account and a posted state
Posted, and it says so The line carries its account and its posted state on the face of the screen. There is no second place to go and check whether it worked.
The audit entry generated by the bank posting, naming the person, the action and account 5420
A year later, this is still answerable The audit entry names the person, the action and the account. Putting something right is another entry rather than a change to this one, so the trail records what happened rather than only where things ended up.

Follow a figure to the entry behind it

A total on a report is a question, not an answer. Open it and keep going until you reach the document.

The report library, listing every report grouped by subject with a search across them
Forty-nine reports, in one searchable list Grouped the way an accountant looks for things: financial statements, payables and receivables, transactions, taxes and balances, financial performance, stock, and a group called things to look at. A report that lives on its own screen, the VAT return say, is listed here too with a link rather than an apology.
A profit and loss report showing sales revenue of £900
Start with a number you want to explain Sales revenue of £900. Every figure on a Murgese report is a way in rather than the end of the line, and the report says how many nil accounts it has hidden and the moment it read the books.
The sales revenue account detail showing invoice INV-1000 and the counterpart accounts
The entries, and the other side of each one The account detail names invoice INV-1000 and shows what it posted against. From here the invoice itself is one more step, which is the difference between a report you can defend and a report you can only print.

Read the business, not just record it

Management accounts, the business cut by property or site, and the one list a credit controller works from.

Management accounts for a month, each line against budget and against last year, with the position and working capital beneath
The month and the year, against budget and against last year Prepared through the year rather than only at the year end. A figure on its own tells nobody anything, so every line carries the period, the budget, the variance and the same period last year, with the position and working capital underneath. Where no budget is set the screen says so rather than printing a column of noughts.
Profit and loss by site, with income, costs and result for each property and a total that agrees with the profit and loss
Which property, site or job made the money A second label beside the account on every posting, and a profit and loss per site from it. The total is the whole period, tagged and untagged together, so it agrees with the profit and loss line for line rather than living in a spreadsheet that does not.
The credit control worklist, showing what to chase, what is overdue, what is promised and what is disputed
The list somebody can actually work from Ordered by who to chase today, with money on account at the top so nobody rings a customer who has already paid. A disputed invoice is flagged rather than reclassified: it is still owed and it still ages, and what changes is that the list stops telling somebody to ring them.

The two returns a contractor files most

Nine boxes and a CIS300, prepared from the ledger and taken apart before anybody signs them off.

A nine box VAT return for a filed period, with its checks, late claims and ratio tests
Nine boxes, and what is worth checking first The return for a period, on the basis the company is registered under. Late claims are counted and named, the ratio checks say what a wholly standard rated business normally looks like, and a period already filed says so and refuses to be quietly rewritten.
The transaction by box breakdown behind the VAT return
Every box, and the transactions inside it The amount and the number of transactions behind each box, so a figure that looks wrong can be taken apart rather than argued about. Preparation and review is what these screens show. No return was filed here, and filing needs its own setup.
The CIS monthly return, with each subcontractor's verification state and the rate that follows from it
The CIS month, and the rate each subcontractor earns The CIS300 built from the payments actually made. Verification fixes the rate and the screen holds it per subcontractor with the date it was obtained and the date it goes stale. Never verified means 30%, whatever anybody has typed against them. Verification requests cannot be sent from here and the screen says so, and says exactly what to do instead.

Close the year, and compute the tax

Statutory accounts under FRS 105 or FRS 102 Section 1A, and the corporation tax return built from them rather than typed beside them.

The year-end accounts screen, with its tabs and the audit exemption conditions tested against the ledger
The accounts, with the conditions tested rather than assumed Company details, directors, sections, notes, wording, approval and the iXBRL, in the order the work is done. Audit exemption is worked against the year's own figures and each condition shown with its limit. Where balance sheet accounts have not been reconciled it says so, names the amount unexplained, and prepares the accounts anyway rather than refusing.
The company tax return screen, stating why the return cannot be sent and listing every box filled or not
Every box, filled or not, with the reason beside it The CT600 built from a posted computation rather than from a screen nobody saved. It is not sent: HMRC have not recognised this software for Corporation Tax Online, and that is printed on the screen instead of hidden behind a disabled button. The boxes it does not fill are named, so what has to be added by hand is visible before it goes in.

Before you trust any of it

Bring a client's whole history across, then make the software check itself against a period you have already filed.

The import screen listing the files a whole history needs, with what each one is and where to export it from
The whole history, not a closing trial balance Every posting from Xero or QuickBooks, with the chart, the contacts and the documents, and then verified against the source file account by account. Each file is identified by what is in it rather than by its name, so the order they are added in does not matter.
The check against a filed period, showing figures compared, agreed, differed and not checked
Recompute a year you have already filed Take a period you signed, recompute the VAT returns, the CIS returns and the key figures from the records, and name every difference against what was actually submitted. The right answer is known before the check starts, because it is whatever was filed.
The explanation on the filed period check of what a difference between the two sets of figures can mean
A difference is not by itself a fault It is one of three things, and which one it is has to be decided by looking at the figures behind it. It may be a fault here. It may be a fault in the original filing, which is worth finding too and is not unusual. Or it may be a difference that is defensible on both sides, such as a late claim or a prior-year correction. The screen says so rather than implying the software won.

AI, if the firm wants it, and checked when it does

Murgese reads documents with its own reader, on your computer. AI is an option a firm turns on with an account of its own, and everything it writes is checked before anybody uses it. The answers in these screens were scripted with a test stand-in, not written by a model.

Practice settings in Murgese, with Murgese's own reader in use for invoices and statements, analysis and drafting off, and Claude, OpenAI and Azure OpenAI listed as the alternatives
Its own reader, unless the firm chooses otherwise Practice settings, Reading and analysing with AI. Invoices, receipts and bank statements are read by Murgese's own reader, on this computer, and nothing is sent anywhere. A firm that wants AI can choose Claude, OpenAI or Azure OpenAI, with an account of its own. Analysis and drafting is a separate switch, and here it is off.
The confirmation Murgese asks for before anything is sent to Anthropic, with three statements ticked and suggested wording for an engagement letter and a privacy notice
Nothing is sent until the firm confirms three things That it has accepted the provider's data processing terms, that its clients have been told, and that it has read its professional body's guidance. The answer is recorded on the audit trail with the name of whoever gave it, once for each provider, and wording to start from is offered for the engagement letter and the privacy notice.
An analysis of a profit and loss account in Murgese, with one figure marked as not in the figures sent and a reference to a standard flagged for checking. The answer was scripted for the demonstration.
Every figure checked against the figures sent Analyse with AI on a profit and loss account. What comes back is a draft to judge, not a finding. A figure that is not in what was sent, and cannot be worked out from it, is printed in red under its sentence; a reference to a standard is flagged to be checked; a point that could be said of any company is marked General and put last.
Policies and notes drafted with AI in Murgese: two proposals ticked, one left unticked because it holds a figure that is not in the accounts. The wording was scripted for the demonstration.
Proposals to tick, never changes made for you Draft policies and notes with AI, on the year-end accounts. Each proposal is ticked or left. One with a figure that is not in the accounts starts unticked, and a fact the books cannot give is left as a bracketed prompt to fill in. Nothing changes until somebody presses Use the ticked wording.
Two pieces of wording drafted with AI waiting to be marked reviewed before the accounts can be approved, each with who drafted and who accepted it
Read again before the accounts can be approved Wording drafted with AI stays on a list, with who drafted it and who accepted it, until somebody marks it reviewed. The accounts cannot be approved while anything is on it.

The film

Three and a half minutes, end to end

The same five journeys, played out in full: a practice day, a bank line coded and reported on, the VAT return through to the company tax return, the thirteen reports on the firm, and a set of books brought across and checked against a year already filed.

Three minutes thirty five, with subtitles. The narration is synthesised. Request the software

What the tour is not

Two things worth being plain about

The VAT screens show a return being prepared and reviewed, and no return was filed here. The company tax screen shows a CT600 prepared, with the reason it cannot be sent printed on the screen itself. A checklist step reading "File with HMRC" is a box somebody ticks once they have filed, not evidence that the software has filed anything. The status page sets out where all of that stands.

Every company, client, name and figure in these screens is invented. The screens themselves, and the layout of them, are the application.

Run it on a period you already know the answer to

A tour is worth less than half an hour with the software on figures you can check. Request the installer and the manual, and see whether it agrees with you.