Knowledge Center logo

Rackson process walkthroughs

Screenshot walkthroughs for the recurring Rackson system processes — prelim reports, COS audit, labor reports, period-end tie-out, and the weekly ACH upload.

Step-by-step system walkthroughs specific to the Rackson engagement, each converted from a recorded process document with its screenshots.

Source: the five process documents in the Rackson SharePoint process folder, each of which has an accompanying screen recording. See Source documents for the recordings and their runtimes.

The walkthroughs

Running and delivering prelim reports

Run the Corp and Store prelim packages for both entities, save internally, and deliver to the client SharePoint site.

COS % audit report

Generate the report, isolate the pink-flagged outlier stores with Excel's colour filter, and file it.

Store and corp labor reports

Pull payroll GL detail from ProWork, split by brand and Corp/Store level, and save to the Prelims folder.

Period end financial report tie out

Run the core financial reports and tie cash, net income, and the clearing account across them.

Weekly ACH bank file upload

Generate the ACH file in Intacct, validate and submit through TD Bank, and confirm back in Intacct.

How these relate to the close

WalkthroughCadenceClose checklist
Running and delivering prelim reportsEach periodWD3 — Send Preliminary Financials
Store and corp labor reportsEach pay periodFeeds the prelim package
COS % audit reportEach periodAfter inventory is posted
Period end financial report tie outEach period endBefore the period is closed
Weekly ACH bank file uploadWeeklyOutside the close cycle

The COS % audit report and the prelim reports are also documented as workpapers — see RRS prelims and RCY prelims — where the emphasis is on what to review and which thresholds matter. The pages here cover how to produce them.

Conventions used in these walkthroughs

  • Always overwrite a defaulted date. Several Intacct reports default the As of date to today rather than period end. Every one of these processes calls this out because it silently pulls the wrong period.
  • Save forward under the current period's file name, matching the naming used for the prior period's file in the same folder.
  • Nothing internal goes to the client site. Do not upload internal working files, credential sheets, or anything other than the finished reports to the client-facing SharePoint site.