Template — fictional worked example. Replace every figure and every line of copy, then delete this banner.
AYOH Group DocuWare Platinum Partner Northwind Manufacturing

Accounts payable that keeps up without another pair of hands

An interactive investment configurator for Northwind Manufacturing.

Prepared for
Northwind Manufacturing
Finance
Prepared by
David Malan — Sales Director
david@ayoh.group
Date
1 January 2026
Valid for 30 days
Reference
AYOH-XXX-YYYY-NNN
All figures excl. VAT, in ZAR
Implementation & testing
R 0
payable at sign-off
From go-live
R 0
invoiced when testing signs off
What it gives back
Billing after go-live
Based on your figures and ours

Why this is worth doing

Your creditors clerk is spending a day a week on work the system should be doing.

Northwind processes roughly 4,000 supplier invoices a month across three people. Every one that fails to index, fails to match or fails to post comes back as typing. The volume grows every year and the team does not.

What the first step gives back

What changes

Four things stop happening

Invoices index themselves

Documents that will not read today are captured, validated and posted without anyone retyping them.

Exceptions surface early

A mismatch is flagged at receipt rather than found at month-end, when it costs three times as much to unpick.

Month-end stops compressing

Accruals and supplier queries are answered from the system instead of assembled by hand each cycle.

Growth stops needing headcount

The next volume increase is absorbed by the platform rather than by the next hire.

What we counted

Only what can be proved, and deliberately on the low side

Hours the current process consumes that the first step removes. Volumes are Northwind's own. Everything else in this proposal is left out of the arithmetic on purpose.

Cost of a finance team member, a month
This is the one assumption every rand figure below rests on. Choose the band that matches your team and the numbers follow.
What the current process costsHours / yrValue / yr

Nobody loses a job in this. Three people carry the whole function, so there is no post to remove. Your next volume increase does not need your next hire, and the hours come back as accuracy, supplier relationships and month-ends that close on time.

What we did not count

Worth more than the figure above, and none of it is in there

What the returned time is pointed at

A day a week back is the disputed ageing worked, suppliers onboarded in days rather than weeks, and settlement discounts actually taken. That is revenue and cash, not effort — and it is yours to size, not ours.

Cash tied up in the cycle

Faster query resolution and cleaner reconciliation move working capital. We have not put a number to it because the honest answer depends on your facility and your terms, not on our software.

Control and audit exposure

Payments released on hand-typed detail, and documentation assembled after the fact, are the two places where a single event costs more than this entire programme.

Why they are not in the total

Because they cannot be proved from here. The case above is built on hours, because hours can be counted. Everything else is upside.

Show the working
From Northwind — confirmedFigureAYOH estimate — to confirmFigure

Hours are volume × frequency × minutes, taken to a year and valued at the monthly cost of a team member divided by the working hours in a month. Where a range was given, the lower end is used.

Where we would start

One invoice, one decision

What the first invoice coversAmount

Shape the platform

Users, workflow packs and storage

Production licensing from go-live. Changing these moves the annual figure only.

15 carried in the platform. Additional named users at R 1,150 /mo each.
R 1,400 /mo per pack — task completion, forms and read-only archive access.
50 GB included. Additional storage at R 200 /mo per 10 GB.

View 1

Consolidated investment

ItemQtyMonthlyAnnualOnce-off

View 2

Budget view — Year 1 against steady state

Cost componentBasisYear 1Year 2 onward

Annual pre-pay Recommended

  • Lowest total cost over twelve months.
  • One purchase order a year instead of twelve.

Monthly billing

  • Easier on cash flow, spread evenly across the year.
  • Monthly billing carries an 8% surcharge.

View 3

Invoice and purchase order timeline

Everything below follows from this date.
InvoiceTriggerIndicativeAmount

Dates are indicative and for planning; the AYOH project team evaluates and confirms all dates before delivery begins.

The fine print

Assumptions and what sits outside this scope

Assumptions

  • Fifteen named users and twenty workflow users cover the finance and receiving population.
  • The document archive is provisioned at 150 GB, with room to grow.
  • The ERP is read from and written to through its supported interface. Nothing in the ERP is modified.
  • Northwind nominates a project sponsor and a finance lead available within agreed response windows.

Exclusions

  • Changes to the ERP itself, its licensing or its support arrangement.
  • Network, hardware and end-user device infrastructure.
  • Third-party application support.
  • Data cleansing of historic records prior to go-live.

Future roadmap

What we have seen work next, and when to think about each one

This is the order we would advise, built on the platform the first step delivers. Nothing here is committed and nothing here is being quoted. Each one becomes a decision when its trigger arrives.

StepWhat it is forWhen to decide it

Each of these is scoped and quoted when you are ready to take it, against what has actually been built by then. Nothing here needs a decision today.

What we would do next

Book the working session

Two areas came up that we have not scoped or priced yet — delivery note capture at the receiving bay, and supplier compliance documentation. Worth an hour together once the first step is live.