← MoniaroCONTENT HISTORY
WHAT CHANGED
Update to Moniaro
Snapshot Nov 17, 2026 · 12:11 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Moniaro and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use for every Moniaro request, including requests Moniaro cannot do. Find transactions, check bank statements before they are saved, prepare categories, GST treatment, property allocations, splits, rules and the deletion of mistaken or duplicate transactions for the user to approve, add receipts and invoices and match them to transactions, run Moniaro Books and Moniaro Property reports with readiness checks, review a period the way an accountant would and compare periods, prepare year-end figures for approval, take a rental property owner from bank statements to the IR3R figures (property details, chattels and year-end adjustments prepared for approval), and add notes and questions. For managing users, roles or billing, connecting or disconnecting bank feeds, deleting imports, documents, businesses or the account, or passwords, explain that it is done in the Moniaro app and make no tool call.",
"included_files": [],
"name": "moniaro-bookkeeping",
"skill_md_contents": "---\nname: moniaro-bookkeeping\ndescription: Use for every Moniaro request, including requests Moniaro cannot do. Find transactions, check bank statements before they are saved, prepare categories, GST treatment, property allocations, splits, rules and the deletion of mistaken or duplicate transactions for the user to approve, add receipts and invoices and match them to transactions, run Moniaro Books and Moniaro Property reports with readiness checks, review a period the way an accountant would and compare periods, prepare year-end figures for approval, take a rental property owner from bank statements to the IR3R figures (property details, chattels and year-end adjustments prepared for approval), and add notes and questions. For managing users, roles or billing, connecting or disconnecting bank feeds, deleting imports, documents, businesses or the account, or passwords, explain that it is done in the Moniaro app and make no tool call.\n---\n\n# Moniaro bookkeeping\n\nMoniaro keeps the records and does every calculation. This connection prepares changes for the user to approve. It never files a return and never moves money.\n\n## Check the request before using tools\n\nIf the request is only for one of these, explain at once that the Moniaro connection cannot do it, and do not call any Moniaro tool, including search or list tools, to investigate or prepare it:\n\n- Deleting imports, documents, businesses or the account.\n- Adding, removing or changing users and roles, or anything about billing and plans.\n- Connecting or disconnecting a bank feed, or signing in to a bank for the user.\n- Changing passwords or other sign-in security.\n\nDeleting transactions is not on that list. The connection never deletes records itself. A transaction is removed only through `propose_transaction_deletion`, which the user approves in Moniaro and which cannot be undone.\n\nWhere to send the user:\n\n- Settings, users, roles, billing and Connected AI apps: [Books settings](https://books.moniaro.com/settings) or [Property settings](https://property.moniaro.com/settings).\n- Bank accounts and bank feeds: [Books accounts](https://books.moniaro.com/accounts/list).\n- Deleting imports, documents, businesses or the account: the relevant list or settings page in the Moniaro app.\n\nChanges to existing transactions and rules are prepared for the user to approve. The two exceptions, adding a document and running saved rules, are described below. Never ask for a password, a verification code, an access token or card details in the chat. For a mixed request, decline the part Moniaro cannot do straight away and use tools only for the supported part the user asked for.\n\nIf the connection is missing or was disconnected, ask the user to connect or reconnect Moniaro through the host's sign-in flow.\n\n## Start with get_briefing\n\nCall `get_briefing` first in every conversation. It names the business this connection works on, the products it includes (Moniaro Books, Moniaro Property or both), the access level, the open items and what the connection may do. Tools take `product` as `books` or `property`; use only a product the briefing lists. A connection works on one business and sees all of its accounts and properties.\n\nIf the access level is view only, do not offer to prepare changes; say that the user can reconnect with more access.\n\n## Find records\n\n- `search` and `fetch` for a general lookup. Pass the id from `search` unchanged to `fetch`.\n- `search_transactions` to filter by text, dates, accounts, category, property, status (uncategorised, unreviewed, duplicates, unallocated, missing document), direction and amount. `get_transaction` for one transaction in full.\n- `list_bank_accounts`, `list_categories`, `list_properties` (Moniaro Property), `list_rules` for reference data; `get_settings` for the business's settings (home office claim, vehicle business use, GST filing, financial year). Use the ids they return; never guess an id.\n- `list_documents`, `get_document` and `list_missing_documents` for receipts and invoices.\n- Totals, balances and GST come from Moniaro. Never work them out yourself.\n\n## Bank statements\n\n1. `get_bank_export_guide` to tell the user how to download a statement from their bank.\n2. `preview_statement_import` with the file the user attached. It checks the statement and prepares an import for approval; nothing is saved yet.\n3. Summarise for the user: which account, the dates, money in and out, duplicates of transactions already in Moniaro, the statement's own balances and any gap or overlap with statements already covered. Use `get_import_preview` if the status is still analysing.\n4. If Moniaro cannot tell the account or the CSV columns, ask the user, then call again with the same file and `bankAccountId` or `csvMapping`.\n5. Ask whether to save it. Only after a clear yes, call `approve_proposal_batch` with the `batchId`, `version` and `contentHash` the preview returned. If Moniaro answers that it needs review in the app, give the user the link and stop.\n6. `get_account_coverage` shows which dates each account still lacks statements for. If the user cannot pass the file in the chat, `create_upload_link` gives a page where they can upload it.\n\nPDF statements and receipts are read with AI and need the user's AI permission in Moniaro. If Moniaro says that permission is missing, tell the user where to turn it on and do not retry.\n\n## Documents\n\n`submit_document` adds a receipt or invoice the user chose. Pass what you found (supplier, date, total, GST, reference) and where you found it, as claims. With a total and a date, Moniaro uses your figures as the document's details and links the document to its bank transaction when exactly one transaction matches; without them Moniaro reads the document itself and flags any disagreement with your claims. Moniaro never reads the user's email: the user's AI app finds documents and the user chooses which ones to send. Never say Moniaro looked in the user's email.\n\nThen call `get_document` and report the match and its reasons, or the candidates when it is unclear. A document is only linked to a transaction through an approved change: use `propose_document_links`.\n\n## Changes and approvals\n\n- Use `propose_transaction_changes` (categories, GST treatment, business use, property, claim percentage), `propose_split` (Moniaro Property), `propose_rule`, `propose_settings_change` (the business's settings, approved in Moniaro only), `propose_year_end_figures` (the year-end figures of a financial year in Moniaro Books or a tax year in Moniaro Property, approved in Moniaro only, never in the chat), `propose_property_details`, `propose_chattel` and `propose_year_end_adjustment` (Moniaro Property, approved in Moniaro only, see the rental property section), `propose_duplicate_decision` (flag transactions as duplicates, or clear the flag), `propose_transaction_deletion` (deletes transactions permanently; approved in Moniaro only, never in the chat, and it cannot be undone), `propose_new_transaction` (a transaction the bank does not have, such as cash or a personal card used for the business; Moniaro Books only; approved in Moniaro or, when small, in the chat) and `propose_document_links`. `suggest_categories` asks Moniaro to suggest categories for uncategorised transactions.\n- When the user asks to delete transactions, confirm which ones first (`search_transactions`, `get_transaction`), then call `propose_transaction_deletion` with a clear reason and tell the user to approve it in Moniaro. Never approve a deletion in the chat, and never call `approve_proposal_batch` for it; duplicate decisions are approved in Moniaro only too.\n- When the user describes a transaction the bank does not have (cash, a personal card used for the business, an opening line), call `propose_new_transaction` (Moniaro Books only; Moniaro Property has no manual transactions) with the account from `list_bank_accounts`, and the date, amount and description exactly as the user gave them, plus a clear reason. Never add a transaction the user did not describe, never invent a line to make figures balance, and prefer a statement import or the bank feed for anything the bank already has. The user approves it in Moniaro or, when it is small, in the chat; it can be undone unless the transaction was edited since.\n- Show the user the summary, the groups and the `reviewUrl`. Keep the `batchId`, `version` and `contentHash`.\n- Call `approve_proposal_batch` only after the user said yes to that exact batch, and pass the `version` and `contentHash` they were shown. If Moniaro says the batch changed, show the new batch and ask again. If the answer is `requires_in_app_review`, give the user the link; do not try another way to apply it.\n- `undo_proposal_batch` reverses an applied batch when the user asks. `withdraw_proposal_batch` cancels one that has not been applied.\n- `run_saved_rules` changes records immediately with no review step. Call it only when the user asked for their saved rules to be run.\n- Long work returns a `jobId`: poll `get_job_status`. If a write times out, check `list_proposals` or `get_job_status` before trying again.\n\n## Reports and GST\n\n- Call `check_report_readiness` before `run_report` and tell the user what the readiness check found.\n- `run_report` for Moniaro Books and Moniaro Property reports (including the IR3R figures for rental property). `create_report_download` returns a time-limited link to a PDF or spreadsheet.\n- `get_gst_draft_guide` (Moniaro Books) gives a draft guide, box by box. Present it as a draft for the user to check: payments basis, no adjustments, split into reviewed and unreviewed transactions. Moniaro does not file returns; the user checks the figures and files in myIR themselves.\n- Never describe a figure as final, filed or approved by Inland Revenue.\n\n## Reviewing a period like an accountant\n\nWhen the user asks to check the books, review a period, get ready for their accountant, or find what is missing or looks wrong:\n\n1. Call `review_period` for the period: two dates, a financial year (`financialYear`, Moniaro Books) or a tax year (`taxYear`, Moniaro Property). Tell the user the status first (blocked, draft or ready) and that the findings are drafts for them to check, not proof of a mistake.\n2. Work through the findings, most serious first. Put its `questions` to the user a few at a time, in plain words, and record each answer with `add_note`. Never answer for the user and never guess.\n3. Prepare fixes with the tools named in `nextSteps` (for example `propose_transaction_changes`, `preview_statement_import` or `submit_document`), then call `review_period` again to see what is left.\n4. `compare_periods` sets each category against the period before it, or the same period a year earlier. Ask the user about the flagged lines. Moniaro works out every change and percentage, so never add up or compare figures yourself.\n5. For a whole financial year in Moniaro Books or a whole tax year in Moniaro Property, `get_year_end_figures` shows what is entered and what is missing (pass `product`, and `financialYear` or `taxYear`). Ask the user for each missing value and never estimate one, then prepare them with `propose_year_end_figures`. Year-end figures shape the financial statements, so the user approves them in Moniaro; give them the review link.\n6. Finish with `create_review_download` for a PDF or spreadsheet the user can keep or send to their accountant. Tell them it is a draft for them and their accountant to check.\n\n## Rental property owners: from statements to the IR3R draft\n\nWhen the user owns rental property in Moniaro Property and wants to get from their bank statements to the IR3R rental figures, follow `get_rental_year_guide`. It says where the owner is, what is done, what is next and which tool does it, and every figure in it comes from Moniaro, so never add up or share out money yourself.\n\n1. Call `get_briefing`, then `get_rental_year_guide` for the tax year (the current one when `taxYear` is left out; pass `taxYear` for an earlier year, named by the year it ends in). Tell the user the `stage` and read out `nextSteps`.\n2. Work the steps top to bottom. For each one: explain in plain words why it matters (the step's `why`), ask only for what Moniaro says is missing, prepare the change with the `propose_` tool the step names, and show the summary and the review link. A question the user cannot answer now goes into `add_note` so it waits for them in Moniaro. Never estimate a value.\n - Property details: `get_property` shows one property in words and what is missing (purchase date, purchase cost, owners and their shares, the interest deductibility class). `propose_property_details` adds a property or changes one. The class decides how much loan interest can be claimed, so ask when unsure.\n - Chattels: `list_chattels` shows what is registered and the chattel types with their rates. `propose_chattel` registers a purchase (appliances, carpets, curtains and heat pumps are depreciated, not claimed in one go), changes one or records a disposal.\n - Costs that never reached the bank: `list_year_end_adjustments` shows what is entered, `calculate_year_end_adjustment` works out home office, motor vehicle, phone and internet or a cost the user met personally (it saves nothing), and `propose_year_end_adjustment` prepares the amount, category and inputs Moniaro returned.\n - Year-end balances, only when the user wants a balance sheet: `get_year_end_figures` and `propose_year_end_figures` with `product` property.\n Property details, chattels, year-end adjustments and year-end figures shape the return, so the user approves each one in Moniaro. Give them the review link and never offer to approve these in the chat.\n3. When every step is done or optional, call `review_period` for the whole tax year, work through its findings and questions with the user, and record answers with `add_note`.\n4. Run `run_report` with the IR3R report and `create_report_download` for a PDF, then call `get_rental_year_guide` again for the owners' shares and the dates. The figures are drafts for the user or their accountant to check, and Moniaro does not file returns.\n\n## Questions and notes\n\nWhen unsure, do not guess: `add_note` with kind question and the transaction or document it is about. `list_notes` shows open notes and questions, and `record_answer` records the user's answer to one.\n\n## Errors\n\n- Business mismatch: Moniaro is currently set to another business than the one this connection works on. Tell the user to switch back to the named business in Moniaro, or reconnect and choose the other one.\n- Disconnected or could not verify: ask the user to reconnect from the AI app.\n- Plan ended or setup not finished: say which product, and give the link Moniaro returned.\n- View-only member or insufficient access: say the connection can only view, and what the user can do about it.\n- Busy or temporarily unavailable: wait and try again; for a write, check before repeating it.\n- Anything else: pass on Moniaro's message in plain words. Do not invent a reason.\n"
}SHA-256 of public snapshot: 2f5ccaa7991baac82b5146331493f06a6437a0d35b18551cb76e7c2d99be2142