Weekly Authorize.Net settlement report for finance

Every Monday at 8am, generate a written weekly settlement report from Authorize.Net and deliver it to the finance team. The tone is executive-ready, not raw numbers: full sentences, plain English, story first with the figures behind the story.

Start by calling Authorize.Net Get Settled Batch List for the last seven days with per-batch statistics enabled. Roll the batches up into a single weekly view: gross volume, net after refunds, refund count and refund rate, chargeback count, and decline rate. Compute the same figures for the seven days before that so you can call out notable week-over-week shifts (a jump or drop of about 15% or more in any headline number, or any absolute swing worth flagging to a CFO).

For any batch that looks unusual, drill in. Treat these as signals: refund count materially above the batch-over-batch average, decline rate meaningfully higher than the trailing weekly baseline, or any chargeback activity at all. For each suspect batch, call Authorize.Net Get Batch Statistics for the per-payment-type breakdown, then Authorize.Net Get Transaction List for that batch to identify the top drivers (biggest refunds, largest declines, specific customers or amounts behind the movement). Do not drill into batches that look normal.

Also build a top customers by revenue list for the week, aggregated across transactions from the batches you inspected, showing at least the top five with their totals.

Compose the written brief. Structure it as a short executive summary paragraph (what happened this week, one or two sentences), followed by short sections for Volume, Refunds and chargebacks, Notable movements (any flagged batches with the top drivers explained in prose), Top customers, and Week-over-week shifts. Avoid raw JSON, tables of ids, or verbatim API field names in the output. Reference dollar amounts with commas and two decimals.

Deliver in two places. First, use Slack Send a Message to post a short recap to the configured #finance channel: the executive summary paragraph, the headline numbers as bullet points, and a single line flagging anything unusual. Keep the Slack message tight, well under 15 lines, using Slack mrkdwn (single asterisks for bold). Then use Gmail Send a Message to send the full written brief to the configured recipient list, with a subject line like "Weekly settlement report — week ending {date}" and the full body inline (not as an attachment).

If Authorize.Net returns no settled batches for the week (a fully quiet period), still send both messages, but make the brief a one-paragraph note confirming zero settlement activity and flagging that as itself worth checking. If any Authorize.Net call fails, send the Slack recap with what you have and a note that the full email brief was skipped due to a data-fetch error.