Integration model map¶
Use this map before opening the generated field reference. It identifies the models that form Accountify's supported integration boundaries, why they matter, and how the custom application should use them.
Ownership boundary¶
| Layer | Owns | Must not own |
|---|---|---|
| Accountify UI | Work queues, suggestions, review, client requests, approvals, exception explanations | Ledger rules, stock valuation, tax computation |
| Accountify backend | Tenant routing, secrets, permissions, idempotency, locks, policy checks, readback, operational audit | Browser-held Odoo credentials, duplicated Odoo accounting logic |
| Odoo | Legal ledger, taxes, posting, reconciliation, structured invoice artifacts/transport, purchase/receipt links, stock history | Accountify task assignment, extraction confidence, client collaboration |
Core models¶
| Workflow | Model | Purpose | Accountify use |
|---|---|---|---|
| Contacts | res.partner |
Customer, vendor, contact, and commercial identity | Read / controlled create-write |
| Companies | res.company |
Legal entity and company-specific configuration | Read |
| Accounting | account.move |
Journal entry, customer invoice, vendor bill, credit note | Read / draft create-write / guarded method |
| Accounting | account.move.line |
Ledger, invoice, payable, receivable, tax, and reconciliation lines | Read / nested draft write / guarded reconcile method |
| Banking | account.bank.statement.line |
Imported bank or card transaction awaiting/holding reconciliation | Read; mutation through wrapper |
| Reconciliation | account.partial.reconcile |
Native partial matching result | Read verification |
| Reconciliation | account.full.reconcile |
Native full reconciliation grouping | Read verification |
| Accounting setup | account.journal |
Purchase, sales, bank, cash, and general journals | Read configuration |
| Accounting setup | account.account |
Chart of accounts and reconcilable-account behavior | Read configuration |
| Tax | account.tax |
Purchase/sales tax computation and reporting behavior | Read; reference on draft lines |
| Attachments | ir.attachment |
Source invoice and other record-linked files | Read / controlled create |
| Documents | documents.document |
Optional Odoo Documents workflow layer | Read / optional integration |
| E-invoicing | account_edi_proxy_client.user |
Company-bound electronic-invoicing proxy registration and operating mode | Operations-only readiness read; never copy keys/secrets |
| E-invoicing | account.edi.xml.cii |
CII serialization used by Factur-X/XRechnung support | Capability evidence; do not invoke as a generic browser API |
| E-invoicing | account.edi.xml.ubl_de |
German UBL/XRechnung specialization | Capability evidence; do not invoke as a generic browser API |
| E-invoicing | account_peppol.service |
Odoo Peppol service behavior | Capability/operations evidence; Odoo owns transport |
| Automation | base.automation |
Studio automated action and webhook trigger | Bootstrap / drift check |
| Automation | ir.actions.server |
Versioned server-action code behind the reconciliation wrapper | Bootstrap / drift check |
| CRM | crm.lead |
Lead or opportunity pipeline record | Read / controlled create-write |
| Purchasing | purchase.order |
RFQ and confirmed vendor order | Read / guarded create / native methods |
| Purchasing | purchase.order.line |
Ordered product/service, price, taxes, receipts, invoicing | Read / nested create-write |
| Inventory | stock.picking |
Receipt, delivery, or internal transfer | Read / guarded native methods |
| Inventory | stock.move |
Planned/completed product movement | Read |
| Inventory | stock.move.line |
Detailed moved quantities, lots, packages, and locations | Read / guarded operational input |
| Inventory | stock.quant |
Quantity at location/lot/package/owner | Read; avoid direct quantity writes |
| Inventory | stock.location |
Physical or virtual stock location | Read configuration |
| Inventory | stock.lot |
Lot or serial traceability | Read / controlled create |
| Inventory | stock.warehouse |
Warehouse routes and operation configuration | Read configuration |
Current runtime capability¶
The June 29, 2026 snapshot contains 764 models and 15,789 fields.
| Capability | Runtime evidence | Status |
|---|---|---|
| Accounting and bank reconciliation | Core accounting, statement, residual, reconcile-result, automation models | Available |
| Supplier bill coding | Bills, bill lines, vendors, journals, accounts, taxes, attachments | Available and smoke-tested for draft flow |
| CRM | crm.lead and supporting CRM models |
Installed |
| Purchase | purchase.order and purchase.order.line |
Installed and smoke-tested |
| Inventory receipts | Requested stock.* models and warehouse configuration |
Installed and smoke-tested for the current company |
| German e-invoicing | account_peppol, UBL/CII, German localization, partner format/endpoint, company registration, and invoice status fields |
Runtime surface available; per-company send/receive fixtures pending |
| Website | No website model in the snapshot |
Not installed/visible |
| Manufacturing | No mrp.production model in the snapshot |
Not installed/visible |
| Subscriptions | No subscription-named model in the snapshot | Not installed/visible |
Installed is not operationally ready
A model appearing in the snapshot proves metadata visibility, not tenant configuration or end-to-end readiness. Use the tenant capability checks before enabling a workflow.