“Proficient in Excel” is the least informative phrase in British recruitment. Software skills are among the easiest competences to evidence properly, because the software itself produces artefacts, yet most candidates still offer adjectives. This record shows how to do better, using the accounting stack of Sage, Excel and Xero as worked examples.
Why adjectives fail for software
Software claims fail because the words are unanchored: one candidate’s “advanced” is another’s “opened it twice”. Employers know this, which is why software claims are among the first things tested in practical interviews. The credible alternative is to anchor every claim to one of three things: an artefact the reader can open, an assessment someone else scored, or a demonstration you can perform on request. A claim with an anchor is evidence; a claim without one is hope.
Artefacts: let the software testify
Every serious tool produces inspectable output. In Excel, a workbook with named ranges, documented formulas, data validation and a pivot-based summary demonstrates more in ninety seconds of scrutiny than any bullet point. In Sage 50, a practice company’s reconciled bank, posted journals and month-end reports show the workflow was actually run. In Xero, a clean practice organisation with bank rules, reconciled statements and a management report pack does the same. Build these artefacts on synthetic data, label them as practice, date them, and file them in your portfolio with the provenance line described elsewhere in this publication. The point is not beauty; it is that a competent reviewer can open the file and see technique.
Assessed courses: borrow a scorer’s credibility
Self-directed learning becomes evidence when someone else assesses it. A software course that ends in a timed, invigilated assessment with a published pass mark gives you a scored, dated, third-party record, which is a different evidential class from a completion certificate. When citing such a course, state the assessment method and standard plainly, name the provider, and keep the certificate and any unit breakdown in your qualification file. Where the provider holds recognised accreditation, cite it precisely and checkably. If a course was unassessed, it still belongs in your CPD log as learning activity, honestly labelled; the discipline of describing each credential as exactly what it is runs through every record in this publication, and careers guidance from the National Careers Service similarly encourages matching claimed skills to demonstrable training and experience.
Version and feature honesty
Software moves, and feature-level honesty is part of credibility. Name the version or plan you used where it matters, because workflows differ between them, and an interviewer who asks about a feature your version lacked will expose a vague claim instantly. Better, name the features you actually command: in Excel, lookups, pivot tables, validation, conditional aggregation; in Sage or Xero, the modules you ran end to end. Feature-level claims are small, numerous and individually checkable, which is exactly the texture sceptical readers trust, and exactly what generic proficiency statements lack.
Demonstration: the interview endgame
Practical tests are now common for software-heavy roles, and the candidates who thrive treat the test as their best moment rather than a threat. Prepare by rehearsing your own artefacts: rebuild the reconciliation, rebuild the pivot summary, aloud, explaining decisions as you go, because narration under mild pressure is the skill the interview actually measures. If no test is offered, volunteer the artefact: “I can walk you through a workbook that shows this” converts an interview claim into a demonstration on the spot, and interviewers rarely decline.
The practice-company method
The single most productive habit for building software evidence from a standing start is the practice company: a complete, synthetic business that lives inside your tools. Invent a small firm, give it a chart of accounts, a bank account, suppliers, customers and a monthly rhythm, then run it. Post its invoices, reconcile its bank, produce its month-end pack, build its Excel summary. A practice company converts passive learning into produced work at a rate no tutorial matches, because every feature you learn immediately has somewhere real to land. It also compounds: after three months you do not have three exercises, you have a business with history, and history is what makes reports, comparisons and corrections meaningful. Label everything synthetic, date your month-ends, and the practice company becomes a self-refreshing portfolio that answers the Monday-morning question by demonstration.
Free tools, trials and staying legal
Build evidence only on software you are licensed to use. Vendors provide legitimate low-cost routes: time-limited trials, education editions and free tiers all produce artefacts that are exactly as persuasive as ones made on a full licence. State plainly which edition your artefact was built on when versions differ materially. What you must not do is build your evidence on cracked or shared licences, because the artefact then documents a compliance problem alongside the skill, and employers in regulated sectors notice exactly this kind of detail.
Keeping software evidence current
Software evidence ages faster than any other kind, so wire it into your maintenance habits. Each quarter, refresh one artefact using the current version of the tool, log the refresh in your CPD record, and re-verify any vendor badges you display. A dated trail of current artefacts answers the employer’s real question, which is never “did you once learn this software” but “can you sit down on Monday and use it”. Anchored artefacts, third-party assessment, feature honesty and rehearsed demonstration answer that question before it is asked, which is what credible evidence is for. Run the quarterly refresh alongside the CPD log and portfolio review described in the companion records, and the three habits reinforce one another: the refresh generates the log entry, the log entry points at the artefact, and the artefact keeps the portfolio current. One connected system, maintained in minutes a week, is worth more at interview than any list of software names, however long, because it can be opened, checked and questioned, and it holds.