Wie togrant.com mit Odoo kommuniziert.
100% Standard-Odoo-API. Dieselbe XML-RPC-Schnittstelle, die seit Version 8 mit jeder Odoo-Installation ausgeliefert wird, genau so verwendet wie die Odoo-Dokumentation es vorschreibt. Ihr Odoo bleibt so, wie Odoo Inc. es entworfen hat; togrant.com ist lediglich ein wohlverhaltener API-Client, der daneben sitzt.
▶ Die vollständige Synchronisation in Aktion sehen — the 3-minute walkthrough shows every read and write between togrant.com and Odoo.
Was in Odoo synchronisiert wird
togrant.com writes into three standard Odoo models — the ones already designed for project work and analytic accounting. Everything else in your Odoo keeps doing what it was doing.
- project.project — one Odoo project per togrant.com project. Carries name, code, partner (donor), date range.
- account.analytic.plan & account.analytic.account — three analytic plans, dynamically populated with the donor's budget categories and detail lines.
- budget.budget & budget.line (Odoo 17+) — budget plans posted per project so finance staff see the planned numbers next to actuals.
We never write to res.partner, account.move,
account.move.line, or anything in the chart of accounts.
That's finance's territory.
Die drei Analysepläne
Odoo 17 introduced multi-plan analytic accounting, and that's the mechanism togrant.com leans on. Each plan slices analytic lines by a different axis; combined, they give you per-project + per-donor + per-line-item drill-down.
| Plan | Axis | Example accounts |
|---|---|---|
| Plan 1 — Project | Which togrant.com project | PRJ-001 Civic Voices UgandaPRJ-002 Civic Voices Burundi |
| Plan 2 — Donor budget line | Which donor category | HRTRVEQPIND |
| Plan 3 — Donor budget detail | Which specific budget line | 1.1.1.a Project Director2.1 International flights |
A single bill in Odoo can be tagged with one analytic account from each plan. Sum across one axis to get per-project actuals; sum across another to get per-donor-line actuals. Same data, different views.
Wie wir schreiben
Every write goes through an idempotency key shaped like
tenant_id:entity_type:entity_id:operation. Before any
mutation, we check whether the operation has already succeeded. If
it has, we skip and reuse the existing Odoo ID. This means:
- Network blip mid-sync? Retrying never creates duplicates.
- Two togrant.com users press "Sync" at the same time? One wins, the other no-ops.
- You delete a project and recreate it? We notice the new ID and start fresh — no orphan analytic accounts.
Das Synchronisationslog
Every call writes a sync_log row: timestamp, tenant,
entity, operation, idempotency key, HTTP status, response size,
latency, error message (if any).
Read the sync log chapter in the manual
for a tour of the columns + how to read a failed sync. The log is:
- Append-only. No edits, no deletes. Auditors love this.
- Redacted. API keys, bearer tokens, and any field matching
password|secretget scrubbed before write. - Truncated at 16 KB per payload. Long Odoo error messages don't blow up our storage.
- Searchable for 90 days. Older rows get archived; available on request.
Verbindungsstatus
A 5-minute cron pings each tenant's Odoo with a no-op call and records the result. The admin dashboard shows a green / amber / red pill per tenant. Integration health is its own manual chapter with what each state means and the steps to recover. Red for more than 15 minutes triggers an alert to the support team — usually before the customer notices.
Kompatibilität
- Odoo versions: 17, 18, 19 (Community + Enterprise).
- Required modules: Analytic Accounting (built-in), Projects (built-in), Budget Management (built-in in 17+).
- Optional: Multi-company, multi-currency. If you have these on, togrant.com uses them.
- Auth: service-account user with read/write on Projects, Analytic Accounting, Budgets. No admin rights needed.
Wo Odoo das Steuer behält
Some parts of your Odoo are the parts your finance team built their workflow around. togrant.com respects those boundaries so the people doing the books keep doing what they were doing:
- Chart of accounts and journal entries — owned by Odoo. We never post entries; finance keeps the same general-ledger workflow they already trust.
- Donor and supplier records — donors live as togrant.com records (with their own grant history); your Odoo
res.partnerstays curated by finance for actual transactions. - Fiscal-year settings — read by togrant.com so periods line up with your reporting, but written by you in Odoo settings.
- Bank reconciliation and payments — Odoo's bread and butter, untouched.
- HR and timesheets — Odoo (or your existing tool) keeps owning these; togrant.com focuses on grant lifecycle.
Clean boundaries mean an Odoo upgrade rarely needs anything from us, and a togrant.com release rarely needs anything from your finance team.