The job card, the parts it consumed and the invoice are one chain.

Field work is recorded twice in most businesses: once by the engineer on site, and again by whoever turns that into an invoice. The second recording is where parts go missing and labour gets rounded down.

Chikito records it once. A job card carries the labour and the parts it consumed, the parts leave stock, and the invoice is built from what the job actually used.

Field service

What gets in the way

Parts consumed off the books

Van stock is still stock. Parts issued to a job leave inventory against that job, so consumption and cost stay attached to the work that caused them.

Assets out on hire

A rented asset is neither sold nor available. Rentals track what is out, with whom, and when it is due back.

Billing that lags the work

When the invoice is assembled from the job card rather than from memory, it can be raised the day the job closes.

One record, end to end

How the work moves

The same record travels the whole way. No export step, no re-keying between stages.

  1. 01

    Work order

    Raised against the customer and the asset it concerns.

  2. 02

    Job card

    Labour and parts recorded against the job as it is done.

  3. 03

    Return

    Rented assets come back in, and availability updates.

  4. 04

    Invoice

    Built from the job card, posting straight to the ledger.

Questions

Field service & rentals, specifically

Can we track rented assets and sold stock in one system?

Yes — rentals and inventory share the same item records, so an asset's availability reflects both.

Do engineers need a separate app?

Work orders and job cards are part of the same workspace, scoped so each person sees only the work assigned to them.

Tell us how your field service business runs

We'll show you the product working against your processes, not a slide deck.