Prompt Library

You are a senior indirect tax advisor at a European multinational. I need a formal VAT advisory memo on the following transaction:

Supplier: [Entity A, Country A, VAT reg: XX]
Customer: [Entity B, Country B, VAT reg: YY — or "not VAT registered"]
Supply type: [goods / services / digital services / intangibles]
Delivery/performance: [describe how and where]
Contract value: [EUR amount]

Analyse: (1) place of supply determination under Articles 31–59 of the EU VAT Directive 2006/112/EC, (2) applicable VAT rate or exemption with directive article reference, (3) reverse charge applicability and self-assessment obligations, (4) invoicing requirements including mandatory fields, (5) documentation we must retain. If the treatment differs depending on customer status (B2B vs B2C), address both branches. Flag any ECJ case law relevant to this transaction type.

Output as a formal advisory memo with: Executive Summary, Analysis (structured by the five points above), Conclusion, and a Limitations / caveats paragraph.

You are a VAT compliance specialist. Review the following invoice data and produce a structured risk assessment:

[Paste invoice details — supplier name, address, VAT number, customer details, invoice date, description of goods/services, net amount, VAT rate applied, VAT amount, total, any reference numbers]

For each line item or field, assess compliance against: (1) mandatory invoice fields under Article 226 of Directive 2006/112/EC and local implementing rules for [country], (2) correct VAT rate or exemption applied, (3) reverse charge notation if required (Article 194/196), (4) VAT number format validity per VIES, (5) input VAT recovery eligibility for our business.

Output as a risk matrix with columns: Field / Issue | Compliance Status (✓ / ⚠ / ✗) | Risk Level (High/Med/Low) | Finding | Corrective Action Required | Deadline.

Include a summary row count of compliant / at-risk / non-compliant fields and an overall recovery risk verdict.

You are a VAT partner-level advisor. Draft a formal advisory note justifying the VAT treatment applied to the following transaction:

Transaction: [describe in detail — nature of supply, parties, contractual terms, payment structure]
Treatment applied: [zero-rated export / exempt under Article 132 / reverse charge / OSS scheme]
Jurisdiction: [country and applicable legislation]

The note must: (1) identify the precise legal basis (EU directive article + national implementing provision + statutory instrument number), (2) apply and distinguish the most relevant ECJ cases [list any you know of — or ask AI to identify them], (3) address any conditions that must be satisfied and confirm they are met, (4) identify any documentation that must be in place before the supply is made, (5) set out what would happen if the conditions are not met (retrospective standard-rating, penalties, interest).

Tone: suitable for submission to tax authorities if challenged. Length: approximately 1,500 words. End with a one-paragraph executive summary suitable for a non-tax reader.

You are a European indirect tax specialist. Create a detailed comparison of input VAT recovery rules for the following expense categories across France, Germany, Netherlands, Belgium, and United Kingdom (post-Brexit):

Expense categories: (1) Business entertainment and hospitality, (2) Company cars — purchase, (3) Company cars — fuel, (4) Hotel accommodation, (5) Meals during business travel, (6) Mobile phones and subscriptions, (7) Subsistence allowances, (8) Marketing and promotional gifts, (9) Professional advisory fees, (10) Employee training.

For each combination of country × expense category provide: (a) recovery percentage allowed, (b) key conditions, (c) documentation required, (d) any de minimis thresholds, (e) common pitfalls. Flag any recent changes (post-2022).

Output as a formatted table with countries as column headers and expense types as row headers. Include a footnotes section explaining material restrictions and a separate "Action Points" section listing anything we should immediately review in our AP coding.

You are a VAT specialist with expertise in complex supply characterisation. Analyse whether the following arrangement constitutes a single composite supply, multiple independent supplies, or an ancillary supply under EU VAT law:

Arrangement: [describe the bundle — e.g., Canon sells a multifunction printer + installation + three-year maintenance + consumables subscription + remote monitoring service, all on a single contract at a bundled price]

Apply the following framework: (1) Card Protection Plan (CPP) test — what is the economic reality from the typical customer's perspective? (2) Levob test — are elements so closely linked that splitting would be artificial? (3) Loyalty Management Group / Astra Zeneca — does the consideration structure change the analysis? (4) If single supply, identify the principal element and analyse whether any ancillary elements inherit its VAT treatment.

Output as a decision tree that can be reused for similar bundled arrangements. Each branch point should state: Question → Yes path → No path → Conclusion. Append a worked example applying the tree to the specific arrangement described above. End with a recommended VAT treatment and confidence level (High/Medium/Low).

You are a VAT structuring specialist. Map the VAT obligations for the following proposed supply chain change:

Current structure: [describe current transaction flow — entities, countries, goods/service movements, title transfer points, invoicing flows]
Proposed structure: [describe proposed changes]
Entities involved: [list each Canon entity with country and VAT registration status]

For each transaction leg in the proposed structure: (1) identify the supplier and customer, (2) determine place of supply, (3) confirm VAT registration requirements in each country, (4) specify the applicable VAT treatment (standard-rated, zero-rated, exempt, reverse charge, not subject to VAT), (5) identify invoice requirements, (6) flag any chain transaction / triangulation simplification applicability, (7) identify any new VAT registration obligations triggered.

Output as a flowchart using ASCII/text notation showing each entity as a box, each transaction leg as an arrow labelled with the VAT treatment. Below the flowchart, provide a transaction summary table and a "New Obligations Triggered" section listing registrations, filings, or procedural changes required before the new structure goes live.

You are a VAT group structuring advisor. Evaluate whether [Entity X] should be added to our existing VAT group in [country].

Current group members: [list entities with turnover and partial exemption status]
Proposed new member: [Entity X — turnover, business activities, VAT-exempt income percentage, intercompany supplies with existing members, non-business activities]
Jurisdiction rules: [country]-specific VAT grouping legislation.

Analyse across six dimensions: (1) Cash flow — modelling the VAT cash flow impact of grouping intercompany supplies (show calculation assumptions), (2) Partial exemption — will addition of Entity X improve or worsen the overall recovery percentage? Show pro-forma calculation, (3) Administrative burden — consolidated returns vs current separate filings, (4) Joint and several liability — extent of exposure from Entity X's historic liabilities, (5) Exit complexity — what would it take to remove Entity X later? (6) Regulatory risk — is the grouping arrangement robust under the Skandia / Larentia ECJ case line?

Output as a weighted scoring matrix (define weights) with a final recommendation of Add / Do Not Add / Add with conditions. Attach assumptions and key risks.

You are a VAT fixed establishment specialist. Assess whether [Entity / Non-EU principal] has a fixed establishment (FE) in [Country] for VAT purposes based on the following facts:

Facts: [describe — number of staff on site, their roles and authority, premises (owned/leased/shared), equipment, duration of presence, contractual arrangements with the local entity, invoicing and contracting entity, CIT permanent establishment position]

Apply the following analytical framework: (1) DFDS Torline test — is there a sufficient degree of permanence and a suitable structure in terms of human and technical resources? (2) Welmory — does the FE receive or make supplies? (3) Dong Yang Electronics — should we look through a subsidiary structure? (4) Berlin Chemie — is the resource available to the entity "as its own"? (5) Titanium — does mere property ownership constitute an FE?

For each test: state the question, apply the facts, reach a conclusion, and assign a risk rating (High / Medium / Low / Negligible). Provide an overall FE risk verdict. Recommend: (a) any immediate structural changes to reduce FE risk, (b) documentation we should put in place, (c) whether an advance ruling should be sought. Flag any country-specific divergence from the ECJ position.

You are a senior VAT advisor preparing for a formal meeting with [country] tax authority regarding [specific VAT position or audit query].

Background: [describe the issue — e.g., authority is challenging our zero-rating of services to non-EU customers; they issued an information notice on [date]; our filing position is X; their draft assessment is EUR Y]

Prepare a meeting pack structured as follows:
Slide 1 — Meeting objective and our desired outcome
Slide 2 — Timeline of events (chronological, factual)
Slide 3 — Our legal position: primary legislation → directive → ECJ case law
Slide 4 — Key evidence and documentation we will present
Slide 5 — Where we agree with the authority's analysis
Slide 6 — Where we disagree and why (specific rebuttal of each authority argument)
Slide 7 — Proposed resolution options (ranked by preference)
Slide 8 — Fallback positions and acceptable compromises
Slide 9 — Next steps and timeline

For each slide provide: headline (one sentence), 4–6 bullet points with substance, any supporting data points. Flag where we have weak points that the authority may press on and suggest pre-emptive responses.

You are a VAT technical lead. Build a reusable decision tree for determining the correct VAT treatment of [supply type — e.g., software licensing / installation services / lease of equipment / financial services with ancillary supplies] across our key markets: Netherlands, Germany, France, Belgium, UK, and UAE.

The tree must branch on: (1) Nature of customer — taxable person vs private individual, (2) Customer location — same country / EU / non-EU, (3) Use by customer — business vs private, (4) Whether supply is of goods or services (and if services, which category), (5) Whether reverse charge applies, (6) Whether any simplification measure (OSS, triangulation, call-off stock) is available.

For each terminal branch state: VAT treatment, invoice requirement, reporting obligation (which return box / EC Sales List / Intrastat), and rate. Where the answer differs by country, produce a country-specific column.

Format the decision tree in numbered outline form (1 → 1.1 → 1.1.1 etc.) followed by a summary table. Include a "Common Errors" section listing the three most frequent misclassifications for this supply type and their financial consequence.

You are a VAT regulatory intelligence specialist. Research and compile all material indirect tax legislative and regulatory changes effective in [quarter/year] for the following jurisdictions: Netherlands, Germany, France, Belgium, Italy, Poland, Spain, Portugal, UAE, and UK.

For each change identified: (1) describe the change in plain language, (2) cite the specific legislation or directive (with article numbers), (3) state the effective date, (4) categorise as: Rate change / Exemption change / New reporting obligation / E-invoicing mandate / Penalty change / Procedure change / Other, (5) assess impact on Canon operations as: Action Required / Monitor / Informational, (6) identify the internal owner who should act.

Output as a table sorted by jurisdiction then effective date. Include a separate "Urgent Action" summary at the top listing any items where the effective date is within 90 days. For items marked "Action Required," append a one-paragraph implementation note explaining what specifically needs to change in our processes or systems.

You are a VAT litigator and ECJ case law specialist. Analyse the following ECJ ruling and produce a structured impact assessment for Canon's European operations:

Case: [C-XXX/XX — paste the case name and a brief description of the facts, or ask AI to retrieve it]

Your analysis must cover: (1) Summary of facts — 150 words max, (2) Question(s) referred to the ECJ, (3) ECJ's ruling and reasoning — key passages and legal principles established, (4) How this changes or confirms the prior legal position, (5) Which of our current VAT treatments are potentially affected — be specific (name the supply type, the entities, the approximate annual value), (6) For each affected area: risk level, financial exposure estimate, and recommended response, (7) Whether other member states are likely to implement this ruling differently and what that means for our EU filings, (8) Whether a proactive change is preferable to waiting for authority challenge.

Append a one-page "Executive Briefing" version suitable for sharing with the Head of Tax — no jargon, focused on business impact and required decisions.

You are a digital economy VAT specialist. Research and document the current VAT treatment of the following digital service / SaaS / cloud supply in [country]:

Service description: [describe precisely — e.g., cloud-hosted document management software sold on a per-seat monthly subscription to business customers; customer accesses via browser; no physical media; Canon hosts servers in Ireland]

Your research must cover: (1) Classification — is this a "telecommunications service," "broadcasting service," "electronically supplied service" (ESS), or something else under the EU VAT Directive? Apply the Annex II categories and the implementing regulation (EU) 282/2011, (2) Place of supply — Article 44 (B2B) or Article 45/58 (B2C), including OSS implications, (3) Current statutory rate in [country], (4) Any published guidance or rulings from [country] tax authority on this specific type of supply, (5) Recent case law (post-2020), (6) ViDA reform implications — how might this change under the proposed 2025–2028 rules? (7) Action points for our billing system, ERP configuration, and return reporting.

Include a "Jurisdiction Comparison" appendix covering how [2–3 other key countries] treat the same supply differently.

You are an expert in both transfer pricing and indirect tax. Identify and resolve potential inconsistencies between our intercompany transfer pricing policy and our VAT treatment for the following intercompany services:

Services in scope: [list — e.g., management fees, IP royalties, shared IT services, intragroup financing, distribution services, procurement services]
TP methodology applied: [TNMM / Cost Plus / CUP — describe]
VAT treatment applied: [describe current invoicing, rates, reverse charge application]

For each service: (1) Is the TP characterisation consistent with the VAT characterisation? (e.g., if TP treats as a service, VAT should not treat as a deemed supply of goods), (2) Is the taxable amount for VAT consistent with the arm's length price? Flag any year-end TP adjustments that create retrospective VAT issues, (3) Does the VAT recovery position align with the TP cost allocation? (4) Are the legal agreements consistent with the substance claimed in both TP documentation and VAT filings? (5) DEMPE analysis — if IP-related, does the entity paying the royalty have the VAT recovery right?

Output as a comparison table with a RAG status per service. Append a reconciliation procedure that our tax team should run quarterly to keep TP and VAT aligned.

You are a VAT in the Digital Age (ViDA) implementation specialist. Assess Canon's readiness for the three pillars of the EU ViDA reform package expected to take effect in phases from 2025–2028:

Pillar 1 — Digital reporting requirements (DRR): Real-time transaction-level reporting for intra-EU B2B supplies
Pillar 2 — Deemed supplier rules for platform economy: Impact on any marketplace or platform activities
Pillar 3 — Single VAT registration: OSS extension, removal of domestic registration requirements for certain supplies

For each pillar: (1) What exactly is changing and on what timeline? (2) Which of our current systems (Oracle R12, IDF, Orion, data lake) are affected and how? (3) What master data elements are new or need cleansing? (4) What process changes are required in AP, AR, and tax compliance? (5) Readiness rating: 1 (not started) to 5 (fully ready).

Output as a heat map (text format: table with RAG colouring described) with Pillar × Impact Area (Systems / Data / Process / People / Governance) as axes. Append a prioritised implementation roadmap with recommended start dates.

You are a local indirect tax specialist for [country]. Research and summarise all published guidance from [country tax authority name] on the topic of [specific issue — e.g., VAT treatment of leasing vs hire purchase / call-off stock post-Brexit / bad debt relief / partial exemption special methods] issued in the last three years.

For each piece of guidance: (1) Title, publication date, and reference number, (2) Key positions taken, (3) Whether this represents a change from previous guidance or case law, (4) Any safe harbour positions offered, (5) Practical examples given by the authority, (6) Anything that conflicts with ECJ case law and what that means in practice.

Then provide: (a) a "What This Means for Canon" section — specific transactions or processes affected, (b) a gap analysis showing where our current treatment diverges from the guidance, (c) a recommended response for each gap: immediate correction / voluntary disclosure / seek ruling / defend current position with reasoning.

Keep the bullet summaries crisp — each finding should be understandable in 30 seconds.

You are an indirect tax specialist in emerging digital economy transactions. Produce a briefing note on the VAT treatment of the following digital asset activity:

Activity: [describe — e.g., Canon accepting crypto payment for equipment sales / issuing Canon-branded loyalty tokens / selling NFT-backed product warranties / receiving carbon credits]

Cover: (1) Current EU VAT position — is this a supply of goods, services, or outside scope? Apply the Hedqvist ruling and subsequent ECJ/CJEU developments. (2) Treatment in Netherlands, Germany, and UK specifically — do they diverge? (3) How is the consideration valued for VAT purposes? Conversion rate, timing, and documentation. (4) Input VAT recovery implications — are any related costs blocked? (5) ViDA and the proposed new digital asset rules under CJEU pending cases. (6) Customs implications if tokens represent physical goods. (7) Compliance actions: what do we need to add to our VAT return, invoicing system, and reconciliation process?

Conclude with a risk rating (High / Medium / Low) and three immediate action points. The briefing should be usable as a standalone document that could be sent to our external advisors for peer review.

You are a statistical reporting and EU VAT compliance specialist. Map our Intrastat and EC Sales List (ESL) / Recapitulative Statement obligations across all EU member states where we have movements of goods or services.

For each country: (1) Intrastat — arrival threshold, dispatch threshold, current year-to-date value vs threshold (insert figures from our ERP: [paste or describe data source]), reporting frequency, filing deadline, format (XML / online portal), statistical value vs invoice value requirements, (2) ESL — applicable supply types (goods, services, triangulation), reporting period, deadline, amendment procedure, (3) Any country-specific additional statistical reporting (e.g., Germany's "Zusammenfassende Meldung" nuances, France's DEB/DES split).

Flag: any countries where we are above-threshold but not currently filing, any countries where our ERP classification of "intra-EU movement" may be inconsistent, any countries that have replaced Intrastat with a new digital system.

Output as a master table. Append an "Immediate Actions" section for any identified gaps and a recommended ERP query we can run monthly to monitor threshold proximity.

You are a global indirect tax policy specialist. Produce a briefing memo on the OECD's VAT/GST Guidelines on the digital economy and their relevance to Canon's international business model.

Cover: (1) Summary of the OECD destination principle for digital services — what is it and how does it differ from EU rules? (2) Which non-EU jurisdictions we operate in have already adopted OECD-aligned rules (Australia, Singapore, Japan, UAE, etc.) and what that means for our invoicing and filing, (3) Where there is material divergence between local implementation and OECD guidelines that creates double taxation or non-taxation risk, (4) The "economic nexus" concept — at what revenue thresholds do we become required to register in key markets? Show a table of thresholds vs our estimated in-country revenue, (5) Implications for our OSS compliance — does OSS satisfy non-EU jurisdictions' local registration requirements? (6) Recommended monitoring framework — how do we track rule changes in 30+ jurisdictions without dedicated local advisors in each?

Conclude with a maturity assessment of our current non-EU indirect tax compliance programme on a 1–5 scale across: Registration, Filing Accuracy, Technology, Governance.

You are a partial exemption specialist. Guide me through a review of our current partial exemption method in [country] to determine whether it remains appropriate or whether a special method should be negotiated with the tax authority.

Current method: [Standard method / special method agreed in year XXXX / describe calculation approach]
Business mix: [% of exempt income, e.g., financial services / property income / grants — describe]
Current recovery percentage: [X%]
Overhead VAT spend: [EUR amount]

Step 1 — Diagnose: Calculate the standard method recovery percentage using our latest 12-month figures. Is it "fair and reasonable" per [country] law?
Step 2 — Identify distortions: Are there any large one-off transactions, property deals, or capital items inflating or deflating the percentage?
Step 3 — Model alternatives: Calculate what the recovery rate would be under: (a) transaction count method, (b) floor area method, (c) staff headcount method, (d) income-based with carve-outs.
Step 4 — Capital goods scheme: Are any capital items subject to adjustment obligations? List them with adjustment periods remaining.
Step 5 — Recommend: Based on the modelling, should we stick with the current method, self-select a different method, or approach the authority for a special method agreement?

For each step, specify the exact data we need to pull from Oracle R12 and which ZX_LINES / GL_CODE_COMBINATIONS fields to use.

You are a VAT risk and controversy specialist. Analyse the following transaction pattern and produce a structured risk assessment:

Transaction pattern: [describe — e.g., Canon NL invoices Canon DE for management services; Canon DE does not declare these as received services on its VAT return; the services relate partly to Canon DE's exempt financial activities]

Data available: [describe what you have — e.g., AP invoice listing, ZX_LINES extract, VAT return workings]

For each risk identified: (1) Risk description — precise technical issue, (2) Relevant legislation and case law, (3) Probability of authority challenge: High / Medium / Low (with reasoning), (4) Financial impact: estimated VAT exposure + potential penalty % + interest calculation, (5) Mitigating factors already in place, (6) Recommended mitigation steps, (7) Residual risk after mitigation, (8) Owner and deadline.

Rank risks by Expected Value (Probability × Impact). Present the top 5 in detail and the remainder in summary. Include a "systemic vs one-off" classification for each risk — systemic risks require process changes, one-off risks may only need retrospective correction. Conclude with a recommended reserve amount for the CFO to consider.

You are a European VAT registration compliance specialist. Perform a comprehensive analysis of our potential unregistered VAT obligations across EU member states.

Our business activities: [describe — warehouse locations, installation and commissioning services, attendance at trade events, goods movement routes, digital service revenues by country, property interests, employees travelling and working across borders, call-off stock arrangements]

For each EU member state: check whether any of the following triggers a registration obligation:
□ Domestic sales above the distance selling threshold (or any B2C sales post-OSS)
□ Goods held in warehouse / fulfilment centre
□ Installation or assembly of goods
□ Services connected with immovable property
□ Admission to events or exhibitions
□ Domestic reverse charge on construction services (as recipient)
□ Call-off stock movements where simplification conditions are not met
□ Non-established taxable person making domestic B2B supplies
□ Fiscal representative requirement

Output as a checklist table: Country | Trigger Present | Registered? | Gap? | Urgency | Estimated Backdated Exposure | Recommended Action. Flag the five highest-risk gaps for immediate escalation. Include the voluntary disclosure regime available in each country where a gap exists.

You are a VAT transaction specialist. Analyse the VAT implications of the following proposed business restructuring:

Proposed change: [describe — e.g., consolidation of Canon NL and Canon BE into a single operating entity in NL; transfer of distribution function from DE to a new Swiss entity; spin-off of the IT services division into a separate legal entity]

For each step in the restructuring sequence: (1) Identify whether it constitutes a supply of goods, supply of services, or transfer of a going concern (TOGC), (2) If TOGC: confirm the TOGC conditions are met in each jurisdiction (list conditions explicitly), (3) If a supply: determine the taxable amount, rate, and cash flow impact, (4) Impact on VAT group memberships — do any existing groups need to be dissolved or reconfigured? (5) Impact on existing VAT registrations — which can be deregistered and when? (6) Historic VAT reclaim positions — are there adjustment period obligations (capital goods scheme) triggered? (7) New filing obligations — what new returns, ESLs, or Intrastat filings are required from the effective date?

Output as a step-by-step flowchart with VAT analysis at each node. Append a "Pre-Completion Checklist" of VAT actions that must be completed before the legal effective date and a "Day 1 Compliance" list of immediate post-restructuring actions.

You are a VAT risk management specialist. Produce a VAT risk heat map for [division / entity / country cluster]:

Business activities in scope: [describe the division's main transaction types, volumes, geographies, and any known historic issues]

Score each of the following risk dimensions on a 1 (low) to 5 (high) scale, with a written rationale for each score:

Dimension 1 — Registration compliance: Are all required registrations in place and up to date?
Dimension 2 — Rate and classification accuracy: Is the VAT rate / exemption applied correctly to each product/service category?
Dimension 3 — Input tax recovery: Is the correct proportion of input VAT being recovered? Any partial exemption, non-business, or blocked input tax issues?
Dimension 4 — Reporting and filing accuracy: Are returns filed on time with correct figures? Any known errors in prior periods?
Dimension 5 — E-invoicing readiness: Are we meeting country mandates? Any rejected invoices or format errors?
Dimension 6 — Intercompany / transfer pricing alignment: Are intercompany charges properly subjected to VAT?
Dimension 7 — Reverse charge self-assessment: Are all received services and goods correctly self-assessed?
Dimension 8 — Documentation and record retention: Are records sufficient to survive an audit?

Output as a heat map table (RAG) and a prioritised action plan for any dimension scoring 3 or above.

You are a VAT risk quantification specialist. Calculate our statute of limitations VAT exposure for the following open periods and identified uncertainties:

Jurisdictions: [list — e.g., NL, DE, FR, BE, IT, PL]
Known treatment uncertainties: [list each — e.g., "reverse charge on software licences from US vendor not self-assessed 2019–2021," "German VAT group was disbanded but we may have missed a VAT period," "Italian domestic reverse charge on subcontractors not applied"]

For each jurisdiction × uncertainty combination: (1) State the applicable statute of limitations period (standard and extended for fraud / negligence), (2) Calculate which periods are still open, (3) Estimate the VAT exposure: transactions in scope × rate × estimated error rate, (4) Add estimated penalty (% per country), (5) Add estimated interest (rate × months open), (6) Total financial exposure, (7) Probability of authority detection in next 12 months, (8) Expected value = exposure × probability.

Output as a table sorted by expected value descending. Include a "Voluntary Disclosure" column showing how much the exposure reduces if we self-correct. Conclude with a total reserve recommendation and a go/no-go decision framework for voluntary disclosure.

You are a customs and VAT specialist. Guide me through an alignment review between our import customs declarations and our import VAT accounting to identify potential discrepancies and risks:

Scope: [describe — e.g., all EU import entries for Canon NL in the last 12 months; approximately X shipments; goods imported from Japan, China, US]

Step 1 — Data extraction: Specify the exact Oracle R12 queries and data lake tables needed to extract: AP invoices for imports, corresponding customs entry numbers, declared customs values, tariff codes, duty amounts, import VAT amounts, and GL postings.

Step 2 — Valuation reconciliation: Compare the customs transaction value (CTV) to the AP invoice value. Flag variances > [threshold]%. Common causes: royalties not included in CTV, related-party price adjustments, assists not declared.

Step 3 — Tariff classification check: Review top 20 commodity codes by import value. For each, confirm: correct 10-digit CN code, applicable duty rate, any preference certificate claimed, any quota utilisation.

Step 4 — Import VAT accounting reconciliation: Confirm import VAT per postponed accounting entries matches Box 1 / Box 4 of VAT return.

Step 5 — Preference and reliefs: List all preference claims. Verify supplier declarations or REX registrations are current.

Step 6 — Output: Risk findings table, top 5 financial exposures, recommended corrective actions, and an ongoing monthly reconciliation procedure.

You are a VAT recovery audit specialist. Conduct a methodological audit of our current input VAT recovery approach and produce a written procedure document that covers both the "as-is" and recommended "to-be" process.

Current approach: [describe — e.g., we apply full recovery to all overhead VAT; we have a blanket 80% recovery for car-related costs; we do not apportion VAT on costs that relate to both taxable and exempt supplies]

Audit scope covers: (1) Identification of directly attributable costs — do we correctly allocate input VAT to taxable vs exempt activities? (2) Residual (overhead) input VAT — are all overhead costs properly included in the partial exemption calculation? (3) Blocked input tax — are we correctly identifying and blocking VAT on entertainment, private use, and specific excluded categories per [country] law? (4) Capital goods scheme — are all capital items (land, property, computers, aircraft) registered and adjustment calculations being performed annually? (5) Non-business activities — are we correctly excluding non-business input VAT from recovery? (6) Timing — are we claiming input VAT in the correct period?

Output as a procedure document with: (a) Purpose and scope, (b) Roles and responsibilities (RACI), (c) Step-by-step monthly process, (d) Oracle R12 transaction codes and report names, (e) Key controls and reconciliation checks, (f) Exception handling procedure, (g) Document retention requirements.

You are a VAT simplification measure specialist. Review our current use of EU VAT simplification measures and confirm eligibility conditions are still met following recent business changes:

Simplification measures currently in use: [list — e.g., triangulation simplification for NL → DE → PL chains, call-off stock simplification in Belgium and Czech Republic, OSS scheme for B2C digital services, margin scheme for second-hand equipment, domestic reverse charge in Germany for construction subcontractors]

Business changes since last review: [describe — e.g., new warehouse opened in Poland, German entity changed legal form, UK entity no longer in EU, new product category added]

For each simplification measure: assess against a checklist of ALL eligibility conditions. For example, for call-off stock: □ Goods transported to another MS, □ Supplier not established in destination MS, □ Buyer VAT number known at time of transport, □ Goods entered in the call-off register within 12 months, □ No substitution of buyer, □ Return goods procedure documented, □ EC Sales List correctly filed including call-off stock lines.

Output: one checklist per measure, with a pass/fail per condition, overall eligibility verdict, and any corrective actions required. Flag any measure where we are using the simplification but one or more conditions are not met — these represent priority remediation items.

You are a VAT audit defence specialist. Prepare a comprehensive pre-audit readiness assessment for a potential [country] VAT audit covering the period [YYYY to YYYY]:

Known authority focus areas (if any): [e.g., "authority has indicated interest in our intercompany service charges and reverse charge compliance" or "routine audit, no specific topics indicated"]

Assess readiness across the following audit preparation workstreams:

Documentation: □ VAT returns and workings retained for all periods, □ Backup data reconciled to returns, □ Invoices (input and output) accessible for all periods, □ Contract documentation for key supplies, □ Customs documents for import VAT, □ Evidence of VIES checks for zero-rated intra-EU supplies, □ Proof of export documentation for exports

Technical positions: □ Written technical analysis prepared for any non-standard VAT treatment, □ Advance rulings obtained where applicable, □ ECJ/national case law supporting our positions identified

Process documentation: □ Written VAT procedures for all material transaction types, □ Evidence of management oversight and controls

People readiness: □ Key contacts identified for each audit query area, □ Backup contacts identified in case of staff changes, □ External advisor briefed and on standby

For each item: status (✓ Ready / ⚠ Partially Ready / ✗ Not Ready), priority (H/M/L), owner, and deadline. Append a "common authority query" list for [country] audits and our pre-prepared response for each.

You are a VAT compliance specialist focusing on employee expense VAT recovery. Design a comprehensive procedure for managing VAT on employee expense claims in [country]:

Current situation: [describe — e.g., employees submit expenses via Concur; finance manually reviews for VAT; recovery rate is assumed 100% for all business expenses; no review of receipt validity or blocked categories]

The procedure must cover: (1) Eligible vs ineligible expense categories — produce a definitive list for [country] with recovery percentage, (2) Receipt requirements — what constitutes a valid VAT invoice vs a simple receipt for recovery purposes? Minimum fields required, (3) Entertainment threshold — where is the line between recoverable business entertainment and blocked hospitality? Include worked examples, (4) Car expenses — fuel scale charges, private use adjustments, vehicle type rules, (5) Home working — what portion of home broadband, mobile, and equipment is recoverable? (6) Foreign travel — can we recover VAT incurred in other EU member states via the 8th Directive refund procedure? Process and deadlines. (7) System configuration — what Concur / Oracle fields should flag items for VAT review?

Output as a policy document with: policy statement, scope, expense type matrix (table), step-by-step claim process, approver checklist, common errors and how to avoid them, and quarterly compliance monitoring procedure.

You are an e-invoicing implementation specialist. Produce a detailed mandate brief for [country] that our IDF programme team can use as a definitive technical reference:

Required sections:
1. Legal basis — legislation reference, directive transposition, effective date(s), phased rollout schedule (if applicable, split by taxpayer category / transaction type)
2. Scope — which transaction types are mandatory (B2B / B2G / B2C), which are excluded (e.g., financial services, exports), any registration threshold
3. Technical format — required XML schema (e.g., UBL 2.1, CII, FatturaPA, Factur-X), version number, mandatory vs optional fields, country-specific extensions
4. Transmission model — clearance (real-time authority approval required) vs post-audit (send directly to buyer and report to authority), platform name, API specification reference
5. Mandatory data fields — list every field required that is NOT in our current Oracle R12 AP/AR invoice output, highlighting the gaps
6. Archiving requirements — retention period, format, accessibility requirements
7. Penalties — penalty regime for non-compliant invoices, for late submission, for format errors
8. Testing environment — sandbox availability, test data requirements, certification process
9. Key open questions — items where the regulation is still ambiguous or where implementing decree is pending

Conclude with a RAG status assessment of our IDF platform's current readiness for this country.

You are a technical e-invoicing architect. Produce a detailed data field comparison for e-invoicing requirements across [Country A] and [Country B], mapped against our current Oracle R12 AR invoice output:

Structure the comparison as follows:
Column 1 — Data field name (use the XML element name from each country's schema)
Column 2 — [Country A] — mandatory (M) / conditional (C) / optional (O)
Column 3 — [Country B] — mandatory (M) / conditional (C) / optional (O)
Column 4 — Oracle R12 source table and column (e.g., RA_CUSTOMER_TRX_ALL.TRX_NUMBER)
Column 5 — Currently populated in R12? (Y / N / Partial)
Column 6 — Gap type: Missing field / Wrong format / Different logic / New master data required / No gap
Column 7 — Remediation approach: R12 config / custom DFF / master data enrichment / calculated at extraction / IDF mapping layer

Cover at minimum: Supplier and buyer identifiers (name, address, VAT, legal entity ID), Line-item detail (description, quantity, unit, unit price, discount), Tax lines (rate, amount, regime code, exemption reason), Payment terms and bank details, Reference numbers (PO, contract, delivery note), Digital signature requirements.

Summarise gaps by count and complexity. Flag any field that requires a new master data object to be created in R12.

You are a technology procurement specialist for finance systems. Evaluate the following e-invoicing vendor proposal against our requirements for the IDF programme:

Vendor: [vendor name]
Countries in scope for this evaluation: [list]
Our key requirements: Oracle R12 integration (preferably via API or SFTP), Support for [list formats], Clearance model support for [countries], SLA: 99.9% uptime, implementation timeline < 6 months for first country, 5-year TCO target < EUR [X]

Evaluate across the following weighted criteria:
— Functional coverage (25%): country formats supported, clearance vs post-audit model coverage, archiving module included
— Technical architecture (20%): Oracle R12 connector, API vs file-based, data transformation capability, scalability
— Implementation approach (15%): methodology, timeline, reference clients on R12, local country expertise
— Support model (10%): SLA terms, helpdesk hours, escalation path, language support
— Vendor stability (10%): revenue, client count, ownership, financial health, roadmap commitments
— Total cost of ownership (15%): licence model, implementation fees, per-transaction cost, annual maintenance
— References (5%): similar-sized multinationals, same-country implementations, R12 clients

For each criterion: score 1–5, evidence cited from the proposal, gaps vs our requirements. Produce a weighted total score and a recommendation: Proceed to negotiation / Request further information / Reject.

You are a programme manager specialising in finance system cutovers. Create a detailed cutover plan for the [country] e-invoicing go-live on [target date]:

The plan must cover the period from T-30 days through to T+14 days (hypercare end).

For each day or phase, specify: Activity | Owner | Duration | Dependency | Success Criterion | Rollback Trigger

Key activities to plan: Freeze of test environment and sign-off of UAT, Production environment preparation and configuration lock, Master data verification (customer VAT numbers, supplier details, country config), Oracle R12 AR/AP configuration freeze, IDF platform production credentials and endpoint configuration, Parallel run execution (send invoices via both old and new process, compare outputs), Reconciliation of parallel run results, Go / No-go decision meeting (criteria must be pre-defined), Cutover night: sequence of steps, responsible person, and time estimate for each, Day 1 post-go-live monitoring checklist, Hypercare support rota (who is on call, for how long, escalation contacts), First invoice acceptance confirmation from authority / recipient, Issue log review at T+3, T+7, T+14.

Also include: Rollback procedure (what triggers it, what steps, who authorises), Communication plan (who is notified when, what message), Lessons learned session (when, format, attendees).

You are a test manager for an e-invoicing implementation. Design a comprehensive testing strategy for [country] e-invoicing covering all test phases from unit testing through hypercare:

Phase 1 — Unit testing (Oracle R12 side)
Step 1.1: Define test cases for each AR transaction type (standard invoice, credit memo, debit memo, intercompany). For each: input data, expected output fields, pass/fail criteria.
Step 1.2: Verify all mandatory fields are populated from R12 master data and transaction data.
Step 1.3: Test edge cases: zero-value lines, multi-currency, partial shipments, cancelled invoices.

Phase 2 — Integration testing (R12 to IDF)
Step 2.1: End-to-end message flow test: R12 extraction → IDF transformation → [country format] XML generation.
Step 2.2: Error handling test: deliberately introduce bad data; confirm IDF error log captures correctly; confirm no silent failures.
Step 2.3: Performance test: volume of [X] invoices per hour; confirm processing within SLA.

Phase 3 — Authority sandbox testing
Step 3.1: Register in [country authority] test portal. Obtain test credentials.
Step 3.2: Submit each transaction type and capture authority response codes.
Step 3.3: Test rejection scenarios and resubmission workflow.

Phase 4 — Parallel run
Step 4.1: Define parallel run period (recommend minimum 2 weeks).
Step 4.2: Success criteria for moving to production: [define — e.g., 100% acceptance rate in sandbox, zero data reconciliation variances].

Phase 5 — Go-live readiness gates
For each gate: criterion, measurement method, pass threshold, sign-off authority.

You are an IDF programme delivery lead. Facilitate a lessons-learned exercise for the [completed country] e-invoicing implementation and translate findings into actionable recommendations for the [next country] rollout.

Structure the lessons learned as follows:

Section 1 — What went well (sustain and repeat)
• [For each item: What happened? Why did it work? How do we replicate it?]

Section 2 — What did not go well (avoid or mitigate)
• [For each item: What happened? Root cause? Financial/time impact? How do we prevent recurrence?]

Section 3 — What we would do differently
• [For each item: What was the approach taken? What is the better approach? Effort to implement change?]

Section 4 — Key metrics comparison (planned vs actual)
• Timeline: planned go-live vs actual
• Budget: planned vs actual (by workstream)
• Issues raised: number, severity distribution, resolution time
• Rejection rate in first 30 days vs target
• Hypercare issues per day trend

Section 5 — Updated implementation playbook for [next country]
• Top 10 changes to the standard approach based on this experience
• New risk items to add to the RAID log from day 1
• Master data quality checks to run before any future go-live

Keep each bullet actionable. Each recommendation should be assignable to a specific owner.

You are a data quality specialist for Oracle R12 e-invoicing readiness. Conduct a data quality assessment of the master data and transaction data required for [country] e-invoicing:

Data domains to assess:
1. Customer master (HZ_CUST_ACCOUNTS / HZ_PARTIES): VAT registration number completeness and format validity, address completeness (street, city, postcode, country ISO code), legal entity name vs trading name, email for e-invoice delivery
2. Supplier master (AP_SUPPLIERS / AP_SUPPLIER_SITES_ALL): VAT number format and VIES validation status, IBAN/bank account for buyer-initiated payments
3. Legal entity / ORG setup (XLE_ENTITY_PROFILES): Company registration number, legal entity VAT number, registered address, e-invoicing platform credentials
4. Tax codes (ZX_RATES_B / ZX_LINES): Mapping of every tax rate code to [country] e-invoicing exemption reason code, reverse charge flag accuracy
5. Item master: Product classification code (e.g., CPV for public sector, HS code for customs-linked invoicing)
6. Transaction data (RA_CUSTOMER_TRX_ALL): PO number population rate, delivery note reference, contract reference

For each domain: measure completeness (% populated), accuracy (% passing validation rule), remediation action, estimated effort (person-days), owner, and target completion date.

Output as a data quality dashboard table. Append the Oracle R12 SQL queries we should run to extract each metric.

You are a change management specialist for a finance transformation programme. Produce a change impact assessment for the [country] e-invoicing go-live, covering all affected stakeholder groups:

Assess impact on the following groups: AP team, AR team, Tax compliance team, IT / Oracle support team, Treasury (payment process changes), Procurement (supplier communication), Sales (customer communication), Shared Services Centre, Legal (contract clauses), External auditors.

For each group provide: (1) What specifically changes in their day-to-day work? (Be precise — e.g., "AR team must now check IDF portal each morning for rejection notifications and resubmit within 24 hours"), (2) Volume of change: High / Medium / Low, (3) Readiness assessment: 1–5 (1 = unaware, 5 = fully ready), (4) Training required: format, duration, mandatory vs optional, (5) Communication required: what message, from whom, by when, (6) Support needed during go-live: dedicated resource, user guide, helpdesk.

Then produce a RACI matrix for the 15 most critical ongoing operational tasks in the post-go-live steady state: Task | Responsible | Accountable | Consulted | Informed.

Conclude with a change risk assessment: which stakeholder group is the highest change risk and why?

You are an enterprise architect for the IDF e-invoicing programme. Build a comprehensive dependency map for the [country] e-invoicing implementation, covering upstream and downstream systems, data flows, and organisational dependencies:

Map the following layers:

Layer 1 — Source systems feeding the e-invoice
• Oracle R12 AR (RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, ZX_LINES) — what data is extracted, at what frequency, via what interface?
• Oracle R12 AP (for inbound e-invoice handling) — how does received e-invoice data flow back into AP_INVOICES_ALL?
• Master data systems (HZ, AP_SUPPLIERS, XLE) — who maintains these? What is the latency between a data change and it being available for e-invoicing?

Layer 2 — IDF platform
• Transformation and validation engine — what format does it receive from R12? What does it output to the authority?
• Error handling and resubmission workflow
• Archiving module

Layer 3 — [Country] tax authority platform
• API endpoint details, authentication method, expected response time, maximum message size

Layer 4 — Downstream impacts
• GL posting of e-invoice status (accepted / rejected) — how does this flow back to Oracle?
• VAT return population — how does the IDF submission log link to our ZX_LINES data?

For each dependency: owner, criticality (H/M/L), readiness status, and risk if unavailable.

Output as a layered flowchart in text/ASCII notation, then a dependency register table.

You are the IDF programme director. Prepare a steering committee update pack for the quarterly review meeting. The audience are senior executives (CFO, CIO, Regional Finance Directors) who need to make decisions, not review detail.

Insert current programme data: [paste your current milestone tracker, budget summary, and RAID log — or describe the current status]

Structure the pack as follows:

Slide 1 — Programme RAG Status (one-page visual)
Overall RAG | Last period trend | Key message in 2 sentences

Slide 2 — Milestone tracker
Country | Planned go-live | Current forecast | RAG | Reason for any amber/red | Decision needed from committee

Slide 3 — Achievements since last steering committee
Bullet each achievement, quantify where possible (e.g., "X invoices processed successfully in [country]")

Slide 4 — Issues and risks requiring steering committee attention
For each item: Issue/Risk description | Impact if not resolved | Proposed resolution | Decision required from committee | Deadline

Slide 5 — Budget status
Planned spend to date | Actual spend to date | Variance | Forecast to complete | Variance to budget | Key drivers of variance

Slide 6 — Resource and capacity
Current resource position | Gaps | Options to fill gaps | Recommendation

Slide 7 — Next period plan
Next 90 days top 5 milestones | Dependencies on business stakeholders | What we need from the committee today

Each slide: provide the headline (one sentence takeaway), 4–6 supporting bullets.

You are a senior programme manager for the IDF e-invoicing programme. Analyse our current project plan and identify the critical path for the next 90 days:

Current plan: [paste Gantt or milestone list — or describe: "We are implementing e-invoicing for France (go-live: [date]), Germany (go-live: [date]), and Italy (go-live: [date]). Current date is [date]. Current status: [describe]"]

For the critical path analysis: (1) List every milestone in the next 90 days across all active countries, (2) Map dependencies between milestones (predecessor → successor), (3) Identify the critical path — the sequence of tasks where any delay directly delays the overall go-live, (4) For each critical path item: current status, owner, confidence level (H/M/L), and what would cause it to slip.

Then for each item on the critical path that is at risk: (a) Quantify the delay (in working days) if it slips, (b) Identify the downstream consequence, (c) Propose a specific contingency action.

Output as: (1) A week-by-week 90-day calendar grid showing milestones by country with RAG status, (2) A critical path list sorted by earliest-start date, (3) A "top 5 items that could derail the programme" summary with specific mitigations. Flag any milestone where we are currently past the latest-start date and still show green — these are hidden risks.

You are a programme manager. Update and present the RAID log for the IDF programme steering committee. The log must be executive-friendly: concise, action-oriented, and focused on items requiring committee attention.

Input: [paste current RAID log — or describe the current known risks, assumptions, issues, and dependencies]

Format the output as four separate tables:

RISKS table: Risk ID | Risk Description (2 lines max) | Probability (H/M/L) | Impact (H/M/L) | Current Mitigation | Residual Risk | Owner | Review Date | Escalate to Committee? (Y/N)

ASSUMPTIONS table: Assumption ID | Assumption | Validation Status (Confirmed / Unvalidated / Invalidated) | Impact if Wrong | Owner | Action Required

ISSUES table: Issue ID | Issue Description | Date Raised | Impact (H/M/L) | Resolution Owner | Target Resolution Date | Status (Open / In Progress / Escalated / Closed) | Committee Decision Required? (Y/N)

DEPENDENCIES table: Dependency ID | Description | Providing Party | Required By Date | Current Status | Risk if Late

For any item marked "Escalate to Committee" or "Committee Decision Required": draft the specific question the committee needs to answer and the options available to them. Sort each table by severity/urgency. Remove any items that are closed and more than 30 days old.

You are a resource planning manager. Produce a resource capacity analysis for the IDF programme for [quarter]:

Programme resource profile: [list roles — e.g., Programme Manager, Tax SME (Oracle), Tax SME (VAT), Oracle Technical Lead, IDF Platform Specialist, Test Manager, Change Manager, Project Coordinator]

For each role: (1) Required effort in days for this quarter by workstream (France go-live, Germany preparation, Italy scoping, programme management overhead), (2) Named resource(s) assigned, (3) Available capacity in days this quarter (accounting for holidays, other projects, BAU obligations), (4) Capacity gap or surplus in days.

Then for any gap: propose resolution options — e.g., extend contractor, hire temporary resource, defer scope, re-prioritise, redistribute to surplus resources. For each option: cost, lead time, risk.

Output as: (1) A capacity table (roles × workstreams showing demand), (2) A supply table (named resources × availability), (3) A demand vs supply gap table by role, (4) A recommended resource action plan with decision deadline. Flag any single points of failure where one person holds critical knowledge with no backup.

You are a programme change controller. Produce a formal change request impact assessment for the following proposed scope change to the IDF programme:

Change request: [describe — e.g., "Add real-time VAT validation of customer VAT numbers via VIES API at point of invoice creation in Oracle R12 AR, before e-invoice submission. This was not in original scope."]
Requested by: [name / department]
Requested implementation date: [date]
Business justification provided: [summarise]

Assess impact across eight dimensions:
1. Timeline — how many working days does this add to the current plan? Which milestone(s) are affected?
2. Budget — estimated additional cost: development, testing, infrastructure, licence, project management
3. Technical complexity — level of effort and technical risk; existing architecture impact
4. Resource — additional people required; can existing team absorb or do we need new skills?
5. Dependencies — does this create new dependencies on other systems or teams?
6. Risk — what new risks does this introduce? How does it affect existing risks?
7. Benefits — does this add quantifiable business value? How does it affect programme benefits realisation?
8. Alternatives — is there a lower-impact way to achieve the same business objective?

Score each dimension 1 (minimal impact) to 5 (major impact). Provide a weighted impact total. Conclude with a recommendation: Approve / Approve with conditions / Reject / Defer, with clear reasoning. Include a response to the requestor draft.

You are an experienced programme coordinator. Extract and structure the following meeting transcript into a formal minutes document:

[Paste transcript or detailed notes from the meeting]

Meeting: [title]
Date: [date]
Attendees: [list names and roles]
Chair: [name]

Structure the output as:

1. DECISIONS MADE (numbered list)
For each decision: What was decided | Who decided | Any conditions or caveats | Who needs to be informed

2. ACTION ITEMS (table)
Ref # | Action description (specific and measurable) | Owner | Due date | Priority (H/M/L) | Dependencies

3. RISKS AND ISSUES RAISED
For each: Description | Raised by | Current status | Proposed owner | Next step

4. ESCALATION ITEMS
Items that need to go to a higher level for decision — for each: what the question is, what options were discussed, what the group recommends, and who the escalation is to.

5. PARKING LOT
Items discussed but not resolved — to be carried to next meeting.

6. NEXT MEETING
Date, time, location, standing agenda items based on today's open actions.

Cross-reference: flag any action item that contradicts a previously made decision, or any new risk that should be added to the RAID log.

You are a programme benefits manager. Design and populate a benefits realisation tracker for the IDF e-invoicing programme:

Programme benefits originally committed: [describe — e.g., "reduction in manual invoice processing effort, penalty avoidance, improved cash flow from faster invoice acceptance, reduction in payment disputes"]

For each benefit: (1) Benefit name and description, (2) Category: Financial (hard) / Financial (soft) / Strategic / Risk avoidance, (3) Measurement metric — the specific KPI that proves the benefit has been realised, (4) Measurement method — where does the data come from? Which Oracle or IDF report? Who extracts it? How often?, (5) Baseline value — what is the metric today, before IDF? (6) Target value — what commitment was made in the business case? (7) Realisation timeline — by when should the full benefit be visible?, (8) Current actual — what is the metric showing today?, (9) Variance to target — are we on track?, (10) Benefit owner — who is accountable for delivering this benefit?

Append a "Benefits Realisation Roadmap" showing when each benefit should become measurable (some benefits only visible 6–12 months post go-live). Include a quarterly reporting cadence and escalation trigger (e.g., "if actual is more than 20% below target in quarter 3 post go-live, escalate to CFO").

You are a programme governance specialist. Design a governance framework for the IDF e-invoicing programme that covers the full programme lifecycle:

Programme context: [describe — e.g., 18-month programme, 8 country implementations, EUR X budget, executive sponsor is CFO, business owner is Head of Tax Technology, delivery partner is [vendor]]

The governance framework must define:

1. Decision rights matrix
For each type of decision (scope change, budget reallocation, resource change, timeline change, go/no-go for each country, vendor contract variation): Who can decide alone? Who must be consulted? Who must approve? What threshold triggers escalation?

2. Meeting cadence and governance bodies
For each governance body (Steering Committee, Programme Board, Country Workstream, Daily Standup): purpose, membership, frequency, chair, quorum, minutes and action tracking.

3. Escalation path
Define the exact escalation chain with triggers. E.g.: "Any issue with potential financial impact > EUR X must be escalated to Steering Committee within 48 hours." Include a decision escalation SLA at each level.

4. Change control process
Step-by-step: how a change request is raised, assessed, reviewed, decided, communicated, and recorded.

5. Reporting hierarchy
What is reported to whom, at what frequency, in what format. Who produces each report? What is the sign-off requirement?

6. Programme closure criteria
What must be true before the programme is formally closed and handed over to BAU? Who signs off?

Output as a formal procedure document with numbered sections, flowcharts (text), and a responsibility summary table.

You are a risk manager for the IDF programme. Develop detailed risk response plans for the top 5 programme-level risks:

Top 5 risks (revise based on your actual RAID log):
1. Oracle R12 upgrade / patch conflict with IDF integration during implementation window
2. Key tax SME resource lost mid-programme (single point of failure)
3. Country regulatory deadline brought forward without adequate notice
4. IDF vendor unable to deliver [country] format on committed timeline
5. Customer master data quality too poor for [country] go-live (VAT number completeness below threshold)

For each risk, produce a response plan covering:
• Risk description and current probability / impact rating
• Trigger events — what specific observable event signals this risk is materialising?
• Response strategy: Avoid / Reduce / Transfer / Accept
• Specific response actions (numbered, with owner and deadline)
• Contingency plan — if the risk materialises despite mitigation, what do we do in the first 24 hours / first week / first month?
• Budget contingency reserve: how much should we hold for this risk? (Probability × Impact × cost estimate)
• Residual risk after mitigation is in place
• Review frequency

Conclude with a total contingency reserve recommendation and a "war room" protocol — who is called into a crisis response team, how fast, and who leads it.

You are a stakeholder engagement specialist for the IDF programme. Design a comprehensive stakeholder engagement plan for the [implementation phase]:

First, map all stakeholders using a Power / Interest grid. Categorise each as: Manage Closely (high power, high interest) / Keep Satisfied (high power, low interest) / Keep Informed (low power, high interest) / Monitor (low power, low interest).

Stakeholders to map: CFO, CIO, Head of Tax, Tax Technology Manager, Country Finance Directors (list by country), IT Director, AR Manager, AP Manager, External auditors, Tax authority contacts (by country), IDF platform vendor, Oracle support partner, End users (AP and AR clerks).

For each stakeholder / group: (1) Current attitude: Champion / Supporter / Neutral / Resistant / Blocker, (2) Desired attitude at programme completion, (3) Key concerns or questions they have about the programme, (4) Engagement frequency and preferred channel (face-to-face / email / report / workshop), (5) Key message tailored to their interests and concerns, (6) Owner responsible for maintaining the relationship.

Then produce a RACI matrix for the 10 most important programme communications: Communication | Responsible (drafts) | Accountable (approves) | Consulted (input) | Informed (receives).

Flag any stakeholder who is currently "Resistant" or "Blocker" and provide a specific influence strategy.

You are a portfolio manager. Analyse the interdependencies between the IDF e-invoicing programme and other concurrent Canon IT and Finance initiatives to identify resource conflicts and timeline clashes:

IDF programme: [describe current timeline, key milestones, technology platforms involved: Oracle R12, IDF platform, data lake]

Other concurrent initiatives: [list — e.g., Oracle R12 upgrade project, Finance shared services migration, ERP consolidation project, Microsoft 365 Copilot rollout, new CRM implementation, annual close activities, external VAT audit in [country]]

For each pair of IDF and concurrent initiative: (1) Shared resources: which named individuals or teams are working on both? (2) Shared technology: do both programmes require changes to the same system at the same time? (3) Timeline conflict: are there overlapping peak periods (e.g., both require Oracle UAT in October)? (4) Dependency: does IDF depend on the other initiative completing first, or vice versa? (5) Risk: what is the consequence if the conflict is not managed? (6) Resolution: proposed approach (sequence, additional resources, scope reduction).

Output as: (1) Interdependency matrix (IDF workstreams × other initiatives, showing conflict type), (2) Resource conflict table (named person × projects they're on × % allocation × conflict period), (3) Recommended programme board decisions to resolve the top 3 conflicts. Flag any item where the conflict is severe enough that one programme must formally request a timeline change from another programme's steering committee.

You are the IDF programme director preparing a one-page status update for the CFO. The CFO has 5 minutes to read this before a board meeting. Every word must earn its place.

Insert current data: [paste your milestone tracker, budget actuals, and top risks]

Structure the one-pager as:

HEADLINE (one sentence): Overall programme status in plain language — what is the most important thing the CFO needs to know today?

RAG STATUS TABLE: Country | Phase | RAG | Trend (↑↓→) | Go-live forecast | Comment (10 words max)

KEY ACHIEVEMENTS THIS PERIOD (3 bullets max, quantified where possible)

DECISIONS REQUIRED FROM CFO (numbered, each with: the question, the two or three options, the programme team's recommendation, and the consequence of delay)

TOP 3 RISKS: Risk | Potential impact in EUR | Mitigation in place | Residual risk

FINANCIALS: Budget approved | Spend to date | Forecast to complete | Variance | Commentary

NEXT MILESTONE: What happens next, by when, and what success looks like.

Format constraints: fits on one A4 page. No jargon. No passive voice. Numbers over adjectives ("reduced processing time by 3.5 hours per day" not "significantly improved efficiency").

You are the Tax Technology Manager making an internal investment case for additional Microsoft 365 Copilot Pro licences for the Finance and Tax team. Your audience is the Finance leadership team who control the budget and are sceptical of technology spend without clear ROI.

Context: Current state — [describe: how many licences do we have, who uses them, what tasks are they used for today]. Proposed investment — [X additional licences at EUR Y/month = EUR Z annual cost].

Build the business case across four value pillars:

1. COST AVOIDANCE: What external advisory spend is reduced? Estimate hours of external advisor time replaced per year × hourly rate. Show the calculation.
2. PRODUCTIVITY SAVINGS: For each specific task type (VAT memo drafting, return preparation, regulatory research, meeting minutes, data analysis), estimate: current time per occurrence × frequency per year × FTE cost rate = annual saving. Build a table.
3. RISK REDUCTION: What compliance risks are reduced? Quantify: e.g., earlier detection of legislative changes, faster response to authority queries, reduced error rate in manual processes.
4. COMPETITIVE / STRATEGIC VALUE: What can we do with Copilot Pro that we cannot do today? What would we lose if competitors adopt and we do not?

Conclude with: payback period, NPV at 3 years, sensitivity analysis (what if productivity gains are 50% of estimated?), and a recommended decision.

Anticipate and pre-empt the three most likely objections from the Finance leadership team.

You are the Tax Technology Manager writing a quarterly update for Canon's internal Innovation Hub newsletter. Audience: finance and IT professionals across the organisation who are curious about AI adoption but not experts. Tone: honest, practical, and engaging — show the real experience, not just the successes.

Quarter in review: [Q1/Q2/Q3/Q4 YYYY]

Write the update in four sections:

WHAT WE LAUNCHED (with honest assessment)
For each initiative: what we built or deployed, who uses it, what it does, and — critically — how well it actually worked in practice. Include one thing that surprised us (positive or negative).

NUMBERS THAT MATTER
3–5 metrics that prove impact: e.g., time saved per week, prompts run, user adoption rate, accuracy rate. If a metric disappointed, say so and explain why.

WHAT WE LEARNED THE HARD WAY
Two or three genuine lessons — things that did not work as expected, prompts that produced poor output, processes where AI was not the right tool. This builds credibility.

WHAT IS COMING NEXT QUARTER
Two or three specific initiatives planned, with the business problem each solves. Ask readers for volunteers, input, or collaboration.

End with one practical tip readers can use immediately — a specific prompt or workflow they can try this week.

Word count target: 400–500 words. Avoid corporate speak. Write as if you are talking to a colleague in the corridor.

You are the Head of Tax preparing a board-level presentation on e-invoicing compliance. The board are non-tax specialists: they understand risk, regulation, and investment, but not VAT technicalities. Your goal is to secure continued investment in the IDF programme and board-level awareness of the compliance obligation.

Prepare a 6-slide narrative:

Slide 1 — The regulatory wave: "E-invoicing is becoming law across Europe — and the timelines are not negotiable"
Show: map of countries with mandates, go-live dates, penalty regimes. Key message: this is a compliance obligation, not an optional improvement.

Slide 2 — What this means for Canon specifically
Show: which entities are affected, which transaction volumes are in scope, what the consequence of non-compliance looks like in EUR (penalty per invoice × volume).

Slide 3 — Our response: the IDF programme
Show: what IDF is, what it does, current status (RAG), investment to date, and forecast to complete. Keep it simple: "We are [X]% through, we have spent EUR [Y], we forecast EUR [Z] to complete."

Slide 4 — What happens if we do not invest
Show: penalty exposure calculation, reputational risk, operational disruption (authorities can block invoice acceptance), competitor comparison.

Slide 5 — Decision required from the board
State clearly: "We are asking the board to approve [specific decision — funding, resource, executive sponsor support, etc.]." Show the options and the consequence of each.

Slide 6 — Beyond compliance: the opportunity
Show: 2–3 operational benefits that e-invoicing enables (faster payment cycles, automated reconciliation, real-time audit trail). Frame as: compliance investment that also drives efficiency.

For each slide: a one-sentence headline, 4–5 bullets with substance, any supporting figure or statistic.

You are the Head of Tax writing an all-team communication to the Finance and Tax department (approximately [X] people) introducing expanded use of AI tools. Several team members are enthusiastic early adopters; others are anxious about job security; some are simply sceptical of technology promises. Your communication must speak to all three groups.

Context: [describe what is being introduced — e.g., "From [date], all finance team members will have access to Copilot Pro. This comes alongside our expanded Prompt Library and a training programme launching in [month]."]

Email structure:

Subject line: [Propose 3 options — choose the least corporate-sounding]

Opening: Why now? One short paragraph on why the timing is right — link to regulatory changes, workload, or a specific team pain point the reader recognises.

What is changing: Three bullet points — specific, concrete, no jargon.

What is NOT changing: Address the job security concern directly and honestly. Do not be dismissive — acknowledge the concern, state the reality clearly.

Quick wins — try this week: Three specific things a finance professional can do with the tool in their existing workflow, each described in one sentence.

How to get support: Named contacts, training dates, where to find the Prompt Library.

Call to action: One specific, low-barrier action you are asking everyone to take before [date].

Closing: Personal, not corporate. Write as a leader, not a policy document.

Tone: warm, direct, honest. Maximum 350 words. Test: would a sceptical team member feel respected after reading this?

You are a Finance Technology manager preparing an internal business case presentation for [initiative — e.g., automated VAT reconciliation tool / data lake expansion / real-time tax dashboard / AI-powered contract review].

Audience: Finance leadership team. Decision needed: approve budget of EUR [X] and resource of [Y] FTEs for [Z] months.

Build the presentation as follows:

Slide 1 — Problem Statement
What is the specific pain point? Quantify it: how many hours wasted, how many errors, what financial risk, what regulatory exposure. Use real data from our environment where possible.

Slide 2 — Proposed Solution
What exactly are we proposing to build or buy? One paragraph plain-language description. What it does, what it does not do. Who uses it.

Slide 3 — Options Considered
Three options: (1) Do nothing — show the cost of inaction, (2) Proposed solution — the recommendation, (3) Alternative approach — a different way to solve the same problem. For each: pros, cons, cost, timeline.

Slide 4 — Investment Required
One-time costs, ongoing costs, internal resource, external resource, timeline. Show as a table: item | year 1 | year 2 | year 3.

Slide 5 — Return on Investment
Benefits quantified: time saved × cost rate, risk reduced × probability × exposure, error rate reduction × cost per error. Show payback period and 3-year NPV. Include sensitivity analysis.

Slide 6 — Risks and Mitigations
Top 3 risks. For each: probability, impact, mitigation, residual risk.

Slide 7 — Recommendation and Next Steps
Clear ask. What you need approved today. What happens next if approved. What happens if deferred. Timeline for decision.

Format: executive-quality slides. Each slide: one headline sentence (the "so what"), 4–5 supporting bullets. No prose paragraphs on slides.

You are the Tax Technology Manager writing the monthly newsletter for the Tax team. The goal is to keep the team informed, engaged, and ahead of regulatory changes — without adding to their email overload.

Month: [Month YYYY]

Newsletter sections (keep each concise — total target: 600 words):

🔴 URGENT: Deadline reminders
Any filing deadlines, legislative effective dates, or project milestones in the next 30 days. Table format: Deadline | Country | Action Required | Owner.

📋 REGULATORY UPDATES
2–3 most important tax law changes affecting our jurisdictions this month. For each: what changed, which entities are affected, what action (if any) is needed, and who owns it.

🚀 IDF PROGRAMME UPDATE
One paragraph — where we are, what happened this month, what is coming next. Include one metric (e.g., "X invoices processed in [country] since go-live with Y% acceptance rate").

🤖 AI TIP OF THE MONTH
One specific prompt or workflow the team can use immediately. Include the actual prompt text, copy-ready. Explain in 2 sentences what it does and when to use it.

📅 UPCOMING
3–5 events, training sessions, or milestones in the next 60 days that the team should have in their diary.

💡 DID YOU KNOW?
One interesting fact, ECJ case, or regulatory quirk that is relevant to our work — explained simply in 3 sentences.

Tone: professional but human. Use first person ("we", "our team"). Use emojis sparingly (as section headers only). Write as someone who respects their colleagues' time.

You are the Tax Technology Manager presenting at [conference name] on the topic of "Practical AI adoption in a corporate tax function." Your audience are peer tax professionals at other multinationals: they are curious but also sceptical of vendor hype. Your credibility comes from sharing real experience, not polished theory.

Presentation structure (25 minutes + 5 minutes Q&A):

Slide 1 — Who I am and why this talk is different (2 min)
Not a vendor. Real implementation. Sharing what worked, what did not, and what surprised us.

Slides 2–3 — The starting point: what problem were we trying to solve? (3 min)
Describe the specific pain point that drove AI adoption. Quantify the problem — give numbers.

Slides 4–6 — What we built and how (8 min)
Three specific use cases with real examples:
• Use case 1: [e.g., Automated VAT research and memo drafting] — what it is, how we built it, what the prompt looks like, what the output quality is like honestly.
• Use case 2: [e.g., E-invoicing error analysis from data lake] — same structure.
• Use case 3: [e.g., Regulatory change monitoring] — same structure.

Slide 7 — The numbers (3 min)
What we can actually measure: time saved, adoption rate, error reduction. What we cannot yet measure and why.

Slide 8 — What we got wrong (4 min)
The three biggest mistakes or false starts. Be specific. This is the slide the audience will remember.

Slide 9 — What comes next (2 min)
Our 12-month roadmap. What we are watching in the market.

Slide 10 — Three things you can do next week (2 min)
Practical, low-cost starting points. No vendor required.

For each slide: one-line headline, 4 speaker-note bullets, any visual suggestion.

You are a Tax Technology Manager writing a LinkedIn post sharing a genuine insight from your experience implementing AI tools in a corporate tax function.

Topic: [choose one — e.g., "What I learned after 6 months of using Copilot Pro for VAT research" / "Why our first AI prompt library failed — and what we built instead" / "The e-invoicing implementation lesson I wish someone had told us earlier"]

Write three versions of the post:

Version A — Contrarian / thought leadership angle
Open with a statement that challenges a common assumption ("Everyone says AI will replace tax advisors. Here is what I actually observed after 6 months..."). Share one specific, unexpected finding. End with a question to drive comments.

Version B — Practical / how-to angle
Open with a specific problem ("Last month I needed to draft 12 VAT advisory memos in 3 days. Here is exactly how I did it with AI..."). Give 3 numbered practical steps with real detail. End with an offer (e.g., "Drop a comment if you want the prompt template I used").

Version C — Story / narrative angle
Open with a specific moment or conversation ("I almost missed a German e-invoicing deadline. Here is what happened and what I changed..."). Tell the story with a clear problem → action → lesson structure. End with one takeaway.

For each version: approximately 200 words, no corporate jargon, write in first person as a practitioner, include 3 relevant hashtags. Recommend which version to post and why.

You are the IDF programme director. Draft three versions of an elevator pitch explaining the IDF e-invoicing programme to a senior leader who has no background in tax or e-invoicing. Each pitch must be deliverable in 60 seconds (approximately 130–150 words spoken).

The pitches must answer: What is IDF? Why does Canon need it? What happens if we do not do it? What are we doing about it? What do we need from the listener?

Version 1 — The risk framing
Lead with compliance risk and penalty exposure. Quantify the downside. End with the ask.

Version 2 — The opportunity framing
Lead with the operational efficiency angle. Frame e-invoicing as a platform for modernising our finance processes. End with the ask.

Version 3 — The competitor framing
Lead with market context — what our industry peers are doing. Position IDF as essential to remaining competitive. End with the ask.

For each version: write out the full spoken text (not bullets), mark where to pause for emphasis [PAUSE], note which statistic or fact will have the most impact for this particular audience, and suggest the follow-up question to ask after delivering the pitch to continue the conversation.

You are a finance transformation specialist. Map the following finance process end-to-end and identify every step where AI could add value:

Process: [describe — e.g., monthly VAT return preparation for Netherlands — from data extraction through Oracle R12, to return completion, review, approval, filing, and payment]

For each process step: (1) Step name and description, (2) Current inputs and outputs, (3) Current duration (hours/minutes), (4) Current FTE involved, (5) AI tool most applicable: Copilot Chat / Copilot Pro with data plugin / Python + AI API / Custom prompt / No AI applicable, (6) Specific AI task: Summarise / Draft / Classify / Validate / Extract / Calculate / Detect anomaly / Generate code, (7) Estimated time saving with AI (%), (8) Implementation complexity: Low (prompt only) / Medium (template + data) / High (integration required), (9) Risk: Low (reviewing output) / Medium (AI drafts, human approves) / High (AI acts autonomously), (10) Prerequisites for AI adoption.

Output as a table sorted by: time saving × implementation complexity (easy wins first). Append a "top 5 quick wins" summary that the team can implement this month without any IT involvement — just better prompts. Then a "6-month roadmap" for the medium-complexity items.

You are an Oracle R12 and indirect tax specialist. Analyse our Chart of Accounts structure and recommend how to leverage segment values for automated VAT determination, reducing reliance on manual tax code selection:

Our CoA structure: [describe — e.g., Segment 1: Entity (4 chars), Segment 2: Cost Centre (4 chars), Segment 3: Natural Account (6 chars), Segment 4: Sub-Account (4 chars), Segment 5: Intercompany (4 chars)]

Sample values: [provide 10–15 example account combinations with their current manual VAT treatment]

Analyse: (1) Which segment combinations reliably predict the correct VAT treatment without further information? (e.g., all transactions to natural account 6100 are VAT-exempt under Article 132 — can this be automated?), (2) Where does the account combination not provide enough information to determine VAT treatment? What additional data point is needed (e.g., customer country, item description, PO type)?, (3) Recommended Oracle R12 configuration: for each high-confidence segment combination, specify the ZX_LINES TAX_CLASSIFICATION_CODE that should be auto-applied and the Oracle eBTax rule structure to implement it, (4) Estimated coverage: if we implement these rules, what percentage of transaction volume would be auto-classified vs still requiring manual review?

Produce: (a) A mapping table (segment combination → tax classification → confidence level → implementation route), (b) A list of "always-manual" transaction types with explanation, (c) An implementation sequence ordered by coverage impact.

You are a finance transformation lead. Design a monthly close acceleration plan for the tax and finance team using AI tools. The goal is to reduce the close cycle from [X days] to [Y days] within 6 months:

Current close activities: [list all activities in the close process with their current start day, duration, and owner — e.g., "Day 1–2: GL transaction posting review (4 hours, AP team)," "Day 3: Intercompany reconciliation (6 hours, Tax team)," etc.]

For each activity: (1) Current start day in close cycle, (2) Current duration, (3) AI tool to apply (Copilot Pro / custom prompt / automated data extract / anomaly detection), (4) Specific AI task description — be precise about what the AI does (e.g., "AI generates reconciliation exceptions list from two data lake tables; human reviews exceptions only"), (5) AI-assisted target duration, (6) Time saving in hours, (7) Dependencies for AI implementation (data availability, system access, training), (8) Implementation effort (hours to build the AI-assisted version), (9) Risk: what happens if AI makes an error at this step?

Output as a Gantt-style table showing current close timeline vs AI-assisted target timeline. Highlight the critical path. Append: (a) a "month 1 quick wins" list (no IT, just prompts), (b) a "6-month implementation plan" for the bigger changes, (c) a governance note on human review requirements for AI-generated outputs in the close process.

You are a data governance specialist for the IDF data lake. Design a data quality assessment and monitoring framework covering all tables critical to e-invoicing and tax reporting:

Tables in scope: [list — or use: AP_INVOICES_ALL, RA_CUSTOMER_TRX_ALL, ZX_LINES, AP_SUPPLIERS, HZ_CUST_ACCOUNTS, IDF_EINVOICE_LOG, ORION_DET_LOG]

For each table, define:
1. Critical data elements: which columns are essential for the business purpose of this table?
2. Quality dimensions per element:
   • Completeness: % of rows where this field is not null
   • Accuracy: % of values that pass a validation rule (specify the rule, e.g., "VAT number matches VIES format")
   • Consistency: % of values consistent with related tables (specify the cross-table check)
   • Timeliness: maximum acceptable lag between source system and data lake
3. Measurement query: the SQL or data lake query to measure each dimension
4. Acceptable threshold: minimum quality level (e.g., ">98% complete is Green, 95–98% is Amber, <95% is Red")
5. Remediation workflow: if threshold is breached, who is notified, what investigation steps, what escalation path

Then define: (a) monitoring cadence (daily, weekly, monthly per table), (b) a data quality scorecard format (output as a template), (c) an issue management log for data quality incidents, (d) quarterly data quality review meeting agenda template.

You are a finance transformation director. Build a finance process digitisation roadmap showing the journey from current state to a modern AI-augmented finance function over 18 months:

Current state: [describe honestly — e.g., "Heavy reliance on Excel for reconciliations, manual VAT coding in R12, email-based approval workflows, monthly reporting takes 10 days, data lake exists but underused, 2 Copilot Pro licences in tax team"]

Target state: [describe the ambition — e.g., "AI-assisted close cycle under 5 days, automated VAT determination for 80% of transactions, real-time tax dashboard, AI-generated first draft of all standard compliance outputs, data lake as single source of truth for all tax reporting"]

Structure the roadmap as three 6-month phases:

Phase 1 (Months 1–6) — Foundation: quick wins and infrastructure
Phase 2 (Months 7–12) — Scale: systematic automation of core processes
Phase 3 (Months 13–18) — Optimise: advanced AI, predictive analytics, self-service reporting

For each initiative in each phase: (1) Initiative name, (2) Business problem solved, (3) Technology/tool, (4) Expected benefit (quantified), (5) Investment required (EUR + FTE days), (6) Dependency on other initiatives, (7) Success metric.

Also show: (a) cumulative benefit realisation curve by quarter (chart in text format), (b) total investment by phase, (c) payback timeline, (d) headcount implication (roles that evolve, skills needed, training plan).

You are an accounts payable transformation specialist. Conduct a systematic review of the AP process and identify AI optimisation opportunities across the full invoice-to-payment cycle:

Current AP profile: [describe — e.g., volume of invoices per month, split of PO-matched vs non-PO, current touchless rate, average processing time, top exception types, FTE count, Oracle R12 version, any current automation tools like OCR]

Step 1 — Invoice receipt and capture
Current: [describe]. AI opportunity: intelligent document processing to extract fields from unstructured PDFs/emails into structured R12 AP_INVOICES_ALL data. Evaluate: current OCR capability, missing fields, exception handling.

Step 2 — PO matching (2-way and 3-way)
Current: [describe]. AI opportunity: AI-assisted exception resolution — for each hold type (price, quantity, receipt), can AI suggest the resolution based on historical patterns? Specify what data it would use (AP_HOLDS_ALL, RCV_TRANSACTIONS, PO_DISTRIBUTIONS_ALL).

Step 3 — Non-PO invoice approval routing
Current: [describe]. AI opportunity: AI-suggested cost centre and GL account based on invoice description + supplier history. Specify the Oracle fields and the training data needed.

Step 4 — Payment timing optimisation
Current: [describe]. AI opportunity: dynamic discounting recommendation — which invoices to pay early based on supplier discount terms vs our cost of capital?

Step 5 — Supplier query handling
Current: [describe]. AI opportunity: AI draft responses to standard supplier queries based on AP_CHECKS_ALL payment status.

For each step: current baseline metric, target metric with AI, specific tool, implementation effort, and data source in Oracle R12.

You are a finance automation architect. Evaluate our top 10 manual finance processes and recommend whether Robotic Process Automation (RPA), AI (large language model / generative AI), traditional rule-based automation, or a human-in-the-loop hybrid is most appropriate for each:

The 10 processes: [list your actual processes, or use these defaults: (1) Monthly VAT return data extraction from R12, (2) Invoice coding review for non-PO invoices, (3) Intercompany reconciliation, (4) Bank statement reconciliation, (5) Fixed asset register update, (6) Expense claim VAT recovery review, (7) Intrastat data preparation, (8) Regulatory change monitoring and summarisation, (9) Tax provision calculation, (10) Audit data room preparation]

For each process, score 1–5 on:
• Rule complexity: is the logic fixed (1) or highly variable/judgement-based (5)?
• Input variability: always structured data (1) or unstructured/variable format (5)?
• Volume: low volume (1) or very high volume (5)?
• Error consequence: low-risk error (1) or high financial/regulatory risk (5)?
• Change frequency: process never changes (1) or changes constantly (5)?

Then recommend: RPA (best for high-volume, rule-based, structured, stable), AI (best for variable input, judgement-based, unstructured), Rule-based (best for simple, stable, low-volume), Hybrid (human review of AI output for high-consequence items).

For each recommendation: specific tool suggestion, estimated implementation cost, expected annual saving, and implementation timeline. Sort output by ROI.

You are an organisational design specialist for finance functions. Draft an operating model for a future AI-augmented tax function at a European multinational, assuming a 3-year transformation horizon:

Current function: [describe — e.g., 12 FTEs: Head of Tax, 2 tax managers, 4 tax specialists, 3 VAT compliance analysts, 1 tax technology lead, 1 coordinator. Main activities: VAT compliance, transfer pricing, tax accounting, e-invoicing, R12 support, external advisor management]

AI tools assumed available: Copilot Pro, custom LLM-powered prompts, automated data extraction from Oracle R12 and data lake, IDF e-invoicing platform.

Define the target operating model across:

1. Roles that evolve significantly
For each role: current activities → activities removed (automated) → activities added (oversight, AI-augmented, higher value) → net skill change required → reskilling investment.

2. New roles required
Describe 2–3 new roles the function will need: title, purpose, skills required, reporting line.

3. Technology stack
Map: AI tool → process it supports → human oversight model → governance.

4. Governance model for AI-generated outputs
For each output type (VAT return, advisory memo, regulatory alert, reconciliation): quality assurance steps, sign-off required, documentation retained.

5. Productivity model
Show: current FTE × hours on each activity vs target. Does the function grow, shrink, or redeploy? What is the upskilling investment required?

6. Change management for the team
How do you bring the existing team on this journey? Training plan, engagement approach, milestone recognition.

You are a GL and automation specialist. Analyse our journal entry process and identify which journal types are suitable for AI-assisted automation, which for full automation, and which must remain fully manual:

Journal types in scope: [list — or use: Monthly accruals (recurring), Monthly accruals (judgement-based), Intercompany elimination entries, FX revaluation journals, Tax provision journals, Fixed asset depreciation, Payroll journals, VAT clearing journals, Bad debt provisions, One-off reclassifications]

For each journal type, assess:
1. Recurring pattern: does this journal follow the same pattern every period? (Y/N/Partial)
2. Data source: where does the input data come from? (Oracle table, spreadsheet, external system, manual estimate)
3. Judgement required: is human judgement needed to determine the amount or account? (None / Some / High)
4. Materiality: what is the average monthly value and the consequence of error?
5. Automation recommendation: Full automation (prepare + post) / AI-assisted (AI prepares, human reviews and posts) / Template-assisted (AI populates template, human validates inputs) / Fully manual (cannot be automated safely)
6. Specific automation approach: which Oracle R12 functionality, data lake query, or AI prompt would implement this?
7. Control requirement: what compensating control is needed if automation is applied?

Output as a table. Append: (a) estimated annual hour saving by journal type, (b) implementation sequence (quick wins first), (c) the Oracle R12 journal import template fields for the top 3 automatable journal types.

You are a shared services transformation director. Design an AI enhancement plan for our Finance Shared Services Centre (SSC) covering the key service lines:

SSC profile: [describe — location, headcount, services in scope, current technology, SLA performance, key pain points reported by business users]

Service lines to cover: (1) Transaction processing (AP invoice processing, AR cash application, GL journal posting), (2) Query management (supplier queries, customer queries, internal finance helpdesk), (3) Reporting (standard management reports, statutory pack preparation, intercompany reports), (4) Reconciliations (bank, intercompany, balance sheet), (5) Exception handling (payment holds, invoice disputes, VAT discrepancies)

For each service line: (a) Current SLA and performance against it, (b) Top 3 pain points (quantified where possible), (c) AI tool to apply and specific use case, (d) Expected SLA improvement, (e) FTE impact (redeployment or efficiency), (f) Implementation approach and timeline, (g) Change management considerations for SSC team.

Conclude with: (1) Prioritised implementation roadmap showing quick wins vs multi-quarter programmes, (2) Investment summary (one-time + ongoing), (3) Benefits case (time saving + error reduction + SLA improvement + FTE redeployment opportunity), (4) Governance model for AI quality assurance in the SSC context.

You are a VAT compliance manager. Build a comprehensive VAT compliance calendar for all entities and jurisdictions in scope for [year]:

Entities and jurisdictions: [list — e.g., Canon NL (Netherlands, EU VAT), Canon DE (Germany, EU VAT, OSS), Canon FR (France, EU VAT), Canon BE (Belgium), Canon UK (UK VAT post-Brexit), etc.]

For each entity × jurisdiction combination, produce a month-by-month calendar covering:
• VAT return filing deadline (standard and extended where applicable)
• Payment deadline (note where payment date differs from filing date)
• Intrastat Arrivals filing (if above threshold)
• Intrastat Dispatches filing (if above threshold)
• EC Sales List / Recapitulative Statement filing
• OSS return (if applicable) — quarterly, due 31st of month following quarter
• Annual return or reconciliation (where applicable)
• Any country-specific obligation (e.g., Spain SII real-time reporting, Portugal SAF-T, Italy esterometro)

Output format: 12-column table (Jan–Dec) with a row per obligation per entity. Use colour coding described in text: Green = normal, Amber = extended deadline available, Red = hard deadline with automatic penalty.

Append: (a) a "busiest periods" summary showing which months have the highest compliance burden, (b) a resource planning note recommending when annual leave should be restricted, (c) a "first-time in a new year" checklist covering threshold resets, new rates effective from January, and updated form versions.

You are a VAT compliance quality reviewer. Analyse the following VAT return data and identify all anomalies, unusual patterns, and items requiring investigation before submission:

Return data: [paste the return workings — or describe: "Netherlands VAT return for [period], Box 1a: EUR X, Box 1b: EUR Y, Box 4a: EUR Z, etc." — include prior period comparatives and year-to-date figures]

Analyse for: (1) Unusual ratios — effective VAT rate vs expected rate given our business mix, input recovery rate vs prior periods, Box-by-box variances vs prior period (flag anything >15% with no known business reason), (2) Large round number items (potential estimation risk), (3) Items that should appear but are absent (e.g., no reverse charge on IT services received from US vendors in a period where we know purchases occurred), (4) Items that appear but may be incorrect (e.g., VAT on intercompany transactions that should be outside scope), (5) Timing issues — are there accruals that should be in a different period? (6) Cross-check: does the VAT return figure agree to the GL VAT control account, the ZX_LINES SSOT, and the bank payment? Identify reconciling items.

Output as a risk matrix: Finding | Box/Line affected | Amount at risk | Root cause hypothesis | Action required | Owner | Deadline. Assign an overall submission risk rating (High / Medium / Low) and state whether the return is ready to submit or requires further investigation.

You are an Oracle R12 eBTax specialist. Review our current reverse charge configuration and identify scenarios where the system fails to self-assess and recommend corrective configuration:

Current configuration: [describe — e.g., "We have reverse charge tax rules in eBTax for EU services received from non-EU suppliers. The rules fire based on the supplier's country (AP_SUPPLIER_SITES_ALL.COUNTRY) and the AP invoice type. We are not applying reverse charge to intra-EU services received from EU-registered suppliers where we are the recipient."]

Step 1 — Identify all reverse charge scenarios applicable in our jurisdictions
List: (a) Services received from non-EU suppliers (Article 196 VAT Directive), (b) Intra-EU services received from EU suppliers (B2B service rule), (c) Domestic reverse charge categories (construction, mobile phones, emissions certificates per country), (d) Imports of services — any scenarios where IOSS or import VAT interacts.

Step 2 — For each scenario, test whether R12 currently self-assesses correctly
Provide the Oracle AP transaction setup (supplier site country, invoice type, tax classification code, AP_INVOICE_LINES_ALL.TAX_CLASSIFICATION_CODE populated?) and the ZX_LINES output (SELF_ASSESSED_FLAG = 'Y'?). Identify failures.

Step 3 — Root cause each failure
For each failure: is it a missing eBTax rule? Incorrect rule sequence? Master data issue (supplier site country missing)? Tax classification code mapping error?

Step 4 — Recommend configuration changes
For each fix: specify the eBTax rule change (Regime, Tax, Status, Rate, Rule Type, Determining Factor), test case to validate, and rollout approach (can we apply retroactively?).

Step 5 — Estimate financial exposure
For each uncorrected period: AP invoice value × missed reverse charge rate = exposure. Recommend voluntary disclosure or correction on next return.

You are a senior VAT controversy specialist. Draft a formal response to the following tax authority information request:

Authority: [country tax authority name]
Reference: [authority reference number]
Date of request: [date]
Response deadline: [date]
Topic: [describe — e.g., "Authority is requesting explanation of the zero-rating applied to our services supplied to non-EU customers in periods [YYYY–YYYY], specifically requesting: (a) copies of all relevant contracts, (b) evidence of where services were performed, (c) explanation of our VAT treatment with legal basis, (d) list of all supplies in scope with values"]

Our position: [describe — e.g., "We zero-rate these services under Section X of the VAT Act on the basis that the services are specifically connected with land outside the EU. We believe this is correct based on the following case law..."]

Draft the response as a formal letter covering:
1. Opening: acknowledge the request, state the scope of our response
2. Background: brief factual description of our business and the transaction type in question
3. Our VAT treatment: set out the position clearly with legal basis (statute + case law)
4. Response to each specific question raised (numbered to match their request)
5. List of enclosed documents
6. Any caveats or limitations on the information provided
7. Offer to discuss / meet if the authority has further questions

Flag within the draft: [WEAK POINT] where our position is less robust, [STRONG EVIDENCE] where we have compelling support, and [CONFIRM BEFORE SENDING] where you need to verify a fact. Professional formal tone throughout.

You are a VAT compliance manager. Design a robust monthly VAT reconciliation procedure that links the GL, the VAT return, the ZX_LINES SSOT, bank payments, and any open assessments — creating an auditable end-to-end trail:

Entity: [entity name]
Jurisdiction: [country]
ERP: Oracle R12
Reporting periods: Monthly

The procedure must define:

Step 1 — GL VAT account extraction
Which GL accounts are included in the VAT control (list GL natural account codes). Oracle query: select from GL_BALANCES where CODE_COMBINATION_ID in (select from GL_CODE_COMBINATIONS where SEGMENT3 in [list]). Expected output format.

Step 2 — ZX_LINES SSOT reconciliation
Extract total TAX_AMT from ZX_LINES for the period, split by APPLICATION_ID (AP=200, AR=222) and SELF_ASSESSED_FLAG. Compare to GL VAT balance. Maximum acceptable variance: [EUR threshold].

Step 3 — VAT return figure reconciliation
Map each return box to the ZX_LINES data extract. For each box: data source, calculation, expected reconciling items (e.g., Box 5 net payment = Box 1 output tax − Box 4 input tax, adjusted for any prior period corrections).

Step 4 — Bank payment reconciliation
Confirm payment posted to bank matches the return figure. Flag any instalment payments or deferred payment arrangements.

Step 5 — Open items review
List any items in the GL VAT account that are aged > 90 days. Investigate and clear or escalate.

Step 6 — Sign-off and documentation
Preparer certification, reviewer sign-off, document retention location, escalation trigger.

Include: exception threshold table, standard journal templates for common reconciling items, and the monthly timetable (which task by which day of the month).

You are a VAT bad debt relief specialist. Design the end-to-end process for identifying, claiming, and monitoring VAT bad debt relief in [country]:

Legal framework: [country] VAT bad debt relief is available under [legislation reference]. Key conditions: (a) debt must be [X months] overdue from the later of the invoice due date or the date of supply, (b) the debt must have been written off in the accounts, (c) the output VAT must have been accounted for and paid to the authority, (d) [any other conditions — e.g., customer notification requirement, proof of insolvency].

Step 1 — Identification
Oracle R12 query: extract from AR_PAYMENT_SCHEDULES_ALL where STATUS='OP' and DUE_DATE < (SYSDATE minus [threshold days]) and AMOUNT_DUE_REMAINING > 0. Join to RA_CUSTOMER_TRX_ALL for VAT amounts. Join to ZX_LINES for TAX_AMT to confirm VAT was accounted for.

Step 2 — Eligibility validation
For each identified debt: (a) confirm write-off has been approved in the accounts (evidence required), (b) confirm original output VAT was paid in the return for the period of supply, (c) check whether any payment has been received since the invoice date that reduces the claim, (d) check whether the customer has been placed into insolvency proceedings (if this affects the claim procedure).

Step 3 — Claim preparation
Calculate: VAT element of the bad debt = gross outstanding × (standard rate / (1 + standard rate)). Prepare claim schedule: invoice reference | original VAT amount | amount already recovered | net claim.

Step 4 — Return inclusion and documentation
Specify which return box to include the claim. Documentation to retain: write-off authorisation, aged debt report, original invoice, evidence of debt pursuit.

Step 5 — Monitoring
If the customer subsequently pays after relief has been claimed, repayment obligation arises. Set up Oracle AR watch-list for any cash received against written-off invoices.

You are a VAT group compliance manager. Design a comprehensive monthly VAT group reporting package template that can be completed by each group member and consolidated at the group level:

VAT group jurisdiction: [country]
Group members: [list — e.g., Parent Co, Sub A, Sub B, Sub C]
Group representative member: [name]

The reporting package must contain the following schedules:

Schedule 1 — Intra-group supplies (informational only, not on return)
Table: Supplier member | Recipient member | Nature of supply | Amount exc. VAT | VAT rate | VAT amount | Invoice reference. Note: intra-group supplies are disregarded for VAT return purposes — this schedule is for transfer pricing and internal monitoring only.

Schedule 2 — External output tax (by member)
Table: Member | Transaction type (goods/services/exempt) | Net amount | VAT rate | VAT amount | Return box.

Schedule 3 — Input tax (by member and category)
Table: Member | Expense category | Gross amount | Input VAT claimed | Recovery rate applied | Blocked amount | Net VAT recovered | Return box.

Schedule 4 — Partial exemption calculation
Group-level calculation: total taxable turnover / total turnover = recovery percentage. Show each member's contribution. Show rounding adjustments.

Schedule 5 — Prior period adjustments and exceptional items
Any corrections to prior periods, one-off items, or estimated figures pending confirmation.

Schedule 6 — Group return summary
Consolidated figures feeding each return box. Sign-off section: Preparer, Reviewer, Authorised Signatory, Date.

Also define: submission deadlines from each member to the representative, escalation procedure for late submissions, amendment procedure if a member discovers an error after the group return is filed.

You are a VAT compliance director. Conduct a VAT compliance health check for [entity] covering the last [X] years. This health check should be thorough enough to identify issues before an external audit and to inform our risk reserve calculation:

Structure as a numbered checklist across 10 domains. For each item: status (✓ Confirmed / ⚠ Needs Review / ✗ Issue Found / N/A), finding, evidence reviewed, and recommended action.

1. REGISTRATION
□ VAT registration certificate current and correct legal name/address?
□ All new business activities reviewed for registration triggers?
□ Any deregistration obligations missed?

2. FILING TIMELINESS
□ All returns filed by deadline for each period?
□ Any late filing penalties? Status of appeals?

3. RATE APPLICATION ACCURACY
□ Sample test of 50 sales invoices — correct rate applied to each?
□ Any rate changes in the period properly implemented?

4. INPUT TAX RECOVERY
□ Partial exemption calculation reviewed by external advisor in last 3 years?
□ Capital goods scheme register complete and adjustments calculated?
□ Blocked input tax (entertainment, private use) correctly identified?

5. REVERSE CHARGE COMPLIANCE
□ All services received from overseas suppliers self-assessed?
□ Domestic reverse charge applied where applicable?

6. ZERO-RATING DOCUMENTATION
□ Evidence of export / intra-EU supply on file for all zero-rated sales?
□ VIES validation of customer VAT numbers documented?

7. INTERCOMPANY TRANSACTIONS
□ All intra-group supplies correctly treated for VAT?
□ Transfer pricing adjustments reviewed for VAT impact?

8. E-INVOICING
□ Compliance with all mandatory e-invoicing requirements in our jurisdictions?

9. RECORD RETENTION
□ VAT records retained for statutory period in accessible format?

10. TRAINING AND AWARENESS
□ Key AP/AR staff trained on VAT requirements in last 12 months?

Conclude with an overall health score (1–10), top 3 priority remediation items, and estimated external advisor cost to rectify identified issues.

You are an Oracle R12 data specialist and VAT compliance analyst. Write the SQL queries needed to reconcile our Intrastat, EC Sales List, and VAT return figures to a single source of truth, identifying any discrepancies between filings:

Context: We file VAT returns, ESL, and Intrastat for [list of entities and countries]. All three filings should be consistent: the same intra-EU dispatch value should appear in Box 3 of the VAT return, on the ESL, and as Intrastat dispatch value (with some differences for statistical value vs invoice value).

Write the following queries against our Oracle R12 / data lake schema:

Query 1 — Intra-EU supplies for VAT return (Box 3)
SELECT entity, period, SUM(taxable_amt) as intra_eu_supplies
FROM zx_lines
WHERE tax_regime_code LIKE 'EU_%' AND self_assessed_flag = 'N' AND application_id = 222
  AND tax_determine_date BETWEEN :start_date AND :end_date
GROUP BY entity, period;

Query 2 — EC Sales List values (from AR transactions)
[Write this query joining RA_CUSTOMER_TRX_ALL, HZ_CUST_ACCOUNTS, HZ_PARTIES, and filtering for EU customers with zero-rated supplies]

Query 3 — Intrastat dispatch values
[Write this query from the relevant Intrastat data source — specify if this is a custom table, MTD filing data, or extracted from Oracle inventory movement tables]

Query 4 — Reconciliation query
[Write a query that joins the three outputs above and shows variance by entity × period, flagging any variance above EUR 1,000]

For each query: add inline comments explaining each join condition and filter, list the Oracle tables used with their schema prefix, note any data quality assumptions, and flag fields that may be NULL if master data is incomplete.

You are a VAT compliance and systems specialist. Design an automated VIES (VAT Information Exchange System) validation procedure that integrates with Oracle R12 to ensure customer VAT numbers are valid before zero-rating intra-EU supplies:

Business requirement: Before applying zero-rate to an intra-EU B2B supply, we must confirm the customer's VAT number is valid on VIES on the transaction date. Evidence of this check must be retained for audit purposes.

Step 1 — Identify the validation trigger points
At what points in the Order-to-Cash process should VIES validation occur? Define: (a) New customer creation in HZ_PARTIES, (b) Order creation in OE_ORDER_HEADERS_ALL, (c) Invoice creation in RA_CUSTOMER_TRX_ALL, (d) Monthly batch check of all active EU customers.

Step 2 — VIES API integration design
VIES provides a SOAP API. Describe the integration design: input (member state code + VAT number), expected response (valid/invalid + registered name/address), error handling (API unavailable → fallback procedure), logging to a custom Oracle table (specify table structure and fields to capture: VAT_NUMBER, MEMBER_STATE, VALIDATION_DATE, RESULT, TRADER_NAME, TRADER_ADDRESS, REQUEST_IDENTIFIER).

Step 3 — Oracle R12 data model changes
Where is the validation result stored? Recommend: add DFF (Descriptive Flexfield) to HZ_CUST_ACCOUNTS for VIES_VALIDATION_DATE and VIES_VALIDATION_RESULT, or create a custom table XXCNL_VIES_VALIDATIONS with the fields above. Write the DDL for the custom table.

Step 4 — Downstream impact on zero-rating
Specify the eBTax rule condition: "Zero-rate intra-EU supply only if HZ_CUST_ACCOUNTS.VIES_VALIDATION_RESULT = 'VALID' AND VIES_VALIDATION_DATE >= invoice date − 30 days."

Step 5 — Exception handling
Customer VAT number invalid on VIES but customer insists they are registered: escalation procedure, who approves override, documentation required.

Step 6 — Monthly reporting
Oracle query to list all zero-rated invoices where VIES validation is older than 90 days or missing.

You are an AI change management specialist. Conduct an AI readiness assessment for [team name — e.g., Tax Compliance team, 12 people] to inform the design of our AI adoption programme:

Assessment dimensions (score each 1–5 based on evidence gathered, not self-assessment):

1. Data maturity: Is the team's core data structured, accessible, and trustworthy? Score based on: data lake availability, Oracle R12 data quality, dependency on Excel vs system data, proportion of processes that already have digital data inputs.

2. Process documentation: Are processes written down? Score based on: existence of written procedures, process maps, desk instructions. High score = AI can be trained/prompted on documented process; low score = process lives in people's heads.

3. Digital literacy: Can team members use AI tools independently? Score based on: current Copilot usage data, Excel proficiency, comfort with new technology, prior experience with automation.

4. Change appetite: Is the team willing to change how they work? Score based on: leadership signals observed, team sentiment from 1-on-1s, history of adopting previous technology changes.

5. Leadership support: Does leadership actively enable AI adoption? Score based on: budget allocated, time ring-fenced for learning, leaders publicly using AI themselves, AI included in performance objectives.

6. Use case clarity: Does the team have specific, concrete AI use cases they want to solve? Score based on: number of identified use cases, quality of problem framing, alignment to business value.

For each dimension: score (1–5), evidence basis, key barrier, and recommended intervention. Produce an overall readiness score and place the team on a maturity matrix: Laggard / Follower / Early Adopter / Leader. Design a 90-day activation plan tailored to their specific score profile.

You are an AI learning and development specialist. Design a 12-week AI enablement programme for finance professionals, differentiating between Copilot Chat (browser-based) and Copilot Pro (integrated in M365) tracks:

Learner profile: Finance and Tax professionals with varying Excel proficiency. Not technical. Primary goal: use AI to do their current job better, faster, and with fewer errors. Not interested in coding.

Programme design principles: (1) Every session must include a hands-on exercise with a real finance task, (2) No more than 90 minutes per week of structured learning — must fit around their day job, (3) Each week builds on the previous, (4) Include peer sharing — one person per week shares their best prompt or time saving.

Week-by-week curriculum:
Weeks 1–3: Foundations
• Week 1: What AI can and cannot do — calibrating expectations. Exercise: use AI to summarise a tax regulation you actually need to understand.
• Week 2: Prompt anatomy — Role, Task, Context, Format, Constraints. Exercise: rewrite three of your existing email templates as AI prompts.
• Week 3: First real use case — AI-assisted research. Exercise: use AI to research [specific VAT question relevant to their work].

Weeks 4–6: Core workflows
[Continue this structure through week 12, covering: data analysis with Copilot, document drafting, meeting preparation, regulatory monitoring, email management, Excel data tasks]

For each week: learning objective, content (30 min), exercise (45 min), peer share topic, take-away prompt template. Include assessment criteria for graduation and a "certification" badge design concept.

You are a responsible AI governance specialist. Develop a Responsible AI Framework for the Finance and Tax function that balances enabling AI use with appropriate risk management:

Context: Our function is adopting Microsoft Copilot Pro and custom AI prompts for tasks including VAT research, compliance memo drafting, data analysis, and regulatory monitoring. We operate in regulated environments where AI output errors could result in financial penalties, reputational damage, or incorrect advice to business partners.

The framework must define:

1. Acceptable use cases (tiered by risk)
Tier 1 — Low risk (AI output used directly): Research summarisation, meeting minutes, email drafts, translation.
Tier 2 — Medium risk (AI output reviewed before use): Compliance memos, regulatory analysis, process documentation.
Tier 3 — High risk (AI output reviewed by subject matter expert before any business reliance): Tax advice, VAT return inputs, audit defence documents, external communications.
Tier 4 — Prohibited: AI making autonomous decisions, AI accessing confidential client data without consent, AI generating synthetic financial data presented as real.

2. Data handling rules
What data can be entered into AI prompts? What must never be entered (personal data, client confidential information, unpublished financial results, M&A sensitive information)? How do we classify data before deciding to use AI?

3. Validation requirements by tier
For each tier: what review steps are required, who signs off, what documentation is retained?

4. Disclosure requirements
When must we disclose to a recipient that AI was used to prepare a document? What disclosure language do we use?

5. Incident reporting
If AI produces materially incorrect output that is acted upon: reporting procedure, root cause analysis, remediation.

6. Governance
Who owns the framework? Review cadence. How are new use cases assessed before adoption?

Format: formal policy document with numbered sections, a one-page quick reference card, and a use-case classification flowchart.

You are a Microsoft 365 Copilot product specialist and finance transformation advisor. Analyse the Microsoft 365 Copilot product roadmap and map upcoming features to specific Tax and Finance use cases, estimating when each feature will be production-ready for our environment:

Copilot features to assess (include latest roadmap items as of your knowledge cutoff, and flag where you are uncertain about availability dates): Copilot in Excel (data analysis, formula generation, Python integration), Copilot in Word (document drafting, summarisation), Copilot in Outlook (email drafting, meeting preparation), Copilot in Teams (meeting notes, action extraction), Copilot Pages (collaborative AI output), Copilot Studio (custom agent building), Microsoft 365 Copilot extensibility (plugins, Graph connectors), Copilot for Finance (coming feature — reconciliation, variance analysis), Copilot with SharePoint (document Q&A), Copilot with Power BI (natural language data querying).

For each feature: (1) Feature description — what it does, (2) Availability status: GA / Preview / Announced / Rumoured — flag your confidence level, (3) Specific Tax/Finance use case — describe a concrete scenario in our environment, (4) Prerequisites: licence, M365 version, IT configuration, (5) Estimated productivity impact: High/Medium/Low with reasoning, (6) Implementation effort: plug-and-play / configuration needed / custom development, (7) Our recommended adoption priority.

Append a "watch list" of 3–5 features not yet available that would be transformative for our function when they arrive, with an indication of what to do today to prepare.

You are an organisational change specialist. Design an AI Champions Network for the Finance function at Canon. The network should drive grassroots AI adoption, reduce the load on the central AI/tech team, and create self-sustaining momentum:

Network purpose: Identify, develop, and empower a network of 8–12 finance professionals who are enthusiastic early AI adopters and willing to support their colleagues. Champions are not the most senior people — they are the most curious and helpful.

Design the network across six components:

1. Selection criteria
What makes a good champion? Define 5–7 criteria. How do we identify them (self-nomination, manager nomination, data on Copilot usage)? How many champions per team/location?

2. Role definition
What do champions actually do? Be specific: time commitment per week, activities (peer support, prompt sharing, onboarding new colleagues, testing new features, feeding back issues to the AI team), what they do NOT do (they are not IT helpdesk, not responsible for governance).

3. Training pathway
How do champions develop beyond standard user training? Define: baseline requirement, advanced curriculum (3 modules), access to beta features, connection to Microsoft's champion community.

4. Recognition and motivation
How do we keep champions engaged? Non-financial recognition ideas that work in a corporate environment. Visibility to leadership. Career development angle.

5. Governance and coordination
How does the champion network connect to the AI steering group? Monthly champion call agenda template. How are champions replaced when they move roles?

6. Success measurement
How do we know the network is working? Define 3–5 metrics with measurement method and target.

Output as a formal network charter document.

You are an L&D specialist and AI prompt engineer. Design a three-level prompt engineering certification programme specifically for tax and finance professionals:

Level 1 — Foundation (Accessible to all finance staff)
Competency: Can write effective single-turn prompts for research, summarisation, and drafting tasks using the CONTEXT method.
Assessment: Write 3 prompts from a set brief (one research, one draft, one analysis). Assessed on: role clarity, specificity, format instruction, constraints. Pass mark: 2 of 3 rated "Effective" by assessor.
Time to complete: 4 hours self-study + 1 hour assessed exercise.
Badge: "AI-Fluent Finance Professional"

Level 2 — Intermediate (For regular power users)
Competency: Can design multi-step prompt workflows, build reusable prompt templates, provide effective examples (few-shot prompting), and critically evaluate AI output quality.
Assessment: Submit a prompt library of 10 prompts for their specific role, with evidence of real-world use and output quality commentary. Plus a 30-minute practical test.
Prerequisites: Level 1 certified + minimum 60 days active Copilot usage.
Time to complete: 8 hours self-study + peer review + assessment.
Badge: "AI Prompt Engineer — Finance"

Level 3 — Advanced (For champions and team leads)
Competency: Can design custom agents using Copilot Studio, build prompt chains that call data sources (SharePoint, data lake), evaluate and govern AI use in their team, and train others.
Assessment: Build and demonstrate a working custom prompt workflow that delivers measurable time saving in a real finance process. Present to a panel.
Prerequisites: Level 2 certified + nominated by line manager.
Time to complete: 16 hours self-study + project + panel presentation.
Badge: "AI Transformation Lead — Finance"

For each level: full curriculum outline (topics and learning objectives), resource list, assessment rubric, renewal requirement (annual), and how the certification is recorded in our HR system.

You are a tax technology analyst and AI strategy advisor. Produce a competitive landscape analysis examining how peer multinationals and leading tax functions are using AI, to inform Canon's AI adoption strategy:

Research scope: Focus on companies of comparable size (EUR 3–30bn revenue, European-headquartered multinationals) in technology, manufacturing, and distribution sectors. Sources: publicly available information — conference presentations, published case studies, vendor references, professional body surveys (KPMG, Deloitte, EY, PwC tax technology surveys), LinkedIn thought leadership.

Structure the analysis as:

WHAT LEADING TAX FUNCTIONS ARE DOING WITH AI (by use case category)
For each category (VAT compliance, e-invoicing, transfer pricing, tax provision, audit defence, regulatory monitoring): What are the most advanced companies doing? What tools are they using? What measurable outcomes have they reported?

WHERE CANON IS RELATIVE TO PEERS
Honest assessment: which capabilities put us ahead, which are table stakes we must match, which are differentiators we should aspire to?

BEST PRACTICES TO ADOPT (top 5)
For each: what it is, who is doing it, what we would need to implement it, and the expected benefit.

PITFALLS TO AVOID (top 3)
What have early adopters done wrong? Specific failure modes: over-reliance on AI output, data privacy breaches, productivity gains that disappeared when AI made errors, change management failures.

EMERGING CAPABILITIES TO WATCH
3–5 AI capabilities not yet widely adopted but likely to become important in 2–3 years. For each: what it is, who is developing it, when it might be production-ready, and what we should do today to prepare.

Keep each bullet to 2–3 sentences maximum. Cite sources where available.

You are a data strategy and AI architect. Develop a data strategy for enabling AI in the Tax function, covering the full data value chain from source systems to AI-ready datasets:

Current data landscape: [describe — e.g., "Oracle R12 is our primary ERP; we have a data lake in [technology] with tables from Oracle, Orion, and IDF; data quality is inconsistent; most tax analysis still done by extracting to Excel; no single source of truth for tax reporting"]

The data strategy must address six pillars:

1. Data sources and integration
Map all data sources relevant to tax (Oracle R12 tables, Orion, IDF, external regulatory data, VIES API, customs data). For each: current availability in the data lake, update frequency, data quality rating, and integration priority.

2. Data quality requirements for AI
AI produces better output when input data is high quality. Define minimum quality standards for the top 10 data elements most used in tax AI prompts. Include: completeness threshold, accuracy validation rule, and current gap.

3. Data architecture recommendations
Should we build a tax-specific "gold layer" in the data lake? Define what tables it contains, how it is populated, who maintains it. Recommend: medallion architecture (bronze/silver/gold) applied to tax data.

4. Governance
Who owns each data domain? How are schema changes to Oracle R12 notified to the data lake team? How is data lineage documented?

5. Privacy and compliance
Which data elements contain personal data (GDPR)? What anonymisation or pseudonymisation is required before data is used in AI prompts? How do we manage data residency requirements?

6. Roadmap
Phase 1 (3 months): quick wins — which existing data is AI-ready today?
Phase 2 (6 months): quality improvement programme.
Phase 3 (12 months): gold layer build and advanced AI use cases enabled.

You are an innovation programme manager. Design a structured innovation pipeline process for Finance AI ideas — from initial idea capture through pilot, scaling, and eventual retirement:

Problem: Good AI ideas emerge from the team informally but are never systematically captured, evaluated, or progressed. Some are tried, fail quietly, and are never analysed. Others succeed but are never scaled. We need a repeatable, lightweight process that does not create bureaucracy but does create accountability.

Design the pipeline across five stages:

Stage 1 — Ideation (always open)
How do team members submit ideas? Design a simple one-page "Idea Canvas" template: (a) Problem statement (what pain are you feeling?), (b) Proposed AI solution (what would it do?), (c) Who benefits and how many people? (d) Rough effort estimate: hours to try vs hours saved per month, (e) Data needed.
Submission channel. Who reviews? Frequency of review.

Stage 2 — Evaluation (monthly)
Assessment criteria: business value (1–5), feasibility (1–5), strategic fit (1–5), implementation effort (1–5). Who scores? How are ties broken? Output: Approve for pilot / Park / Reject with reason.

Stage 3 — Pilot (30–60 days)
What does a pilot look like? Define: minimum viable prompt or tool, success criteria (pre-agreed), measurement method, owner. What resources can a pilot access without additional approval?

Stage 4 — Scaling decision
Pass/fail criteria for moving from pilot to full adoption. If pass: who builds the production version? How is it documented and maintained? If fail: what is captured in the lessons-learned log?

Stage 5 — Retirement
When should we retire an AI tool or prompt? Define triggers: superseded by better approach, underlying data changed, accuracy degraded, team no longer uses it. Who makes the retirement decision? How is it communicated?

Append: a pipeline dashboard template showing all ideas by stage, and a quarterly innovation review meeting agenda.

You are the Tax Technology Manager. Create a one-page technology strategy document showing how AI, e-invoicing (IDF), and the data lake converge to create a modern tax function over the next 18 months. Audience: CFO and CIO. Purpose: alignment on direction, priorities, and interdependencies.

Structure as a single A4 page (or one dense slide) with the following sections:

VISION STATEMENT (one sentence): What does the modern Canon tax function look like in 18 months?

CURRENT STATE (3 bullets): The three most significant limitations of today's technology setup.

THE THREE PILLARS (diagram description):
Pillar 1 — E-invoicing (IDF): Status, countries live/in progress, what it delivers (compliance + data).
Pillar 2 — Data Lake: What data is available today, what we are adding, what becomes possible.
Pillar 3 — AI (Copilot + custom prompts): What is live today, what is next, what it enables.

THE CONVERGENCE THESIS (the key insight, 2–3 sentences):
Why these three pillars together are more valuable than each alone. Specifically: e-invoicing generates structured real-time data → data lake makes it queryable → AI makes it actionable for humans without technical skills.

18-MONTH ROADMAP (timeline strip):
Quarters 1–6 with 2–3 milestones per quarter, colour-coded by pillar.

KEY ENABLERS REQUIRED:
What we need to make this happen — list 3–5 items (budget, headcount, IT capacity, vendor contracts, data governance decisions). For each, who needs to decide.

WHAT SUCCESS LOOKS LIKE:
3 measurable outcomes by month 18 that prove the strategy worked.

Format: this should be dense but readable in 5 minutes. No jargon. Diagrams described in text. Use numbers wherever possible.

You are a technology procurement specialist. Build a weighted scoring matrix to evaluate competing vendors for [vendor type — e.g., e-invoicing platform / VAT compliance software / tax data management system / AI-powered contract review tool]:

First, confirm the weighting structure is appropriate for this category. Proposed weights (adjust if needed):
• Functional coverage: 25% — does it do what we need, for all our countries and transaction types?
• Technical architecture: 20% — Oracle R12 integration maturity, scalability, security, API design
• Implementation approach: 15% — methodology, timeline, project governance, local expertise
• Vendor stability: 10% — financial health, client base, ownership, product roadmap commitment
• Support model: 10% — SLA, helpdesk hours, escalation path, account management quality
• Total cost of ownership (5 years): 15% — all-in cost including licence, implementation, BAU, change requests
• References: 5% — quality of references in our sector and geography

For each criterion: define 5 scoring levels (1 = does not meet, 5 = exceeds requirements) with specific descriptions of what each score looks like for this category. This prevents assessors from applying different standards.

Then produce: (a) the blank scoring matrix for completing during the evaluation, (b) a worked example scoring one vendor to calibrate assessors, (c) guidance on how to run a scoring calibration session so multiple assessors reach consistent scores.

Also: add a "must-have / deal-breaker" list — 5 requirements where any score of 1 should automatically disqualify the vendor regardless of total score.

You are a vendor evaluation specialist. Analyse the RFP response from [vendor name] against our published requirements for [system type]:

Our requirements (paste the requirements list or describe): [list your functional and non-functional requirements]
Vendor response: [paste the relevant sections of their response or summarise their claims]

For each requirement, classify the vendor's response as:
✓ FULLY MET — vendor provides the capability out of the box, with evidence (reference client, product demo, documented feature)
~ PARTIALLY MET — capability exists but with gaps (describe the gap) or requires configuration/customisation (estimate effort)
~ MET VIA WORKAROUND — vendor proposes an alternative approach (describe and assess whether the workaround is acceptable)
✗ NOT MET — vendor does not offer this capability
? UNVERIFIED — vendor claims to meet this but provided insufficient evidence (list what evidence is needed)

After classifying all requirements, produce:
1. A summary table: Total requirements | Fully Met | Partially Met | Workaround | Not Met | Unverified
2. A "critical gaps" list — requirements that are NOT MET and are marked as mandatory in our specification
3. A "due diligence deep-dive" list — requirements marked UNVERIFIED where we need a product demonstration or technical workshop before scoring
4. A recommended response to the vendor — what clarifications to request before the scoring deadline
5. A preliminary score for this vendor's functional coverage criterion (out of 5) based on this analysis

You are a technology finance specialist. Build a 5-year total cost of ownership (TCO) model comparing [Vendor A] vs [Vendor B] for [system type]:

Cost inputs for each vendor (provide what you know; AI will flag where assumptions are needed):
[Vendor A]: Licence model (SaaS per user / per transaction / flat fee), implementation quote, annual maintenance %, estimated change request rate, internal resource required.
[Vendor B]: Same structure.

Build the TCO model across the following cost categories:

YEAR 1 IMPLEMENTATION COSTS (one-time)
• Software licence (first year)
• Implementation partner fees
• Internal resource (FTE days × daily rate)
• Infrastructure / hosting setup
• Testing and data migration
• Training

YEARS 1–5 RECURRING COSTS (annual)
• Software licence / subscription
• Annual maintenance / support fee
• Internal administration resource
• Hosting / infrastructure
• Estimated change requests (per year, based on vendor's change request pricing)
• External advisory support (ongoing)

RISK-ADJUSTED COSTS
• Estimated cost of implementation overrun (probability × typical overrun %)
• Estimated cost of vendor lock-in at year 5 (migration cost if we switch)

Output as: (a) Detailed cost table by category × year for each vendor, (b) 5-year total comparison with variance, (c) NPV comparison at [X%] discount rate, (d) Break-even analysis — if Vendor A is cheaper to implement but more expensive annually, in which year does Vendor B become cheaper overall? (e) Sensitivity table: how does the decision change if actual usage is 50% / 100% / 150% of projected volume?

You are a vendor risk and procurement specialist. Prepare a comprehensive due diligence questionnaire for [vendor name] in the context of a [system type] procurement. This questionnaire is intended to identify risks before contract signing:

Section 1 — Financial stability
□ Provide last 3 years audited financial statements
□ Current revenue, ARR, and growth rate
□ Ownership structure — is the company PE-backed? What are the PE fund's expected exit timelines?
□ Customer concentration — does any single customer represent >20% of revenue?
□ Any pending litigation, regulatory investigation, or material disputes?

Section 2 — Product and roadmap
□ Product roadmap for the next 24 months — what is committed vs aspirational?
□ What percentage of R&D spend goes to our specific module?
□ How are product decisions made? Is there a customer advisory board?
□ What is the vendor's policy on deprecated features?
□ Have any major features been removed or degraded in the last 3 years?

Section 3 — Existing customer base and retention
□ Total number of active customers by size segment
□ Annual gross revenue retention rate for the last 3 years
□ Number of customers who have churned in the last 3 years — can we speak with any?
□ Provide 5 reference customers of similar size and complexity — in our industry, using Oracle R12

Section 4 — Support and service
□ Helpdesk hours and languages supported
□ Average first-response time and resolution time by severity (provide data, not targets)
□ Dedicated account manager — who, and what is their client load?
□ Escalation path if standard support fails

Section 5 — Security and data protection
□ Security certifications: ISO 27001, SOC 2 Type II — provide current certificates
□ Sub-processor list and data residency locations
□ Penetration testing frequency and last report summary
□ Data breach history — any incidents in last 3 years?

Section 6 — Contract and commercials
□ Standard contractual SLA commitments
□ Data export rights — can we extract all our data in an open format at any time?
□ Exit clause — what are the conditions and penalties for early termination?
□ Price escalation mechanism — what limits apply to annual price increases?

For each item: add the information we expect to receive and a red flag indicator (what answer would be a deal-breaker or require escalation to legal).

You are a solutions architect specialising in Oracle R12 integrations. Evaluate [vendor name]'s API documentation and integration architecture for compatibility with our Oracle R12 environment:

Our technical context: Oracle R12 version [X], hosted [on-premise / Oracle Cloud], integration middleware [describe — e.g., Oracle SOA Suite / MuleSoft / custom SFTP], data lake technology [describe], typical data volumes: [X invoices per day / Y per month].

Evaluate the vendor's integration approach across seven dimensions:

1. API design quality
REST or SOAP? OpenAPI spec available? Authentication (OAuth 2.0, API key, basic auth)? Versioning policy? Backwards compatibility commitments? Rate limits that could affect our volume?

2. Oracle R12 connector
Do they have a pre-built Oracle R12 connector? If yes: which R12 version was it certified on? Which modules (AP, AR, GL)? Is it maintained by the vendor or a third party? If no: what integration effort is required?

3. Data transformation
Does the vendor handle transformation of R12 data formats to their required format? Or is transformation our responsibility? What data mapping tools are provided?

4. Error handling and monitoring
How are integration errors surfaced? Is there an integration dashboard? What is the retry mechanism for failed messages? How are we notified of failures?

5. Scalability
What is the documented maximum throughput? Have they tested at volumes comparable to ours? What is the degradation curve under load?

6. Security
Is data encrypted in transit and at rest? What is their certificate management approach? Do they support IP whitelisting?

7. Vendor integration support
What integration support is included in the licence? What is available at additional cost? Do they have Oracle R12 integration engineers on staff?

Conclude: overall integration risk rating (Low/Medium/High), estimated internal development effort, recommended integration architecture, and 5 questions to put to the vendor at the technical deep-dive.

You are a financial close specialist. Generate a month-end close checklist for [entity name, country] with period end [date] and group reporting deadline of Day+[X].

Entity profile: Oracle R12, IFRS reporting, [describe entity — e.g., European sales subsidiary with intercompany transactions and lease portfolio].

Structure the checklist in three tiers:
• TIER 1 — Critical path (must complete before anything else can proceed)
• TIER 2 — Parallel workstream (can run simultaneously with other tasks)
• TIER 3 — Final steps (require all above to be complete)

For each item: task description | responsible role | dependency | Oracle module/report | due date (as Day+X) | estimated time | status field.

Flag the top 3 items that, if delayed, would push the group reporting deadline. Include a contingency note for each: what to do if the item is not complete by its deadline.

You are a financial controller. Design a risk-based journal entry review framework for [entity name]:

Journal entry population: approximately [X] journals per month, split approximately [Y%] recurring, [Z%] manual, [W%] system-generated.

The framework should prioritize review effort based on risk, covering:
1. High-risk indicators that trigger mandatory senior review: unusual accounts, round numbers, period-end only, late postings, top-sided entries, reversals not reversed
2. Preparer segregation rules — who cannot review their own entries
3. Documentation standards: what narrative and attachment are required per journal type
4. Threshold-based approval matrix (by EUR amount and by journal type)
5. Post-posting analytical checks — what to scan for next-day

Output as a risk matrix with: Journal type | Risk rating | Review requirement | Approval level | Documentation required | Analytical check.

Also include a one-page quick-reference card for the team.

You are an accounting controller. Write a period-end accruals completeness procedure for [entity], covering the following accrual categories:

• Vendor invoices not yet received (goods/services received, not invoiced)
• Employment costs (holiday pay, bonus, social charges not yet invoiced)
• Utilities and occupancy costs
• Professional services (audit, legal, consulting)
• IT and subscription services
• Intercompany management fees and recharges
• VAT and tax provisions

For each category:
1. Data source for identifying what should be accrued (PO report, open delivery, headcount data, contract schedule)
2. Calculation method (straight-line, percentage of contract, budget-based)
3. Minimum threshold below which no accrual is required (materiality)
4. Oracle AP account coding
5. Reversal — automatic or manual, in which period
6. Sign-off required before posting

End with: how to document and evidence the completeness assessment for audit purposes.

You are a financial controller. Write a balance sheet reconciliation procedure for [entity] covering the following account categories:

• Cash and bank (reconcile to bank statement)
• Trade receivables (reconcile to AR subledger + AR aging)
• Prepayments (reconcile to prepayment schedule)
• Intercompany receivables (reconcile to counterparty confirmation)
• Fixed assets (reconcile to FA register)
• Trade payables (reconcile to AP subledger)
• Accrued liabilities (reconcile to accrual schedule)
• VAT (reconcile to VAT return)
• Intercompany payables

For each account category:
1. Reconciliation frequency (monthly / quarterly)
2. System source for book balance
3. Supporting source for reconciling item
4. Acceptable reconciling items (with documentation required)
5. Unacceptable items that must be cleared before sign-off
6. Sign-off requirement and deadline
7. Maximum aged items policy (unreconciled items >90 days → escalation)

You are an IFRS technical accounting advisor. Build a decision tree to determine the correct accounting treatment for the following transaction:

Transaction: [describe clearly — e.g., "We are entering a contract where we pay EUR 2M upfront to a supplier for exclusive use of a data centre rack for 5 years. The supplier operates the data centre. We can substitute our specific rack with another identical one at any time."]

The decision tree must navigate through:
1. Is this a lease under IFRS 16? (Identified asset test → right to obtain substantially all economic benefits → right to direct use)
2. If not a lease: is it an intangible asset under IAS 38 or a prepaid service cost?
3. If a lease: is it a short-term or low-value lease (practical expedients)?
4. Finance vs operating lease classification (for lessors)
5. What is the measurement basis: cost model vs revaluation model?

For each decision node: the question, the test to apply, the IFRS reference, and which branch to follow for each answer. End with: a worked example using the actual transaction facts.

You are an asset accounting specialist. Prepare a fixed asset disposal analysis for the following:

Asset details:
• Asset category: [e.g., IT equipment / leasehold improvement / vehicle]
• Original cost: [EUR]
• Accumulated depreciation at disposal date: [EUR]
• Net book value at disposal date: [EUR]
• Proceeds received (if any): [EUR / nil]
• Disposal date: [date]
• Reason for disposal: [sale / scrapped / donated / replaced / lease end]

Calculate:
1. Profit or loss on disposal (proceeds minus NBV)
2. Correct journal entry for disposal
3. If an IFRS 16 right-of-use asset: specific derecognition treatment
4. VAT implications of the disposal (if proceeds received)
5. How this appears in the statement of cash flows (investing activities)
6. Any disclosure required in the financial statements

Flag if the asset was part of an impairment or revaluation group — that changes the treatment.

You are a group consolidation specialist. Design a GAAP bridge adjustment schedule template for a subsidiary in [country] filing statutory accounts under [local GAAP standard] and reporting to the group under IFRS.

The schedule must capture, for each adjustment:
• Adjustment ID and description
• Local GAAP treatment and amount
• IFRS treatment and amount
• Adjustment required (Dr/Cr and amount)
• IFRS standard applicable
• Deferred tax impact (temporary or permanent difference?)
• Frequency: one-time or recurring each period
• Evidence/documentation reference

Cover the following adjustment categories for [country]:
1. Revenue recognition (local rules vs IFRS 15)
2. Lease accounting (local rules vs IFRS 16) — identify all leases not recognized locally
3. Employee benefits (local pension or termination pay vs IAS 19)
4. Provisions (local approach vs IAS 37 constructive obligations)
5. Deferred tax (any local rate differences, local exemptions)
6. Financial instruments at amortized cost vs fair value (IFRS 9)

Include a summary total row for: total adjustment to equity, total adjustment to profit or loss, total deferred tax impact.

You are an IAS 21 specialist. Determine the functional currency for the following entity:

Entity: [name, country, legal form]
Primary business: [describe — sales company / manufacturing / holding / treasury / service centre]
Main customers: [country/currencies — describe concentration]
Main suppliers: [country/currencies]
Main costs (labour, rent, utilities): [currencies]
Financing: [currency of main debt / equity injections]
Intercompany transactions: [describe — what is invoiced in which currency]
Management accounts prepared in: [currency]

Apply IAS 21.9–14 primary and secondary indicators:
Primary: currency that mainly influences selling prices; currency of the country whose competitive forces determine selling prices
Secondary: currency of inputs, labour, financing

For each indicator: assess which currency dominates and why.
Conclusion: recommended functional currency with reasoning.
Also address: what changes if the functional currency is different from the local presentation currency? What additional translation is required?

You are a group consolidation specialist. Design an intercompany elimination matrix for the following group structure:

Parent: [Entity A, country]
Subsidiaries: [Entity B, C, D — countries]

Intercompany transaction types to eliminate:
1. Management fees / service charges
2. Dividend payments
3. Intercompany loans (principal and interest)
4. Goods / inventory transfers (including unrealized profit in stock)
5. Intercompany receivables and payables (balancing eliminations)
6. Intercompany revenue and cost (profit and loss eliminations)

For each transaction type create:
• Which entities are involved
• Which entries in Entity A, B, C, D
• What the group-level elimination journal is
• Which IFRS 10 or IAS 27 paragraph governs
• Deferred tax impact at group level
• Risk of error (High/Med/Low) and most common mistake made

Format as a matrix table. Highlight any eliminations that create a deferred tax asset at group level that is not recognized in any subsidiary's standalone accounts.

You are an IFRS 3 business combinations specialist. Prepare a purchase price allocation framework memo for the following acquisition:

Acquired entity: [company name, country]
Acquisition date: [date]
Total consideration: [EUR — cash / shares / contingent consideration]
Provisional net assets at acquisition date (book value): [EUR]
Provisional goodwill (consideration minus book net assets): [EUR]

Scope of the PPA exercise:
1. Identify all intangible assets that must be recognized separately from goodwill (IFRS 3.B31): customer relationships, trade names, technology, order backlog, non-compete agreements
2. For each intangible: fair value method (multi-period excess earnings / relief from royalty / cost approach), useful life, and deferred tax liability
3. Assess inventory at acquisition: is cost = fair value, or is a step-up required?
4. Assess any contingent liabilities requiring recognition at fair value
5. Deferred tax on all PPA adjustments
6. Final goodwill after all adjustments

Set out: measurement timeline (12-month period allowed under IFRS 3), who needs to be involved (valuation specialists), and disclosure requirements in the acquisition-year financial statements.

You are a statutory accounts and audit preparation specialist. Create an audit preparation pack checklist for [entity, country] for the year ended [date]:

The checklist should be organized by audit area and include:

FINANCIAL STATEMENTS:
□ Draft statutory financial statements (in local GAAP format for [country])
□ Supporting schedules for each material balance sheet line
□ Prior year comparative reconciliation
□ Directors' report / management report (if required by local law)

BY AUDIT AREA — for each area, list the schedules and documents to prepare:
• Revenue: recognition workings, contract listings, cut-off evidence
• Receivables: aging, provision calculation, subsequent receipts, disputed balances
• Fixed assets: FA register, additions/disposals, depreciation reconciliation, impairment review
• Leases: IFRS 16 / local lease schedule, contract copies
• Provisions: calculation, basis, historical accuracy analysis
• Tax: CIT provision, deferred tax reconciliation, tax compliance status
• Related party: intercompany confirmations, TP documentation summary
• Going concern: management assessment, cash flow forecast, covenant compliance

For each item: preparer, reviewer, deadline, and file reference. Include a cover page summarizing the audit timeline and key contacts.

You are an IAS 29 specialist. Assess whether IAS 29 Financial Reporting in Hyperinflationary Economies applies to the following subsidiary and, if so, what adjustments are required:

Entity: [company name]
Country: [country]
Functional currency: [currency]
Three-year cumulative inflation rate: [%] (if known)
Latest year inflation rate: [%]

Apply IAS 29.3 qualitative and quantitative indicators:
• Population prefers to hold wealth in non-monetary assets or in a stable foreign currency
• Prices are generally quoted in a stable foreign currency
• Sales and purchases on credit take account of expected loss of purchasing power
• Interest rates, wages, and prices are linked to a price index
• Cumulative inflation over three years approaches or exceeds 100%

If IAS 29 applies:
1. Which assets require restatement (non-monetary vs monetary)?
2. How is the general price index applied to non-monetary items?
3. How are comparative figures restated?
4. What is the translation approach when consolidating into EUR (IAS 21.43)?
5. What disclosures are required?
6. Practical steps for our Oracle R12 team to implement the restatement

You are an IAS 2 inventory accounting specialist. Design a comprehensive inventory provision methodology for [entity], covering the following inventory categories:

• Finished goods — saleable product lines
• Spare parts and service components
• Consumables (toner, ink, paper)
• Work in progress (if applicable)
• Raw materials (if applicable)

For each category, define:
1. Provision trigger: what age or condition triggers a provision review?
2. Provision basis: percentage of cost by aging band (e.g., 25% at 6M, 50% at 12M, 100% at 18M) vs specific identification
3. NRV test: how to estimate net realizable value for each category
4. Write-off threshold: when does a provision become a write-off?
5. Reversal conditions: what would justify reversing a provision?
6. Authorization: who must approve the provision / write-off recommendation?
7. Oracle Inventory: which report provides the aging data?

Include a provision calculation template (tabular format) and the journal entry for provision creation, increase, decrease, and write-off.

You are a cost accounting specialist. Perform a COGS reconciliation and variance analysis for [entity] for the period [month/year]:

Inputs:
• Opening inventory balance: [EUR]
• Purchases / goods received in period: [EUR]
• Transfers in (intercompany): [EUR]
• Expected COGS (standard cost × units sold): [EUR]
• Closing inventory per system: [EUR]
• Actual COGS per GL: [EUR]
• COGS variance (actual vs expected): [EUR]

Analyse:
1. Theoretical COGS cross-check: opening + purchases + transfers − closing = COGS. Does this match?
2. Break down the variance by likely cause: purchase price variance, volume variance, mix variance, FX variance, system timing issue
3. Which Oracle Inventory / Purchasing reports to run for each variance component
4. Materiality assessment: is the variance within acceptable tolerance ([X%] of COGS or [EUR Y])?
5. Proposed journal adjustments (if any)
6. Management commentary for the variance in the monthly reporting pack

Include a formatted reconciliation bridge table.

You are a group consolidation specialist. Calculate and document the intercompany profit in inventory (UPII) elimination for the following group:

Selling entity: [Entity A, country, margin on intercompany sales: [X%] of transfer price]
Buying entities: [Entity B / C / D with inventory held at period end]

Data available:
• Total intercompany inventory held by Entity B at cost: [EUR]
• Total intercompany inventory held by Entity C at cost: [EUR]
• Total intercompany inventory held by Entity D at cost: [EUR]
• Prior period UPII balance (opening): [EUR]

Calculate for each buying entity:
1. UPII in closing inventory = IC inventory × [margin% ÷ (1 + margin%)]
2. Movement in UPII vs prior period
3. Consolidation adjustment journal (Dr COS / Cr Inventory)
4. Deferred tax on UPII: [tax rate]% on the UPII movement
5. Net impact on group consolidated profit and equity

Format as a reconciliation table. Also provide the Oracle query that extracts intercompany inventory balances by product category.

You are an inventory audit specialist. Write a step-by-step investigation guide for the following physical count discrepancy:

Warehouse: [name, location]
Count date: [date]
System quantity (Oracle Inventory): [units]
Physically counted: [units]
Net variance: [units / EUR value]
Product category: [describe]
Initial observations: [describe any patterns observed — concentrated in one location? One product? Recent deliveries not processed?]

The guide must cover the following investigation steps in sequence:

STEP 1: Rule out count errors
STEP 2: Review recent transactions (GRNs, shipments, transfers, adjustments) in the count window
STEP 3: Check for unprocessed paperwork (deliveries received but not scanned, returns not processed)
STEP 4: Identify if this is a systemic vs one-off variance
STEP 5: Escalation — who to involve and when
STEP 6: Adjusting journal — when and how to process in Oracle
STEP 7: Root cause analysis and preventive action

For each step: specific action, Oracle report or transaction screen to use, person responsible, and time to complete.

You are an IAS 2 inventory valuation specialist. Conduct an NRV test for the following slow-moving product lines identified in our aging report:

[For each product line, provide or ask AI to provide the structure for:]
• Product line name / SKU
• Quantity on hand
• Cost per unit (weighted average)
• Last sale date
• Recent selling price (last 3 months)
• Estimated costs to sell (marketing, sales commission, distribution)
• Any known obsolescence factors (product discontinued / superseded / seasonal)

For each product line, calculate:
1. NRV = Estimated selling price − Estimated costs to sell
2. Write-down required = Max(0, Cost − NRV)
3. Total write-down [EUR]
4. Key assumption used and sensitivity (what if selling price drops a further 10%?)

Output as a risk matrix: Product line | Cost | NRV | Write-down | Risk level | Management action required | Approver.

Include aggregate summary and materiality assessment vs total inventory balance.

You are an IFRS inventory accounting policy specialist. Review our group inventory accounting policy and identify any gaps or inconsistencies vs IAS 2 requirements:

Our current policy states:
[Paste or summarize your current inventory accounting policy]

Entity context: [describe — manufacturing? Distribution? Mixed? Number of entities applying this policy?]

Review the policy against IAS 2 requirements covering:
1. Cost measurement method: is FIFO, AVCO, or standard cost correctly applied per IAS 2.25? Is the method consistent across similar inventory?
2. Cost components: are all costs in IAS 2.10 included (purchase price, import duties, transport, handling) and are all IAS 2.16 exclusions removed (selling costs, abnormal waste, admin overhead)?
3. NRV: is the review process and definition of NRV per IAS 2.9 correctly described?
4. Provisioning: is the approach for write-downs consistent with IAS 2 measurement principles?
5. Write-back: does the policy address the requirement to reverse write-downs when circumstances change (IAS 2.33)?
6. Disclosure: does the policy commit to the disclosures required by IAS 2.36?

For each gap: severity (critical / significant / minor), recommended policy wording, and timeline to correct.

You are an intercompany reconciliation specialist. Analyze the following intercompany reconciliation gaps and produce a prioritized resolution plan:

Period: [month/year]
Group close deadline: [Day+X]

IC differences by transaction type:
[List each: Transaction type | Entity pair | Difference EUR | Aged (days) | Status]

For each difference:
1. Root cause category: timing / currency / missing transaction / error / dispute / methodology difference
2. Materiality: above or below [EUR threshold] for mandatory investigation before close?
3. Resolution urgency: must resolve before close / can carry with explanation / can carry to next period
4. Responsible party: which entity needs to act?
5. Resolution action: specific next step

Output as a risk matrix sorted by: urgency (close-blocker first), then materiality. Include a summary row with total unresolved differences and percentage of total IC volume they represent.

Also: which differences, if unresolved, would require a top-side adjustment at group level and what would that adjustment be?

You are an intercompany close process specialist. Draft a suite of three IC confirmation communications for use in the month-end close process:

GROUP CONTEXT:
• Entities: [list 4-6 entity names and countries]
• IC close deadline: Day+[X] from period end
• Confirmation format: email (no portal available)

COMMUNICATION 1 — Pre-close IC statement (sent Day+1):
Sent by each entity to their counterparties. Must include:
• Entity's AR and AP balances by counterparty as at period end
• Request for confirmation or differences by [Day+X deadline]
• Contact person

COMMUNICATION 2 — Difference notification (sent when a difference is identified):
Sent by the entity finding the difference. Must include:
• Amount of difference
• Transaction type and reference
• Their balance vs counterparty's balance
• Proposed resolution and deadline

COMMUNICATION 3 — Escalation notification (sent if unresolved by Day+[X]):
Sent by the Group Finance team to both Finance Directors. Must include:
• Difference amount and impact on group close
• History of communication
• Required action and hard deadline

Each communication should be professional, specific, and actionable.

You are a treasury and intercompany netting specialist. Calculate the monthly netting settlement for the following group entities and prepare payment instructions:

Netting cycle: [month/year]
Settlement currency: EUR
Settlement date: [date]
Netting center entity: [name]

Gross intercompany payables (before netting):
[Entity A owes Entity B: EUR X]
[Entity B owes Entity C: EUR Y]
[Entity C owes Entity A: EUR Z]
[Entity A owes Entity D: EUR W]
[Entity D owes Entity B: EUR V]
[Add more as needed]

For each entity, calculate:
1. Total gross payables
2. Total gross receivables
3. Net position (positive = net receiver / negative = net payer)
4. Settlement instruction (pay to or receive from netting center)
5. FX conversion required (if any entity's payables are in non-EUR currencies)

Verify: netting center net position = 0 after all settlements.
Format as a settlement memo suitable for treasury approval, followed by formal payment instructions.

You are an intercompany treasury specialist. Prepare an intercompany loan tracking schedule for [entity] for the period [year]:

Loans outstanding:
[For each loan: Lender entity | Borrower entity | Currency | Principal | Rate % | Calculation basis | Drawdown date | Maturity date]

For the current period, calculate for each loan:
1. Opening principal balance
2. Any drawdowns or repayments in the period
3. Closing principal balance
4. Interest for the period (exact day count on [actual/360 or actual/365] basis)
5. Interest accrued but not yet paid
6. Withholding tax applicable on interest (if the payment crosses a border)
7. Counterparty journal: what does the lender entity record vs the borrower entity?
8. IC reconciliation check: do the balances agree between lender and borrower ledgers?

Output as a structured table. Flag any loans approaching maturity in the next 12 months or any where the interest rate may need a TP benchmark review.

You are an intercompany reconciliation manager. Interpret the following IC difference aging report and recommend a remediation strategy:

[Paste or describe your aging report: total differences by age band (0-30 / 31-60 / 61-90 / 91-180 / 180+ days) and by transaction type, for each entity pair]

Analyze:
1. What is the overall IC reconciliation health score (% of IC volume reconciled within 30 days of period end)?
2. Which transaction types account for the most aged differences — and what does this tell us about the process?
3. Which entity pairs have the worst reconciliation performance?
4. For differences >90 days: are there systemic issues (methodology, timing, FX) or genuine errors?
5. What is the group's balance sheet exposure from unresolved IC differences (potential mis-statement)?

Recommend:
• Top 3 process improvements that would prevent the most common difference types
• For aged differences >90 days: clear-down plan with accountabilities and deadlines
• KPI: what should the target IC matching rate be within 5 days of period end?

You are a group accounting policy specialist. Document the intercompany methodology differences that are acceptable at group level vs those that must be eliminated:

Group context: [entities, currencies, IFRS reporting, intercompany transaction types]

ACCEPTABLE METHODOLOGY DIFFERENCES (document each):
1. FX translation differences on monetary items — explain why these arise legitimately and how they are treated at group level
2. Timing differences in the recognition of goods in transit — policy for the cut-off
3. Different accrual methods for intercompany management fees — acceptable if within [X] days of actual invoice

DIFFERENCES THAT MUST BE ELIMINATED BEFORE CLOSE:
1. Different treatment of IC dividends declared but not paid — both entities must record on declaration date
2. Different capitalization vs expense decisions for IC IT services — must align per group policy
3. Different recognition of IC revenue vs IC cost — must match in the same period

For each acceptable difference: how to present in the group IC reconciliation commentary.
For each mandatory elimination: the resolution procedure and who is accountable.

Include a quick reference one-page decision guide: "If my IC difference is caused by [X], then [action]."

You are a B2B credit risk specialist. Design a credit risk scoring model for assessing new and existing customers:

Business context: Technology company, average customer invoice value [EUR], typical payment terms NET [X] days, customer base: [describe mix — large corporate, SME, public sector].

The scorecard must evaluate:
FINANCIAL INDICATORS (from annual accounts or credit bureau):
• Revenue trend (3-year growth rate)
• EBITDA margin vs sector average
• Current ratio (current assets ÷ current liabilities)
• Days payable outstanding trend
• Debt-to-equity ratio
• Credit bureau score or rating

BEHAVIORAL INDICATORS (from our AR history):
• Average days to pay (vs terms)
• Number of disputes raised
• Disputes resolved in our favor (%)
• Payment plan history
• Communication responsiveness when contacted

For each factor: scoring range (1–5), weight (% of total), and guidance on how to score.
Total score → Credit risk band (Low / Medium / High / Unacceptable) → Recommended credit limit formula → Payment terms → Required security (none / credit insurance / advance payment / parent guarantee).

You are a credit control manager. Design a collection strategy guide segmented by customer type and overdue duration:

Customer segments:
• SEGMENT A: Strategic key account (>EUR [X] annual revenue, long-term relationship)
• SEGMENT B: Standard commercial customer
• SEGMENT C: Public sector / government entity (different legal framework)
• SEGMENT D: New customer (<12 months relationship)
• SEGMENT E: Customer with prior late payment history

For each segment × overdue duration (7 days / 30 days / 60 days / 90+ days), specify:
1. Communication channel (email / phone / formal letter / account manager involvement)
2. Tone and approach (friendly reminder / firmer notice / formal demand)
3. Credit hold trigger (at what point do we suspend new orders?)
4. Management escalation trigger
5. Legal referral criteria
6. Interest charges: when to apply and how to calculate per local law in [country]

Also: what NOT to do — common mistakes that damage customer relationships unnecessarily. Include a one-page decision flowchart.

You are an AR performance specialist. Analyze the following DSO data and design a 90-day improvement plan:

Current DSO: [X] days
Target DSO: [Y] days (aligned with our payment terms of NET [Z] days)
Required improvement: [X−Y] days

Current AR aging:
• Not yet due: [EUR] / [%]
• 1-30 days overdue: [EUR] / [%]
• 31-60 days overdue: [EUR] / [%]
• 61+ days overdue: [EUR] / [%]

Root cause analysis (if known): [describe — e.g., large customer habitually paying at 45 days, disputed invoices blocking payment, billing errors causing reprocessing delays]

Design a 90-day action plan with:
1. Root cause priority ranking
2. Specific action for each root cause (process change / customer conversation / system fix)
3. Expected DSO improvement from each action
4. Responsible owner and deadline
5. Metrics to track weekly progress

Quantify: if we achieve [X] days DSO improvement, what is the cash release in EUR (using our annual revenue of [EUR])?

You are an accounts receivable dispute management specialist. Design a customer dispute tracking and resolution framework for [entity]:

Dispute volume: approximately [X] disputes per month
Average dispute value: [EUR]
Main dispute types observed: [describe — pricing errors / short delivery / quality / duplicate invoice / unauthorized deduction / other]

The framework must define:

1. INTAKE: How disputes are logged (system field requirements), who logs them, and SLA for initial acknowledgment to customer

2. CLASSIFICATION: Dispute type categories, validity assessment (valid claim vs invalid claim), and evidence required to assess each type

3. ROUTING: Who investigates each type (Accounts Receivable / Sales / Operations / Legal), and escalation thresholds by value

4. RESOLUTION: Standard resolution path by type, credit note issuance procedure, partial payment matching

5. SLA TARGETS: Resolution time by dispute type and value (e.g., pricing dispute <[X] days, quality dispute <[Y] days)

6. REPORTING: Monthly dispute dashboard — what to measure (open disputes, average resolution time, reasons, amount tied up, rate of disputes in our favor)

7. PREVENTION: What each dispute type tells us about upstream process failures and how to fix them

You are a credit control and accounting specialist. Prepare a bad debt provision and write-off proposal for management approval:

Period: [quarter/year end]
Total AR outstanding: [EUR]

SPECIFIC PROVISION PROPOSALS:
[For each account: Customer name | Outstanding amount | Overdue age | Reason for provision | Proposed provision amount | Recovery probability estimate]

GENERAL PROVISION (IFRS 9 ECL model):
• Applied to balance of AR after specific provisions
• Historical loss rate by aging band: [provide your rates or ask AI to suggest appropriate rates for your industry]

Calculate:
1. Total specific provision: [EUR]
2. Total general provision (ECL): [EUR]
3. Total provision balance: [EUR]
4. Prior period provision balance: [EUR]
5. P&L charge / (release) for the period: [EUR]

WRITE-OFF PROPOSALS (amount beyond recovery):
[List any accounts recommended for write-off with justification: legal proceedings failed / insolvency confirmed / commercial decision]

Include: journal entry, disclosure in financial statements, management presentation summary, and any VAT bad debt relief available for written-off amounts in [country].

You are a credit control performance specialist. Design a monthly credit control dashboard for [entity] covering the following KPIs:

COLLECTION EFFECTIVENESS:
• Days Sales Outstanding (DSO) — actual vs target vs prior period
• Collection Effectiveness Index (CEI) = collections ÷ opening AR + sales × 100
• % of AR collected within terms (NET [X] days)
• % of overdue AR that is >90 days (indicator of chronic non-payers)

RISK INDICATORS:
• Total AR at risk (customers on credit hold or with disputes)
• New credit limits granted this month (value, number of customers)
• Customers with credit limit exceeded
• Credit insurance utilization rate (if applicable)

ACTIVITY METRICS:
• Number of collection calls / emails made
• Number of disputes opened vs resolved
• Average dispute resolution time (days)
• Number of accounts referred for legal action

For each KPI:
• Calculation formula
• Data source (Oracle AR module / manual)
• Measurement frequency
• Target threshold and RAG status definition (Green / Amber / Red)
• Suggested visualization type (trend line / bar / gauge)

Also: design the one-page layout for this dashboard, describing where each KPI appears and how it links to supporting detail.

You are a finance transformation specialist. Conduct a maturity assessment for the following finance processes at [entity / group level]:

Processes to assess:
1. Record-to-Report (close, consolidation, reporting)
2. Purchase-to-Pay (procurement, AP, payment)
3. Order-to-Cash (AR, credit, collections)
4. Tax compliance (VAT, CIT, e-invoicing)
5. Treasury (cash management, intercompany, FX)
6. Financial planning and analysis (budgeting, forecasting, management reporting)

For each process, rate maturity on a 1–5 scale:
1 = Ad hoc / undocumented / relies on individual knowledge
2 = Documented but inconsistently followed
3 = Standardized and consistently executed
4 = Measured and continuously improved
5 = Automated, predictive, and benchmarked vs best practice

For each process:
• Current maturity level: [1–5]
• Evidence for the rating (what does level [X] look like in practice here?)
• Target maturity level (12 months)
• Gap: what would need to change to reach target?
• Priority: High / Medium / Low (based on business impact of improvement)

Produce a heat map summary and a top 5 improvement priorities.

You are a finance AI adoption specialist. Design a 12-month AI adoption roadmap for [Finance team / Tax team / Shared Services team]:

Current state:
• AI tools available: [Copilot Chat — all / Copilot Pro — tax team / KNIME — data team]
• AI adoption rate: approximately [X%] of team using AI tools weekly
• Key barriers: [describe — e.g., "lack of confidence in outputs, no prompts library, manager skepticism"]
• Team profile: [X people, mix of senior/junior, describe main activities]

Design a month-by-month roadmap covering:
• Month 1–2: Foundation (training, safe usage policy, prompt starter pack)
• Month 3–4: Quick wins (identify 3 high-ROI use cases, run pilots)
• Month 5–6: Expansion (broaden to additional use cases and team members)
• Month 7–9: Integration (embed AI into standard processes, measure time savings)
• Month 10–12: Optimization (build agents, automate workflows, share learnings)

For each phase:
• Key activities and milestones
• Who leads each activity
• Metrics to show progress (adoption rate, hours saved, satisfaction score)
• Dependencies and risks

Include: a governance model (who decides which AI tools are approved and for what use), and a quarterly steering review agenda.

You are a finance governance specialist. Assess the completeness and quality of finance policies and procedures for [entity / group]:

POLICY INVENTORY — rate each:
[For each policy listed, provide: Last updated | Owner | Quality rating 1–5 | Key gap identified]

Policies to assess:
1. Revenue recognition policy
2. Expense and T&E policy
3. Fixed assets capitalization policy
4. Inventory valuation policy
5. Credit and collection policy
6. Intercompany pricing policy
7. Tax compliance policy (VAT / CIT)
8. Journal entry authorization policy
9. Financial reporting and close policy
10. Delegation of authority / approval matrix

For each policy, assess:
• Is it documented and accessible?
• Is it current (updated within last 2 years / reflects current standards)?
• Is it specific enough to guide decisions without manager intervention?
• Is there evidence of compliance monitoring?
• Does it cover all entities in scope?

Output as a risk matrix: Policy | Status | Risk level | Priority action | Owner | Deadline.
Flag any areas where absence of a policy creates regulatory, audit, or control risk.

You are an L&D specialist for finance professionals. Design a training needs analysis and curriculum for [Finance / Tax / Shared Services] team:

Team roles:
• [Role 1, e.g., VAT Compliance Analyst — 3 people]
• [Role 2, e.g., Finance Controller — 2 people]
• [Role 3, e.g., AP Specialist — 5 people]
• [Add more as needed]

Upcoming requirements driving training needs:
• [e.g., E-invoicing go-live in [country] — Q3 target]
• [e.g., IFRS 18 effective next year]
• [e.g., AI tools rollout — Copilot Chat for all, Copilot Pro for senior team]
• [e.g., New Oracle R12 module going live — Project Accounting]

For each role × skill area, create a training matrix:
Rows: Skill areas (technical accounting / tax / systems / AI tools / communication / leadership)
Columns: Roles
Cells: G = Gap (training urgently needed) / D = Developing (training recommended) / P = Proficient (no training needed now)

Then produce a prioritized 12-month training calendar: course name | format (classroom/online/OJT) | provider (internal/external) | duration | target roles | scheduled month | estimated cost.

You are a finance benchmarking analyst. Research and provide benchmark data for the following finance function metrics, comparing [entity/group] to industry benchmarks:

Context: [EUR X revenue / Y employees in finance / industry: technology & imaging / geography: European operations]

Metrics to benchmark:
1. Finance cost as % of revenue
2. Number of FTEs per EUR 1B revenue (finance headcount productivity)
3. Days to close (monthly accounts close)
4. AP touchless processing rate (invoices processed without human intervention)
5. DSO (Days Sales Outstanding)
6. Error rate (journals requiring correction or restatement)
7. Copilot / AI tool adoption rate
8. Finance employee satisfaction score (if available)
9. External audit cost as % of revenue
10. Number of material audit findings per year

For each metric:
• Our current performance: [to be filled in]
• Industry median (Hackett / APQC / Gartner benchmark)
• Top quartile performance
• Bottom quartile performance
• Gap to median / gap to top quartile
• Priority: is closing this gap worth investing in?

Cite benchmark sources. Flag metrics where our performance is below median — these are candidates for the improvement roadmap.

You are a finance transformation adviser. Draft a business case for establishing or expanding a Finance Shared Services Center (SSC) for [organization]:

Current state:
• Finance activities currently decentralized across [X] entities in [Y countries]
• Current total finance FTE: [X] across all entities
• Activities considered for SSC: [list — AP processing / AR collections / GL close / expense processing / reporting / tax compliance support]
• Excluded (remain local): [list — statutory accounts / local tax filings / treasury / business partnering]

The business case must cover:
1. SCOPE: Which activities and which entities are in scope, and in what phase?
2. FINANCIAL CASE: Cost savings (FTE reduction, scale economies, real estate) vs investment (setup, transition, systems); NPV and payback period at [X years]
3. SERVICE QUALITY CASE: How will service levels improve vs current (SLA, error rate, close speed)?
4. RISK ASSESSMENT: Transition risk, knowledge loss risk, regulatory risk (some countries restrict outsourcing of certain finance activities)
5. OPERATING MODEL: Location options [describe 2-3], governance model, performance management
6. TIMELINE: 18-month implementation plan with milestones
7. RECOMMENDATION: Preferred option with go / no-go criteria

Format suitable for CFO review and board approval.