Use this page as the simple office manual. Start at the top, run the teammate, open Get Output, fix red/yellow items, then rerun until the package is ready.
| Step | Who | What they do | Go here |
|---|---|---|---|
| 1 | Coffee | Sort the dropped files and build the client's process map. | Team 501 |
| 2 | FetaCheese | Run BTF bank/card reconciliation from bank file + MIP Exp GL, then review the red/yellow evidence. | FetaCheese |
| 3 | Brad | Run payroll checks and hold payroll rows that cannot safely import. | Brad |
| 4 | Agent501 | Build the full output package: BTF-ready workbook, coded review, AR/AP detail, MIP import, review queue, manifest, history, and next steps. | Get Output |
| 5 | Coffee | Work exceptions or route them back to FetaCheese for bank/card fixes and Brad for payroll fixes. | Inbox |
| 6 | Agent501 | Rebuild from corrected inputs: Coffee decisions plus FetaCheese / Brad fixes. | Get Output |
| 7 | Sandy | Review the clean package. If FAILs remain, send it back before sign-off. | Sign-off |
| 8 | Agent501 | Email the signed/latest output package ZIP to the required reviewer or client contact. | Get Output |
| Input | Plain meaning | Used by | Important note |
|---|---|---|---|
| Bank file (Harbor Trust) | What actually cleared the bank. | FetaCheese BTF reconciliation | Can be the local NCS master workbook for testing. |
| Exp GL detail from MIP | What Agent501 already recorded in MIP. | FetaCheese BTF reconciliation | This is a real dependency. The local synthetic file is only for testing the button. |
| NCS transaction master | The history Agent501 learns from and codes. | Agent501 + output package | Used to make BTF, AR, AP, coded rows, and review queue files. |
| GL code / chart file | The official list of allowed GL codes and dimensions. | Agent501 validation + reviewer confidence | Use this to catch invalid GLs before export/sign-off. |
| Prior BTF / posted MIP export | Continuity and proof that prior/final files landed correctly. | FetaCheese / Sandy close-out | Recommended when closing the loop after fixes. |
| Rule | Plain meaning |
|---|---|
| One client, one brain | Each client has its own brain and its own corrections. A lesson taught on one client never reaches another. |
| How agents know | The client selected at login is the active client. Automation Lab, Get Output, Coffee inbox, stamps, and approvals all read that active client before writing lessons. |
| What feeds the brain | CPA/reviewer approvals, Coffee inbox resolutions, stamp overrides, and Get Output teaching become correction rows for that client only. |
| When to update | Use Update Agents in Get Output or Update Client Brain in Automation Lab after corrections are approved. |
| File name pattern | Open this when... |
|---|---|
NCS_BTF_Bank_Transfer_File_ready.xlsx | You want the BTF-ready workbook to copy/review. |
NCS_Agent501_Coded_Review.xlsx | You want to see what the coding brain filled and what needs a glance. |
NCS_Reviewer_Signoff_Record.xlsx | You need the reviewer/stamped record. |
NCS_AR_Deposit_Detail.xlsx | You are working money in, deposits, AR, grants, contracts, donations. |
NCS_AP_Disbursement_Detail.xlsx | You are working money out, checks, bills, disbursements. |
NCS_MIP_CD_Cash_Disbursement_Import.csv | You are preparing the cash-disbursement import for MIP. |
NCS_Agent501_Auto_Coded_Rows.csv | You want to inspect rows Agent501 handled automatically. |
NCS_Human_Review_Queue.csv | You want the rows a human must fix or approve. |
NCS_Data_Quality_Metrics.csv | You want the run metrics, gate status, and review counts. |
NCS_Agent501_Teaching_History.csv | You want who taught what, when, and how review counts changed. |
NCS_Output_Manifest.html/json | You want the official map of every file in the package. |
NCS_Next_Steps.md | You want the short checklist for what to do next. |
| Thing | What it means |
|---|---|
| Button | Use Get Output - Email latest output package. |
| Attachment | The suite makes one zip containing the latest BTF, coded review, AR/AP detail, MIP import, review queue, metrics, teaching history, manifest, and next-step files. |
| Setup | Email is configured by your administrator. |
| Area | Status | Plain meaning |
|---|---|---|
| Local automation | Ready for pilot | Upload/select files, build package, review/teach, rerun, and download files locally. |
| Output package | Multi-file | Get Output does not create one file. It creates the full office package plus an email ZIP. |
| Accounting judgment | Human-approved | Agent501 suggests and learns; reviewer/CPA approval is still required for uncertain coding. |
| Needs SMTP | Email works after SMTP settings are provided when the suite starts. |
| Status | Meaning | Action |
|---|---|---|
| FAIL | Would break or corrupt the books. | Stop. Open evidence and fix before sign-off or MIP import. |
| WARN | Needs a human look. | Review, approve, or teach the brain. |
| OK | Looks ready. | Spot-check and continue. |