Five automations to prepare for quarterly tax work at an accounting practice

One invoice arrives by email, another through messaging, and a third is still waiting to be scanned. Before reviewing their tax treatment, someone has to find them and establish whether the client file is complete. That preparatory work is a good place to start automating.

It helps to separate quarterly preparation from filing deadlines. September is not a universal tax closing date. For taxpayers subject to the relevant Spanish state tax obligations, the AEAT sets, for example, 20 October as the deadline for the quarterly VAT self-assessment for the third quarter of 2026. The specific obligation, frequency and direct-debit deadlines need checking for each client; in territories with a foral tax regime, consult the competent tax administration. AEAT calendar.

I would prioritise workflows according to where your client files get held up, without trying to connect all five at once.

1. Receive documents with an acknowledgement

A form can collect the client, period, document type and file. The system assigns a reference and confirms receipt. I would retain the original, check for duplicates and put illegible documents or those without an identified client in a separate queue.

Renaming does not settle tax classification: a suggested label such as “investment” needs professional validation. Nor would I put a full Spanish tax identification number, or NIF, in every reminder's subject line. What matters is knowing what was received, where it is and who needs to review it.

2. Ask for missing items once per status

The reminder must check the client file before going out. If the client has already supplied the invoice, an issue is open or someone is speaking to them, it stops. The internal deadline for supplying documents may precede the tax deadline: the message must distinguish them.

I would use the agreed channel for managing the service and a link to the document area. I would not attach sensitive tax information to a brief reminder. I would measure how many repeated requests are sent because the client file has not been updated.

3. Set up clients without copying every detail again

An initial form can collect data and documents relevant to the contracted service, flag missing items and prepare the client record. A person checks identity, scope and consistency before activating the file.

I would avoid requesting certificates with private keys by default through a general form. Authorisations and access to administrative procedures need their own secure process. Automating client setup does not automatically grant access to tax procedures.

4. Extract fields and keep uncertainties visible

Document reading can suggest dates, taxable amounts and tax amounts. The draft should let the reviewer return to the file and locate the original data. Corrective invoices, multiple tax amounts, blurred images or totals that do not reconcile go to review.

Checking that a sum matches does not establish correct tax treatment. I would keep validation and filing authorisation with the responsible professional, with changes recorded.

5. Report from confirmed statuses

A summary can bring together outstanding documents, reviewed drafts and filed returns. Every status needs a date and supporting evidence: “filed” only after the acknowledgement has been received and checked. Forecast amounts are distinguished from final amounts, with their update date shown.

To choose the first workflow, take a sample of completed client files and record reception, review and correction minutes separately. In a hypothetical trial, saving files might be quick while chasing missing documents consumes almost all the time. Until measuring it, I would not assume filing is your priority.

Start with a hold-up you can observe, then check whether it stopped recurring.