Status
Where the software stands today
What is finished, what is being worked on, and what Murgese does not do. This page is kept current, and it is the first thing we change when something moves.
Accounting software makes claims that a UK accountant reads as regulatory statements. We would rather set out the position in one place than have you infer it from a feature list.
Current version 2.9.38, released 07/10/2026. Last checked 25 September 2026.
- In the product
- Finished. You can use it today.
- In progress
- Being worked on, and not available today. Read the sentence beside it for what that means in practice. We do not give dates, because a date we missed would be worse than no date at all.
- Planned
- On the list, and nobody is building it today. Different from being worked on, and we would rather you knew which.
- Not planned
- Not there, and not on the list.
| Area | Status | What that means |
|---|---|---|
| VAT under Making Tax Digital | In progress | Murgese is not HMRC recognised today and is not on HMRC's list. Builds ship without vendor credentials, and the product itself says on the screen that the build cannot file. It prepares the return, and you submit it. One part of that application has now been checked against HMRC rather than against ourselves: the fraud prevention headers that must accompany every submission were put through HMRC's own test service on 29 August 2026, which returned no errors and one warning, that the product has no second authentication factor to report. It is not a submission, and it is not recognition. Recognition is being worked towards, and this page changes when it arrives. |
| Income tax under Making Tax Digital | In progress | The quarterly updates, the accounting adjustments, the calculation and the final declaration are built and work end to end. Nothing is sent to HMRC: Murgese Ltd does not hold HMRC's production credentials for the Income Tax interfaces, which are granted separately from the VAT ones, and the product says so on every Income Tax screen rather than letting anybody find out at the deadline. Prepare and lock the quarters here, and file by the route you file by now. |
| Corporation tax, CT600 | In progress | The computation and the CT600 are prepared in full. Submission to HMRC is not available today, for the same reason as above, and is being worked towards alongside it. |
| Companies House filing | In progress | Looking a company up on the register is a different thing from filing to it, and the lookup works: you register for your own free Companies House API key, which takes a couple of minutes, and paste it into the settings screen. We cannot ship a key of our own, because their developer guidelines forbid keys in application code, an installer is a published file, and the limit is 600 requests every five minutes per key, so one shared key would mean one busy firm throttling everybody and one revocation breaking every installation at once. On filing: iXBRL accounts have been exercised against a test harness of our own, not against Companies House. No live presenter filing has been made yet. Moving to live filing is on the list. |
| Bank feeds | Planned | The panels are not shown in the software you install: neither the bank feeds panel on the settings screen nor the feed panel on a client's Bank screen. There is no date for turning them on. Nothing has been deleted. The routes, the provider library, any stored credentials and the reconciliation are all still there, so a firm that already had a feed keeps its lines and its matching, and switching the panels back on is one word in one file. The feed was never connected to a provider in any case, not even in a sandbox, and a firm would also have needed its own account with the provider. Statement import from a file is the route that works, in seven UK layouts. The five end-to-end tests that drive the feed still run against the real panel, so the part that usually rots while a feature is off is the part being watched. |
| macOS version | Planned | There is no macOS build to install, nobody is building one at the moment, and there is no date. What a Mac can do is use Murgese in a browser: the Windows machine running it serves the application to other devices over HTTPS, so a Mac, an iPad or an Android tablet reaches it on the office network, or from outside the office through your own VPN into that network. The one step is trusting the office certificate on the device using it. The written instructions for that cover Windows, so on a Mac or a tablet you are installing the same certificate file yourself, without a guide from us. It works; it is not documented, and we would rather say which of those two things we are claiming. |
| Code signed installer | In the product | From version 1.93.0 the installer is signed by Murgese Ltd, so Windows names the publisher rather than saying the publisher is unknown. Windows may still show a warning on the first run of a new release: the certificate is an ordinary code signing certificate rather than an extended validation one, and reputation with Microsoft's SmartScreen is earned over time rather than bought. Choose More info, then Run anyway. We would rather say that than tell you the warning has gone. |
| The desktop runtime, and what it is hardened against | In the product | Murgese is an Electron application and runs on Electron 44, which carries Chromium M152 and is supported until March 2027. The window runs with context isolation on, Node integration off, and inside the operating system's own sandbox, with a content security policy and the arguments crossing between the two halves of the application checked. The sign-in page does not tell the office network which firm the installation belongs to, and an email address that has no account costs a would-be intruder the same time as a wrong password, so a list of addresses cannot be turned into a list of your staff. One thing is refused on purpose and the reasoning is written into the source: the session token stays in the browser's own storage, because on this installation the books are a file in the same Windows profile, so moving the token would protect the weaker of the two secrets and cost you the thing where reopening Murgese does not ask for your password again. |
| Screen readers and the keyboard | In the product | More than six hundred labels across the application are joined to the field they name, so a screen reader announces what it has landed on rather than reading an unnamed box. A dialogue holds the keyboard while it is open rather than letting thirty tab presses walk onto the screen behind it, and Escape hands focus back to the button that opened it. The status filters say in words which one is on rather than showing it only in a border colour, and the sidebar search hint measures 5.4 to 1 against its background on every theme. This has not been tested with a person who uses a screen reader every day, which is the only test that settles it. |
| Updating to a new version | In the product | Murgese looks for a new version only when somebody chooses Help, then Check for updates. A daily check exists and is off until a firm switches it on, and an update can also be installed from a file with no internet connection at all. In a firm using the office server, one machine reaches us and the others get the update from it, so nothing about the rest of the firm's PCs leaves the building. Before anything is installed, the download is checked against the checksum in the release notice and its signature is checked against Murgese Ltd: an installer that is unsigned, signed by somebody else, or altered after signing is refused on the machine rather than merely reported. |
| CIS subcontractor verification | In progress | Verification requests cannot be sent from the product. That service runs on HMRC's older CIS Online channel rather than the Making Tax Digital interfaces, and needs its own vendor recognition. Verify through HMRC's own service or by telephone and record the answer here: the rate, the CIS300 and the staleness date all follow from it. |
| The VAT schemes Murgese records but does not work out | Not planned | Three retail schemes are recorded against a client and refused by name, with the reason on the screen. Apportionment Scheme 2 works from expected selling prices on a rolling twelve months, Direct Calculation Scheme 2 turns on an annual stock adjustment, and a bespoke scheme is agreed between one business and HMRC and written for that business. The Auctioneers' Scheme is refused in the same way, because its margin takes in the commission and the charges made to both sides, so the figures are different ones. In each case you work the output tax out yourself and put it on the return as an adjustment, which is recorded and can be taken back off. Point of Sale, Apportionment Scheme 1 and Direct Calculation Scheme 1 are worked out in full. |
| Partial exemption | In the product | The calculation is set out on the VAT screen as a working paper: the input tax split between taxable, exempt, residual and blocked, the recovery percentage, and each de minimis test with its figure and its limit. It is reported rather than applied. Box 4 is not reduced by a computed number: the restriction goes on the return as an adjustment you make, which posts a journal and records who made it and why. Input tax that has not been attributed is listed by document and the calculation says it is incomplete until it is, rather than assuming it. |
| Self Assessment and the partnership return | In the product | The SA100 with the supplementary pages: SA101 additional information, SA102 employment, SA103 self-employment in full, SA104 partnership, SA105 UK property, SA106 foreign, SA108 capital gains, SA109 residence and remittance, and the SA110 tax calculation. The SA800 partnership return with the partnership statement and each partner's share. Prepared from the books rather than retyped, with the figure behind every box. Preparation only: see the income tax row above for filing. |
| Payroll | Not planned | Murgese does not calculate payroll and there is no plan for it to. Run your payroll wherever you run it now; it will read a P32 so the month does not have to be typed in, and the payroll screen takes the totals off that summary and posts them as one journal, and then checks that what was posted has actually been paid over to HMRC and the pension provider. |
| Audit | Not planned | There is no audit functionality, and none is planned. Accounts are prepared unaudited and the accountants' report says so. |
| A full annual cycle | In progress | Murgese has not yet been run alongside another package for a complete year. Nothing it reports has been confirmed against a real filing, except where a user has run the check against a filed period. This one takes a year to change, whatever anybody does. |
| Ledger, sales, purchases, bank, reports | In the product | Double entry in whole pence, the document types, statement import from a CSV or the bank's own PDF and coding, bank rules that suggest rather than post unless told to, reconciliation, and the statements with comparatives and multi-period runs. |
| VAT and CIS preparation | In the product | The nine boxes on cash or accrual, the margin schemes and the retail schemes, the CIS domestic reverse charge, postponed import VAT, adjustments, the approval pack, the filed archive, recorded verifications, deduction statements and the CIS300. |
| Year-end accounts | In the product | FRS 105, FRS 102 Section 1A, the Charities SORP and dormant accounts, with iXBRL output. |
| Leases under FRS 102 as amended | In the product | For accounting periods beginning on or after 1 January 2026, leases a company holds as lessee go on its balance sheet. Murgese keeps the register, works out one schedule per lease, posts the month-end interest and depreciation, handles a lease already running at the date of initial application, a rent review, a reassessment, a break with a payment to leave and an end agreed with the lessor, and writes the Section 1A leases policy and note. The note is held back, and the filing with it, until the register agrees with the ledger. Lessor accounting, subleases and sale and leaseback are not covered, and this is FRS 102 as amended rather than IFRS 16. FRS 105 was not changed: a micro-entity's leases stay off its balance sheet, and nothing here applies to one. |
| Deferred tax and the Section 1A tax note | In the product | Deferred tax under FRS 102 Section 29, worked out at the year end from the corporation tax computation posted for it and posted in one journal, with the tax note that Section 1A asks for from periods beginning on or after 1 January 2026. Three things it does not do, and we would rather say so than let you find out at a year end. The structures and buildings allowance is entered by hand as another timing difference rather than worked out. Revaluations are not covered. And where nothing was carried at the start of the year and something should have been, the screen estimates how much and explains where the figure came from, but it does not post the restated comparative for you: correcting a material omission in earlier accounts is a decision, and it stays yours. |
| Migration and the filed period check | In the product | Whole history from Xero or QuickBooks with a reconciliation against the source, and a recomputation of a filed period compared with what was submitted. |
| Anti-money laundering, Practice edition | In the product | The firm’s record under the Money Laundering Regulations 2017: a risk assessment for each client with the rules that force enhanced due diligence, directors and owners read from Companies House, evidence for each person, review dates on the deadlines, the MLRO’s log, the firm-wide risk assessment and policies, training, five-year retention and inspection packs. Off until the firm switches it on. The firm stays responsible for its compliance. |
| Identity and sanctions checks through ComplyCube or Veriphy | In progress | Built into the anti-money laundering screens from each provider’s own documentation, on the firm’s own account with the provider, and not yet run against either provider’s own service. Until it has been, a check made in the provider’s own portal is recorded on the client’s file as another provider’s report. This row changes when both have been tried. |
What we will not say
Murgese is not described anywhere on this site as recognised, certified, compliant, guaranteed, proven or trusted by anyone, because none of that would be true yet. Nor will you find a promised date against anything above. Work is under way on all of it, and we would rather tell you where it stands than tell you when it will land and be wrong. If you find something on these pages that reads as a professional or regulatory endorsement, tell us and we will change it.
What is true is worth more anyway. The software runs on your own machine, it brings a client's entire history across rather than a closing balance, it will check itself against a period you have already filed, and everything it produces can be got back out again years later.
Judge it on where it actually stands
This page is the honest position and it is updated first. If what is missing matters to you, say so and we will tell you where it sits.