TaxMaxby AI Cloud Craft

TaxMax / For / Tax advisers

You already go to the source. Now prove it.

For chartered tax advisers and technical specialists: legislation as records with byte-level provenance, and a flag wherever the official publisher's own files conflict.

Text last reviewed 2026-11-15 · Read as plain text

1The standard

In Elden v HMRC [2026] UKFTT 41 (TC) the First-tier Tribunal said that “the human who relies on its use bears the responsibility for the accuracy” of AI output, directed that cases be referred to “by direct quotes from the judgement”, and noted that it “will consider making references to any professional body”.

You do not need telling to read the legislation. The harder questions are the ones the official site does not answer for you. Is the text in front of me exactly what was published? Did my tool, or my junior, or the AI, alter it on the way? And is the published text itself consistent?

The publisher is frank about the limits of the data it provides to software: “the legislation is somewhat out of date”, and “the completeness and accuracy of the data cannot be guaranteed”.

2What is different

What a specialist gets that a search box does not give

Provenance per provision

Each record names the SHA-256 fingerprint of the two official files it was read from and the byte ranges of its text in each. The files are the publisher’s own, so anyone who fetches the same bytes can check a record against them.

Two independent readings

The publisher’s XML and its Akoma Ntoso version are read by separately written extractors and compared provision by provision. Agreement is required, not assumed.

Inconsistency made visible

Across 27 Acts we found 124 places where the two official files differ, including dates stated in one and not the other, and list items lettered differently. Each is shown with both values. The full catalogue.

Exact answers about absence

A lookup returns the record; or the record marked unresolved with both versions; or “not observed”, meaning our release holds no such provision in that view. A view it does not support (a date range, “in force”) is refused as unsupported. It never says a provision does not exist.

Stated extent

Each record carries the territorial extent the publisher states for it or that it inherits, and says which of the two it is.

Refusal over approximation

Where a document cannot be read without guessing, the whole Act is refused and the reason published. 2 so far.

3A file note

The citation, with its provenance

A real one, made from the released record of section 4(1) of the Value Added Tax Act 1994. The byte ranges and file fingerprints in it can be checked against the publisher’s files. The build and record fingerprints are ours.

Value Added Tax Act 1994, section 4(1)
“VAT shall be charged on any supply of goods or services made in the United Kingdom, where it is a taxable supply made by a taxable person in the course or furtherance of any business carried on by him.”

Source: legislation.gov.uk, the publisher’s current view, fetched 14 November 2026.
Publisher’s XML, bytes 132648-132649, 132673-132874, file SHA-256 7ff1600a8df7ebcdff5d5660a0c01477cc3edb5daf174669a9cf2a1bb5befdc1
Akoma Ntoso, bytes 2660576-2660579, 2660643-2660646, 2660653-2660851, file SHA-256 5eeeac94b859dd7368f5a98f514138db735231de90fda00df57c079dafdc2f04
The two files agree on this provision. Extent as stated or inherited: E+W+S+N.I..
TaxMax build 4c333e82c849f92ff50f3b6469fa092730eba578242ab2ab79d6c9845f44b5a6, record d156e468028ba34fe85d37c1fb27327c00024acff838b864195d1f49d8ade956
Not an official version; not a statement of the law in force on any date.
4Limits a specialist will ask about

The questions you would put to us

Is it the law in force?

No. Each record is the publisher’s current revised view as fetched. Point-in-time versions are planned and not yet built. Prospective and unapplied amendments are recorded where the publisher states them and are not applied by us.

Does comparing two files from one publisher prove anything?

It proves less than two independent publishers would, and we say so. It is designed to catch extraction error on our side and inconsistency on the publisher’s. It cannot catch an error common to both files. For anything that turns on a word, check the King’s Printer copy.

Secondary legislation, guidance, cases?

Not yet. Statutory instruments are planned next, by arrangement with the publisher. Case law waits on a licence from The National Archives for computational use, which we have applied for.

Who checks the checkers?

Every release is reviewed by two AI systems from different developers, against written briefs, with deliberately planted faults that each build must catch. The company’s director is accountable for each release. The method page sets it out in full.