A clearer handover between UK businesses and their accountants

Agree what a complete document pack contains

Suggested practice: identify the business and reporting period before collecting files. Keep invoices, receipts and credit notes distinct, and link each item to its original document. A folder name alone is not enough to explain an unusual transaction.

• Supplier and customer details, invoice number, supply and invoice dates.
• Currency, net amount, VAT shown and total, checked against the source.
• A reference to the purchase or property, a review owner and any outstanding question.

GOV.UK — What invoices must include

Keep a question open until someone resolves it

Example: a supplier sends a second version of an invoice. Keep both versions traceable and ask whether the second replaces the first or is a separate transaction. Do not silently overwrite an amount or assume that a second file represents another expense.

Use a shared exception list with the document reference, question, owner and agreed follow-up date. The business supplies missing evidence; the accountant reviews the accounting and tax treatment within the agreed engagement. These are suggested team responsibilities, not a statutory status system.

Separate collection, approval and the HMRC submission

Agree who prepares the records, who reviews them and which service performs the relevant filing. Income Tax and VAT are separate workflows. Where MTD for VAT applies, check the digital-link requirements across the actual software chain; a spreadsheet export or a successful download alone does not settle that question.

Yelnitax’s public preview does not file returns or establish agent authority. Confirm the product’s supported formats, access and exports before making them part of a client engagement.

HMRC — Keeping VAT recordsHMRC — Using MTD for Income Tax

Test a handover before increasing the volume

Choose a normal invoice, a credit note and an item with missing information. Agree the expected fields and review decisions, then compare the result in the receiving software. Record who accepted the result and what remains unresolved.

For an initial discussion, use fictional or redacted samples. Explain the accounting package, the review rhythm and the exceptions that cause repeated work; do not send client credentials with the documents.