Tinkerbird

Devland · 23 October 2026
Discussion draft · fee to be agreed

About Tinkerbird

Tinkerbird is Akoma’s AI and digital practice. We help businesses put AI to work on the jobs that take up too much time, from capturing paper records to checking invoices and following up on meetings.

We start by understanding how your team works, then build and test practical tools on your own records. Your people keep the decisions and approvals. Start with one useful piece of work and build from there.

Supplier accounts

Supplier invoice checks

Start with around five completed invoices from one supplier. We prepare the checks and the differences in one workbook, so you can compare the result with your accounts team’s work.

Your suggestion was to see a small example before taking on a bigger piece of work. This proposal starts there.

Proposed change

Muhammed spends a lot of his own time checking invoices against the deals he negotiated, including discounts and rebates, and a price that comes in wrong can go back and forth with a supplier’s salesman several times before it is settled.

Today

  1. Capture the invoice line by line.
  2. Compare each price with the deal sheet by hand.
  3. Raise a claim for any difference.
  4. Check the claim again.
  5. Muhammed checks it again.
  6. Tick it off against the supplier statement.

Proposed

  1. Export the statement and invoice lines from React.
  2. Each invoice is matched to its statement line, and each price and discount to the agreed deal.
  3. Accounts review the exceptions list: wrong prices, missing invoices and unclear rebates.
  4. Muhammed approves the exceptions, with the evidence beside each one.

A rebate that depends on later volumes or dates is flagged for a person, never assumed.

Approvals: Muhammed and your accounts team approve every invoice and claim. Nothing is posted to React, paid or sent to a supplier by us.

From our meeting on 22 October and Zubair’s notes. We do not yet know how many invoices a month this covers or how long each check takes; the first step records that for one supplier.

First step

Five-invoice sample

Sample records

One supplier statement, around five historical invoices your team has already checked, and the matching React Excel export, with your completed reconciliation, the agreed deal terms and any credits or payment evidence that affect those invoices. Include an awkward invoice if you have one.

Aadil, head of accounts, or a colleague he nominates walks us through one invoice.

Prepared workbook

An Excel workbook with a source reference for every check, plus the differences and missing evidence that need a decision.

We compare it with your completed work, explain each difference, and record the time our check took beside your team’s estimate for the same five.

Time: allow three to five working days after complete files and agreed scope. We confirm this allowance after inspecting the sample.

Fee: to be agreed before work starts, including VAT treatment and whether the demonstration is separately chargeable. No commitment to a later build or ongoing service.

Five invoices show the method. They do not prove the whole supplier balance.

Starting point

Accounts first

You asked to start on the accounts side, because receiving also depends on purchasing prices and the way goods enter the business. Receiving is the bigger job, and it comes later.

Historical invoices give us something your team has already checked, without changing receiving or connecting to live React. The deal terms put in order here are what a later check at receiving would need.

Possible next steps

Your aim is to digitise in stages, towards a live view across the business. After the sample, each further step would have its own scope and price.

  1. 01

    One statement period

    A trial on one complete supplier statement period: opening balance, invoices, credits and payments.

  2. 02

    Deal prices on record

    Deal terms from supplier meetings loaded once, so every invoice from your agreed suppliers is checked against them and the claims list is drafted for accounts.

  3. 03

    Receiving and management reporting

    Goods still checked by hand; the invoice is scanned and captured, then checked against the same deal prices. From there, build towards the live view you described. Stock accuracy and React integration need separate review.

Meeting minutes

Muhammed asked for meeting recordings turned into short minutes with clear actions. Here is a sample from our meeting on 22 October.

View the sample minutes for 22 October

A separate piece of work from the invoice check, scoped on its own if you want it.

Next step

Arrange a sample-selection session with Aadil and Muhammed through Zubair.

Use that session to confirm the supplier, the files, the fee and the review date. We agree the date when we speak.

Supporting detail

Sample review and limits

Every selected invoice ends as a supported match or a named exception. Amounts, dates, references, prices, discounts and rebate treatment agree with the source, or the difference is explained. Unclear scans and missing price terms stay open rather than guessed. Aadil, or his nominee, checks every line against the team’s finished work, and no saving is claimed before it is measured.

Conditional rebates stay flagged until their volume, date or settlement conditions are evidenced. Partial payments, credit notes, VAT, pack sizes, units and price dates follow the rules your team gives us.

No payments, ledger entries, supplier messages, claims sent on your behalf or changes to receiving are included. The first step works from Excel exports and needs no React login or integration.

Your data

We agree in writing the shared folder, who can see it, which tools process it and how long we keep it, before any file is sent. Send only what the five invoices need. No live-system passwords are required.

Proposal basis

Prepared from the three recordings of our 22 October meeting and Zubair’s notes. React, Excel exports and Aadil’s role as head of accounts are confirmed; who gives final sign-off is still to be confirmed. No Devland volume, saving or implementation commitment is assumed.