IS WORK OVER?

Automation index

How much of a Billing clerk’s job can AI already do?

An ERP comes earlier. Issuing the right invoice without blocking the client do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Billing clerk

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Orders, delivery notes and the invoice.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
VAT, withholdings and the one that does not square.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Credit notes, the credit and the client who argues.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Close, the immediate supply and the deadline.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Sales, the extra and not over-billing.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
The right invoice, and not blocking the client.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • delivery notes
  • invoices
  • VAT
  • credit notes
  • immediate supply
  • billing close
  • withholdings
  • orders

Sources for this job· O*NET 43-3021.00· ESCO/ISCO 4311

Backend developer

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • endpoints
  • API contracts
  • queues
  • secrets
  • migrations
  • rollback
  • backend tests
  • write server code

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512

Analyse my job

Jobs with similar scores

  1. 162Instructional designer27%
  2. 163Personal trainer27%
  3. 164Writer27%
  4. 166Hospital pharmacist27%
  5. 167Phoniatrician27%
  6. 168E-learning trainer27%