What recruiters look for first
A recruiter screening for a FICO role checks four things in the first half page: which side you cover (FI, CO or both), which release you know (ECC, S/4HANA on premise, RISE), whether you have delivered full implementations or mainly support, and which industries you have worked in. If those answers are buried on page three, the CV often goes no further.
Put them in a short profile at the top. Name the sub-areas you know well, such as general ledger, accounts payable and receivable, asset accounting, bank accounting, cost centre accounting, internal orders, product costing or profitability analysis. Be specific; "end-to-end FICO" tells a recruiter nothing.
Going deeper: RISE with SAP public and private cloud compared, by Noel D’Costa on noeldcosta.com.
What the hiring manager looks for next
The technical interviewer reads your project section to decide what to ask. They look for scope (company codes, countries, currencies, ledgers), the phases you owned, and evidence of judgement: a design decision, a problem you solved, a close you made faster.
Finance consultants are trusted with the numbers. A CV that shows you understand the accounting, not only the configuration, stands out: period-end close, reconciliations, audit requirements and how your work changed what the finance team could report.
How to describe each project
For each project, give the reader five facts in two or three lines: the type of organisation and industry, the scope (company codes, countries, ledgers or users), the phase you joined and left, what you personally owned, and what was different afterwards. Keep the client name if you are allowed to use it; otherwise describe the organisation, for example "a regional retail group with operations in three countries".
Recruiters and applicant tracking systems search for the words in the job description. Use the exact module and sub-area names, such as "asset accounting" or "product costing", in your profile and project lines, but only where they are true. A keyword without evidence behind it gets you an interview you cannot pass.
Weak lines and strong lines
The same experience can read as a task list or as evidence. These examples are illustrative, written for this guide, and not taken from anyone’s CV. Use them as a pattern for your own facts.
Weak: Configured FI module as per client requirement.
Stronger: Designed and configured general ledger, AP and asset accounting for four company codes in two countries, including parallel ledgers for local and group reporting.
Names the sub-areas, the scale and a design element an interviewer can ask about.
Weak: Responsible for month-end closing activities.
Stronger: Supported the monthly close for a shared service centre, automating GR/IR regrouping and foreign currency valuation so the close moved from day 7 to day 5.
Shows what you did and what changed. Only state a result you can explain in an interview.
Weak: Worked on S/4HANA migration.
Stronger: Led finance data migration for a brownfield S/4HANA conversion: GL balances, open items and fixed assets, with three mock loads reconciled and signed off by the controller.
States the migration type, your objects and how you proved the data was right.
Weak: Good knowledge of CO.
Stronger: Built cost centre hierarchies and assessment cycles for allocating shared service costs to six business units, and settled internal orders for capital projects.
Turns a claim into evidence of what you configured and why.
Common mistakes
- Listing transaction codes instead of describing what you achieved with them.
- One long list of every FICO sub-area, with no sign of where you are strongest.
- No dates, no release and no scale for each project.
- Claiming implementation experience when your role was support, which unravels in the first technical question.
- Leaving out the accounting background or certification that finance hiring managers value.
A structure that works
In this order
- Profile: FI, CO or both; release; implementation or support; industries
- Core skills grouped by sub-area, strongest first
- Projects, newest first: client type, scope, phase, your role, outcome
- Accounting background, certifications and education
- Notice period, location and work authorisation where relevant
If you are starting out
If you are starting out, you cannot show project scope yet, so show the foundations. Lead with your accounting education or finance experience, then your SAP training, certification and any system you have used as an end user.
Describe what you configured in training in plain terms, such as setting up a company code, a chart of accounts and a payment run, and say which release you practised on. Do not present training exercises as client projects; interviewers can tell, and it costs trust.
Next: SAP FICO interview questions and SAP and ERP salary in the UAE.
Only include what you can substantiate. Employers check experience, and every line on your CV may come up in an interview.