See what Claude can do on its own, what Airclerk's NZ Accounting Pack adds, and how approved connections turn selected drafts into controlled, reviewer-ready work inside the systems your practice already runs.
Claude is Anthropic's AI assistant. Airclerk is the New Zealand consultancy that implements it inside accounting practices.
Runs in your firm's own Claude environment, and nothing consequential happens without your reviewer.
Claude can read supplied documents, structure information, explain reports, identify issues and prepare drafts. On its own, the method is generic, the inputs are manual and it cannot safely act on a live client ledger.
The pack adds New Zealand sources, client and period discipline, materiality, reconciliations, result states and named reviewer gates. It turns one-off prompting into a repeatable practice method.
Connections let the configured method reach the records and actions it needs. For Xero, the Airclerk connection is built for a client list, requires an explicit organisation for every write, and can post an approved action with its supporting evidence attached.
The outcome is not more tools. It is more accounting work completed to the firm's review standard.
These are practical use cases supported by the pack and the firm's configured connections. They are not a one-to-one list of the pack's 25 skills. Start where the volume is high, the source material is available and the review is clear.
Lead schedules for each balance-sheet line, tied to the trial balance, with queries and reviewer notes prioritised.
Structures supplied trial-balance exports and supporting files into a first draft.
Client and period headers, materiality, source requirements, tie-out rules, exception severity and result states.
Pulls the named client's ledger detail and supporting Xero records without repeated exports.
Resolves judgement items, approves conclusions and signs the file.
Accruals, prepayments, depreciation and reclassifications drafted from the workpaper that calculated them.
Drafts journal logic from supplied schedules.
Account mapping, debit and credit checks, narration, reconciliation and approval requirements.
Posts the approved journal to the explicitly named Xero organisation with the supporting schedule attached.
Approves the accounting treatment and the write.
Unrecorded expenses identified, calculated and carried into a reviewable accrual schedule.
Reads invoices, contracts and prior-period schedules supplied in the conversation.
Cut-off tests, period logic, materiality, reversal treatment and ledger tie-out.
Checks the named ledger for existing entries and posts an approved journal where configured.
Decides uncertain obligations and approves the entry.
One invoice becomes a period-by-period schedule and an approved accounting entry without spreadsheet re-keying.
Extracts dates, amounts and coverage terms from a supplied document.
NZ date and GST treatment, monthly allocation, reconciliation and the reviewer gate.
Checks the original transaction and posts the approved journal with evidence attached.
Confirms the treatment and approves posting.
Potential assets hiding in repairs or additions are surfaced, checked against the fixed-asset register and prepared for review.
Reviews supplied transaction listings and invoices for capital indicators.
Capital-versus-repair tests, source citations, depreciation-method checks and register-to-ledger reconciliation.
Reads the named client's transactions and asset register and performs approved asset actions where configured.
Makes the capitalisation and tax-treatment decision.
Payday-filing, PAYE, KiwiSaver and ESCT totals are matched to the ledger with exceptions tabled.
Compares supplied payroll and general-ledger exports.
NZ payroll checks, current-source verification, reconciling-difference rules and exception severity.
Retrieves approved Payroll NZ and accounting data for the named organisation.
Resolves payroll exceptions and approves any consequential action.
The cases the ledger cannot decide are flagged before filing, including registration boundaries, adjustments, change of use and zero-rated land.
Organises supplied transactions and identifies unusual items.
Current NZ source checks, issue classification, evidence requirements and a clear result state.
Retrieves transaction-level detail for the named GST period.
Determines the tax position and files the return.
Instalment options, dates, use-of-money-interest exposure and a draft client explanation assembled in one schedule.
Explains supplied calculations and drafts the communication.
Balance-date logic, current IRD verification, option comparison and schedule controls.
Supplies relevant ledger results where approved; the planning workflow can also run from verified supplied figures.
Chooses the advice and communicates it to the client.
Vehicle, loan and unclassified-benefit workings laid out with evidence and alternatives for review.
Extracts information from supplied registers, policies and transactions.
Current-source verification, rate alternatives, evidence gaps and reviewer decision points.
Brings relevant named-client ledger transactions into the review where configured.
Selects and approves the treatment and the filing position.
Captured-activity checks, CDD level and beneficial-ownership information organised under the firm's existing programme.
Structures supplied documents and identifies missing information.
Engagement isolation, escalation points, evidence status and boundaries around compliance-officer decisions.
Approved practice-management or document connections can reduce manual collection; Xero is not required for the primary task.
The compliance officer makes the decisions and handles any suspicious-activity process.
Agency-list progress, missing information, 31 March risks and terminal-tax reminders consolidated into a practice view.
Organises supplied job lists and drafts questionnaires or reminders.
NZ deadline logic, client and period separation, severity, ownership and a controlled status model.
Approved practice-system data keeps status current; Xero context can support individual jobs.
Owns filing decisions, client escalation and final submission.
Correspondence classified by client, deadline and severity, with routine drafts prepared and material items escalated.
Summarises supplied letters and drafts a response.
Client isolation, deadline extraction, authority checks, severity and result states.
Uses only firm-approved correspondence feeds and practice systems; it does not operate myIR.
Approves every response and handles consequential matters.
One engagement query log becomes a single, firm-toned missing-information request instead of repeated emails.
Groups supplied questions and drafts a message.
Client and period controls, duplicate removal, priority, due dates and the firm's communication style.
Approved workpaper, document-store or practice-system connections keep the query list current.
Approves the request and sends it through the firm's normal channel.
Aged receivables, coding exceptions or trial-balance questions answered for one explicitly named client at a time.
Analyses supplied exports for a single entity.
Client and period declarations, ambiguity stops and source labelling.
Selects an unambiguous Xero organisation and retrieves live detail across the practice's approved client list.
Interprets the answer and approves any follow-on write.
Unusual, inconsistent or incomplete coding grouped into a concise review queue.
Finds patterns in a supplied transaction export.
Materiality, client context, evidence requests, prior-treatment comparison and result states.
Retrieves current transaction detail and performs approved corrections where configured.
Decides ambiguous coding and approves corrections.
Repeated workflows checked for missing sources, skipped gates, unresolved differences and incomplete outputs.
Reviews a supplied run or workpaper for obvious omissions.
A defined Workflow Charter, expected stages, named gates and completion criteria.
Approved system events provide evidence of what was read or written; not every monitored workflow requires Xero.
Owns exceptions, control design and remediation.
A substantive question answered at a stated depth, with every relied-on claim linked to a source that was actually opened.
Searches, reasons and drafts a memo.
Source hierarchy, authority status, historical-version checks, a contrary-authority pass and a declared result state.
Optional named-client ledger context can frame the question; no Xero connection is required for primary research.
Reviews the research, decides the position and provides any advice.
One provision, determination, ruling or guidance item checked for status and relevance before someone relies on it.
Finds and summarises candidate material.
Opened-source evidence, in-force dates, binding-status classification and historical-version discipline.
Not required unless client facts need verified ledger context.
Determines whether and how the authority applies.
Agreements, correspondence and supporting records organised into facts, missing evidence and issues before a conclusion is formed.
Extracts and compares the supplied documents.
Confidentiality boundaries, fact and source separation, unresolved-question handling and a no-premature-conclusion rule.
Approved document and ledger connections can confirm bounded facts without placing client details into public search queries.
Forms and approves the tax conclusion.
An existing memo or letter checked claim by claim against official sources, with weaknesses and contrary material surfaced.
Critiques a supplied draft and suggests improvements.
A claim inventory, authority-status checks, source verification, contrary-authority testing and correction without silently rewriting the author's position.
Not required unless the review depends on verified client-ledger facts.
Owns the final position, the wording and the client communication.
An insurance invoice and its coverage period.
The period allocation, reconciled and ready to check.
Source, assumptions and calculation trail retained.
The Airclerk connection holds the write until an authorised reviewer approves.
Posted to Xero through the Airclerk connection, with the supporting evidence attached.
Claude did not replace the reviewer. It removed the exporting, re-keying and blank-page work around the review.
Every output names its client and period. An ambiguous organisation stops the workflow rather than being guessed.
Outputs identify the evidence they used. A schedule either ties to the ledger or states its reconciling difference.
Consequential outputs and writes stop for the responsible reviewer. Approval is an explicit workflow stage, not a habit.
The source, the calculation, the reviewer's decision and the resulting action remain readable afterwards as an AI Workpaper.
Everything runs in the firm's own Claude instance, under the firm's agreement with Anthropic. Client records reach it through connections the firm approves and scopes. The Airclerk connection for Xero runs on the firm's own hardware, where its credentials and refresh tokens remain. Nothing routes through Airclerk.
Xero's own connector in Claude answers summary questions about one connected organisation.
The Airclerk connection runs accounting workflows across the practice's client list.
312 published Xero API operations: 235 Accounting, 6 Assets and 71 Payroll NZ. Every operation Xero publishes for those three APIs.
Xero's connector is useful for summary questions about one connected organisation. Public practice also needs transaction-level records, fixed assets, New Zealand payroll, selection of one client from the whole list, and controlled writes after review.
Counts checked 15 August 2026. The Airclerk connection covers the published Xero Accounting, Assets and Payroll NZ API surface; covering the published specification is not a claim that every operation has been exercised in every live-client scenario. Airclerk is independent, and is not affiliated with or endorsed by Xero or Anthropic.
The implementation is built around year-end workpaper preparation; most of the other skills in the pack feed that file or follow it.
Adapt the accounting skills to the firm's templates, client mix, reviewers and risk settings.
Scope the approved systems, then test the workflow on held-out client jobs, including wrong-client and prompt-injection cases.
Launch with a Workflow Charter, reviewer gates, a retained AI Workpaper, and reviews at 30, 60 and 90 days.
A 20-minute workflow session qualifies the fit: your systems, your client base, your balance-date load. A six-week implementation then builds around year-end workpaper preparation, with the reviewer gates tested before anyone relies on them. Fixed fee, quoted after the session.
Claude is an AI assistant made by Anthropic. Airclerk implements governed workflows that use Claude inside a firm's own environment. Airclerk is not another AI model or chat portal.
No. The connection is one part of an implementation. The outcome is repeatable, reviewer-ready accounting work: the pack supplies the method, and connections let selected workflows reach the systems they require.
No. The implementation runs in the firm's own Claude environment. The Airclerk connection for Xero runs on the firm's hardware, and the firm's Xero credentials and refresh tokens remain there. Connections are approved and scoped by the firm.
Every write through the Airclerk connection must name the Xero organisation it lands in. If a client name matches more than one organisation, the write is refused and the candidates are returned rather than guessed. Consequential writes also remain behind human approval.
No. Outputs are drafts for the firm's own accountants to review, and the reviewing practitioner remains responsible for the file, the position and the client relationship. Airclerk is not a CA firm or tax agent, does not file with Inland Revenue and does not operate myIR.
No. Research, document review and some practice operations run without it. The connection matters where a workflow needs live ledger, fixed-asset or Payroll NZ data, or an approved accounting action.
The pack is an accelerator, not a finished off-the-shelf product. Each implementation adapts it to the firm's templates, systems, client base, reviewers and risk settings.
You bring one recurring job. We map what Claude can do now, what method and controls it needs, which systems it must reach and where human review remains. The session ends with a view on whether it is a sensible first production workflow.
Bring one recurring job. In 20 minutes we will map the work, the systems it touches and the approval that stays with your team.
A working session, not a generic AI demo.
Book a 20-minute practice workflow session
www.airclerk.ai/accounting/claude-workflow-map
or email hello@airclerk.ai
Pick a time that suits, and bring one recurring job.