Choose automatic or semi-automatic invoicing
The team could choose whether invoices were created automatically or first reviewed and approved by a user. Card charging was separate: an invoicing prompt or created invoice was not itself a completed payment.
Historical retrospective - May–June 2026
This article was written afterwards and describes the feature as it worked during the stated period.
The team could choose whether invoices were created automatically or first reviewed and approved by a user. Card charging was separate: an invoicing prompt or created invoice was not itself a completed payment.
Choose the flow
Open invoicing settings and choose automatic or semi-automatic processing for your workflow. Then review a concrete upcoming period from the customer or invoicing overview. In the semi-automatic flow, an action appears to create the invoice and, where configured, start the card charge once prerequisites are met.
Timing, day offsets, the first period, and usage affect when an item becomes ready. With automatic invoicing, the hourly payment process first charges eligible saved cards; after a successful charge, the hourly invoicing process can create the invoice with the payment attached. With semi-automatic invoicing, the background process does not charge the card: when the user submits the manual invoice action, the card is captured first and the invoice is created afterwards. A pending or declined payment must not trigger a new purchase or repeated charge without checking the existing state.
Why was the invoice not sent automatically? Check invoicing mode, period status, the customer’s payment method, and accounting requirements.
When is the card charged? It follows the team’s invoicing flow and the payment status; the invoice shows the result.
See the invoicing and delivery guide (Markdown file, AI agent-friendly) for the current view.


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.
