First Envision

Get in touch.

A few lines is enough. Links welcome. You can also write an email.

DocuMe · Accounting software · our own product · 2025 – now

Forward it. That's the whole job.

DocuMe is our own product. A small Czech business forwards its receipts, invoices and bank statements; each comes back already read, and waits for a person to approve it into Pohoda instead of typing it in.

  • Product
  • Interface design
  • Document reading
  • Bank statements
  • Pohoda integration

Why we built it

Every document reached the books by being retyped.

Czech small businesses keep their books in Pohoda. A receipt arrives as a photo in a chat, an invoice as a PDF in an email, a bank statement as a file nobody can read. Someone types each one in, and a slip turns up a quarter later, in the VAT return.

We built DocuMe so that job becomes a forward, and whoever did the typing does the checking instead. We designed it, built it, and run it ourselves.

For anyone whose books are kept up to date by someone retyping receipts.

What it had to do

  • Take a document however it arrives: a photo, a PDF, a bank file.
  • Read it wherever its supplier happened to put things.
  • Leave the decision to a person, one click per document.
  • Write into a company's books only when two separate decisions allow it.

How it works

In by email. Out as one card.

Every company gets an address of its own. Forward a document to it, or drop it into the app, and it comes back read onto one card: who, when, how much, and the tax.

Checked at the door

Mail to that address is checked, its attachments stored, and the hand-off signed, so the app knows where each document came from.

Read in the background

Reading runs in a queue of its own, so taking a document in never waits for it to be read.

A person decides

Each card waits for someone to check it and approve it. Until then, nothing goes anywhere near the books.

Try it

Forward one.

Pick a document, forward it, and watch what comes back. Then approve it.

Forward

The document Invented

KAVÁRNA NA ROHU

Ukázková 12, Praha

IČO 12345678

8. 9. 2026 14:32

Espresso62,00

Flat white89,00

Croissant68,00

Espresso62,00

Voda 0,5 l45,00

Dort95,00

CELKEM421,00 Kč

z toho DPH 12 %45,11

Děkujeme za návštěvu

What DocuMe read

ReceiptWaitingApproved

Supplier
Kavárna Na Rohu
Date
8. 9. 2026
Total
421,00 Kč
VAT
45,11 Kč · 12 %

Read. Waiting for a person to approve it.

The receipt, the invoice and the statement are invented, and read in advance: the page plays the reading back.

The product

Checking, not typing.

Documents wait in one queue, each with what was read from it, until someone approves it.

DocuMe talks to Pohoda directly, and sends it invoices, credit notes and receipts.

Re-createdInvented documents, the real layout: a forwarded receipt joins the queue, read and waiting.
DocuMe settings, Import from Pohoda: upload a Pohoda XML export when there is no direct connection; importing the same file again creates no duplicates
Demo dataNo direct line? An export from Pohoda does the job.

The hard part

The bank file that disagreed with itself.

Czech banks export statements in one old fixed-width format, under three different file names. DocuMe recognises a statement by what is in it, not what it is called, so a file renamed to slip past an upload filter is still read as one.

The banks' own specifications contradict each other, so every reading keeps the raw field beside what was made of it. Real exports from three banks then proved the specifications wrong in places, and each wrong reading was corrected in place. Nobody had to import anything again.

Try it

Open both locks.

Reading a company's Pohoda needs one approved connection, and changes nothing. Writing needs two more decisions: the company goes live, and an administrator allows writes. Both start closed. Try filing with one of them shut.

  • ReadApproved connection · changes nothingOpen
  • Company is liveThe company decidesClosed
  • Writes allowedAn administrator decidesClosed

Both locks closed. DocuMe reads, and writes nothing.

DocuMe's own rule, played on the page; nothing here touches a real Pohoda.

Where it is now

Live, with no front door yet.

DocuMe runs at app.docume.cz, against both kinds of Pohoda: on a company's own server, and hosted. Connecting one is written up step by step, for someone non-technical to follow on a call with the customer's IT.

Its own website is built and not yet public, so nobody arrives by chance. What it hasn't proved yet is how many companies want it.

DocuMe administration, Pohoda servers: one company's mServer address waits for approval, with writes into that Pohoda switched off
Demo dataThe administrator's side: a company's Pohoda server waits for approval, and writing stays off until someone allows it.

If this is your problem

Your team retypes documents from one screen into another.

We would start with a diagnostic: about a week following your documents from where they arrive to where they are filed, and a written verdict on what can be read automatically, what needs a person, and what it would take.

Next case · Firefly Information Management

Teaching a marketplace what a skill is. →

For founders whose idea needs something the obvious approach can't do.