Finance reporting & reconciliation automation

Spend less time preparing finance reports.

I help accounting and finance teams automate recurring reconciliations, consolidate system exports, and produce Excel reports they can review and reuse.

Free 30-minute call. Start with one recurring task.

Your monthly workflow Illustrative example

01 / Bring your sources together

Billing exportGeneral ledgerAccount mappings

02 / Apply your business rules

  • Standardize and match records
  • Check agreed totals and calculations
  • Flag differences for investigation

03 / Review the result

A report ready for your team

Source references · Reconciliation differences · Items to investigate

The inputs, rules, and checks are agreed for your specific workflow.
15+ years of business experienceFinance, analysis, and operations
MBA & Master in AIBusiness judgment with practical data skills
Work directly with FernandoFrom the first review to the handover
Where I can help

The recurring work
behind your numbers.

For controllers, accounting managers, and finance teams who spend too much time getting data into a usable report.

Monthly reporting

Turn a recurring sequence of exports, lookups, and calculations into a repeatable reporting workflow.

A typical starting point

Consolidate monthly files, apply account mappings, and generate your agreed Excel reporting pack.

Financial reconciliation

Compare financial and operational records, trace differences, and give your team a clear list of items to investigate.

A typical starting point

Match billing data to ledger exports, check totals, and surface missing or conflicting records.

Data consolidation

Bring scattered files together and standardize the fields your reports depend on.

A typical starting point

Combine Excel and CSV exports from multiple locations into one consistent dataset for Excel or Power BI.

Your finance automation partner

Someone who understands the work behind the numbers.

A useful automation starts with understanding the business rules, the people using the report, and the decisions those numbers support.

Fernando Lopez
Fernando Lopez

Founder, From Excel to Python

My background spans more than 15 years of budgeting, business analysis, and operational improvement across banking, pharmaceuticals, transportation, shipping, and retail.

I combine that experience with Python, SQL, Power Query, and Power BI to turn recurring data work into practical processes your team can use.

  • Finance & accounting
  • Reporting & analysis
  • Business operations
Published project stories

See the approach
in practice.

Explore the business problem, the work involved, and the reported outcome in these examples from my experience.

Accounting & month-end close

Bringing scattered accrual data together.

A look at consolidating isolated files, making accrual information easier to access, and surfacing pricing and process anomalies for investigation.

Read the project story
Sales reporting · Corporate experience

Making customer data easier to use.

How a large spreadsheet export became a more focused dataset and a Power BI dashboard for answering customer questions and reviewing sales performance.

Read the project story
A clear first engagement

Start with one recurring workflow.

  1. Review the task

    Walk through your current process, the files involved, and the report your team needs.

  2. Agree the scope

    Define the inputs, business rules, output, acceptance checks, timeline, and fixed project quote.

  3. Build and check

    Build the workflow and compare its agreed outputs with source totals and expected results.

  4. Hand it over

    Receive the code, report, instructions, and a walkthrough so your team can run it again.

Project investment

One workflow. An agreed deliverable.

From CAD 1,499

A fixed project quote follows the review. The number of sources, complexity of the rules, required checks, and final output determine the scope and price.

We agree on the processing environment and any external service costs before work starts.

What you receive

  • Your working automation and source code
  • The report or dataset defined in the scope
  • Checks against the agreed expected results
  • Short operating instructions and a walkthrough
  • 30 days of support for the delivered workflow

You own the delivered code. Enhancements and changes to source formats are quoted separately.

Before you begin

Practical answers.

Clear expectations about how your team will use the workflow and how the work is delivered.

Can we keep using Excel?

Yes. Your workflow can produce the Excel report your team already uses. We agree on the layout and review process before building it.

Do we need to learn Python?

You do not need to write code to use the agreed workflow. Setup, how to run it, and how to review the output are covered in the handover.

Where will our data be processed?

We agree on the environment and how files are shared, processed, and stored before work starts. An initial review can use a sanitized sample. Confidential files are shared only through the agreed channel.

What happens if our source files change?

The workflow is built around the agreed inputs and rules. New columns, changed formats, or new business requirements may need an update. Those changes are reviewed and quoted before additional work begins.

Let's look at your workflow

Bring me the task you repeat every month.

In a free 30-minute call, we will discuss the current steps, the result you need, and whether the task is a good fit for automation.

A description of the process is enough to start. No confidential files are needed for the call.

Scroll to Top
From Excel to Python logo
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.