Live at RR42 · AI Native Systems of Record
NakedERP: One case, from quote to e-invoice.
NakedERP runs quote, order, project, installation and invoice of a commercial-kitchen builder as one continuous thread. Nothing is entered twice, and from any document you reach the others. People and AI agents work in the same records, under the same rules.
Talk to us On the right: the job sheet of an example project.
- 1SalesQuoteQuote with costing, from the enquiry
- 2SalesOrderCreated from the quote, nothing retyped
- 3Project managementProjectProject with tasks and plan
- 4InstallersInstallationInstallation job, installers work in the installation app
- 5AccountingInvoiceProgress invoices as work advances, then the final invoice
Final invoice: how much does the customer retain as security?
Example invoice of €100,000.00. The project manager sets the percentage on the project.
Payment schedule of the invoice · no retentionretention 5%retention 10%
The receivable stays in full. The retention only falls due later.
The invoice leaves NakedERP as an e-invoice: XRechnung or ZUGFeRD.
Each step builds on the one before. It is the same case, not a new document to retype.
- Specification (GAEB)
- Quote costing
- Order
- Project plan
- Delivery note
- Installation job
- Quantity survey
- Variation order
- Daywork sheet
- Defect
- Progress invoice
- Final invoice
- Security retention
- Construction withholding tax
- XRechnung
- ZUGFeRD
- Peppol
- DATEV export
- Maintenance contract
What it covers
NakedERP was built for companies that plan, build and install commercial kitchens, and it runs RR42's own business. It covers CRM, quotations, sales, purchasing and stock, manufacturing, projects and installation jobs, and accounting. Documents leave it as e-invoices (XRechnung, ZUGFeRD, Peppol) and as exports for the accountant (DATEV, Sage BOB). A bank connection, SEPA payment and direct debit runs and a cap table are part of it. Users and agents sign in with RR42's identity service, and the handbook for people is in German.
Chapter 1 · Security retention
The receivable stays whole. The retention falls due later.
On construction contracts the client often retains part of every invoice as security, typically 5% until the end of the warranty period. The project manager enters the percentage once on the project. Every outgoing invoice of the project then gets a payment schedule with two rates.
- After the warranty period, the report “Security retentions” shows the status “Due – request payment”.
- A retention can be replaced by a guarantee.
- If the customer claims the retention because of a defect that was not fixed, NakedERP creates the credit note itself.
Chapter 2 · Installation
The installer enters it. The office sees it at once.
The installation app is where installers work on site. It shows the installation jobs with address, contact person and scope of work. Every saved entry is immediately in the installation job, and so with the office.
- It runs in the phone's browser, nothing has to be installed.
- The customer signs daywork sheets, the briefing record and the handover right on the display.
- Installers report defects on the spot. An entry counts as saved only once the installer confirms it; the app does not work offline.
Chapter 3 · E-invoice
The booked document becomes the e-invoice.
NakedERP creates it from every booked progress invoice and from every outgoing invoice with an e-invoice profile. Public clients such as hospitals, municipalities or state agencies often demand an XRechnung.
- XRechnung: a pure XML file. The client's Leitweg-ID is mandatory.
- ZUGFeRD: a PDF of your invoice with the XML embedded. The customer reads it like a normal PDF, their software reads the XML.
- For sending over the Peppol network, NakedERP also creates an invoice in the Peppol format. Incoming e-invoices become drafts.
- Attachments of booked documents are copied into a per-company archive with a SHA-256 checksum and a retention period, with access for tax audits, holds and a regulated disposal afterwards.
Chapter 4 · AI agents
An agent works as you, with exactly your permissions.
A system of record is where the truth of a business lives. If AI agents are to do real work, that is where they have to work: not in a copy, not behind an export, but in the records, with the same checks as anyone else. NakedERP has a built-in MCP server, and every feature can be used through it, not only a selection.
- The user's roles, record restrictions and field permissions apply. A refusal for lack of permission is final.
- Before it posts, cancels, deletes or sends, the agent asks.
- Each call is logged under the user it acts for, without the payload.
- An AI suite reads tender documents and supplier receipts into reports, bid recommendations and price records that people review.
You Show me the open defects in the project Klinikum Musterstadt.
Agent Defects read, with your permissions.
You Create an order as a draft from the quote.
You Yes, post it.
Log Call recorded under your name, without the content of the request.
Shortened example dialogue
Talk to us.
NakedERP runs at erp.rr42.de and keeps RR42's own books. Stripe payments for rufio subscriptions are booked there automatically and turned into ZUGFeRD e-invoices. For other companies, an instance is set up on request. If you would like to know whether it would fit your company, or how agents could work in your records, talk to us.