Skip to content

Documents and invoices

Invoices and orders reach your system on their own.

I connect your inbox, scanner and KSeF to your accounting system: every document is parsed, checked against named rules, approved by a person and posted. You keep a working pipeline, an error queue and a handover pack any other developer can pick up.

Talk it through

from €1,690 net

26 August

Document queue

  • Purchase invoices from KSeFpulled through the API182 posted
  • Scans and PDFs outside KSeFforeign suppliers, receipts38 of 41
  • Orders from the inboxPDF and Excel, matched to records61 of 64
  • Waiting for human approvalover €1,200 net or a new supplier7 items
  • Error queuemissing tax ID, account outside the VAT register6 items

Posted without manual typing281 of 287

A typical day at a wholesaler: 287 documents in, 6 waiting for a person in the error queue, nothing posted without passing the rules.

Where it hurts

Paperwork eats hours that never show up in the budget

Four situations accounting offices and wholesalers describe most often.

  • Someone retypes invoices by hand

    It looks the same in an accounting office and in a warehouse: someone opens a PDF and retypes the tax ID, the amounts and the line items into Comarch Optima or Subiekt. The market benchmark for manual processing is around 10.9 USD per invoice against 2.8 USD with automated capture. At 500 documents a month that gap shows up in people's calendars, not just in a cost sheet.

  • Orders arrive in ten different formats

    One customer sends a PDF, the next a photo of a delivery note, the third an Excel sheet, the fourth types the line items into the body of the email. A salesperson rekeys all of it and gets product codes and quantities wrong. The format changes the day a supplier upgrades their system.

  • KSeF did not cover everything

    KSeF is already mandatory: since February 2026 for the largest taxpayers and since April 2026 for the remaining VAT payers. Invoices from foreign suppliers, receipts, warehouse documents and orders never enter it and arrive exactly as before. Half the document flow stays outside the register.

  • Errors surface at month-end close

    A duplicated invoice, a bank account outside the VAT register, a price that is not the contracted one: all of it turns up on the last day. The clean-up runs over email because nothing shows which document is stuck and why. There is no record of who approved what either.

What you get

Six parts of a working pipeline

Not a deck and not a prototype. Things that stay with you after handover.

Document intake

A mailbox in Google Workspace or Microsoft 365, a scanner folder, a network drive and the KSeF API. Attachments, email bodies and spreadsheets travel the same route. Every document gets an id and an archived copy before anything else happens to it.

Field extraction, not full text

From an invoice I pull the seller, the tax ID, the number, the dates, net, VAT, gross, the bank account and the line items. From an order: the customer, product codes, quantities and prices. The OCR model is picked per document type, because a faxed scan and a system-generated PDF are two different jobs.

Validation rules

Duplicate, missing tax ID, bank account outside the Polish VAT register (biała lista), price off the agreed list, quantity above what was ordered. Each rule has a name, so you can see which one stopped a document. Rules are described in plain language in the docs, so an accountant can read them without a developer.

Human approval gate

Anything above the agreed limit, every new supplier and every document with a warning waits for a person. You approve in the panel or in Slack, in one click, with the original next to the extracted fields. Nothing moves on without that approval.

Write-back into your system

Comarch Optima and ERP XL, Subiekt GT and nexo, enova365, wFirma, ifirma, BaseLinker. Through the API where your licence allows it, through an import file where it does not. Sales invoices can go on to KSeF through its API.

Error queue and handover

A screen listing the documents that failed, with the reason and a retry button. Plus the repository, a flow diagram, a runbook and the list of credentials. You do not need my phone number for this to keep running next year.

How it runs

Three weeks from samples to production

Every stage ends with something you can check on your own documents.

  1. Week 0

    Samples and quote

    You give me 40-60 real documents from the last month and access to a test database. I check what can be read automatically and what will always stay manual. The output is a fixed scope and a fixed price, before any contract.

  2. Week 1

    Extraction and validation

    I build the intake: a mailbox in Google Workspace or Microsoft 365, the scanner folder, the KSeF API. Documents are split into fields, the tax ID and bank account are checked, and everything is matched against your customer records. I show accuracy on your files, not on a demo.

  3. Week 2

    Write-back and approval

    I wire the write-back into Optima, Subiekt, enova365 or wFirma, through the API or an import file depending on what your licence allows. A gate sits above it: amounts over the limit and new suppliers wait for a human click.

  4. Week 3

    Production and handover

    The pipeline runs alongside the manual process for a few days and we compare results on the same documents. Then we switch over and you get the repository, the diagram, the runbook and every credential. From that day you can run it yourself or with me.

Packages and pricing

One document flow

from€1,690

One stream of documents from intake to a posted record in your accounting system. Usually purchase invoices or orders from the inbox.

  • Intake: mailbox, scanner folder or KSeF API
  • Parsing of PDFs, scans and Excel sheets
  • Checks: tax ID, VAT register, duplicates
  • Approval gate with an amount limit
  • Write-back to Optima, Subiekt, enova365 or wFirma
  • Repository, runbook and handover

Accounting office: 300-800 purchase invoices a month.

Several flows and ERP

from€3,350

Two to four streams plus write-back into the ERP: the document, the customer record, the warehouse document and the order.

  • Everything in One document flow
  • 2-4 document streams
  • Write-back to Comarch ERP XL, Subiekt nexo, enova365
  • Order to delivery to invoice matching
  • Error queue with retry and history
  • Sending sales invoices to KSeF via API

Wholesaler: email orders, purchase invoices and BaseLinker.

Care after launch

from€125/mo

Keeping a live pipeline healthy: monitoring, rule fixes and reacting to changes on the vendors' side.

  • Error queue monitoring and alerts
  • Parser fixes for new document layouts
  • Updates after KSeF and ERP API changes
  • Up to 3 hours of changes a month
  • Reply within one business day
  • Monthly agreement, no notice period

Polish integrators publish roughly €500-9,000 a month to maintain builds like this, depending on scope.

Fixed net prices, agreed after I look at your real documents; in Poland I invoice in złoty (7,200 zł, 14,400 zł and 530 zł a month). The only separate cost is OCR and model usage on your own account.

When not to buy this

I would rather say it before the contract than three weeks in.

  • You handle fewer than 100 documents a month. The OCR built into wFirma or ifirma is enough and costs a fraction of this.
  • Your system has no API and no import format, and the vendor has no plans to open one. Clicking around someone else's interface is not something I sell as a stable solution.
  • You want someone to take responsibility for the books. I deliver the pipeline and the checks; accounting decisions stay on your side.
  • You need a 24/7 response contract. I work alone, so the honest commitment is one business day.

If what you actually need is a store wired to stock and an ERP, that is a separate service: Services

No call needed

Fixed estimate in 24 hours

Describe the task in two sentences. You get a fixed price, a timeline and a plan. If it isn't a fit for us, we say so straight away and point you elsewhere.

  1. 01We read the task and ask two or three questions if anything is unclear
  2. 02We put together the estimate: scope, price, launch date
  3. 03It lands in your inbox within a day. The next move is yours

No newsletters, no unsolicited calls. The answer comes by email.

How we handle your data is explained in our privacy policy.

Questions before we start

  • One document flow starts at €1,690, several flows with ERP write-back start at €3,350, and care after launch starts at €125 a month. The exact number is quoted after I look at your real documents, before any contract. Polish integrators publish bands of roughly €19,000-58,000 for a pipeline that writes into an ERP, because they scope the whole company; I do one process end to end.

  • Yes, if your licence gives you an API or an import format. Comarch Optima and ERP XL, Subiekt GT and nexo, enova365, wFirma, ifirma and BaseLinker all have documented interfaces and I work with each of them. Before quoting I check on your own installation whether the write-back goes through the API or through an import file, because that changes the scope.

  • Because part of your cost documents will never pass through KSeF. Invoices from foreign suppliers, receipts, warehouse documents, contracts and orders still arrive by email as PDFs, scans or spreadsheets. KSeF tidies up domestic invoices; the rest of the flow stays on your desk, and that is the part I automate.

  • A person is, because nothing reaches the books without approval. Every document passes named rules: tax ID, VAT register, duplicate, match against the order. Anything above the agreed limit or from a new supplier waits for approval, and documents the pipeline does not understand land in the error queue with a reason attached. Every action is logged: who, when, and against which version of the file.

  • Three weeks from handing over sample documents to the first day in production. One week goes to extraction and validation, one to write-back and the approval gate, one to running in parallel with the manual process. With several flows and ERP write-back it is usually five to six weeks.

  • From €125 a month for care, plus your own bill for OCR and the model. Vendor pricing is public: Google Document AI charges 1.50 USD per 1,000 pages of basic OCR, Azure Document Intelligence charges 10 USD per 1,000 pages on its prebuilt invoice model and 30 USD on a custom one. At 500 documents a month that is single-digit euros, not hundreds.

  • You are left with a working system and full documentation. The code sits in your repository, the pipeline runs on your infrastructure in the EU or in your own cloud account, and the keys and credentials are yours. The handover includes the flow diagram, the validation rules written out, and a runbook: what to do when a supplier changes a file format or an API stops responding.

Google reviews

5.0

5.0 out of 5 · 3 reviews

  • We received a request to develop an online store that included an AI-powered chatbot and Stripe payment integration. Everything was delivered on time, and we’re continuing to work together. I highly recommend them.
    Volodymyr Likholetovin the last week · Google
  • An excellent developer and a true professional. The work was completed strictly on time, communication was pleasant, everything was done quickly and to the point. I highly recommend him to anyone looking for a reliable, competent specialist.
    Alina Rudenkoin the last week · Google
  • A great programmer. He created an online store quickly and on time.
    Алексa week ago · Google
Let's build it · Open for new projects

Free 30-minute call. No sales pitch - just a real conversation about what you need and whether we're the right studio to build it.

  1. 30 mindiscovery call
  2. 24 hoursfixed estimate
  3. 0hidden invoices
5.0 · 3 reviews

No sales pitch - just a clear read on your scope.

WhatsAppLet's talk