Skip to content

CTC Billing, QBO And Document Process Baseline

  • Evidence date: 2026-07-17
  • Evidence class: source-reconciled current-state baseline
  • Scope: Client 1 (ctc-execution); no provider, DB, browser mutation or deployment evidence

Canonical Owners

CTC_BILLING_DOCUMENT_CLOSE_WORKFLOW.md owns daily reconciliation. The transaction, AR Billing, QBO, document, BOL email and packing-list email workflows own their respective atomic results. User procedure is available in Local and Production Wiki through ar-billing-qbo, billing and ctc-daily.

Reconciled Current Boundaries

  • Generic transaction close is local state only: it does not prove QBO, file, print or email completion.
  • AR Billing confirm creates local invoice state and then attempts QBO sync; the manual review-first procedure is a safety practice, not a server guard.
  • QBO groups can independently end SYNCED, ERROR or SKIPPED. Provider invoice creation precedes the final local status save.
  • Transaction-object storage/linking, BOL email and packing-list email are independent effects. Each partial result is reread at its owning boundary.

Source-Reconciled Gaps

  • An ERROR or SYNCING QBO row does not prove provider absence. Search by customer, document number and amount before any retry.
  • Generic close and AR confirm lack a proven complete prior-state/concurrency guard; do not infer exactly-once invoice creation.
  • File object and T_FILE registration can diverge; shared paths and email multipart/provider results require manual reconciliation rather than replay.

Limits

This baseline preserves the WP03-10 source findings only. It does not approve draft lifecycle, prove QBO/Gmail delivery, repair concurrency/file gaps, or establish Production/provider/field acceptance.

---

Source: docs/research/processes/2026-07-17/CTC_BILLING_QBO_DOCUMENT_PROCESS_BASELINE.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.