A network engineer walks into an ACS application holding a CCNA, an AZ-104, and eight years of hands-on infrastructure work, and assumes the certificates are the strong part of the file. For most applications they are the weakest. The certifications accepted for ACS skills assessment support your case; they seldom carry it, and several of the most popular certs do not count in the way their holders expect.
The reason is structural. ACS runs two separate mechanisms for vendor certifications, and which one applies to you is decided before anyone reads your certificate: it depends on the ANZSCO occupation code you nominate. Get that mapping wrong and even a stack of professional-level certs adds nothing to your result.
How Vendor Certifications Fit Into ACS Skills Assessment
The first mechanism is professional currency evidence. Under the Recognition of Prior Learning (RPL) pathway, ACS's route for applicants who have substantial ICT experience but no formally assessed ICT qualification, any legitimate IT vendor certification can be submitted to show your knowledge is current. ACS names CCNA directly as an example of a cert accepted this way, and this channel is open to every RPL application regardless of occupation. The catch is what it does: professional currency evidence supports a submission, never replaces the substantive evidence, and on its own it decides nothing.
The second mechanism is the formal accepted vendor certification list. This is a short, specific register that applies only to DevOps and Cyber Security ANZSCO codes. If you nominate DevOps Engineer or a cyber security code, a handful of named certs can be submitted as formal vendor certification evidence. Nominate anything else and that list is irrelevant to you.
Most guides blur these two into a single "certs are accepted" claim. They are not the same thing. One more point worth flagging: vendor certs are not exclusive to RPL. For DevOps and Cyber Security codes, ACS also permits optional vendor certification evidence under the General Skills pathway, so the formal list is tied to those occupations, not to a single pathway. For how the routes differ, see our pathways comparison and pathways explained.
The AQF Diploma ICT Standard That Certifications Must Meet
ACS's current test is alignment to current knowledge in the nominated occupation and its ANZSCO code. That is the operative language on the ACS InfoHub today, and the shift matters.
Older ACS guidance, a 2020 guidelines document still echoed on migration forums, framed specific certs as comparable to AQF Diploma level ICT, mapping competency to four areas: technical problem-solving, technical implementation, communication of technical concepts, and work in a team and project context. You will still see MCSE, MCSD, and CCNP cited against that AQF Diploma benchmark in community threads. Treat it as historical. The current InfoHub does not use AQF Diploma equivalency as the vendor-cert test, and building your submission around superseded language is a self-inflicted weakness.
What survives from the old framing is the underlying logic: tier and scope decide weight, not the vendor's name. A professional-tier cert that covers design and operations across a broad domain evidences more occupation knowledge than a foundational cert that covers awareness only. The AWS logo on the badge does not raise the value. The exam's depth, and how far it overlaps with your nominated occupation, is the whole question.
Which Certifications Carry RPL Weight, Vendor by Vendor
The table below maps all four vendors across both mechanisms. The pattern is not what most cert-holders expect.
Vendor | Formal Accepted List | Professional Currency Evidence |
|---|---|---|
AWS | DevOps Engineer Professional only (DevOps codes) | SAA-C03, SAP-C02, SOA-C02, all non-DevOps codes |
Cisco | None | CCNA 200-301, CCNP (track-specific), networking/infrastructure codes |
Microsoft | DevOps Engineer Expert only (DevOps codes) | AZ-104 Azure Administrator, AZ-900 (limited weight) |
CompTIA | Security+, CySA+, PenTest+, SecurityX (cyber security codes) | Network+, limited; A+, entry-level support only |
AWS Certifications: Solutions Architect and SysOps Administrator
Only AWS Certified DevOps Engineer Professional sits on the ACS formal accepted list, and only for DevOps codes. The certs most AWS professionals actually hold, Solutions Architect Associate (SAA-C03), Solutions Architect Professional (SAP-C02), and SysOps Administrator Associate (SOA-C02), are not on that list. Under a non-DevOps code, they enter as professional currency evidence only, which is where these associate and professional tiers become your strongest realistic RPL candidates.
They still help. SAP-C02 in particular evidences architecture-level knowledge that reads well for a systems or cloud occupation. But these certs need pairing with matching work experience. They will not clear a submission by themselves.
Cisco Certifications: CCNA and CCNP
No Cisco certification appears on the ACS formal accepted list, not CCNA, not CCNP, not CCIE. ACS cites CCNA (200-301) only as an example of professional currency evidence, and track-specific CCNP variants sit in the same category. For a networking occupation such as Computer Network and Systems Engineer or Network Administrator, a CCNP is genuinely useful currency evidence that maps cleanly to the occupation's knowledge areas. Its formal standing is currency evidence, nothing more. Do not present a Cisco cert as if it were on an approved register. ACS does not maintain one that includes it.
Microsoft Certifications: Foundational vs Role-Based Tiers
Microsoft mirrors AWS. Only Microsoft DevOps Engineer Expert is on the formal list, for DevOps codes. AZ-104 Azure Administrator, the strongest single Azure operations cert most administrators hold, is not formally accepted for any code; it enters as professional currency evidence. The gap between tiers is real. AZ-900 Azure Fundamentals certifies conceptual awareness and adds little beyond confirming basic literacy, while AZ-104 certifies operational administration and reads as substantive currency when it sits on top of real experience. Foundational certs establish that you are current. Role-based certs establish what you can actually do.
CompTIA Certifications: Security+, Network+, and A+
CompTIA has the widest formal presence of the four, and it is entirely inside Cyber Security. Security+ (SY0-701), CySA+, PenTest+, and SecurityX (formerly CASP+) are all on the formal accepted list for cyber security codes. Network+ and A+ are not. A+ certifies entry-level support competency and falls short for any ANZSCO code above first-line ICT support; presenting it for a software engineering or network engineering occupation asks it to carry weight it was never built to hold.
Based on each vendor's published exam domains compared with ACS's occupation-knowledge criteria, the mapping is consistent: professional and expert-tier certs whose blueprints span design, implementation, and operations align with graduate-level occupation knowledge, while associate and foundational tiers evidence currency but rarely reach occupation-depth alone. That is this site's analysis of public exam blueprints, not a claim about how any individual file was assessed.
What a Complete RPL Submission Includes Alongside Certifications
A certificate is a data point. ACS assesses a case.
The substantive evidence in an RPL application is the two RPL project reports and your employment history, not your badges. Start with a competency mapping statement: a short written mapping that ties each certification to the specific occupation-knowledge areas it evidences, in your own words, against your nominated ANZSCO code. It converts a transcript into an argument the assessor can follow. This is the single highest-value document a cert-holder can add.
Behind the certs sits the experience requirement. The RPL pathway is built for applicants with substantial relevant ICT experience (check current ACS guidance for the exact threshold), documented through your employment history and project reports. The two-year recency rule that people often pin to work history actually governs professional currency evidence: certifications and CPD must have been completed within the last two years to still count as current. A cert confirms currency; the documented experience confirms competence. Both must be present.
The document mechanics trip people who never read the certificate itself closely. Each vendor certification you submit must display the issuing authority, the validation or certificate number (or a digital badge link ACS can verify), your full name matching the application, the issuance date, the expiry date, and proof of renewal where the cert has one. Miss a field and the cert can be set aside before its content is ever weighed.
For the complete evidence set, work from our ACS RPL document checklist rather than assembling it from memory.
On cost and timing: the RPL application fee is $625 excluding GST as of July 2026, per the ACS.org.au fee schedule. ACS does not publish a fixed turnaround on its RPL pathway page. Third-party migration consultancies commonly cite eight to twelve weeks, so treat that as indicative only and confirm the current timeframe directly with ACS before you plan around it.
Three Patterns That Get Certification-Heavy RPL Applications Rejected
Certification-led submissions tend to fail the same three ways. For the full catalogue, see our RPL rejection reasons self-audit guide; what follows covers the cert-specific ones.
The most common, by a distance: submitting a certification transcript as standalone competency evidence with no written mapping to ACS occupation outcomes. A PDF of your badge tells the assessor you passed an exam. It does not tell them which occupation-knowledge areas that exam covers, or how they connect to your nominated code. That inference is your job. Leaving it undone is the number-one rejection cause for cert-supported files.
The second pattern: a certification in a domain that does not match the nominated ANZSCO code. Submit a Cisco CCNA as evidence for Developer Programmer, and an assessor sees a networking credential offered for a software development occupation. The knowledge domains barely overlap; the mismatch is obvious on the first read, and it registers as either a misread of the occupation or padding. Align the cert to the code, or leave it out.
The third: relying on an expired or superseded certification with no renewal trail. Currency evidence that has lapsed is, by definition, not current. An expired cert without proof of renewal or equivalent continuing professional development carries reduced weight, and for a credential whose entire job was to show current knowledge, reduced weight can round down to none.
FAQs About Certifications and ACS Skills Assessment
Can I Use an Expired Vendor Certification as RPL Evidence?
Yes, but with reduced weight, and only if you show it stayed current. An expired certification submitted as professional currency evidence works against its own purpose unless you attach proof of renewal or equivalent continuing professional development. Without a renewal trail, an expired cert may add nothing. Submit the current version, or pair the lapsed one with recent CPD evidence.
Does ACS Distinguish AWS Associate from Professional Certs?
In practice, yes, through depth rather than a published tier rule. Neither SAA-C03 (associate) nor SAP-C02 (professional) is on the formal accepted list, so both enter as professional currency evidence under a non-DevOps code. The professional tier evidences broader design and operations knowledge and reads as stronger currency, but both still need matching work experience to count for anything.
Do I Document All My Certifications or Just the Highest?
Document each one that aligns with your nominated ANZSCO code. There is no rule requiring you to submit only your highest cert. Two certs covering different, relevant knowledge domains build a wider evidence base than one. The test is relevance to the occupation, not seniority of the badge, so drop any cert whose domain does not match your code.
Can CompTIA A+ Support an ACS Assessment for a Software Engineering ANZSCO Code?
Effectively no. A+ certifies entry-level hardware and support competency, which sits below the knowledge expected for a software engineering occupation and does not appear on any formal accepted list. It might surface as minor currency evidence, but it cannot carry a software engineering submission and will not offset a thin experience record. Lead with development-relevant evidence instead.
Is a Vendor Certification Enough on Its Own for ACS RPL?
No. No certification, on either mechanism, replaces the RPL pathway's substantive requirements: substantial relevant ICT experience (check current ACS guidance) and the two RPL project reports. Certs are supporting evidence. They strengthen a case built on documented experience; they cannot be the case.
Certifications shift an ACS result at the margin, and only when they are mapped to the right occupation and backed by the experience underneath them. Before you submit, work through the full ACS RPL document checklist to confirm exactly what evidence belongs alongside your certifications.