Hi, I'm Juan García.

I like noticing the things everyone ends up accepting as “that's just how it's done,” and testing whether they can be done better.

I get involved, I watch how work actually happens, and when I find a useful way to improve something, I try to build it. Here are four real problems I learned to solve.

See the problems

The problem

Part of the time went into finding or typing information that was already available. Before entering it, each invoice also had to be checked for what it needed to move forward.

What I did

I built a workflow that recognizes useful information, separates the cases that need attention, and leaves the correct invoices ready for the next step. The person keeps the final decision.

Imagine…

Imagine you receive a folder with many invoices. Instead of opening them one by one and starting from scratch, you load them into a tool that reads them, organizes the information, and shows what can move forward and what needs review.

Visual walkthrough · 20 s

From five invoices to a file uploaded to the system.

Will start when it enters view.

Incoming

Invoice 1

Invoice 2

Invoice 3

Invoice 4

Invoice 5

Validator

Review

Don't continue

Read the full sequence

Five invoices arrive.
They're loaded into the validator.
Each invoice is validated.
Two don't continue.
The invoice under review is approved.
The approved ones are grouped.
The upload file is generated.
The file is loaded into the system.

The problem

The documents needed for a payment were stored apart from each other. Putting the backup together meant locating the invoices and other matching documents and gathering them one by one.

What I did

I used the reference of each payment record to locate and check the documents that belonged to it. When more than one option was possible, the case stayed visible for review.

Imagine…

Imagine a payment record, Ref. 12456. Its invoices and related emails are stored apart from each other. The tool identifies which ones belong to that reference, checks they match, and brings them together to leave the backup ready to process the payment.

Visual walkthrough · 14 s

From separate documents to a ready payment backup.

Will start when it enters view.

Payment record

Ref. 12456

Review

Documents

Invoice 1

12456

Invoice 2

12456

Invoice 2

12456

Invoice

98765

The problem

When there are many payments to prepare, a manual review can miss a repeated reference, incorrect tax information, or a bank account entered wrong. If the payment gets processed like that, fixing it later means follow-up, clarifying with the supplier, and extra work.

What I did

I built a check that runs before the output is generated — reference, tax information, and bank details. Errors stay visible so they can be fixed, and the file is only created once everything checks out.

Imagine…

Imagine five payments to process. One repeats another's reference, another has tax information to review, and another has a bank account to review. What's needed gets fixed, the repeated one is set aside, and the correct payments end up together in a file that's uploaded to the bank's portal.

Visual walkthrough · 21 s

From several payments to review to payments processed at the bank.

Will start when it enters view.

Payments to process

Ref. 0001 Food supplier $10,000.00

Ref. 0002 Carpentry supplier $8,500.00

Ref. 0003 Produce supplier $12,300.00

Ref. 0001 Labour supplier $10,000.00

Ref. 0005 Maintenance supplier $6,900.00

Not prepared yet

Read the full sequence

Five payments arrive to be processed.
Each one is checked.
Two are correct; the other three need review.
With one problem left, the output is blocked.
The flagged tax and bank details are corrected.
The payment with the duplicate reference is set aside.
No problems are left.
The correct payments end up together in a file.
The file is uploaded to the bank's portal.
The payments are processed.

The problem

Preparing each notice meant writing the message, finding the supplier's email, locating their file, and attaching it. Without a clear record of what was sent, some suppliers ended up asking for their receipt again.

What I did

I built a tool with an editable template that links each supplier to their recipient and their document. From a single list, the emails are prepared and sent, each with its matching file.

Imagine…

Imagine several payments already made. The tool finds the recipient and document for each supplier, prepares the emails on the same template, and sends them from a single list, each with a different file.

Visual walkthrough · 20 s

Several emails, one template, different files.

Will start when it enters view.

Database

Food supplier payments@alimentos.example

Carpentry supplier payments@carpinteria.example

Produce supplier payments@verduras.example

Maintenance supplier payments@mantenimiento.example

Documents

Ref. 0001 Ref. 0002 Ref. 0003 Ref. 0005 Ref. 0007 Ref. 0011 Ref. 0014 Ref. 0018

Ref. 0001

Food supplier

To —payments@alimentos.example

Attached —Ref. 0001

To payments@alimentos.example

Hi, Food supplier

Attached Payment documentation · Ref. 0001

Sent

Payment notice

FromJuan García

Topayments@alimentos.example

CCcxc@alimentos.example

SubjectPayment notice

Hi, Food supplier:

Attached is the documentation for your payment.

Please review the instructions for confirming your payment.

Best regards,
Juan García
Accounts Payable
555 555 5555

Payment documentation Ref. 0001.pdf

Ref. 0002

Carpentry supplier

To —payments@carpinteria.example

Attached —Ref. 0002

To payments@carpinteria.example

Hi, Carpentry supplier

Attached Payment documentation · Ref. 0002

Sent

Ref. 0003

Produce supplier

To —payments@verduras.example

Attached —Ref. 0003

To payments@verduras.example

Hi, Produce supplier

Attached Payment documentation · Ref. 0003

Sent

Ref. 0005

Maintenance supplier

To —payments@mantenimiento.example

Attached —Ref. 0005

To payments@mantenimiento.example

Hi, Maintenance supplier

Attached Payment documentation · Ref. 0005

Sent

Send

Read the full sequence

Suppliers with receipts to send.
Each recipient is found in the database.
Each supplier's document is found.
The emails are prepared for sending.
Here's what one of the emails looks like before it's sent.
Each email is sent with its file.
Emails sent.

You've seen what I've built. Now, a bit about me.

Outside of work.

I enjoy photography, going out on shoots, and public speaking. Things I enjoy — and I'm still practicing them too.

Group celebrating the completion of a photography course

Let's talk?

If any of this reminded you of something your team deals with, you have a project in mind, or you'd just like to know more about my work, get in touch.

WhatsApp LinkedIn Download CV

Hi, I'm Juan García.

Do you get a lot of invoices, and entering them one by one still eats up time?

The problem

What I did

Imagine…

From five invoices to a file uploaded to the system.

Does putting together payment backup mean hunting down files one by one?

The problem

What I did

Imagine…

From separate documents to a ready payment backup.

Do you process many payments? How do you avoid duplicates and incorrect data?

The problem

What I did

Imagine…

From several payments to review to payments processed at the bank.

Do you send receipts to many suppliers? Do you still prepare each email separately?

The problem

What I did

Imagine…

Several emails, one template, different files.

You've seen what I've built. Now, a bit about me.

Outside of work.

Let's talk?