WORK ARCHITECTURE — WORKFLOW MAP
DRAFT — PENDING OPERATOR REVIEW

Month-End Close Workflow

Statements come in, remaining transactions get coded, every bank and credit card account reconciles, recurring journal entries post, and the custom financial reports refresh. The staff close must complete by the 10th of the month.

Trigger
Triggered when the recurring month-end close project opens in Financial Cents after a client's month ends
End state
The workflow ends when the books are reconciled, reports carry the firm disclaimer, and the close is formally handed to the lead accountant for review
3 phases6 processes14 core activities6 open questions
1

Statement and Feed Gathering

Staff Accountant

This phase begins when the month-end recurring project opens in Financial Cents. Client emails are checked for pinned items, bank statements are largely pre-pulled by a separate intern project before the close opens, staff collects bank stragglers and credit card statements, and the feeds are swept for anything left uncoded. The staff close must complete by the 10th of the month. Ends with a Role handoff from Staff Accountant to Staff Accountant reconciliation work. Transferred: complete statements and fully coded feeds for the month. Acceptance criteria: every available account statement is filed and no uncoded feed items remain.

PROCESS 1.1

Statement Collection Process

Role

Staff Accountant

Trigger

Triggered by the close project opening

End state

Ends when every account's statement for the month is in hand

PROCESS 1.2

Feed Completion Process

Role

Staff Accountant

Trigger

Triggered by statements arriving

End state

Ends when no uncoded feed items remain for the month

2

Reconciliation and Journal Entries

Staff Accountant

This phase begins when statement and feed gathering completes; carried forward: coded feeds and filed statements; entry criteria: phase 1 checklist complete in Financial Cents. Every bank and credit card account reconciles to its statement, and the client's recurring monthly journal entries are prepared, validated, and posted. Ends when the trial balance reflects a fully reconciled, fully adjusted month.

PROCESS 2.1

Account Reconciliation Process

Role

Staff Accountant

Trigger

Triggered by fully coded feeds

End state

Ends when every account reconciles with no unexplained difference

PROCESS 2.2

Recurring Journal Entry Process

Role

Staff Accountant

Trigger

Triggered by reconciled accounts

End state

Ends when the month's recurring entries are in QuickBooks Online

3

Reporting and Review Handoff

Staff Accountant

This phase begins when reconciliation and journal entry work completes; carried forward: a reconciled and adjusted month; entry criteria: reconciliations complete in QuickBooks Online. The custom financial reports refresh, the disclaimer is verified, an error pass runs, and the close formally hands to the lead accountant. The formal handoff to the lead accountant is a Functional handoff under the function split. This phase ends the workflow when the first task in the review project is checked, signaling the lead that the month is ready for review.

PROCESS 3.1

Report Refresh Process

Role

Staff Accountant

Trigger

Triggered by the completed reconciliation and adjustment work

End state

Ends when the report package is current and clean

PROCESS 3.2

Review Handoff Process

Role

Staff Accountant

Trigger

Triggered by a clean report package

End state

Ends when the lead accountant has the contractor list, draft request side-task status, and the ready-for-review signal

WORKFLOW MAP REVIEW

Notes & Assumptions

Sources and confidence

  • Built from the Financial Cents "**Monthly Client - Month End Close" template (11 tasks, Staff Accountant role). TGF Holdings shows monthly close instances since March.
  • Process 2.2 (recurring journal entries) is draft because the activity library location remains partially open, but the month-end template and workshop confirm the work exists. The template is applied template-then-tailor per client; TGF's project may have condensed template steps, so double-check remains pending.
  • The whole map is marked DRAFT pending the follow-up review session (~2026-07-14).

Structure notes

  • Three phases, below the four-phase guideline; single-owner monthly loop with natural stages. Kept natural rather than padded.
  • The template is flat (one section); the phase and process structure is our grouping.

Assumptions to verify

  • Function split applied (2026-07-07 workshop): staff accounting, lead accounting, controller accounting, CFO, and advisory are mapped as distinct functions, so handoffs between them are typed Functional. The full split was confirmed by the operator on 2026-07-08 (staff accounting and lead accounting are their own functions); the earlier decision-record wording that kept staff/lead role-level is superseded.
  • The intern/staff statement split is answered: interns pre-pull bank statements; staff pulls cards and straggler bank statements.
  • Intern statement pre-pull context: roughly three interns spend two days each month across the client base; pulls run against mostly small local bank portals using the firm's read-only accountant logins, with MFA codes going to a shared codes inbox or firm Google Voice number for about 80 percent of clients. The rest are legacy personal-number setups. Automation vendors covered only about a quarter of the firm's banks, making this a named improvement target.
  • AI involvement in statement pulls is gated on scoped read-only bank access; per-bank login SOPs are the anticipated pattern.
  • Journal entries are placed after reconciliation; in practice some entries may need to post before accounts can reconcile.
  • Leads verify each account's reconciliation detail during review; with up to 15 bank accounts per client this gets skipped under load and is a named quality improvement target.
FOR THE MAPPING SESSION

All open questions (6)

Phase 1: Statement and Feed Gathering

Jump to phase ↑
  • Q4

    For each client: how many bank and credit card accounts, at which institutions?

    And credential storage shows two positions - the workshop's vault systems vs the blank per-client password-log spreadsheet in the template folder - which is current practice?

Phase 2: Reconciliation and Journal Entries

Jump to phase ↑
  • Q1

    Where does the recurring monthly journal entry-type library live, separate from client-specific tailored template tasks?

  • Q2

    Which clients have journal entry skills built already, and which entry types does the current skill library cover?

Phase 3: Reporting and Review Handoff

Jump to phase ↑
  • Q3

    Custom financial reports: dates are updated in QuickBooks custom reports; how much do report formats vary by client?

  • Q6

    Build the elementary staff review checklist for the pre-handoff sanity pass: the year-end checklist's Staff tab, including P&L reasonability trends, Miscellaneous, Uncategorized, unapplied, and Suspense balances, other-income accuracy, and class coding, is the starting model to adapt to monthly.

Workflow-wide

  • Q5

    Did the Financial Cents month-end template condense any steps versus the process the team described?

    Double-check while folding in templates.