ERP
naios-erpv0.4.0Your company's money within NAiOS: budgets, orders, delivery notes, and invoices with VeriFactu, expenses, stock, treasury, and a business copilot
Description
The NAiOS ERP for any company: product and service catalog, the complete cycle budget→order→delivery note→invoice with branded PDF, series numbering, and invoicing according to VeriFactu (immutable chained records and submission to the AEAT). Collections and due dates, expenses with VAT, stock with alerts, quarterly summaries for the management, and an AI that answers "how much did we invoice in July?" or prepares a budget through conversation.
Features (6)
Immutable chained records, verification QR code, and submission to the AEAT: the legal obligation, solved out of the box
Budget → order → delivery note → invoice with one click, branded PDF, and email sending
VAT per line, equivalence surcharge, and IRPF: from self-employed to LLC without configuring anything strange
Who owes you, what is due, expenses with VAT, and the quarterly summary ready for management
Inventory that decreases when invoicing and increases when purchasing, with minimum alerts
"Make a budget for Acme", "how much did we invoice in July?", "who owes me money?"
Changelog
- FACe: AUTOMATIC sending via the SSPP service (SOAP transport + mTLS like VeriFactu, signed Invoice in base64) — "Send to FACe" button that registers the number only
- Platform gate face_send_enabled (default OFF) + service URL: the circuit is ready, the actual sending is assembled after validating in the FACe test environment with a certificate. The exact envelope is quoted with the official WSDL (verified=false)
- FACe (opt-in PER COMPANY, never out of the box): the three DIR3 codes in the AAPP client record, Invoice with AdministrativeCentres and mandatory SIGNED, and the record of submissions with their statuses (prepared → uploaded → registered/rejected → paid)
- honest v1: NAiOS prepares and signs; the file is uploaded to face.gob.es and the registration number is brought here — automatic transport will arrive with the first real AAPP client rolling
- E3a: official VERI*FACTU footprint (Order HAC/1177/2024) verified against the vectors published by the AEAT, in double chain with the internal one
- SOAP envelope according to official schemas (validated with complete XSD): Breakdown, Chaining, InformationSystem, corrective and cancellation
- Platform switch for submission (factory off): the queue retains with honest status until validation E3b
- AcceptedWithErrors registered as accepted with notice — only a clean acceptance unlocks production mode
- Verification QR code with the date in official format dd-mm-yyyy
- E0-E5: catalog, commercial documents, VeriFactu invoicing (test mode), collections, expenses, stock, and copilot