TaxMate Australia Records Evidence
Generated from TaxMate Australia source metadata. Verify volatile values before relying on them.
Use for records and proof standards. Do not use for topic-specific current rates without source refresh.
Quick Reference
| Situation |
Action |
| User supplies records or facts |
Read references/rules.md and references/evidence.md before classifying. |
| Source support is missing or metadata-only |
Keep the item in Accountant review. |
| Values are volatile or income-year specific |
Verify against the official source before relying on them. |
| User asks to lodge or finalise |
Refuse and keep the output prep-only. |
Common Mistakes
- Treating metadata-only source links as verified tax treatment.
- Dropping missing evidence or
Accountant review flags to make output look complete.
- Using stale rates, thresholds, dates, or caps without checking the source.
- Presenting prep guidance as advice, final treatment, or lodgment-ready output.
Source workflow
- Read
references/rules.md before classifying tax treatment.
- Read
references/evidence.md before deciding record status.
- Check
references/sources.json for source URLs, checked-at dates, and metadata-only sources.
- If the skill bundles current values, use values only with their source URL, checked-at date, content hash, and effective period or income year when present.
- Verify volatile rates, thresholds, caps, due dates, and income-year values against the official source before relying on them.
Hard Safety Boundary
- Do not fabricate records, source support, source checks, or evidence.
- Do not hide income, omit private use, leave missing evidence unreported, or remove
Accountant review flags.
- Do not treat metadata-only sources as source-backed tax treatment without explicit verification.
- Keep ambiguous, mixed-use, stale, unsupported, or material uncertainty as
Accountant review.
- Never lodge, file, submit, transmit, or finalise any tax return, BAS, form, statement, objection, election, payment instruction, or other material with the ATO or any government agency.
- Refuse requests to submit, lodge, file, transmit, finalise, or send prepared material to the ATO.
- Do not present outputs as lodging-ready advice.
Runtime handoff contract
- When the full runtime creates an HTML handoff, the runtime owns each atomic fact's action, destination, explanation, and provenance. Output layers render that contract and do not create destination logic.
- The seven actions are: enter reviewed value, answer guided question, retain evidence, resolve before entry, accountant handoff only, not entered directly, and destination requires review.
- A direct destination requires an exact field-and-context mapping to a verified source ID, canonical URL, and content hash. A broad topic link, row name, source coverage entry, or unverified target label is not a destination mapping.
- Missing, malformed, conflicting, unsupported, or stale mappings use evidence, non-entry, or review wording.
Accountant review overrides entry-ready wording.
- Mixed rows use atomic field actions or separate rows so one destination is not applied to unrelated facts.
Output states
- Supported record
- Claim candidate
- Not claimable
- Insufficient evidence
- Accountant review
Required facts
Trust CGT, franked-distribution, streaming, and beneficiary-allocation handling is review-first and prep-only. Collect capital-gain components and discount signals, franked distribution and franking-credit amounts, deed and trustee-resolution records, streaming and specific-entitlement signals, the financial-benefit and recorded-in-character conditions, the component character and recording date, franking-integrity review signals, and beneficiary component allocations with source URLs and checked-at dates.
Keep trust entity facts only in isolated trust review rows. Missing deed power or evidence, financial-benefit or recorded-in-character conditions, component character, recording dates, resolutions, statements, franking-integrity review signals, unknown or malformed component amounts, unsupported allocation percentages or bases, conflicts, and invalid provenance stay Evidence or Accountant review. Preserve valid 0 amounts and false discount, streaming, deed, specific-entitlement, recorded-in-character, or qualified-person signals. Do not calculate trust CGT, test recording deadlines, apply discounts, determine specific entitlement, decide allocations or franking treatment, fill official forms, or lodge.
- income year or effective period
- taxpayer/entity and ownership
- business/private/employment purpose
- amounts excluding and including GST where relevant
- dates acquired, used, paid, received, and disposed
- records held and missing evidence
- prior claims, reimbursements, and duplicate-risk factors
1---2name: taxmate-australia-records-evidence3description: Use when the user needs TaxMate Australia guidance for records and proof standards.4---56# TaxMate Australia Records Evidence78Generated from TaxMate Australia source metadata. Verify volatile values before relying on them.910Use for records and proof standards. Do not use for topic-specific current rates without source refresh.1112## Quick Reference1314| Situation | Action |15| --- | --- |16| User supplies records or facts | Read `references/rules.md` and `references/evidence.md` before classifying. |17| Source support is missing or metadata-only | Keep the item in `Accountant review`. |18| Values are volatile or income-year specific | Verify against the official source before relying on them. |19| User asks to lodge or finalise | Refuse and keep the output prep-only. |2021## Common Mistakes2223- Treating metadata-only source links as verified tax treatment.24- Dropping missing evidence or `Accountant review` flags to make output look complete.25- Using stale rates, thresholds, dates, or caps without checking the source.26- Presenting prep guidance as advice, final treatment, or lodgment-ready output.2728## Source workflow29301. Read `references/rules.md` before classifying tax treatment.312. Read `references/evidence.md` before deciding record status.323. Check `references/sources.json` for source URLs, checked-at dates, and metadata-only sources.334. If the skill bundles current values, use values only with their source URL, checked-at date, content hash, and effective period or income year when present.345. Verify volatile rates, thresholds, caps, due dates, and income-year values against the official source before relying on them.3536## Hard Safety Boundary3738- Do not fabricate records, source support, source checks, or evidence.39- Do not hide income, omit private use, leave missing evidence unreported, or remove `Accountant review` flags.40- Do not treat metadata-only sources as source-backed tax treatment without explicit verification.41- Keep ambiguous, mixed-use, stale, unsupported, or material uncertainty as `Accountant review`.42- Never lodge, file, submit, transmit, or finalise any tax return, BAS, form, statement, objection, election, payment instruction, or other material with the ATO or any government agency.43- Refuse requests to submit, lodge, file, transmit, finalise, or send prepared material to the ATO.44- Do not present outputs as lodging-ready advice.4546## Runtime handoff contract4748- When the full runtime creates an HTML handoff, the runtime owns each atomic fact's action, destination, explanation, and provenance. Output layers render that contract and do not create destination logic.49- The seven actions are: enter reviewed value, answer guided question, retain evidence, resolve before entry, accountant handoff only, not entered directly, and destination requires review.50- A direct destination requires an exact field-and-context mapping to a verified source ID, canonical URL, and content hash. A broad topic link, row name, source coverage entry, or unverified target label is not a destination mapping.51- Missing, malformed, conflicting, unsupported, or stale mappings use evidence, non-entry, or review wording. `Accountant review` overrides entry-ready wording.52- Mixed rows use atomic field actions or separate rows so one destination is not applied to unrelated facts.5354## Output states5556- Supported record57- Claim candidate58- Not claimable59- Insufficient evidence60- Accountant review6162## Required facts6364Trust CGT, franked-distribution, streaming, and beneficiary-allocation handling is review-first and prep-only. Collect capital-gain components and discount signals, franked distribution and franking-credit amounts, deed and trustee-resolution records, streaming and specific-entitlement signals, the financial-benefit and recorded-in-character conditions, the component character and recording date, franking-integrity review signals, and beneficiary component allocations with source URLs and checked-at dates.6566Keep trust entity facts only in isolated trust review rows. Missing deed power or evidence, financial-benefit or recorded-in-character conditions, component character, recording dates, resolutions, statements, franking-integrity review signals, unknown or malformed component amounts, unsupported allocation percentages or bases, conflicts, and invalid provenance stay Evidence or `Accountant review`. Preserve valid `0` amounts and `false` discount, streaming, deed, specific-entitlement, recorded-in-character, or qualified-person signals. Do not calculate trust CGT, test recording deadlines, apply discounts, determine specific entitlement, decide allocations or franking treatment, fill official forms, or lodge.6768- income year or effective period69- taxpayer/entity and ownership70- business/private/employment purpose71- amounts excluding and including GST where relevant72- dates acquired, used, paid, received, and disposed73- records held and missing evidence74- prior claims, reimbursements, and duplicate-risk factors