Cost invoices, interim invoices to the client, amendments and retentions tied to the stage and budget item. The accountant and the site manager look at the same numbers in the ERP and in the site system.
An invoice from the steel supplier reaches accounting described as "Wilanów". Which BoQ item and which stage, nobody adds. At the end of the build the cost is known, but not where it leaked.
How much you withheld from subcontractors, how much the client withheld from you and when each comes back, one person knows from Excel. After they leave, someone discovers a retention due three years ago.
Progress protocol, statement, attachments, inspector approval, then the invoice. Every step in a different file and a different inbox. Payment terms count from submission, so a week's slip costs money.
The ERP stays the ledger. The integration gives every invoice a site, a stage and a budget item, and sends the result back to where the site manager and the board look.
Three years ago features like these needed a data science team. Today language models read emails, documents and photos, and we build them into the system we make for you. Below is what makes sense in this solution. A person approves, AI prepares.
AI reads the invoice from KSeF or a PDF, recognizes the supplier, the material and the site from the description and the purchase order, and proposes a budget item. The site manager approves with one click.
Example invoice "B500 reinforcing steel, 12 t, delivery Wilanów" → site Wilanów, stage "structure", BoQ item 2.3, for approval
A unit price above the purchase order, a quantity above the delivery note, a second invoice for the same stage from a subcontractor. The alert goes to the site manager, not to the accountant after the fact.
Example a concrete invoice priced above the framework agreement with the batching plant → held for clarification with a price comparison
The model compares the pace of spending and progress with the history of similar sites and shows where a stage budget will not close, before you see it in the invoices.
Example plumbing: most of the budget spent at half the progress → an overrun forecast with amount and stage, for a conversation with the subcontractor
The board and the site manager ask in plain language, the answer comes from ERP and site system data.
Example "how much retention do we owe subcontractors this quarter?" → a list of six with amounts, dates and sites
We do not replace Comarch or enova. Invoices come in where they do today, and the integration adds a site, a stage and a budget item and sends the result to the site system.
We start with the flow that hurts most. Usually that is assigning cost invoices to the budget. Retentions and interim invoices follow once the first flow runs.
You have the diagnosis, we build the solution. Web applications, B2B portals and automations for companies without a large IT department. Today a system can read emails and documents, suggest decisions and answer customers on its own, so we build that in from the first version, not as an add-on a year later.
We agree scope, price and dates upfront, show progress every week, and the code and data stay yours.
You describe how an invoice travels from site to accounting today and where the retentions are, we tell you which flow to start with and how long it takes.
Write to us