Vol. I · No. 19

Back Office Beat

Mon–Fri, 6:30 a.m. MT · Three to five items · Free

Published by J9 Systems
Subscribe

The daily brief · No. 9

Tuesday, October 20, 2026

IRS: Q3 Form 941 is due Nov. 2, or Nov. 10 if every deposit was on time

By Carter Josephson · Filed 5:11 AM MDT MT

The IRS Form 941 for Q3 is due Nov. 2, or Nov. 10 if every deposit was on time. First thing today, check your Q3 deposits against your IRS account, which takes about 30 minutes and decides your date.

In this brief

  1. 1IRS: Q3 Form 941 is due Nov. 2, or Nov. 10 if every deposit was on timeTry it
  2. 2Google Chat starts posting Gemini meeting recaps by default; wider rollout Oct. 27Try it
  3. 3OpenAI file uploads and image tools errored for 43 minutes on Oct. 19Ignore
  4. 4OpenCode Console breach leaks AI API keys of 1.4% of users; most small shops unaffectedIgnore
  1. IRS: Q3 Form 941 is due Nov. 2, or Nov. 10 if every deposit was on time

    Oct. 31 falls on a Saturday, so the filing date moves to Monday. A check of your deposits now decides which date you get.

    By Carter Josephson · · Share this item

    What happened

    The IRS tax calendar lists the third-quarter Form 941 as due Nov. 2, 2026, because Oct. 31 is a Saturday. Employers who made all their payroll tax deposits on time and paid in full have until Nov. 10.

    What it means for a 10-to-50-person business

    The Nov. 10 grace date only applies if every deposit for the quarter went in on time and in full. Take a 20-person electrical contractor with $9,000 in federal payroll tax a month. It deposits monthly by the 15th. If it missed the Sept. 15 deposit by a week, it loses the extra eight days and the return is due Nov. 2. Late deposits carry penalties of 2% to 15% of the amount, depending on how late. Late filing adds its own penalty on top. If your payroll provider files for you, the effect on you is small: confirm the filing is queued and that each deposit shows as paid on your IRS business account. The same calendar lists Form 2290 (heavy vehicle use tax) on Nov. 2 for trucks of 55,000 pounds or more first used in September. Most service fleets are lighter and can ignore that line.

    What to do
    Try it

    This week, check that all three Q3 deposits show as paid, and ask your payroll provider whether the 941 files on Nov. 2 or Nov. 10.

    What it costs
    What it costs
    Checking Q3 deposits against your IRS account
    30 min
    Asking your payroll provider to confirm filing date
    10 min
    Doing nothing
    $0 if a provider files on time; a missed Nov. 2 date means a late-filing penalty of 5% of tax due per month, plus interest
    Sources
    irs.gov (primary) · IRS Publication 509 (2026), Tax Calendars
  2. Google Chat starts posting Gemini meeting recaps by default; wider rollout Oct. 27

    If your firm uses Gemini note-taking in Meet, summaries and action items will start landing in team chats unless you change one setting.

    By Carter Josephson · · Share this item

    What happened

    Google is adding meeting recaps to Google Chat: a card with a summary, key decisions, action items with owners, and links to the Gemini notes, recording and transcript, posted automatically in the meeting's chat after any Meet call with 'Take notes for me' on. It is on by default for Business Standard, Business Plus, Enterprise Standard, Enterprise Plus and Frontline Plus organizations with Gemini enabled, rolling out to Rapid Release domains from Oct. 16, 2026 and to Scheduled Release domains from Oct. 27, 2026, with up to 15 days for each to reach everyone.

    What it means for a 10-to-50-person business

    This only matters if you run internal meetings in Google Meet and already use Gemini's 'Take notes for me'. Most trades shops that meet in the yard or on the phone can ignore it. Take a 14-person accounting firm on Business Standard with a weekly 30-minute staff meeting. Assume an office manager spends 15 minutes after each meeting writing up who owes what. That is about 1 hour a month, or roughly $600 a year at $50 an hour. The recap card now does that write-up and puts it where the team already talks, and staff who missed the call can read it instead of the transcript. Two catches. First, it is on by default, so recaps of sensitive calls (partner pay, client disputes) will show up in the group chat unless the host sets 'Send notes to' to hosts and co-hosts only. Second, Gemini decides the action items and owners, so someone should check them for the first few weeks. Small law practices should review the sharing default before relying on it.

    What to do
    Try it

    Let the recap run on your next two internal Meet calls, compare its action items with what was actually agreed, and tell meeting hosts to switch 'Send notes to' to hosts and co-hosts only for confidential meetings.

    What it costs
    What it costs
    Feature price
    none stated by Google; requires Business Standard or higher with Gemini enabled
    Admin check of Gemini and note-sharing settings
    0.5 hr (≈ $25 at $50/hr)
    Manual recap writing replaced, assume 4 meetings/mo × 15 min
    ≈ 12 hrs/yr (≈ $600 at $50/hr)
    Reviewing AI action items for first month
    ≈ 1 hr (≈ $50 at $50/hr)
    Doing nothing
    $0; recaps appear automatically by about Nov. 11 on Scheduled Release if Gemini note-taking is on
    Sources
    workspaceupdates.googleblog.com (primary) · Google Help: Get meeting recaps with Gemini in Google Chat · Google Help: Use 'Take notes for me' in Google Meet · Workspace Admin Help: Manage Google Workspace smart features for your users
  3. OpenAI file uploads and image tools errored for 43 minutes on Oct. 19

    A short OpenAI outage hit ChatGPT file uploads and three APIs on Monday morning; the cost to a small shop is small, and only automations need a check.

    By Carter Josephson · · Share this item

    What happened

    OpenAI's status page reported elevated errors on Monday, Oct. 19, 2026, in ChatGPT file uploads and image generation and in the Responses, Images and Files APIs, all listed as degraded performance. The incident was posted at 9:31 a.m. and marked resolved at 10:14 a.m., with OpenAI stating that all impacted services had fully recovered.

    What it means for a 10-to-50-person business

    The effect on a 10-to-50-person business is small. This was degraded performance, not a full outage, and it lasted about 43 minutes. The feed timestamp puts the start at 13:31 UTC, which is 7:31 a.m. in Denver. Example: a 14-person accounting firm has 6 staff using ChatGPT to summarise client PDFs. If each lost 15 minutes to failed uploads and retries, that is 1.5 hours, or about $75 at $50 an hour. That is one time, and it is already over. The one group that should look is any shop with an automation that sends files or images to OpenAI's API, for example a Zapier, Make or n8n workflow that reads job photos or invoices. Those runs may have failed silently during the window and will not retry on their own. Everyone who only uses ChatGPT by hand can ignore this. One 43-minute incident is not a reason to switch tools or pay for a backup AI subscription.

    What to do
    Ignore

    Change nothing, but if a Zapier, Make or n8n workflow sends files to OpenAI's API, check its run history for failures between 13:31 and 14:14 UTC on Oct. 19 and replay them.

    What it costs
    What it costs
    Lost staff time, 6 users × 15 min at $50/hr
    ≈ $75 one-time, already incurred
    Replaying failed automation runs, if any
    0.5 hr (≈ $25 at $50/hr)
    Backup AI tool subscription
    $0; not justified by one 43-minute incident
    Doing nothing
    $0; OpenAI reports full recovery as of 10:14 a.m. the same day
    Sources
    status.openai.com (primary) · OpenAI Status page (subscribe to incident alerts)
  4. OpenCode Console breach leaks AI API keys of 1.4% of users; most small shops unaffected

    Unless a developer on your payroll uses OpenCode Console, this one passes you by, but it shows why every AI account you pay for needs a spend cap.

    By Carter Josephson · · Share this item

    What happened

    OpenCode, an open-source AI coding agent, said on Saturday, Oct. 17, that attackers broke into an older system behind its OpenCode Console web platform, affecting 1.4% of Console users, some of whom stored API keys for AI services there, and that it notified all affected users by email. The company says its open-source app and command-line tool were not affected, refunds for unauthorized charges are underway, and affected users should revoke and replace their keys directly with each AI provider.

    What it means for a 10-to-50-person business

    Primary source is OpenCode's own post on X; charge amounts and provider responses come from TechCrunch's reporting. The direct effect on a 10-to-50-person trades or services business is close to zero. OpenCode is a tool for software developers, and only Console users who got an email were hit. The wider lesson is the one worth 15 minutes. An API key is a password that bills you. Take a 25-person accounting firm that pastes an OpenAI key into a Zapier or Make workflow to pull line items off vendor invoices, spending about $40 a month. If that key leaks from any tool that stores it, a stranger can run up charges until someone notices. Affected developers reported hundreds of dollars per account, and a few reported more than $1,000 overnight. A monthly spend cap or budget alert of, say, $75 on each AI account turns an open-ended loss into a small, capped one. Check whether your provider's setting is a hard stop or only an email alert. Firms with no AI API accounts can ignore this entirely.

    What to do
    Ignore

    Unless someone on your team or a contractor uses OpenCode Console, take no action on the breach itself; if you hold OpenAI, Anthropic or Google API keys in any automation tool, spend 15 minutes this month setting a monthly spend cap or budget alert on each account.

    What it costs
    What it costs
    OpenCode exposure for a shop not using Console
    $0
    Setting spend caps or alerts on 3 AI accounts
    15 min (≈ $13 at $50/hr)
    Rotating one leaked key and updating it in Zapier or Make, if ever needed
    30 min per tool (≈ $25 at $50/hr)
    Doing nothing
    $0 unless a key leaks; affected developers reported hundreds of dollars, a few over $1,000 per account
    Sources
    x.com (primary) · TechCrunch: Hackers hit AI coding tool OpenCode, running up charges on users' AI accounts · OpenCode co-founder Dax Raad on refunds for unauthorized charges · Notebookcheck: OpenCode hacked, users urged to revoke their API keys

Also happened

Corrections and updates

None. How corrections work.

Get the next one at 6:30 a.m.