[tompluess]

What

/api/bexio-expense-sync now processes a Moco purchase only when its status is pending. Anything else — an archived purchase above all — is skipped silently.

Why

Moco purchases move pending → archived once the operator has filed them. An archived purchase is closed business and must not be (re-)pushed to Bexio, but every later edit of one still fires a Purchase:update webhook at us.

How

New first gate in sync(), ahead of the "Review pending" tag check:

status = _purchase_status(body)
if status and status != "pending":
    logger.info("expense sync: skipped (status=%s) source_id=%s", status, body.get("id"))
    return {"skipped": "status_not_pending", "status": status}

Three decisions worth calling out:

• Silent. INFO log, no Telegram — those update webhooks repeat, so alerting would be pure noise. The endpoint returns its usual 200 ok=true so Moco stops retrying (same shape as the other routine skips).
• pending-only, not archived-only, so a status Moco grows later can't be silently treated as payable. _purchase_status lowercases and trims first.
• A body with no status still syncs. All five live-webhook fixtures carry status: "pending", but the OCR auto-release hand-off feeds get_purchase output into the same sync(); silently dropping a real bill because some shape omitted the field is the worse failure than syncing one purchase too many.

Tests

Four new cases in tests/test_bexio_expense_sync_service.py — archived skips with zero Bexio/Moco I/O and no Telegram, the casing/other-status sweep, pending still syncing end-to-end, and a status-less body still syncing. Full suite: 691 passed.

CLAUDE.md's service bullet updated in the same commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_014tmj9oSBu9dBe7yBoS4TTs

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
moco-skyr-functions	Ready	Preview	Aug 21, 2026 4:52pm
vercel-functions	Ready	Preview	Aug 21, 2026 4:52pm