Reviewing a client's Making Tax Digital Income Tax year and sending their tax return to HMRC. The review is thirty or more HMRC requests behind one call — every income source's obligations, reporting setup, held position and year-end work, all their other income, losses, liability adjustments, HMRC's calculation, and the declaration with whatever is standing in the way — so it is slow the first time a year is opened and fast afterwards. What it reports as standing in the way is advice rather than a gate: HMRC hold the real rules and a practice that disagrees may proceed. The one exception is the declaration, which HMRC require the software itself to enforce. Behind its own permission, separate from quarterly updates, because HMRC allow a supporting agent to file the second and not the first. This filing is not idempotent: a submission whose outcome is unknown is settled by reconciling it against HMRC's own record, never by sending again.

Reconcile Tax Return

POST /tenants/{tenant}/clients/{client}/mtd/tax-return/{taxYear}/submissions/{submissionCode}/reconcile

Settles a tax return whose outcome nobody knows, by reading HMRC's own record back — the only safe way out of an in-flight submission, because sending again would give HMRC two returns for one year. Refused within HMRC's first hour, when 'no record' and 'never arrived' are the same answer: that refusal is the correct result and its message says so, not a failure to retry around.

Parameters

Name	Type	Description
tenant*	path string	The Tenant.Code
The Tenant.Code
client*	path string
submissionCode*	path string
taxYear*	path string

Responses

200 OK

MtdTaxReturnSubmissionDto

400 Bad Request

401 Unauthorized – Invalid or missing API key

404 Not Found

Reconcile Tax Return

Parameters

Responses

Try it

Related Schemas

MtdTaxReturnSubmissionDto