Know what every mission costs while the month is still open.
Quid codes each supplier invoice line to the right programme, work package, cost centre and entity on arrival, runs the checks before the payment run, and posts to your ERP or DATEV.
Mission costs are hard to see
Which contract paid for this?
Flight hardware, test campaigns and launch services arrive on invoices that say nothing about the work package they belong to. The link is made later, by hand, by one person.
The overhead rate has to hold up.
Cost audits look at the allocation mechanism between labour, material and internal costs. That needs consistent cost centre coding from the first invoice, not a reconciliation at year end.
Funded, eligible and commercial costs sit side by side.
Institutional contracts, R&D tax allowance claims and commercial work run in parallel. The same expense cannot be funded twice, and proving that starts at the invoice line.
Results from teams running Quid.
A space-tech manufacturer. Six times the invoice volume, handled by the same two-person finance team.
Invoices posted automatically. The rest come to you as exceptions.
From first connection to running on live invoices.
From contract to milestone to evidence.
Firm fixed price, ceiling price or cost reimbursement. Each carries its own cost reporting obligation.
Budget sits at WBS (Work Breakdown Structure) level. Suppliers invoice against activity, not against the WBS.
An invoice relates to exactly one milestone, paired with its Milestone Achievement Certificate. Payment follows the certificate.
Long lead hardware, test slots, launch services, advance payments, often in other currencies and under reverse charge.
Nothing in that chain codes the supplier line to the work package. Quid does it on arrival, from your historical postings and your rules.
Project cost report, cost centre subtotals and overhead allocation, each number traceable to its source document and approver.
Line-level coding against your WBS (Work Breakdown Structure)
One invoice can carry lines for three work packages across two entities. Each line is coded separately to GL, cost centre, project and entity. No splitting by hand afterwards.
Price checked against the contract
Supplier lines are checked against contract terms and supplier history. Variances are held before the payment run, not found at reconciliation.
Advance payments and service periods
Launch reservations, insurance and test facility bookings carry service periods. Quid reads the period and proposes the prepaid schedule for you to approve.
Multi-entity, multi-currency
GmbH plus foreign subsidiaries, non-EUR suppliers, import VAT and reverse charge. Central contracts split across the entities that use them.
One invoice line, five dimensions.
Each dimension is assigned at arrival, from your posting history and the rules you set. Nothing waits for the close.
Evidence an auditor can follow.
Every posted line keeps its source document, the reason for the coding decision, the proprietary AI confidence score and the approver. A cost audit question about a work package is answered from the ledger, not from a folder of PDFs.
Two dates worth planning for.
1 January 2027. German businesses above 800,000 euros prior-year turnover must issue structured e-invoices for domestic B2B.
Read what applies to you →R&D tax allowance 2026. The assessment base rises to 12 million euros a year, with a 20 percent overhead flat rate for projects started on or after 1 January 2026. Costs still have to be attributable per project, and the same expense cannot be claimed twice.
Fits your stack. Does not replace it.
Questions
Every mission is different. Can Quid still code our invoices?
Yes. Quid learns from how you have coded invoices before and from the rules you set. Anything it is not sure about comes to you first, and your corrections teach it for next time.
Can we show our auditor where each number comes from?
Yes. Every number links back to the invoice, the reason it was coded that way and the person who approved it.
Can one invoice be split across work packages and entities?
Yes. Coding happens per line, not per document.
We handle export-controlled work. Where does our data sit?
EU hosting with data residency options, role-based access, SSO and SAML. Documents are retained in their original structured format.
Do you replace our ERP?
No. Quid posts into your ERP or DATEV. Your ERP stays the source of truth.
What about non-EUR suppliers and reverse charge?
Multi-currency and reverse charge are handled at coding, with tax codes assigned per line.
See cost per mission before the close.
A 30 minute call on how Quid fits your contract structure and existing stack.
Book a demo