{
  "id": "p_OsIU19-S5choRHgf",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_OsIU19-S5choRHgf",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "Picture your practice in the spring. A handful of your sole-trader and landlord clients have qualifying income over £50,000, which means they have been filing quarterly under Making Tax Digital for Income Tax since April 2026. Now you are looking ahead. The threshold falls to £30,000 in April 2027 and £20,000 in April 2028, and your client list is about to get a lot more quarterly work on it.\n\nThen a post from Sage lands in front of you. It argues that Making Tax Digital is moving compliance \"from inputting data to reviewing it.\" Agentic AI, it says, can \"suggest transaction categories at source, flag possible errors before submission, support the workflow, and help give clients insight, with accountant review at each step.\" That sounds like it was written for your situation.\n\nThe product behind it is the Sage MTD Agent. According to the post, it segments clients by MTD readiness, drafts quarterly reports from digital records for review and HMRC filing, and chases missing documents \"via email, WhatsApp or in-app notifications.\" You also see a headline number: \"up to 80% less admin.\" That is a vendor figure, and no method is given for it, so you should read it as a claim and not as a measurement.\n\nWhat holds up better is the principle Sage repeats in every section: the accountant approves what is sent and submitted. In the post's words, \"Control over automation: You stay responsible for what's submitted.\" For an agent that touches a tax filing, that is the right line to draw, and it is the part you would want to hold Sage to.\n\nSo you do what a careful person does and look at the public API record, in the APIs.io catalog, to see what sits underneath. The Sage provider page lists 13 API pages. The ones this story leans on are there: Sales Invoices, Purchase Invoices, Bank Accounts, Ledger Accounts and Tax Rates. Those are the digital records a quarterly update is drafted from. The Sage agentic access profile counts 25 operations, 12 of them acting, meaning they change something and do not only read.\n\nThen the record stops. None of those API pages describes the MTD Agent itself. Nothing there covers client segmentation, and nothing covers the quarterly submission step. The UK product the post is written for, Sage Accounting, holds just one page in the catalog, the Sage Accounting v3.1 REST API.\n\nThe scores sharpen the picture. Sage rates 40.4 on the Kin Score, in the developing band. Contract quality, at 66.4, carries it, with developer ergonomics and discoverability at 57.1 each. Access clarity sits at 5.3 and operational transparency at 7.9. Agent Readiness is 29.8: error semantics and delegated identity are lit, while dry-run mode, reversibility and idempotency are not. Sage Accounting scores lower, at 20.7, with Agent Readiness of 2.5, which the catalog labels human-only.\n\nThis is where the post turns on the company's own record. The agent's whole promise is to \"flag possible errors before submission.\" But dry-run and reversibility are exactly the dimensions that are unlit. Sage has told accountants they stay in control, and its public record does not yet show a developer how a submission can be previewed or undone.\n\nSo here is what you take away. The review-and-approve design is sound, and it is the part of Sage's pitch you can lean on. The 80% figure is a vendor number, so don't plan your capacity around it. And before you let any agent near a client's quarterly filing, ask the questions the public record leaves open: can a submission be previewed first, and can it be undone? Those are the controls your sign-off depends on.\n\nRead the original: https://apis.io/2026/10/27/sage-puts-an-agent-on-making-tax-digital-and-the-api-record-stops-short/",
  "title": "You're the accountant with a April 2027 deadline, and Sage's agent has a gap you can't see",
  "topics": [
    "making-tax-digital",
    "ai-agents",
    "accounting",
    "agent-readiness"
  ],
  "published_at": "2026-10-27T13:09:46.014Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}