Know what every unit costs while the month is still open.
Quid codes each supplier invoice line to the right unit, project, cost centre and entity on arrival, flags price changes against supplier history, and posts to your ERP or DATEV.
Unit costs are hard to see
Cost per unit lives in a spreadsheet.
Actuators, sensors, PCBs, machined parts and batteries arrive on dozens of invoices. The build cost is pieced together after the close, when it is too late to act on.
Price creep shows up at margin review.
Supplier prices move between orders. Without a line-level check against history, a few percent on an actuator is invisible until the gross margin moves.
R&D and COGS on the same invoice.
One supplier ships parts for a test rig and a production batch. Coding it as one thing is wrong for the project report and wrong for the tax claim.
Results from teams running Quid.
A physical AI and robotics company. Share of finance team time spent on AP, before and after.
Invoices posted automatically. The rest come to you as exceptions.
From first connection to running on live invoices.
From supplier line to cost per unit.
Many small and mid-size suppliers, often outside the EU. Partial deliveries, credit notes, price changes and FX on nearly every order.
Three-way matching answers whether what arrived matches what was ordered and what was billed.
Parts land on a module before they land on a robot. Coding has to carry that far.
Cost per robot, per fleet, per deployment, built from the supplier lines that went into it.
The same invoice can carry R&D project costs and production COGS. Each line is coded for the treatment it needs.
Cost per unit from the lines themselves
Each supplier line is coded to a unit, project and cost centre at arrival. Unit cost is a report, not a monthly reconstruction.
R&D and COGS split at line level
Prototype parts, test rigs and NRE are separated from production units on the same document, so project reporting and the R&D tax allowance claim both hold.
Three-way matching
Order, goods receipt and invoice checked against each other. Mismatches are held before the payment run.
AP and AR connected
Unit sales, leasing and RaaS subscriptions sit on the revenue side. Quid connects to your sources on both, so cost and revenue are in one system.
Price changes caught on arrival.
Every line is checked against your contract and your supplier history. When a part costs more than it did last order, the line is flagged with the previous price, the new price and the difference, before the payment is released.
One invoice line, five dimensions.
Two dates worth planning for.
1 January 2027. Structured e-invoicing becomes mandatory to issue for German businesses above 800,000 euros prior-year turnover.
Read what applies to you →Investitionsbooster. 30 percent declining balance depreciation applies to movable fixed assets acquired between 1 July 2025 and 31 December 2027. Asset and expense coding at arrival decides whether you can use it cleanly.
Fits your stack. Does not replace it.
Questions
Our BOM is in the ERP or PLM. Does Quid replace it?
No. Quid attributes actual supplier invoice lines to the units, projects and cost centres you already use, and posts back. Your BOM stays where it is.
Can one invoice split between an R&D project and a production batch?
Yes. Coding happens per line, with separate GL, cost centre and project per line.
How are supplier price changes detected?
Each line is compared with your contract terms and previous postings for that supplier and part. Differences are flagged and held before the payment run.
Do you handle non-EU suppliers?
Yes. Multi-currency, import VAT and reverse charge are handled at coding.
What happens when Quid codes something wrong?
Lines below your confidence threshold come to you before posting. Your correction becomes the pattern for next time.
How long does setup take?
2 to 4 weeks.
See cost per unit while you can still act on it.
A 30 minute call on how Quid fits your entity structure and existing stack.
Book a demo