SMB Pulse

Close the month in one screen

Close the month from one checklist: see every line the month-end checks flagged, decide each one, and hand the month to the owner for sign-off.

Pick a use case and follow its guide

Close the month in one screen

0 of 8 steps done

Sign in to try the demo
  1. Step 1. Open Operations, then close.list_months, and press Call close.list_months. Under ANSWERED, months lists each month with its status (open, ready_for_sign_off or closed) and run_count. Find the month you are closing: it should be open, checked and waiting to be closed. Open close.list_months

  2. Step 2. Open Operations, then close.run_checks. In month, type the month you are closing, as YYYY-MM. In processors_checked, type stripe and press Enter, then paypal and press Enter. Press Call close.run_checks. The checks match the month's payouts against its deposits and file what they find (payouts that do not match a deposit, uncategorised lines, duplicates, recurring charges, missing receipts, refunds without a credit memo, large month-over-month moves on an account and customer deposits not yet earned) as the month's flags. Nothing is written to the books. A closed month is refused until it is reopened. Open close.run_checks

  3. Step 3. Open Operations, then close.get_checklist. In month, type the same month and press Call close.get_checklist. Under ANSWERED, status is open and flags holds one row per problem. open_kinds lists every kind still holding the month open, with how many of each, however long the checklist is. Each row has a kind in result (for example uncategorised, duplicate, recurring, missing_receipt or refund_without_credit_memo), the payee, a line_count, an amount and a note in plain words: an uncategorised payee says whether it has any history to suggest a category from, a duplicate pairs two charges of the same payee and amount a few days apart, and a regular charge is shown as recurring, not as a duplicate. A bill that was simply split is not flagged. Each row's group_id is what the next step decides on. Running the checks again replaces the flags an earlier run left undecided, so each problem is listed once. A long checklist shows its first 200 rows: to see one kind's rows, type that kind in kind, and turn on open_only to leave out the flags already decided and the lines that agree. Open close.get_checklist

  4. Step 4. Decide the few flags that need judgment, one at a time: a duplicate charge, or an uncategorised payee whose note suggests a category. Open Operations, then close.resolve_flag. In month, type the month; in group_id, type that row's group_id from the checklist; then press Call close.resolve_flag. The decision is recorded with who and when, and a change in QuickBooks action item is filed for you: the app itself changes nothing in the books. To leave one flag for later, use close.defer_flag with the same two fields instead: the deferral is recorded, and next month's checklist shows the flag again as already deferred, so it does not hold that month's sign-off. Open close.resolve_flag

  5. Step 5. Defer the rest in one action per kind. A month files many routine flags, such as small refunds still waiting for their credit memo (refund_without_credit_memo) or receipts still being chased (missing_receipt), and every kind still open must be decided before the month can go for sign-off: a payout without its deposit (date_mismatch, missing_in_quickbooks, unmatched_deposit), an uncategorised payee you are leaving for later (uncategorised), a duplicate or recurring charge, an account that moved a lot on last month (variance) and a customer deposit not yet earned (unearned_deposit) included. Open Operations, then close.defer_flags_of_kind. In month, type the month; in kind, type a kind from the checklist's open_kinds; then press Call close.defer_flags_of_kind. Every flag of that kind that is still open is deferred at once, with who and when, under one change in QuickBooks action item; flags you already decided keep their decision. Under ANSWERED, members says how many it deferred and still_open how many flags are left. Repeat with the next kind in open_kinds until still_open is 0. Open close.defer_flags_of_kind

  6. Step 6. Open Operations, then close.request_sign_off. In month, type the month and press Call close.request_sign_off. The month moves to ready_for_sign_off, with who asked and when. While any flag is neither resolved nor deferred, the app refuses and says how many are left. Open close.request_sign_off

  7. Step 7. The owner opens Operations, then close.write_story, types the month in month and presses Run close.write_story. The cash advisor writes a short month story from the month's variance lines and the deposits not yet earned, and every figure in it is filled by code. The month must be ready for sign-off first; an open month is refused. Open close.write_story

  8. Step 8. The owner opens Operations, then close.sign_off, types the month in month and presses Call close.sign_off. The month moves from ready for sign-off to closed, with who signed and when. Only the owner may sign; any other seat is refused by name. Open close.sign_off

Did it fit your work?