Configure analytic plans, online payments, recurring templates and the accounting settings

Three plans are in use: Project — one analytic account per job, largely auto-created from opportunities and sales orders — Department (cost centres such as Logistics & Delivery or Glass Processing & IGU Line), and Product Line (Curtain Wall & Structural Glazing, Automatic & Sensor Doors, and their siblings). Each plan sets a Default Applicability (Optional, Mandatory, Unavailable) that decides whether documents demand a distribution on that plan, refinable per context in the plan's Applicability tab (by document type, account-code prefix, or product category — note a rule's criteria are all-or-nothing filters). Sub-plans inherit their root's applicability and store their data under the root.

An Analytic Account is one value on a plan — one project, one department — with a customer, a running debit/credit/balance from its analytic items, and stat buttons to the invoices and bills behind them. The Project plan's accounts come mostly from the sales flow; the Department and Product Line accounts are maintained by hand here.

Payment Providers lists every gateway Odoo can integrate — Stripe, PayPal, Paymob, Amazon Payment Services, and twenty more. On this installation all of them are uninstalled, disabled shells: enabling online payment means clicking Install on a gateway, entering its credentials, and setting its state to Enabled (or Test Mode while trialling), which activates its payment methods and publishes it to the portal. Regional card schemes such as Mada are payment-method brands within a card-capable gateway, and Apple Pay is the provider's Allow Express Checkout option — neither is a provider of its own. Until a gateway is enabled, the neighbouring screens stay empty by design: Payment Methods all inactive, Payment Tokens none (tokens are opaque references created only when a customer saves a payment method during a real checkout — card data never lives here), Payment Transactions none. Transactions, once they exist, carry the gateway lifecycle (Draft, Pending, Authorized, Confirmed, Canceled, Error) with Capture/Void on authorized ones and Refund on confirmed ones.

Despite sitting under Online Payments, Recurring Templates is a bookkeeping tool: a template posts a fixed two-line journal entry (debit account, credit account, amount) on a schedule — the shipped examples are the factory rent, the Kahramaa utilities accrual, and quarterly fleet insurance. Set the accounts, journal, amount, start date and interval, choose whether entries generate Unposted or Posted, and move the template to Running; a daily scheduled job back-fills any missed occurrences. Know its edges: the Analytic Account field on the form is not applied to the generated entries in this release (add analytics on the entries themselves), nothing warns if debit and credit are the same account or the amount is zero, and Pay Directly versus Pay Later changes nothing in what gets generated.

Blocks for Enterprise-only services — dynamic reports, OCR digitisation, batch payments, PEPPOL, budgets — either do not appear or lead to modules this edition does not include.

Accounting › Dashboard shows one card per favourite journal: sales and purchase cards count documents To Validate, Unpaid, Late, and To Review with a small activity graph; bank and cash cards show the account balance and outstanding payments; general cards offer draft counts and Post All Entries. The ⋮ menu on each card holds the colour picker and — for administrators — the star that decides whether the journal appears on the dashboard at all, plus a shortcut to the journal's configuration.

"You cannot publish a disabled provider." — enable the provider (or put it in Test Mode) before publishing it to the portal.

"You cannot delete the payment provider …; disable it or uninstall it instead." — shipped providers are never deleted, only disabled.

"Making a request to the provider is not possible because the provider is disabled." — a capture, void, or refund was attempted against a disabled gateway; re-enable it first.

"You can't unarchive tokens linked to inactive payment methods or disabled providers." — restore the provider and method first; the token follows.

"You can't change the company of an analytic account that already has analytic items!" — create a fresh account in the other company instead of moving one with history.

"Partner does not exist" on a bank-statement import — the file's payee names must match partner names exactly; correct the file or the contact and re-import.

A distribution model seems ignored — a higher row targeting the same plan matched first, or one of the row's criteria (company, prefix) does not match the document; check sequence order and criteria.