Getting started with Billy

Billy was added as a separate accounting integration. Connect Billy, complete authorization, and check status, business, and product choices. The current connection supports the document types shown in setup, including invoices and credit notes; a payment is a separate action. Do not copy e-conomic or Dinero fields into Billy. Test with synthetic data and inspect issues and relations in the interface. See the current guide ### What to check

All product updates

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

Billy was added as a separate accounting integration. Connect Billy, complete authorization, and check status, business, and product choices. The current connection supports the document types shown in setup, including invoices and credit notes; a payment is a separate action. Do not copy e-conomic or Dinero fields into Billy. Test with synthetic data and inspect issues and relations in the interface. See the current guide (Markdown file, AI agent-friendly)

What to check

Check the document type before sending and verify customer and product relations. A connected account does not mean every document type or payment flow is available. Use the status and fields Billy displays, then follow the document’s booking afterwards.

First Billy document

Connect Billy and select the business that should receive documents. Review one product and customer before creating an invoice. Check whether the selected PDF comes from Alunta or Billy and whether its number is local or assigned at booking. Send one synthetic document and follow status in both systems.

Review a credit note as its own document. A payment or refund is a separate flow. If a field is not present in Billy’s setup, do not invent an equivalent e-conomic value. Use the available option and check the result.

Questions: Why is a relation pending? The account or product is not ready. Why is the document missing in Billy? Booking or synchronization may still be pending.

Provider-specific boundaries

Describe the Billy connection from the choices actually shown in the Billy module. One plan can have a product mapping while another lacks a valid item, so check each plan before sending many documents. If Billy supplies the PDF or number, wait for the booked status before sending it to the customer.

FAQ: Can Billy receive every Alunta document? Use only the types shown in setup. Is a local payment automatically sent? Only when team payment sync is ready. Must a refund be a credit note? Follow the selected money flow and document status separately.

FAQ and boundaries

Test a Billy integration with one document at a time. Check product, customer, and currency before sending, and see whether Billy accepts the document. Acceptance of delivery does not mean the customer paid. A credit note can affect the original invoice while a refund follows the payment record. Use the current interface to see which actions are available.

Support scenario

After Billy accepts a document, still check the local invoice and payment separately. A document accepted by the provider can be unpaid by the customer. Resolve a missing product or customer relation in mapping, not by registering a fictitious payment.

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.

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.