Station 10 of 10
Certification, portfolio, first job in ERPNext
What you leave this station with
A portfolio of nine outputs you built yourself, an informed decision about the certification, and a first outreach plan you can run in a week.
Nine stations produced a skill. This one converts it into something other people can see — because the market does not hire what it cannot see.
The official certification, as published
The certification is run through Frappe School, and its published detail as read on 6 September 2026:
| Item | Detail |
|---|---|
| Tracks | Two: ERPNext and the Frappe Framework |
| Fee | $200, or ₹15,000 |
| Format | A one-to-one live assessment interview over Google Meet |
| Duration | 45 to 60 minutes |
| Extra condition | A project must be submitted before a slot can be booked on the framework track |
Stop at the format row, because it is unusual. These are not multiple-choice questions whose answers can be memorised; it is a conversation with a person who asks, then follows your answer with another question. The implication is entirely practical: there is no shortcut. Someone who executed the nine stations finds themselves describing what they did; someone who only read is exposed in the fifth minute.
Which is in fact the best news at this station, because a certification whose answers cannot be memorised keeps its value in the market.
Which track? Return to the decision made at station one: the functional track first, and the framework track for a developer. Choosing the framework track while writing no code wastes two hundred dollars.
Verify every figure above yourself before paying. Prices and conditions change, and what is written here is a reading on a stated date rather than a promise.
The portfolio, which is stronger than the certification
Every station closed on a sentence repeated deliberately: “that is a portfolio piece.” Collect them now:
| Output | Where it came from |
|---|---|
| The eight-week plan and how far you executed it | Station one |
| A built training environment and the list of what you broke in it on purpose | Station two |
| A complete company with disciplined master data | Station three |
| The sheet tracing purchase documents through both ledgers | Station four |
| A full sales cycle with its entries read | Station five |
| The costing-method comparison table on your own figures | Station six |
| An executed close checklist and three saved reports | Station seven |
| The seven-question e-invoicing page for your country | Station eight |
| The table of three customisation requests placed on the ladder | Station nine |
Nine outputs, every one of them your own work, and not one of them an attendance certificate.
That is the difference the person interviewing you decides on: a candidate who says “I know ERPNext”, and a candidate who opens the document-trace sheet and explains why the supplier is not credited at receipt. The second one is hired; the first one is thanked.
What to write on your CV, exactly
Write what you did, not what you know:
- “Ran a full purchase cycle from material request to payment and read every document’s entry in both ledgers” — not “familiar with the purchasing module”.
- “Closed a month against an eight-item checklist ending in a period freeze” — not “accounting experience”.
- “Measured the margin difference between FIFO and moving average on identical movements” — not “knowledge of costing methods”.
The difference between the two phrasings is not cosmetic. The first is testable in the interview; the second is an open question you will be asked and will not answer.
Three routes into a first job
Implementation partners. The developing company does not itself deliver implementation services, and the work runs through a partner network of more than two hundred firms worldwide. The structure itself manufactures demand for independent implementers — the clearest market advantage this product specifically has, detailed in the ERPNext guide.
Companies running it. A small or mid-sized business operating the system and needing somebody who understands it from the inside. Entry here is usually under a title like accountant or inventory specialist who knows the system, and it is the fastest door for anyone with an accounting background.
Freelance work. It starts small — setting up a company, cleaning data, building reports — and it is the best route to a visible track record. Its one condition: do not take a whole project before you have run one alongside somebody more experienced than you.
And the rule that saves you a year: do not wait until you are ready. Readiness is built on the second project; the first is necessarily entered incomplete.
The first step, today
A simple outreach plan you can run inside a week:
- Publish one output — the costing table or the close checklist — with a written explanation of what you learned from it.
- Write to five implementation partners with a short message stating what you executed and attaching a single output, not a general CV.
- Answer three questions in the user forums in detail. A generic answer is forgotten; an answer explaining why the system behaves as it does is remembered.
- Book the assessment slot if you decided on the certification, because a booked date does to study what an intention never does.
Where to go after this path
Three directions, all starting here:
Functional depth — manufacturing, projects, maintenance and human resources, all of which assume what you mastered in the first six stations.
Technical depth — the framework track, and building separate apps with the discipline set out at station nine.
Evaluation and selection — becoming the person who decides which system a company buys, rather than only the person who implements it. The route runs through the systems comparison, and through reading each product at its limits rather than off its brochure — a skill no amount of training on a single product will teach.
The sum: ten stations executed, nine outputs produced, and you now know what this system does not do as well as what it does. The second is what makes you a consultant rather than a user.