Credits and billing
Check balances, top up the wallet, and manage any pending subscription top-ups.
Top-ups, alerts, payment methods, and billing details are now managed in Subscription and billing (/credits/). The My plan, Top-ups and alerts, and Payment and invoices views bring these journeys together. See the dedicated space guide for details.
For an organisation billed directly by Beone, top-ups do not depend on the balance or payment method of the Beone root organisation. Your billing details must be complete and payment must be confirmed before credit is added. If your seller is an intermediate reseller, its prefunding checks still apply. The portal and API use the same rules.
Reading the wallet
The balance visible in the top bar and in My plan corresponds to the credit available for the displayed organisation. The history details top-ups and usage.
Topping up the balance
- Open Subscription and billing, then Top-ups and alerts.
- Enter the requested amount excluding VAT.
- Select or enter the proposed payment method.
- Check the total before confirming.
Billing settings, taxes, and accounting file delivery depend on the organisation's configuration.
Understanding usage
A conversation may combine multiple costs: voice duration at the single rate, options, messages, SMS, or external services. Telephone charges from the customer's carrier may be billed separately from BeAI.
Credit alerts
An organisation can enable email credit alerts. Authorised administrators can configure it in Top-ups and alerts, along with the threshold and notification recipients. Outbound campaigns are paused when the balance falls below the required minimum, then resume once credit is restored.
After a charge, the alert is sent when the balance reaches or falls below the threshold, including for SIP calls, Messenger calls, and Picapp calls. A provisional hold or an unbilled call does not trigger this alert. Only one alert is sent as long as the balance remains below the threshold; a top-up rearms the notification for future usage. The alert does not trigger any payment. The same settings apply from the portal and the public API.
Subscriptions and pending top-ups
When a monthly subscription depends on credit from a parent organisation, the top-up is placed on hold if this parent lacks the required amount. It is released immediately once the parent completes a sufficient top-up, whether via the portal or the public API.
If the client organisation changes parent organisation, BeAI automatically reassigns the pending top-up to the new parent and immediately attempts to release it. If their credit remains insufficient, the top-up retains its pending status and will be retried after a subsequent top-up as well as during the daily check.
Invoices and orders
The Payment and invoices view allows you to retrieve top-ups and available documents. Accounting exports use the details and references configured by the master 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.
Website customers with included minutes
For organisations on a website plan, My plan displays minutes as the primary indicator and additional credit separately. See the Subscription and billing guide for renewal rules, overages, Odoo invoices, and cancellation.
Configuration assistant
Sessions offered by Beone do not charge the customer. New sessions confirmed as billable consume included minutes first, then contract overages, or euro credit. The Configuration assistant transaction appears in the history with its unit; any hold placed during the conversation is provisional. See measurement rules and examples.
A call may be rejected if the available credit, after accounting for holds on ongoing calls, does not cover the minimum required to start. With a subscription, included minutes are used first. A rejection due to insufficient balance does not mean the platform is down: check My plan, top up the balance if necessary, and configure your alerts. This rejection does not start a billable conversation.
Filtering and browsing the history
In Usage history, select the unit, transaction direction, search text, and number of rows, then click Filter. Reset restores the initial selection. The Previous and Next links preserve your filters. This history uses server-side pagination: it does not feature the column menus or export options found in administrative lists.
Usage is recorded once the call or processing has ended; a temporary hold is not a charge. Euros remain displayed exclusive of VAT and included minutes separately, alongside their validity period. Payment and invoice lists retain statuses, VAT-inclusive amounts, and links to available documents. No view button triggers a payment.