agentleFS
Sign inStart free
DexterslabAiDexterslabAi/resume-genie/skills/finance-transformation-cv/SKILL.md

finance-transformation-cv

Skill0 starsChanged 19 days agoMITView on GitHub

Specialist CV guidance for finance transformation, GBS and shared services, ERP (SAP S/4HANA, Oracle) and finance automation or AI roles. Covers P2P, O2C and R2R vocabulary, systems and modules, the transformation arc, finance KPIs, controls, and how to position programme work for product owner and AI roles. Use when tailoring or reviewing a CV for finance operations, finance transformation, GBS, ERP or AI-in-finance positions.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Process vocabulary: Use the exact terms, with acronym and full name once each:

    line 12
  2. Distinctive:

    Never relabel a programme role as a product role.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Finance transformation CV

Hiring managers in finance transformation scan for specific vocabulary, systems, scale and outcomes. Generic "led a transformation" bullets don't get shortlisted. This skill adds that domain lens, built from experience of finance transformation and GBS programmes. Read references/career-tracks.md (the finance transformation section) and references/cv-writing.md.

What to check and strengthen

  1. Process vocabulary. Use the exact terms, with acronym and full name once each:
    • P2P / procure-to-pay, O2C / order-to-cash, R2R / record-to-report
    • FP&A, month-end close, intercompany, treasury, tax
  2. Systems. Name them with modules, for example SAP S/4HANA (FI/CO, MM), Oracle Fusion, Workday Financials, Coupa, Ariba, BlackLine, OneStream, Power BI. "ERP experience" alone carries no weight.
  3. The transformation arc. Assessment → target operating model → business case → design → build/test → hypercare → benefits realised. Make clear which stages the candidate owned.
  4. Finance KPIs that land:
    • days to close
    • cost per invoice
    • touchless or straight-through rate
    • first-time-right
    • DPO / DSO
    • working capital released
    • FTE capacity freed
    • audit findings closed
    • SLA attainment
  5. Scale: countries, legal entities, invoices or transactions a month, programme budget, team or vendor size.
  6. Controls: SOX, internal controls, segregation of duties, audit readiness.
  7. AI and automation roles: separate the use case (invoice data extraction, exception triage, cash application matching) from the technology (IDP, RPA, ML, generative AI, agents). Show adoption and control, not just the build.
  8. Product owner and AI pivots: where it's true, translate programme work into product terms:
    • requirements backlog
    • prioritised releases
    • user acceptance as acceptance criteria
    • adoption KPIs
    • discovery with finance users

Rules

  • Numbers come from the candidate only. Otherwise use [placeholders].
  • Never relabel a programme role as a product role. Describe the product-style work that was really done.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free