For administrators and key users: where to create the dropdown values that invoices, payments, and bank forms use – before everyday users start entering transactions.
Overview
Accounting Pro links many fields to shared lists (strategies, statuses, rails, buckets, etc.). If a list is empty, users may see blank dropdowns or pick only demo names they do not want in production. Plan one owner per area (credit, treasury, warehouse) and agree codes and sequences up front.
How it works
Most Accounting Pro lists live under the Accounting app’s configuration menu. In English, open Accounting → Configuration → Account Pro. Exact wording can differ if your database uses another language. You need rights to see Configuration under Accounting (typically “Billing Administrator” or “Adviser” level, plus your company’s policy).
Step-by-step guide
- Install Accounting Pro and enable the related feature groups in General Settings → Accounting Pro (see Turning features on).
- Go to Accounting → Configuration → Account Pro.
- Open each submenu below and create the records your policy needs. Start with a small set (for example three collection strategies) and expand later.
- On each form, fill at least Name and Code. Use short, stable codes – they are easier to search in exports and integrations.
- Set Sequence so the most common option appears first in dropdowns (lower numbers sort first).
- Uncheck Active instead of deleting when you retire a value you still need for old invoices.
- For lists without a menu in your build (quality checks, regulatory flags, storage requirements, recalls), see the table below and coordinate with your Odoo partner.
Fields table
Where to maintain each list, what it feeds in the app, and naming tips.
| List / model | Where in Odoo (typical path) | Used on | Naming tips |
|---|---|---|---|
Collection strategies |
Accounting → Configuration → Account Pro → Collection Strategies |
Invoice: Collection strategy |
Codes like |
Credit-control statuses |
Accounting → Configuration → Account Pro → Credit-control Statuses |
Invoice: Credit-control status |
Align names with your credit committee minutes (within limit, over limit, exception). |
Fraud check flags |
Accounting → Configuration → Account Pro → Fraud Check Flags |
Invoice: Fraud check |
Keep a small set: not checked, needs review, cleared – avoid ten synonyms. |
Fulfillment priorities |
Accounting → Configuration → Account Pro → Fulfillment Priorities |
Invoice: Fulfillment priority |
Match warehouse language (Normal, Rush, VIP) and use sequence for sort order. |
Bank purpose codes |
Accounting → Configuration → Account Pro → Bank Purpose Codes |
Payment & partner bank: regulatory purpose / allowed codes |
Use bank-scheme rules (SWIFT/SEPA); keep Code short; fill Scheme and country when relevant. |
Payment rails |
Accounting → Configuration → Account Pro → Payment Rails |
Partner bank: Preferred payment rails |
Examples: SEPA, SEPA Instant, SWIFT; code uppercase for file generators. |
Bank fee profiles |
Accounting → Configuration → Account Pro → Bank Fee Profiles |
Partner bank: Fee model preference |
Name by behaviour (“Standard SHA”, “Premium OUR”); code unique per company policy. |
Payment strategies |
Accounting → Configuration → Account Pro → Payment Strategies |
Payment: Payment strategy |
Examples: Standard, Urgent same-day, Low cost; tie description to when to pick each. |
Payment approval levels |
Accounting → Configuration → Account Pro → Payment Approval Levels |
Payment: Approval level required |
Optional Minimum amount helps match policy tiers; name roles (“Manager”, “CFO”). |
Treasury buckets |
Accounting → Configuration → Account Pro → Treasury Buckets |
Payment: Treasury bucket |
Examples: Operating, Payroll, Tax, Capex; keep the list short enough to chart. |
Liquidity priorities |
Accounting → Configuration → Account Pro → Liquidity Priorities |
Payment: Liquidity priority |
Describe which bank pool to spend first; code for automation if needed. |
Payment policy results |
Accounting → Configuration → Account Pro → Payment Policy Results |
Payment: Policy result |
Final outcomes only: cleared, rejected, escalated – not free-text reasons. |
Storage requirements |
No standard menu in Accounting Pro – Inventory app or partner customization |
Invoice line: Storage requirement |
Create codes like COLD, FROZEN, AMBIENT; ask your partner to expose a menu if missing. |
Recall campaigns |
No standard menu in Accounting Pro – partner customization or related Inventory/Quality app |
Invoice line: Recall batch |
Use external recall reference in Reference; keep names readable for CS and finance. |
Quality checks |
No standard menu – partner may add a menu or use Technical for admins |
Invoice line: Quality checks (many) |
One row per SOP step (visual inspection, metal detector, etc.). |
Regulatory flags |
No standard menu – partner may add a menu or use Technical for admins |
Invoice line: Regulatory flags |
Short codes (GMP, GDP, HAZMAT); avoid duplicates that mean the same thing. |
Field explanations
Each paragraph matches one row in the table above, in the same order.
Collection strategies
Defines how hard you chase payment for invoices that point to this strategy. Users only pick from what you create here.
Credit-control statuses
Standard labels for “where this customer stands” versus limits. Keeps dashboards and pivots consistent with committee language.
Fraud check flags
Discrete outcomes or states for fraud review on an invoice, not the full investigation narrative.
Fulfillment priorities
Tells operations how urgent shipment is relative to other orders; separate from financial risk.
Bank purpose codes
Legal or bank-mandated purpose-of-payment values; wrong codes can reject wires, so maintain with treasury or banking help.
Payment rails
Technical or commercial rails (SEPA, SWIFT, instant). Shown on partner banks to steer routing preferences.
Bank fee profiles
Describes how fees are usually split for that relationship; pairs with per-payment fee model fields.
Payment strategies
Business strategies for how to process a payment (cost vs speed). Users assign one per payment when enabled.
Payment approval levels
Named approval steps, optionally with minimum amounts, so policy can say “over €X needs CFO level.”
Treasury buckets
Buckets for grouping cash movements in reporting and forecasts.
Liquidity priorities
Rules or rankings for which internal bank balance to use first when several are available.
Payment policy results
Closed-loop results from your payment policy checklist, stored as structured choices on the payment.
Storage requirements
Profiles like cold chain or ambient; used on invoice lines when storage features are on. Without a menu, maintenance is done by admins via Technical or a custom screen your partner adds.
Recall campaigns
Header for a recall event; invoice lines link here so finance and quality share one campaign ID.
Quality checks
Individual checks that can be ticked on a line; should mirror real QA steps for auditability.
Regulatory flags
Tags such as GMP or hazmat; keep the list short and mutually understood by sales, warehouse, and compliance.
Common columns on list forms
Most Account Pro list models offer: Name (shown to users), Code (stable internal key), Sequence (sort order), Active (hide without deleting), and Description (internal help text). Fill Description for anything non-obvious so new staff pick the right value.
Tip: Export your agreed code list to a one-page PDF for sales and warehouse before go-live – fewer wrong dropdown picks than training in the live system alone.
Common mistake: Creating duplicate names (“Urgent” vs “URGENT” vs “Same day urgent”) – reports will split counts across them. Merge and deactivate extras early.