The product by dev2soft

Levora reads the ticket and writes the invoice

From the GAEB bill of quantities through the handwritten measurement to the invoice for the public authority – one chain instead of five tools with a spreadsheet in between.

Built for firms working under framework contracts for road authorities.

levora
Levora – bill of quantities detail with positions, quantities and totals
  • GAEB DA XMLX81 – X84
  • REB 23.003Quantity survey
  • EN 16931XRechnung · ZUGFeRD
  • RSA 21Traffic sign plans
  • GDPRDPA available
  • Hostingin Germany
  1. One site, three items

    What gets built outside ends up on the invoice

    Scroll through a job site: every item the foreman writes down becomes a line.

  2. 01 / 0303.04.0020

    Set kerbstone, concrete

    18.50 + 13.00 = 31.50 m

  3. 02 / 0303.02.0040

    Prepare chippings bed

    21.40 × 3.00 = 64.20 m²

  4. 03 / 0303.02.0010

    Lay concrete paving, 10 cm

    21.40 × 3.00 = 64.20 m²

  5. Three jobs. Three lines. One XRechnung.

    Every figure is put to you for approval. Levora posts nothing on its own.

What arrives in the office

Positions read from the ticket with quantity and unit
ItemDescriptionQuantity
03.04.0020Set kerbstone, concrete31.50 m
03.02.0040Prepare chippings bed64.20 m²
03.02.0010Lay concrete paving, 10 cm64.20 m²

XRechnung to EN 16931

The core

The paper stays. The retyping does not.

Almost every construction software promises to abolish the paperwork. We think that is the wrong move: on a public contract the signed ticket is the evidence, and nobody operates a tablet on site. Levora does not abolish the ticket – it reads it.

1What comes off the site
A hand-filled take-off sheet with 3 items, 3 of them showing the calculationAUFMASSBLATTBauvorhabenDatumBlattPos.-Nr.LeistungBerechnungMengeAufgenommenUnterschrift

Ballpoint pen, a crease in the paper, the foreman’s signature.

2What arrives in the office
Positions read from the ticket with quantity and unit
ItemDescriptionQuantity
01.02.0030Mill off asphalt surface course, 4 cm128.50 m²
01.02.0040Lay bituminous base course96.00 m²
01.04.0110Lift and reset kerbstone24.00 m

XRechnung to EN 16931

Every figure is put to you for approval. Levora posts nothing on its own.

The chain

Six steps – and the hard one is not the invoice

Producing an XRechnung is no great feat any more; a one-off tool and the federal portal both manage it. The work sits in the steps before. That is where Levora starts.

  1. 1Read in the bill of quantities

    Levora – imported bills of quantities in the overview

    The client’s GAEB file becomes the position master – read in as X81 or X83.

  2. 2Price the positions

    Levora – positions with quantities, units and unit prices

    Unit prices entered once, then valid for every call-off.

  3. 3The ticket from site

    Levora – incoming site tickets by date and district

    Filled in by hand, signed, photographed.

  4. 4Read the measurement

    Levora – review view with the quantities read from the ticket

    Levora reads the quantities and puts every one of them up for approval.

  5. 5Quantity onto the position

    Levora – measured quantity assigned to a contract position

    The approved quantity attaches to the position number from the contract.

  6. 6Invoice to the authority

    Levora – invoicing from approved positions

    XRechnung or ZUGFeRD, from those same positions, with the Leitweg-ID.

The difference

Every figure on the invoice leads back to a signed ticket

When the authority asks why position 01.02.0030 says exactly 128.50 m², there are two possible answers. One is the folder someone has to search. The other is a click on the position, underneath which sits the photo of the ticket the figure came from – with date, district and signature.

That is why Levora does not abolish the ticket. A tablet form produces a record. A signed ticket produces evidence.

levora
Levora – an invoiced quantity next to the ticket photo it came from

Sound familiar

Where billing under a framework contract gets stuck

  • The ticket sits in the van for three weeks before anyone sees it
  • The same quantity is typed twice – once on paper, once into Excel
  • At invoicing, nobody can find the call-off it belongs to
  • The invoice bounces because the Leitweg-ID is wrong
  • A colleague is on holiday and nobody knows what is still open

Honestly

Who Levora is not for

  • Not for building construction. The fit is road and civil engineering, with REB, standard traffic plans and framework contracts
  • Not for large firms. Beyond roughly fifty employees you need things Levora deliberately does not do
  • Not bookkeeping. Levora issues invoices; it does not replace your tax adviser
  • Not without paper. If you already measure on a tablet, there is little here for you
  • Not for a handful of jobs. Below about twenty call-offs a month the switch rarely pays

What Levora is built for

The work this is about

Hazard site repair

A hundred small jobs a month, each one to be evidenced separately.

See use cases

Reading the tickets

How handwriting becomes a checked quantity – and where the limits are.

See features

The whole chain

From the GAEB bill of quantities to the invoice, in one place.

See Levora

Go deeper

More about the product

Features

From BoQ upload and review to approval and invoicing.

See features

Use cases

Hazard sites, framework contracts, road building, paving, sewer work.

See use cases

About dev2soft

Who is behind Levora, and what we deliberately do not offer.

About us

Common questions

What firms ask first

Do we have to change the way we work?

Not on site. The Zettel stays paper, the signature stays a signature. What changes is the route from the Zettel to the invoice – it no longer runs through retyping.

Can we bring our existing bills of quantities across?

Yes. GAEB files of phases X81 and X83 are read in, the bid goes back as X84, and the item numbers stay the ones from the contract.

How long does the introduction take?

That depends on how many running contracts are to be brought across. It can only be answered reliably after a look at your documents – which is why the demo runs on your own files and not on a sample data set.

What happens to our data?

Processing in Germany, with a data processing agreement. Zettel carry names and addresses, so the processing routes are chosen such that no content is used to train third-party models.

By dev2soft

A product by dev2soft

Built and operated in Germany

Levora is the first product of its own from dev2soft. Read who is behind the product.

About dev2soft

Something like this for your industry?

What we built for road and civil engineering, we also build for other industries and for individual companies.

Industry software

Go through it on your own documents

Bring a contract bill of quantities and two or three filled-in tickets. Half an hour on those shows whether the switch pays for your firm.

Funding and Digitalbonus

Which German programmes still subsidise digitalisation in a construction firm, what expired in 2024, and where to check your federal state.

Learn more
In preparation

Pricing

How the price for Levora is put together: a company base instead of a per-head price, no setup fee, full data export at any time.

Learn more

Security and data protection

Where the data sits, what is encrypted, how the Zettel recognition treats your documents – and what is not there yet.

Learn more