Billing Write-Off Pack + ACATS Transfer Compliance — Jira + Confluence + SQL + SlackCompliance & Regulatory

Task prompt

Finance Ops is pulling together a quarter-end write-off + ACATS compliance pack and wants the findings posted where the team actually works. Please trace the engineering Jira that implements the past-due subscription invoice billing trigger and confirm the issue key and current status. From the Confluence dunning policy, pull the documented grace period in days and the invoice state the system treats as written off. Then use the subscription invoice data to quantify the written-off population: how many invoices are currently in that state, how many breached grace because they were cancelled more days after the billing date than the documented grace allows, and what share of all write-offs that is (two decimal places). Separately, include the ACATS compliance checkpoint: under FINRA Rule 11870(d), after an ACATS transfer completes, for how many calendar days must the delivering firm forward any assets it later receives for that account to the receiving firm? Use the short post-completion residual forwarding window in 11870(d) — not the ACATS validation/completion timeline, and not a multi-month residual period. Also include one card-auth control metric for the same pack: among approved Mastercard events, what percentage had PIN present (two decimal places)? Deliver this in Slack: create a channel called "billing-writeoff-acats-compliance-pack", post a concise summary there with those findings, then pin it. A readable checklist format is fine, for example: Billing trigger issue key: <key> Billing trigger status: <status> Documented dunning grace days: <days> Writeoff state: <state> Total writeoff count: <count> Grace breach count: <count> Grace breach share pct: <pct> Post-transfer forwarding days: <days> Approved Mastercard PIN present pct: <pct> After posting, reply here briefly with the channel name and that the pack is posted.