How workflows run

Match the automation to the work

Start by looking at how the task gets done. A tax calculation may need the result of an earlier step, while several source documents can be read independently. These examples show how that affects the automation and the checks it needs.

Steps completed in order Four steps connected in a single line, Import, Transform, Verify, Deliver, with an arrow between each pair pointing right. Verify is marked as the review step. The connecting lines flow from left to right, showing the work moving down the line one step at a time. Import Transform Verify Deliver

Complete the steps in order

How it works
Each step uses the result of the one before it. For example, calculate capital cost allowance before using the deduction in your book-to-tax adjustments.
Where it helps
Work where calculations feed other calculations, or a file must be prepared and checked before it can be imported.
A tax example
Our SR&ED automation prepares a workbook from extracted figures, fills an upload template, then loads it into the tax software. Those steps have to run in order.
What to check
Check each result before the next step uses it. If a check fails, stop and show what needs fixing before the work moves on.
Independent documents read at the same time A single Source files node fans out to three documents read at once, Financials, Project docs, and Assessment, which come together into one Upload template node, with arrows on every branch. The branch lines flow from the source out to the three documents and back into the template, showing the reads running at the same time and merging at the end. Source files Financials Project docs Assessment Upload template

Run independent tasks at the same time

How it works
Tasks that do not need one another's results can run together. Their outputs are combined and checked when they finish.
Where it helps
Reading separate source documents or preparing independent entity calculations. Running these tasks together can reduce the total waiting time.
A tax example
Our SR&ED automation reads the financial statements, project write-up, and prior notice of assessment separately. It then brings the extracted figures together for checking.
What to check
Confirm that one task cannot change the data another is using. Reconcile the combined result before using it in the next stage.
Shared calculations updated from one place A central workbook holding shared calculations, surrounded by five entity workbooks. The lines flow from the central workbook outward to every entity workbook, showing an update reaching all of them from one place. The workbooks never connect to each other. Shared calculations Entity A Entity B Entity C Entity D Entity E

Update shared calculations from one place

How it works
A central workbook holds the shared calculations and a record of each workbook's version. Each entity workbook can take an approved update from that central copy.
Where it helps
Groups where many entities use the same calculations. A correction can be prepared and tested in one place, then distributed to the workbooks that need it.
A tax example
For example, entity tax-provision workbooks can share their automation from a central workbook. Each workbook checks for changes and installs an update after its owner approves.
What to check
Keep a clear record of which version each workbook uses. Test an update before wider use and decide who approves it. Owner approval controls when an update runs; the update still needs checking.

A workflow can combine these approaches

Our SR&ED automation reads several documents at once, then prepares and checks the workbook before entering the tax software. Understanding which steps can run together, and which need a checked result first, helps you decide how to automate the work.

Discuss a task your team repeats

Describe how the work gets done. We can help identify what could be automated and where checks are needed.

Type to search across the site.