How to prepare VAT return cover letters from a CSV

Steps

1. 1

   Freeze the reviewed return export

   Start only after the VAT return figures are prepared in the accounting workflow and ready for review. Export one row per client with fields such as `client_name`, `vat_period`, `return_reference`, `output_vat`, `input_vat`, `net_position`, `due_date`, `prepared_by`, `review_status`, `client_question`, and `contact_email`. Treat this as operational draft assembly, not tax advice; the CSV communicates reviewed return information, it does not decide the VAT treatment. Freeze the export before upload so a later spreadsheet edit does not silently change the wording in the generated letters. A common data error is mixing signs in `net_position`, such as `-1240.50` for a reclaim in one row and `Reclaim £1,240.50` in another. Pick one convention and make the template language match it. Include the period as a readable value like `Q2 2026`, but keep due dates structured as `2026-08-07` so the rendering and reviewer comparison stay consistent.

2. 2

   Fit the cover letter around your review process

   Shape the cover letter around the firm’s review status, not just the client message. Include a visible field like `{{ row.review_status }}` near the top so draft batches, manager-approved rows, and partner-ready rows are easy to separate. Keep the reviewed wording direct: period, reference, payable or reclaimable position, due date, attachments, client action, and contact point. Use stock Liquid for optional questions, for example `{{ row.client_question | default: 'No questions raised for this period.' }}`. If the client action changes based on payment status, use a reviewed conditional and keep it simple: `{% if row.net_position contains '-' %}No payment is requested for this reclaim position.{% else %}Please arrange payment by the due date shown above.{% endif %}`. Do not hide tax judgment in the template. The template assembles a communication for review; the return position and client instruction must already have been checked through the firm’s VAT process.

3. 3

   Preview common client scenarios

   Preview examples that represent the real VAT population: payable, reclaimable, nil, late-query, and question-heavy rows. Include a nil period where `output_vat`, `input_vat`, and `net_position` are `0.00`; these often expose awkward wording like “please pay 0.00” unless the template has a reviewed conditional. Check a reclaim row with `net_position` as `-2485.75`, a payable row with `net_position` as `3910.20`, and a client question such as `Please confirm whether the import VAT certificate has been received.` Confirm that due dates like `2026-08-07` render clearly and that `return_reference` matches the accounting export. Multi-currency clients need extra attention: if the VAT return is in GBP but management reports use EUR or USD, the letter should state the VAT currency explicitly. Compare each preview PDF against the frozen export before wider generation, because VAT cover letters are usually reviewed under deadline pressure.

4. 4

   Generate after reviewer approval

   Generate the full batch only after the sample PDFs are accepted by the VAT reviewer or manager responsible for the client communications. Keep the generated PDFs, frozen CSV, and template version together so the firm can reconstruct why a letter stated `Q2 2026`, `return_reference VAT-2026-0482`, or a specific due date. Route the PDFs through the normal manager or partner review before client issue, portal upload, or archive storage. Do not send generated letters directly from an unreviewed batch, even if the values came from the accounting system. If a reviewer identifies a row-level issue, fix the source CSV and regenerate that row instead of editing the PDF by hand. For webhook delivery, include a reviewed status field and verify that only approved rows move downstream. The workflow assembles VAT return cover letter drafts; firm review remains responsible for the tax position, client instruction, and final communication.