Nexfatt: invoice drafts from email

Windows software for Italian FatturaPA workflows: reads billing authorizations and prepares XML and PDF drafts. Sending always needs confirmation.

Project-based businesses do not invoice when the work is finished; they invoice when the client authorizes it. That authorization arrives by email, among dozens of other messages, worded differently every time.

Four steps; the last one is yours

The software performs the first three at regular intervals. It never performs the fourth.

  1. Reads your email. It connects to the mailbox through IMAP and downloads only new messages, keeping track of those already reviewed. It works with Outlook, Gmail, Aruba, and PEC mailboxes.
  2. Recognizes the authorization. It distinguishes a message that authorizes invoicing from a reminder, quote, or order. It evaluates the text, sender, message structure, and content of PDF attachments.
  3. Prepares the invoice. It fills in a draft with the amount, order reference, SAL, CIG, and CUP read from the message. It produces FatturaPA XML and a courtesy PDF, and runs local XML checks based on SDI rejection codes; the final outcome is always determined by SDI.
  4. Waits for confirmation. It stops. Transmission always requires explicit confirmation: a transmitted invoice cannot be modified, and an error can only be corrected with a credit note.

Four Nexfatt editions

  • Nexfatt Starter — €59.00, one-time payment, VAT excluded. One workstation, one company. For getting started without a long-term commitment.
  • Nexfatt Base — €99.00, one-time payment, VAT excluded. One workstation, one company. For a single business managing its own invoicing.
  • Nexfatt Pro — €349.00, one-time payment, VAT excluded. Three workstations, three companies. For multiple legal entities or a small accounting practice.
  • Nexfatt Studio — €749.00, one-time payment, VAT excluded. Ten workstations, twenty-five companies. For accounting practices and administrative-services firms.

What the software does not do

These limitations are stated before purchase, not hidden in the terms. Because these are tax documents, it is best to know in advance where the software’s responsibility ends and yours begins.

  • Transmission to SDI is not automatic and cannot be made automatic: every invoice requires operator confirmation.
  • The software does not perform the required ten-year compliant document preservation, which remains the responsibility of the invoice issuer.
  • Recognition is statistical: it may not recognize an unusually worded authorization, which is why messages below the threshold remain available for review.
  • It does not replace accounting software or an accountant: it prepares the document; it does not keep the books.