Send an invoice and PDF - and find the delivery history
The invoice could be sent from its own view with the selected PDF. The document must be ready and the recipient reachable. Open the invoice, choose send, review the recipient, and confirm. In delivery history, a recorded message with a delivery ID means the email attempt is confirmed; an entry without an ID is still pending or unconfirmed. That does not mean it was read. A resend is a new delivery attempt and does not change payment or booking. A PDF from an accounting system may wait for booking and a final number. An EAN rejection is a separate document-delivery status. See the current guide ### Practical check
Historical retrospective - September 2024–October 2025 This article was written afterwards and describes the feature as it worked during the stated period.
The invoice could be sent from its own view with the selected PDF. The document must be ready and the recipient reachable. Open the invoice, choose send, review the recipient, and confirm. In delivery history, a recorded message with a delivery ID means the email attempt is confirmed; an entry without an ID is still pending or unconfirmed. That does not mean it was read. A resend is a new delivery attempt and does not change payment or booking. A PDF from an accounting system may wait for booking and a final number. An EAN rejection is a separate document-delivery status. See the current guide (Markdown file, AI agent-friendly)
Practical check
If an email is marked sent but the customer cannot find it, check the recipient address, spam filtering, and selected PDF. Resend when the document is ready, but do not treat delivery history as proof of reading or payment. Missing delivery can also mean the document number is not final yet.
Questions: Can a PDF be sent alone? Follow the send option shown. Does resend create another invoice? No, it is another delivery attempt.
Resend workflow
Open the specific invoice rather than only the customer. Check email address, document number, PDF source, and any attachments. Read the delivery log and note whether the latest entry is confirmed or pending. Correct the recipient when needed, choose resend from the invoice actions, and confirm that a new delivery entry appears.
An invoice can be sent without being opened. It can also be delivered while still unpaid. If the document is waiting for booking, resend cannot help until it is ready. For repeated delivery problems, the customer should check mail reception and the team should check document status.
Example: An invoice is marked sent but the recipient cannot find it. The team confirms the address, downloads the selected PDF, and resends. The old invoice does not receive a new amount or payment state; only delivery history gains another attempt.
FAQ and boundaries
Delivery history helps answer “when was it sent?”, but it does not show that the recipient’s server accepted or read it unless the specific status says so. An Alunta PDF and an accounting-system PDF can have different layouts. If the customer pays by bank, check the details in the PDF actually sent. Resend does not change invoice number, lines, credit, or payment status.
Support scenario
Do not treat a local PDF as proof of delivery. The delivery log and its specific status show the attempt. If the customer needs a copy, use the same document source selected by the team. Sending and resending do not change the original invoice due date.
Check after the action
Use this check during follow-up: note what was visible before the action, perform only the selected action, and check the document or mandate afterwards. Read a status again before informing the customer if it changes later. The retrospective describes the documented milestone; the current guide and interface determine today’s steps. Examples use fictional customers, amounts, and dates.
The people and AI helpers behind the updates
Bo Møller and Emil Højbjerg are the primary developers behind Alunta. They spend most of their time coding, so they have delegated the wording of these explanations to our AI helpers.
The AI helpers write from the updates we have deployed to the product. Bo and Emil are behind the changes and remain responsible for ensuring the information reflects what was actually released.
