Skip to content
Industries / Accounting & bookkeeping practices
Accounting & bookkeeping practices · Custom workflow design

Keep client records, reconciliation exceptions and period-end work moving

Coordinate the document chase and review queue around your accounting tools. Preserve the source evidence and leave accounting judgements with the practitioner.

For Practice manager, accountant or bookkeeping business owner

Explore three real work situations ↓
How it could work

Start with a situation you recognise.

Illustrative designs to scope with your team. Select a scenario, then follow the normal path and the exception.

Month-end is waiting on a few client records

Finished result

A source-linked client pack with remaining gaps visible.

  1. 01Read period requirements
  2. 02Match received documents
  3. 03Request specific gaps
  4. 04Update reviewer readiness
When something does not fit

A statement covers the wrong period or the client sends the same receipt twice.

What happens next

Explain the exact mismatch and leave the checklist incomplete until corrected.

Inputs, checks and measurement
What starts the workflow
A practice checklist identifies missing statements, invoices or explanations.
Before taking action
Keep entity, period and document version attached to each item.
Measure the change
Chase minutes per client and incomplete packs reaching review.

One bank payment covers several invoices

Finished result

A reconciled item or a concise evidence-backed exception.

  1. 01Collect payment and invoice candidates
  2. 02Compare dates and references
  3. 03Apply approved match rules
  4. 04Prepare explanation or review
When something does not fit

The payment includes a credit note and a disputed deduction.

What happens next

Assemble the candidate explanation and request the accountant’s decision on the difference.

Inputs, checks and measurement
What starts the workflow
A reconciliation exception cannot be matched by amount alone.
Before taking action
Avoid duplicate allocation and keep currency, fees and partial settlement separate.
Measure the change
Investigation minutes and repeat unmatched items.

Period-end work is waiting between team members

Finished result

A close workflow whose status reflects actual outstanding work.

  1. 01Read close checklist
  2. 02Identify unresolved dependencies
  3. 03Assign review and query owners
  4. 04Confirm completion evidence
When something does not fit

A late source document changes a balance already reviewed.

What happens next

Reopen the affected review step and retain the reason and earlier version.

Inputs, checks and measurement
What starts the workflow
Preparation is finished but review, queries and adjustments have different owners.
Before taking action
Keep prepared, reviewed and finalised states distinct.
Measure the change
Review handoff time and work reopened after incomplete closure.
Fit before features

When custom work makes sense.

Use the ledger’s native rules for standard matching. Custom work is useful for cross-client document collection, unusual reconciliation evidence and ownership of recurring exceptions.

Connect the records you already use

  • Accounting ledgers and bank feeds
  • Client document portal and source records
  • Practice tasks and review approvals

Access, data quality and write permissions are checked during scoping. Integration availability depends on your systems.

Go deeper

The systems behind these scenarios.

Controls, responsibility and recovery

Agree who can change rules, approve exceptions and authorise each write. Keep a history of source records, rule versions and action results. Detect partial failures, reconcile before retrying and assign unresolved cases to a named owner.

AI can extract, classify and prepare information. Validated rules and agreed permissions govern consequential actions; missing evidence triggers review. Test normal cases, exceptions and recovery against acceptance criteria before launch.

Related operating experience

See the foundations running at G3.

G3 is our founder’s retail and venue business in Melbourne. Explore relevant capabilities and their boundaries; your industry’s rules still need their own design and validation.

Questions worth asking first.

Start with a sanitised example, the result you need and one awkward case. We will map a bounded first implementation.

Can matching rules replace an accountant’s judgement?

No. Approved deterministic matches can be completed within scope; uncertain treatment, adjustments and professional conclusions require the designated reviewer.

Can this work across different client accounting systems?

Potentially, after checking each integration and its permissions. The initial scope should define supported records and review boundaries for each system.

How would document chasing stay specific to each client and reporting period?

Build the request from the agreed entity, period and checklist rather than a generic missing-documents email. Match incoming files to that request and identify wrong periods, duplicates or incomplete statements. Confirm portal or mailbox access and communication permissions before enabling any client follow-up.

What happens when a late document changes work already reviewed?

Keep the source document linked to the affected reconciliation or period-end task. Flag which prepared or reviewed result may need reopening and assign it to the designated reviewer. Preserve the previous decision; a new attachment should not silently alter a finalised ledger or erase the review history.

Do we need an ongoing Canvo subscription?

No mandatory Canvo subscription. An agreed implementation includes 12 months of support for the delivered workflows, defects and minor compatibility changes to existing integrations. Optional proactive care and further development are scoped separately. Software, hosting and API costs remain separate.

Your operation, your rules

Bring the handoff that keeps going wrong.

Free workflow review. A$950 ex GST diagnostic. A bounded first deployment from A$4,900 ex GST, with 12 months of included support for the agreed implementation.

See pricing and support scope →