Your systems analyst ANZSCO 261112 ACS skills assessment turns less on how many years you have worked than on whether your documented tasks match the occupation ACS is actually assessing. Two applicants with near-identical résumés routinely get opposite outcomes: one writes about analysing and redesigning existing systems, the other writes about building and testing software, and only the first reads as a systems analyst to the reviewer. This guide walks you through pathway selection, evidence, and submission the way an assessor reads them, using current ACS policy and the ANZSCO 261112 definition rather than the generic migration copy that fills the search results.
What ANZSCO 261112 means for your ACS assessment and visa
ANZSCO is the occupation classification the Australian Bureau of Statistics maintains. ACS uses your nominated code to decide which task descriptors your work has to match. For 261112, the 2021 ABS classification is specific: a Systems Analyst "evaluates processes and methods used in existing ICT systems, proposes modifications, additional system components or new systems to meet user needs." Read that twice before you write anything. The centre of gravity is evaluation of what already exists and the proposal of change, not construction from scratch.
The core systems analyst tasks ACS maps to 261112
ACS reads your employment evidence against the ANZSCO task set for the role. Five descriptors carry the most weight for 261112:
requirements analysis, working out what a system has to do for the business
feasibility studies that weigh options before a build commits budget
systems design, translating those requirements into a workable architecture
preparing detailed technical specifications for developers to implement
coordinating and overseeing system testing against the specification
Notice what is missing. Writing the code, running the test scripts yourself, or managing the delivery schedule are developer and project-manager activities. They can appear in your history, but they cannot be the substance of what you claim.
Which skilled migration visas require a 261112 assessment
A positive ACS result is the gate, not the visa. ANZSCO 261112 sits on the Medium and Long-term Strategic Skills List, which keeps three General Skilled Migration options open: the subclass 189 Skilled Independent visa, the subclass 190 Skilled Nominated visa, and the subclass 491 Skilled Work Regional (Provisional) visa. Ignore any page still listing the 489 or 457; both closed years ago.
The 189 needs no nomination. The 190 and 491 require a state or territory to nominate you, which adds its own criteria and, in some states, its own waiting time.
Choosing the right ACS pathway for your systems analyst background
Every systems analyst ANZSCO 261112 ACS skills assessment runs down one of two pathways, and the choice is made for you by how ACS grades your qualification, not by preference. ACS reviews your degree first and rates its ICT content as Major, Minor, or Insufficient. That single categorisation decides your route.
ICT Major pathway: when your degree carries the application
When ACS rates your bachelor's degree or higher as holding a Major in ICT closely related to 261112, you use the General Skills pathway, which is ACS's name for the degree-based route. You still need relevant employment, but the volume is lower: roughly two to six years depending on how closely your qualification matches and its level, at a minimum of 20 hours a week. The closer the match, the less experience ACS deducts before your skilled date.
RPL pathway: when your experience has to do the work
No degree, a sub-bachelor qualification, or a degree ACS rates as Insufficient in ICT means the Recognition of Prior Learning pathway, where your experience carries the claim. It is heavier. ACS requires at least six years of relevant work, with your most recent experience current or within the last two years, again at 20 hours a week minimum, plus two written project reports covered in Step 3.
How to decide when your background sits between the pathways
A Minor rating is the trap. A computer science degree loaded with mathematics, electronics, or management electives can land a Minor rather than a Major, because ACS counts ICT credit points the way a customs officer weighs the contents of the box, not the label on it. A Minor generally routes you through additional experience requirements rather than the direct Major pathway.
Before you assume the degree route, map your transcript unit by unit. For a full side-by-side, see our ACS pathways comparison and the pathways explained guide.
Step 1: Confirm your work history maps to ANZSCO 261112
Your systems analyst ANZSCO 261112 ACS skills assessment succeeds or fails on one question: does the work map to the code? A reviewer spends far less time on your file than you spent assembling it, so the mapping has to be obvious on the page. The ACS assessment is underpinned by SFIA, the Skills Framework for the Information Age, which is the competency vocabulary the reviewer uses to test whether your described work belongs to 261112. In practice, that means writing your evidence in terms of analytical skills, requirements definition, systems design, and methods, rather than tool lists or ticket counts.
How ACS separates 261112 from BA and developer roles
This is where most 261112 files wobble. The neighbouring code, ANZSCO 261111 ICT Business Analyst, is defined as someone who "identifies and communicates with users to formulate and produce a requirements specification to create system and software solutions." Put the two definitions side by side and the distinction runs in one direction.
The business analyst works upstream, eliciting needs from users and producing the requirement. The systems analyst works downstream of that, evaluating how existing systems behave and proposing the modifications or new components that meet the need. If your evidence is all stakeholder workshops and requirement documents, ACS may read you as a 261111. If it is all coding and unit tests, you read as a developer. ANZSCO 261112 lives in the analytical middle: assess the current system, then design the change.
Task alignment checklist before you write a single document
Before drafting anything, run each claimed year against a short test. Does that year show at least one of the five 261112 descriptors? Does the work involve an existing system you evaluated, not just software you helped build? Can you name the modification or new component you proposed and why?
If a year fails all three questions, do not pad it into the claim. It weakens the file rather than strengthening it.
Step 2: Assemble your qualification and employment evidence
What ACS checks in your transcripts and degree certificate
ACS wants the award certificate and the full academic transcript listing every subject and result. The Major or Minor rating is calculated from those units, not from the degree title. Provide clear colour scans of the original documents, and a certified translation where the originals are not in English. A transcript that omits subjects or grades is the fastest way to stall at the qualification review.
Employment evidence ACS accepts for each year you claim
For every period you claim, ACS expects a signed employment reference on company letterhead stating your title, dates, hours, and duties, backed by proof that the role and pay were real: payslips, tax records, or bank statements covering the period.
Where you cannot get a letter from an employer, whether the role was self-employment, an agency contract, or a company that no longer exists, a statutory declaration from a colleague or client who can attest to your work, sworn before an authorised witness, is ACS's accepted substitute. Contract and freelance work counts the same as permanent work, provided the duties map to 261112 and you can evidence the hours.
Step 3: Write two RPL project reports for your 261112 assessment
ACS requires exactly two project reports, not three episodes. The Recognition of Prior Learning pathway sets a recency rule on them as well.
What a passing systems analyst RPL project report contains
Each report narrates one project or period in your own voice and demonstrates the 261112 competencies in action: the problem in the existing system, the analysis you ran, the design or modification you proposed, and how the outcome was validated. Write in the first person, name the technologies and your specific decisions, and keep the emphasis on your analytical reasoning rather than the team's delivery.
ACS does not publish a fixed word count for these reports, so ignore the "800 to 1000 words" figure that circulates on service sites. Write enough to evidence the competency and no more.
The recency split: one report within 2 years, one within 4
The two reports are not interchangeable. ACS requires one project completed within the last two years and one within the last four years. A systems analyst who has drifted into management recently needs a fresh hands-on project to satisfy the two-year window, which is a constraint worth planning around months before you apply.
Own work only, and the plagiarism check
Both reports must be exclusively your own work. ACS runs submissions through similarity-checking software that compares them with previously published material, which is exactly why the service sites selling ready-made reports are a liability: a report that trips the similarity check sinks the application. Run your own plagiarism scan before you submit.
Three submission mistakes that cause 261112 rejections
1. Describing development or testing work. The single most common 261112 rejection is a file that documents software development, coding, or QA testing rather than systems analysis. If a reviewer finishes your report thinking "developer," the code is wrong.
2. Reusing a job description. Copying duties from a CV or position description instead of narrating what you personally analysed and decided reads as generic and unverifiable.
3. Mismatched dates. Report periods that do not line up with the employment letters and payslips invite scrutiny you do not want. Our RPL rejection self-audit guide breaks down each failure mode.
Step 4: Submit your ACS skills assessment and pay the 2026 fee
Current ACS assessment fees for 261112 applicants
ACS updated its fees on 3 November 2025. The RPL pathway assessment fee is AUD $625. The degree-based General Skills pathway costs AUD $1,498. That gap is real money, and it is another reason to confirm your qualification rating before you commit. For the current schedule and any change since publication, check our ACS fee 2026 guide or the ACS fee page directly.
Standard versus priority processing: the actual timelines
A complete ACS application with no follow-up requests is assessed in about four to six weeks. Priority processing exists, but it does not work the way the service pages imply. ACS applies priority automatically when you have a visa deadline under 12 weeks from your application date, and you need to give at least two weeks' notice. No additional fee is listed for it. For live queue estimates, see our processing time tracker.
How to read your ACS outcome for ANZSCO 261112
What a positive letter confirms and when it expires
A positive assessment states that your skills and qualifications meet the requirement for 261112 and gives you a skilled employment date, the point from which ACS counts your qualifying experience. Watch the validity closely. ACS's InfoHub states that suitable outcomes are valid for two years, not the three years repeated across competitor service pages.
That two-year window works like a passport with a short expiry: useless the day after it lapses, no matter what it cost you. If your assessment expires before you receive a visa invitation or lodge, you cannot use it for nomination and must reassess. Time the application to your expected invitation, not years ahead.
What a negative outcome says and your options
A negative or "unsuitable" result usually points to the mismatch this guide keeps returning to: experience that reads as development or project management, a qualification rated Insufficient, or evidence gaps. You can request a review, supply further evidence, or reapply on the correct pathway once the record supports it. Fix the mapping before you resubmit, because a second file with the same problem gets the same answer.
Full cost and timeline from ACS submission to visa grant
The table below sets out the whole pathway from public inputs so you can budget realistically. The ACS fee is the fixed input; the two larger variables must be confirmed at their official sources because they change and depend on your circumstances.
Stage | Cost input | Where to confirm |
|---|---|---|
ACS skills assessment | AUD $625 (RPL) or $1,498 (General Skills) | ACS fee schedule, effective 3 Nov 2025 |
English test | varies by provider (IELTS, PTE, OET) | your test provider |
State nomination (190 / 491 only) | varies by state; several charge nothing for the nomination itself | your nominating state or territory |
Visa application charge (189 / 190 / 491) | the single largest line item; confirm the current primary-applicant charge | Department of Home Affairs |
On the calendar, the ACS assessment runs the standard window covered in Step 4. After that, you lodge an Expression of Interest in SkillSelect. From there, the wait to an invitation depends on your points score and the occupation's demand, and visa processing follows the invitation.
Because the ACS outcome is valid for only two years, sequence the assessment so it is still live when an invitation is realistic, not the day you first think about migrating.
Questions systems analyst applicants ask before submitting
Can I use a business analyst or project manager role as evidence for 261112?
Only for the parts that are genuinely systems analysis. ACS assesses the tasks you performed, not the title on the contract. A business analyst role that involved evaluating existing systems and designing modifications can support a 261112 claim, but the pure requirement-gathering portions read as 261111 and the delivery-management portions do not count at all. Document the analytical work explicitly.
My degree is in computer science but not closely matched. Do I qualify for the ICT Major pathway?
It depends on how ACS rates the degree's ICT content, not its name. ACS grades ICT credit as Major, Minor, or Insufficient by counting relevant units. A computer science degree heavy on non-ICT electives can receive a Minor, which changes your experience requirement and may push you toward RPL. Map your transcript before assuming the degree route.
How many RPL reports does ACS require, and how long should each be?
ACS requires two project reports: one project completed within the last two years and one within the last four. ACS does not publish a set word count, so write each report long enough to demonstrate the 261112 competencies and no longer. Both must be your own work and pass ACS's similarity check.
Does ACS assess contract and freelance roles the same as permanent employment?
Yes, provided you can evidence them. The duties still have to map to 261112 and meet the 20-hour-a-week minimum. Where you have no employer letter, a statutory declaration from a client or colleague, sworn before an authorised witness, together with payment records, is ACS's accepted proof for self-employed and contract work.
If I worked as a systems analyst under a different job title, can I still claim 261112?
Yes. ACS classifies by the work performed, not the job title. Someone titled "IT Consultant," "Solutions Analyst," or "Application Specialist" who evaluated existing systems and designed modifications can claim 261112, as long as the employment reference and reports describe those tasks in the occupation's terms.
Before you submit, run through the ACS Skills Assessment document checklist to confirm every file is correctly named, formatted, and dated. A single missing or mislabelled document is the most common cause of delay for 261112 applicants, and it is entirely avoidable.