Accounting Software Selection

What it is: The evidence behind a software purchase, recorded so the decision is arguable - and the decision itself still belongs to the business.

Overview

Works out the smallest useful Accounting Software Selection setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

For a Nepal trading, manufacturing or services business, this is the record that makes the purchase arguable: requirements ranked, a candidate shortlist, the same demo tests run against every candidate, the evidence behind every score, cost split so first-year and three-year totals can be compared, and the evaluation status, selection decision, rejection reason and deal-breaker flag kept as four separate fields instead of one opinion. It is an evaluation and decision-support tool, not a bookkeeping, tax-filing, legal or procurement system.

Four guardrails shape every row.

Nothing is invented, and nothing is asserted without a source. Never supply a vendor capability, a price, a compliance status, a demo result or a stakeholder score that the user or a named source did not give. What nobody has verified is Untested for a capability and an empty cost cell with Unknown in Notes for a price. A capability nobody has looked at is Untested; it is not 1 Missing, and a blank is never filled with a plausible number so the row looks finished.

This skill never selects. It may summarise the evidence, name the requirements a candidate fails, and state that a Must-have is failed. It must not declare a package the best option, announce a winner, state a compliance conclusion or record an approval. The business fills Selection Decision itself.