Credits and billing

Credit top-ups, alerts, payment methods and billing details now share the Abonnement et facturation portal (/credits/), organised into offer, wallet and payment views. See the unified portal guide.

Read the wallet

The balance in the top bar and Mon offre is the credit available to the displayed organisation. History lists top-ups and consumption.

Top up the balance

1. Open Abonnement et facturation, then Recharges et alertes.
2. Enter the requested amount excluding VAT.
3. Choose or enter an available payment method.
4. Check the total before confirming.

Billing settings, taxes and accounting file delivery depend on the organisation configuration.

Understand consumption

A conversation can combine several costs: voice duration at the single rate, options, messages, SMS or external services. The customer's operator may invoice telephone charges separately from BeAI.

Credit alerts

An organisation can enable credit alerts by email. Authorised administrators can configure them in Recharges et alertes, with the threshold and notification recipients. Outbound campaigns pause when the balance drops below the required minimum and resume when credit becomes available again.

After consumption is debited, an alert is sent when the balance reaches or falls below the threshold, including SIP, Messenger and Picapp calls. Temporary reservations and unbilled calls do not trigger this alert. Only one alert is sent while the balance remains below the threshold; a top-up rearms it for subsequent consumption. Alerts do not initiate payments. The portal and public API use the same settings.

Invoices and orders

Use Paiement et factures to find top-ups and available documents. Accounting exports use the details and references configured by the root organisation.

Direct invoicing of classic top-ups

For organisations invoiced directly by Beone and admitted to this process, a paid classic top-up can result in an invoice created directly in Odoo. The PDF appears under Payment and invoices when available. Opening an invoice never starts another payment.

For an existing customer whose Odoo link has been verified, invoices use the billing recipients and delivery methods configured in Odoo. Customer records are not overwritten from BeAI. Recipients are frozen when sending starts; a change during a retry requires review.

Only a platform administrator can prepare this switch under Subscription settings, in Classic top-ups: direct invoicing. Select the commercial organisations concerned, enter an ISO 8601 date with an explicit time zone, then use the page’s single Save action. The switch is disabled by default and requires a reviewed list, a date and complete invoicing configuration. Internal or demonstration organisations must remain outside this list.

The date applies to payments actually confirmed from that point onwards. The seller and payment configuration saved on each top-up remain decisive: being in the Beone hierarchy or having a particular name is not sufficient. An organisation invoiced by a third party keeps its usual process, including its UBL export. Previous selections that are no longer available are marked Review required; review them without losing them when changing another form field.

If the order was already open before the chosen date but payment is confirmed afterwards, its invoice is sent for manual review. The paid credit is added normally; no UBL export or automatic Odoo creation or sending is started for this late order. A classic order paid after the organisation subscribes to a plan is also sent for review, without changing the seller.

Activation does not automatically process old top-ups. An invoice already imported or created manually must be explicitly reconciled, without being recreated or resent. An old reference or an ambiguous match blocks automatic creation until it has been checked. If an error occurs or a network response is uncertain, ask for the case to be checked; do not pay for a second top-up to obtain the invoice. Technical reconciliation details are restricted to platform administrators.

The same settings are available through GET and PATCH /api/v1/platform/subscriptions/settings, for platform administrators only. The following example keeps the switch disabled:

{"classic_credit_odoo_enabled":false,"classic_credit_odoo_organisation_ids":[],"classic_credit_odoo_paid_from":null}

The date is normalised to UTC. New IDs must be eligible; retained previous admissions never allow third-party seller invoicing to be forced. An available top-up PDF is accessed through GET /api/v1/credit-orders/{id}/invoice, with the same permissions as viewing it in the portal.

A call can be refused when available credit, after reservations for ongoing calls, cannot cover the minimum starting budget. Included subscription minutes are used first. Insufficient credit is a billing restriction, not a platform outage: check My plan, top up if needed and configure balance alerts. This refusal does not start a billable conversation.

Filtering and browsing history

In Consumption history, choose the unit, movement direction, search text and page size, then select Filter. Reset restores the initial selection. Previous and Next preserve the filters. This history uses server pagination and does not offer the column or export menus of administrative lists.

Consumption is recorded after the call or processing ends; a temporary reservation is not a debit. Euros remain displayed excluding VAT, with included minutes and their period shown separately. Payment and invoice lists retain their statuses, amounts including VAT and available document links. Viewing an item does not retry a payment.