Invoice Metadata Extractor
See what an invoice PDF says about itself: author, software, dates, pages and security.
Write line descriptions specific enough that nobody has to ring you about them.
The result appears here
The Invoice Description Generator writes line descriptions in the shape that gets paid — what it is, what it included, and when — drawing on real line items across thirteen trades, and flags the things that make a description weak.
The line that says "Design work — £3,200" gets queried. The line that says "Brand identity: logo, type scale and colour system, including two rounds of revisions (3 Feb – 14 Mar)" gets paid. The difference costs ten seconds to write and routinely saves three weeks of payment delay.
The pattern is always the same: what it is, what it included, and when it happened. This builds descriptions in that shape, with a catalogue of real line items across thirteen trades — design, web, development, marketing, SEO, photography, consulting, legal, medical, building trades, cleaning, tuition and goods — so you are picking rather than inventing.
It also flags the things that make a description weak: a bare noun with no scope, a date range missing on time-based work, a quantity without a unit, and internal jargon or project code names that mean nothing to the person approving the payment.
Real line items to pick from rather than invent.
The pattern that answers the questions before they are asked.
The fastest way to make an invoice checkable.
Project code names mean nothing to whoever approves the payment.
A PO line, a ticket or a job number — something in their system.
Thirteen sets of real line items, so you are choosing rather than inventing.
The scope, the rounds, the quantity — whatever bounds the work.
Essential on anything time-based, and the fastest way to answer "when was this?"
A PO line, a ticket, a job number — something in their system.
Jargon, missing scope and missing dates are all flagged.
Detailed enough that the person approving it can recognise the work without asking you. That is usually one line: what it is, what it included, and when.
Only alongside a plain description. The person who approves the payment is rarely the person who named the project, and an invoice full of internal codes goes into an exceptions queue.
On anything charged by time, yes. It answers the first question anyone asks about a time-based line and it makes the invoice checkable against their own records.
It can be too long. A description running to four lines is harder to approve than one running to one. Put the detail in a sub-line under the item rather than in the item itself.
What people who use the Invoice Description Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Invoice Description Generator. It takes half a minute and no account.
Write the first reviewSee what an invoice PDF says about itself: author, software, dates, pages and security.
A subscription invoice with the plan, seats, billing period and proration.
Read scanned invoices into CSV rows your accounting system can import.
Labour, materials, testing and certificate references on an electrician’s invoice.
Work out one line: quantity, price, discount and tax, with the arithmetic shown.
What an invoice actually earns after costs, fees, tax and the time it took to get paid.
Reissue an overdue invoice with the days late, interest and an OVERDUE stamp.
Work out a tip, split a bill, and see what each person owes to the penny.