Invoice Requirement.md

1. ORGANIZATIONS MODULE

1.1 Add Billing Usage Question

• Add a mandatory question in the Facturas tab: “Do you want to use DBDriver Movilidad as invoicing software?” Options:
  • Yes, I want to use it as invoicing software.
  • No, I prefer to manage invoicing myself.
• Display mandatory legal note depending on the option chosen.

1.2 Logic When Answer is NO

• If the user selects No, stop asking for additional invoicing-related data.
• Tickets will be generated instead of invoices.

1.3 Logic When Answer is YES

• Ask the administrator to enter legal text to include as invoice footer.

• Implement the Nemon API processes:

  1. Generate the otorgamiento using Nemon API.
  2. Import otorgamiento.
  3. Automate receiving validation response:
     • If validated → start production.
     • If rejected → allow regenerating.
  4. Once validated, store the Nemon API Key.
  5. Include otorgamiento information in the organization data.

2. INVOICES MODULE

2.1 Integration with Nemon

• When invoices are created, send invoice data to Nemon API.
• Receive a QR code from Nemon:
  • QR links to AEAT, showing date, amount, issuer, invoice type.
• Attach QR to the invoice PDF.
• Research/implement sending the PDF to Nemon to receive QR embedded back. (Pending definition by client).

2.2 Tickets Module

• Tickets must be viewable and downloadable.
• Tickets do not include a QR code.

2.3 Extra Charges Module

• Allow creating extra charges on reservations.
• Each extra charge generates a new invoice or ticket depending on the organization settings.

2.4 Returns (Refunds) Module

• Allow partial or full returns for invoices.
• Returns generate:
  • Full refund: same invoice series, negative amounts.
  • Partial refund: create a rectificativa por diferencias with a different series.
• Need to study rectificative guidelines (red area—needs definition).

2.5 Remove Serialization Module

• Remove the serialization configuration module.
• Enforce fixed numbering format: IDORG – INVOICE NUMBER – YEAR
• Apply same numbering pattern to tickets (field renamed to “ticket number”). 

2.6 Rectification for Wrong Billing Details

• If a user wants the invoice in their company name after reservation, create a rectificativa por sustitución (same amount, only name change). 

3. RESERVATIONS MODULE

3.1 Automatic Billing

• When reservations are created, system generates an invoice or ticket automatically depending on organization setup.

3.2 App Download Behavior

• If user downloads a document from the app and it is a ticket, show message: “This document is not a valid invoice. It is a ticket without fiscal validity. If you need an invoice, contact the rental provider.” 

3.3 Backoffice Reservations

• Admins can also create reservations from backoffice.
• Once reservation is created, invoice cannot be edited.
• For offline payments, ask admin to confirm key data before closing reservation to ensure invoice cannot change later.

4. USERS MODULE

4.1 National Format Validation

• If user enters a national-format recipient, validate their NIF before moving to document upload screen.