Dinero: better setup, error messages and per-product income accounts

We’ve tightened up the Dinero setup page and how we surface errors from Dinero. At the same time, we now respect the sales account on each of your individual products, so you can have different income accounts per product.

Per-product income accounts

If you invoice different types of products that should be booked on different accounts, you can now control this directly from your products in Dinero. Alunta respects the sales account you set on each individual product, so each invoice line is booked on the correct account - even when a single invoice contains products on different accounts.

• Sales account per product controls which account invoice lines for that product are booked on. Set it in Dinero under Settings → Products on each product.
• Default revenue account is used as fallback when an invoice line has no linked product, or the product has no sales account set.
• Manual account changes in Dinero are preserved when Alunta updates product details. Previously we overwrote the account field on every sync - we don’t anymore.
• Credit notes follow the same logic and also respect VAT-exempt and OSS routing rules.

To use it, just set the “Sales account” on the individual product in Dinero. Once Alunta has refreshed its product list from Dinero (typically within a few minutes), new invoice lines for that product are booked on the chosen account. If you’re happy with all invoice lines being booked on the same default account, you don’t need to do anything - your setup keeps working exactly as before.

Setup page and error messages

If you’ve previously seen a “Validation Error” in your Integration Errors log, or looked at dropdowns full of accounts that wouldn’t work, here’s what’s different now:

• The “Default revenue account” picker now only shows revenue accounts from your Dinero (what Dinero internally calls the “Turnover” category). The same filter applies to “VAT-exempt revenue account” and OSS country accounts. If Dinero doesn’t respond when the page loads, you’ll see an error at the top and the dropdown will be empty.
• “Default deposit account” now uses Dinero’s dedicated deposit account list instead of showing every account. It’s the same list Dinero uses internally when validating payments, so what we show matches what Dinero accepts.
• If you’ve saved an account that’s not (or no longer) in the matching list, we now show an inline warning on that field saying “not a valid revenue/deposit account”. Your previous value stays selectable in the dropdown until you pick a new one - we don’t silently delete anything for you.
• Save blocks in cases where we can verifiably tell the selection is invalid - i.e. when we successfully fetched the account list from Dinero and your value isn’t in it. If Dinero’s API didn’t respond, we don’t block save; we can’t tell whether your account is valid.
• “Default revenue account” is now a required field when the account list has been loaded. Previously the field could be left blank, and sync would fail later without a clear reason.
• If a plan or invoice failed to sync because the field was blank, you’ll now see a concrete message in Integration Errors: “Dinero sync skipped: no revenue account configured…”. After you pick an account, you need to sync the affected items again from the integration overview - it doesn’t happen automatically.
• The Integration Errors list now shows Dinero’s specific message when Dinero rejects something (e.g. “the account isn’t valid”), instead of a generic “Validation Error”. This applies both to new errors and ones already in your log.
• If your Dinero token can no longer be refreshed, you now see a clear message that the integration needs to be reconnected, instead of a generic “Dinero API request failed”.