Cobra · Dev
A €200,000 supplier backlog cleared in a week, line by line
Context
A supplier statement (GDD, one of Cobra's largest suppliers) showed a significant balance left unpaid, spread across dozens of invoices accumulated over several weeks. The Excel statement sent by the supplier didn't always account for the latest payments already made on the Odoo side — creating a risk of double payment or, conversely, of underestimating what was really left to pay.
What was done
- Systematic reconciliation, on each new statement received, between the supplier file, the real state in Odoo (invoices linked to their purchase orders) and the bank statement — to isolate what was actually still owed.
- Six payment batches prepared and tracked one by one to actual bank confirmation (not just "validated in Odoo": verified against the account statement).
- Two amount discrepancies between the supplier statement and the Odoo invoices spotted and flagged to the supplier for correction (−€60, +€18).
- €200,059.33 settled over the period, in 6 transfers, with a summary email at each step keeping internal accounting and the supplier informed.
What was hard
Telling apart "a transfer is validated in Odoo" from "the money has actually left the bank" — one batch was briefly ambiguous (validated in Odoo, absent from the day's bank statement), resolved by confirming the exact validation time at the bank vs the statement's extraction time (not a real problem, just an execution lag).
Stack
Odoo (invoices, payment vouchers, reconciliation), Excel (supplier statement), bank CSV export.
What this illustrates
A treasury job that isn't spectacular but carries a high reliability stake: every euro traced from the invoice to the actual bank debit, with verification round-trips that could easily have been rushed under the pressure of volume. The kind of task where assistance changes less "what's possible" than "the level of rigor you can maintain" on a large volume without spending your whole day on it.