Invoice notes, your reference, our reference, and footer

A customer note, subscription-line text, general footer, your reference, and our reference have different purposes. Fill each field where it belongs and inspect a fictional PDF before use. e-conomic can have separate reference rules for a first sale. Settings do not necessarily rewrite existing invoices, and the accounting system's PDF may place fields differently. See the current guide ### Check a new invoice

All product updates

Historical retrospective - September 2025–July 2026 This article was written afterwards and describes the feature as it worked during the stated period.

A customer note, subscription-line text, general footer, your reference, and our reference have different purposes. Fill each field where it belongs and inspect a fictional PDF before use. e-conomic can have separate reference rules for a first sale. Settings do not necessarily rewrite existing invoices, and the accounting system’s PDF may place fields differently. See the current guide (Markdown file, AI agent-friendly)

Check a new invoice

Create a new test invoice after saving the fields. Identify text from the customer, subscription line, and footer, and check reference placement in the selected PDF.

Choose the right field

Use the customer note for a customer-specific standing text, line text for subscription content, and the footer for a general message. Use Your reference for the customer’s reference and Our reference for the business reference person or internal reference under the provider setup shown. Check a new PDF before sending.

Changing setup is not a correction of old documents.

Where text appears

Alunta’s PDF and the provider’s PDF can display the same field differently. Use the preview for the local version, but also check a booked document when the accounting system generates the PDF. Do not put sensitive payment details in a general footer; it can appear on every relevant invoice.

FAQ and boundaries

Invoice notes are text fields, not payment instructions unless the team chooses to write such details. A footer can be reused across many documents. Test with a fictional invoice and remember that e-conomic, Dinero, and Billy can place the text differently in their PDFs.

Support scenario

The customer’s reference should help the recipient find the purchase, while the business reference points to the internal contact. Do not use the footer for a value meant for one customer, and check whether the provider PDF shows the field.

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.

If the result differs

If the result does not match expectations, keep the visible status and investigate the relevant prerequisite instead of repeating the action blindly. Check currency, date, customer, payment method, and whether the document was already sent or booked. When answering a customer, distinguish what the system recorded from what the bank or recipient has not yet confirmed.

Close the workflow

A safe workflow ends with a new check, not with clicking Save or Send. Open the new invoice, mandate, or payment record and confirm that the result matches the message the customer receives. If confirmation is still missing, describe the status as pending and set the next review point. Record internally what was selected and which status was shown. This makes the next support check concrete and prevents an already accepted delivery, payment, or relation from being treated as new.

Bo Møller
Bo Møller
Emil Højbjerg
Emil Højbjerg

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.