Unleash the power of AI in accounting. Expert-led, AI-augmented financial management — audit-ready, investor-ready, and always on time. See how it works →
Case study Hospitality Aldgate, London, United Kingdom

How One VBA Workflow Cut Weekly Payment Preparation by More Than 90%

A repetitive weekly payment preparation process was transformed into one guided VBA workflow, reducing manual assembly, strengthening validation, and producing a complete payment package in minutes using the same source files the team already worked with.

accounts_payable_automation_case_study_image_whiz consulting
5 min read
Weekly Processing Time
15 Minutes Turnaround
Down from 3-4 hours
Time Saved
90%
Reduction in time spent on each weekly payment cycle
Workflow Simplification
1 Guided Process
Replacing fragmented manual preparation and four interlinked outputs
The client shared how much easier their weekly routine has become: "We used to spend hours putting everything together. Now, it takes minutes, and we spend less time checking the same details repeatedly."
The client

A London Skybar Managing Fast-Moving Weekly Payment Cycles

Based in Aldgate, London, the business operates a busy Skybar where a steady flow of supplier invoices and weekly payments sits behind day-to-day hospitality operations. Each payment cycle required the finance team to bring together three separate source files and four connected outputs, making accuracy, complete payment details, and timely vendor payments essential.

Industry Hospitality
Headquarter Aldgate, London, United Kingdom
Core Accounting Platform Microsoft Excel VBA
Source Files Aged Payables Summary, aged payables detail, and vendor requisition forms
Workflow File selection, data matching, validation, review, and output generation
Services Used Workflow automation, payables data matching, bank detail validation, guided review, and print-ready payment workbook generation
Delivery Team Whiz Consulting delivery team
Frequency Weekly payment cycle
The challenge

A Weekly Payment Process Built Around Repetitive Manual Assembly

The existing payment preparation process relied heavily on manual work. The finance team had to bring together multiple files, check payment information line by line, identify missing details, and manually assemble interconnected outputs before the weekly payment cycle could move forward.

Three Source Files Cross-Checked by Hand

Every week the team gathered the aged payables summary, the aged payables detail, and the vendor requisition Forms, then compared them against each other manually before anything could move forward.

Line-by-Line Verification Was Required

Bank details and other payment information required manual checking. Missing or mismatched information could not simply be ignored because even one incorrect invoice or absent bank detail could affect the wider payment run.

Four Outputs Were Built Manually

The process did not end with data verification. Four interconnected outputs had to be assembled by hand, adding more repetitive steps to every payment cycle.

Three to Four Hours Spent Every Week

The complete workflow consumed approximately 3-4 hours per weekly cycle. Because the process was recurring, the same manual routine was repeated week after week with little opportunity to recover that time.

High Dependence on Manual Accuracy

The workflow relied on people identifying mismatches and missing information before the payment package was completed. This increased the risk that one overlooked detail could delay the payment process.

The transformation

Rebuilding Weekly Payment Preparation Around One Guided Workflow

Rather than replacing the finance team’s existing files or introducing an entirely new system, the automation was designed around the way the team already worked. The VBA solution continued using the same source documents but connected file selection, matching, validation, review, and output generation into one repeatable process.

Before
  • Three source files handled manually
  • Information cross-checked line by line
  • Missing bank details identified manually
  • Four outputs assembled by hand
  • Process dependent on manual checks
  • Staff focused on repetitive data handling
  • Fragmented workflow
  • 3-4 hours per week cycle
After
  • Existing source files selected through one guided process
  • Data parsed and cross-referenced automatically
  • Missing bank information flagged by the system
  • Final payment package generated automatically
  • Validation built into each stage
  • Team focus shifted toward reviewing information
  • One unified, guided interface
  • Under 15 minutes from start to finish

Make Weekly Payment Preparation Faster and Easier to Control

Reduce repetitive payment administration, strengthen validation, and give your finance team more time for higher-value work.

Book my audit →
Our approach

A Four-Phase Approach to Automated Payment Requisition Preparation

The VBA solution was built around the existing payment workflow rather than forcing the team to adopt new source formats or enter the same information into another system. Each stage removed a specific area of manual work while maintaining a review point before the final payment package was produced.

01

Source File Selection

  • Pointed the tool at the three files the team already produces, with no reformatting needed first.
  • Kept the Aged Payables Summary, Aged Payables Detail, and Vendor Requisition Forms as the only inputs.
  • Required no new systems to learn and no new data entry.
02

Automated Parsing and Matching

  • Once the files were selected, the VBA workflow parsed the source information and cross-referenced the relevant details.
  • The system compared information across the available files rather than requiring staff to verify every relationship manually.
  • Cross-referenced details across the three files in a single pass.
  • Missing bank information was also identified during this stage so incomplete payment records could be addressed before final output generation.
03

Built-In Review and Validation

  • Presented the matched data for the user to review before any output is created.
  • Let the user catch and fix anything unusual at this stage.
  • Moved error detection ahead of the payment, not after it has gone out.
04

Automated Payment Package Generation

  • Once the review was complete, the final output could be produced through the guided workflow.
  • The automation generated the required payment requisition or cheque-payment package without the team manually assembling the four interconnected outputs.
  • Replaced every disjointed step of the old routine with one repeatable, guided workflow.
The results

A Faster Weekly Payment Cycle with Greater Control and Review

The automation changed payment preparation from a repetitive manual exercise into a guided weekly process. The biggest measurable improvement came from reducing preparation time while also introducing more consistent validation across the workflow.

90%+ Less Time per Cycle
Weekly payment preparation fell from three to four hours to under 15 minutes
Under 15 Minutes, Review Included
The 15-minute figure covers the whole run from file selection to the finished workbook, including the user’s own review
Around 150–200 Hours Saved a Year
Across 52 weekly cycles, the team gets back an estimated 150-200 hours, based on saving roughly 2.75 to 3.75 hours each cycle
Validated at Every Step
Accuracy no longer rests on manual checks alone, because the data is system-validated before it becomes an output
One Unified, Guided Process
Four separately assembled outputs became a single guided interface that anyone on the team can repeat
Higher-Value Team Time
The team’s role shifted from entering data to reviewing the tool’s work, freeing hours for higher-value financial work
What this means for you

Key Takeaway for Finance Leaders

Three Building Blocks of Smarter Payment Workflow Automation

i

Automate the Workflow Around Existing Finance Processes

Automation does not always require replacing existing systems. In this case, retaining the source files already used by the team reduced disruption while allowing the repetitive work surrounding those files to be automated.

ii

Use Automation to Shift People from Preparation to Review

The objective should not simply be to perform the same manual steps faster. Greater value comes from allowing automation to handle repetitive matching and preparation while finance professionals concentrate on exceptions, validation, and decision-making.

iii

Keep Validation Inside the Automated Process

Speed is useful only when the resulting payment information can still be reviewed confidently. Building matching, missing-data checks, and user review into the workflow helped reduce processing time without removing control from the finance team.

Want results like these for your team?