You are looking at a live demo. Everything here runs on invented data for a fictional non-profit — no real organisation, no real people. Buttons are visible so you can see the workflow, but nothing you press will change anything. What is this?

Agent501 Official Flow how to run the work

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.

Big Picture

THE CLEAN PATH 1 · SORT Files arrive Coffee sorts them and routes each to its owner 2 · PRE-SCREEN Bank, card, payroll FetaCheese and Brad check before anything is coded 3 · CODE Agent501 Codes every row and builds the output package 4 · GATE Quality gate A failure blocks the export. Nothing posts. 5 · SIGN Sandy signs Then it sends to the client as one ZIP IF SOMETHING IS WRONG HELD Nothing guessed Unclear rows wait for a person to decide CORRECTED Fixed once The correction is kept and reused next month fails teaches Agent501 does this A person does this Stops the month Nothing is signed or sent until every held row is cleared.
1
Choose the client and input files
2
Run the right teammate
3
Open Get Output and evidence
4
Fix issues, teach the brain, rerun

Monthly Workflow

StepWhoWhat they doGo here
1CoffeeSort the dropped files and build the client's process map.Team 501
2FetaCheeseRun BTF bank/card reconciliation from bank file + MIP Exp GL, then review the red/yellow evidence.FetaCheese
3BradRun payroll checks and hold payroll rows that cannot safely import.Brad
4Agent501Build the full output package: BTF-ready workbook, coded review, AR/AP detail, MIP import, review queue, manifest, history, and next steps.Get Output
5CoffeeWork exceptions or route them back to FetaCheese for bank/card fixes and Brad for payroll fixes.Inbox
6Agent501Rebuild from corrected inputs: Coffee decisions plus FetaCheese / Brad fixes.Get Output
7SandyReview the clean package. If FAILs remain, send it back before sign-off.Sign-off
8Agent501Email the signed/latest output package ZIP to the required reviewer or client contact.Get Output

Required Input Files

InputPlain meaningUsed byImportant note
Bank file (Harbor Trust)What actually cleared the bank.FetaCheese BTF reconciliationCan be the local NCS master workbook for testing.
Exp GL detail from MIPWhat Agent501 already recorded in MIP.FetaCheese BTF reconciliationThis is a real dependency. The local synthetic file is only for testing the button.
NCS transaction masterThe history Agent501 learns from and codes.Agent501 + output packageUsed to make BTF, AR, AP, coded rows, and review queue files.
GL code / chart fileThe official list of allowed GL codes and dimensions.Agent501 validation + reviewer confidenceUse this to catch invalid GLs before export/sign-off.
Prior BTF / posted MIP exportContinuity and proof that prior/final files landed correctly.FetaCheese / Sandy close-outRecommended when closing the loop after fixes.

Client-Specific Brain

RulePlain meaning
One client, one brainEach client has its own brain and its own corrections. A lesson taught on one client never reaches another.
How agents knowThe 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 brainCPA/reviewer approvals, Coffee inbox resolutions, stamp overrides, and Get Output teaching become correction rows for that client only.
When to updateUse Update Agents in Get Output or Update Client Brain in Automation Lab after corrections are approved.

Output File Names

File name patternOpen this when...
NCS_BTF_Bank_Transfer_File_ready.xlsxYou want the BTF-ready workbook to copy/review.
NCS_Agent501_Coded_Review.xlsxYou want to see what the coding brain filled and what needs a glance.
NCS_Reviewer_Signoff_Record.xlsxYou need the reviewer/stamped record.
NCS_AR_Deposit_Detail.xlsxYou are working money in, deposits, AR, grants, contracts, donations.
NCS_AP_Disbursement_Detail.xlsxYou are working money out, checks, bills, disbursements.
NCS_MIP_CD_Cash_Disbursement_Import.csvYou are preparing the cash-disbursement import for MIP.
NCS_Agent501_Auto_Coded_Rows.csvYou want to inspect rows Agent501 handled automatically.
NCS_Human_Review_Queue.csvYou want the rows a human must fix or approve.
NCS_Data_Quality_Metrics.csvYou want the run metrics, gate status, and review counts.
NCS_Agent501_Teaching_History.csvYou want who taught what, when, and how review counts changed.
NCS_Output_Manifest.html/jsonYou want the official map of every file in the package.
NCS_Next_Steps.mdYou want the short checklist for what to do next.

Email Delivery

ThingWhat it means
ButtonUse Get Output - Email latest output package.
AttachmentThe 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.
SetupEmail is configured by your administrator.

Product Readiness

AreaStatusPlain meaning
Local automationReady for pilotUpload/select files, build package, review/teach, rerun, and download files locally.
Output packageMulti-fileGet Output does not create one file. It creates the full office package plus an email ZIP.
Accounting judgmentHuman-approvedAgent501 suggests and learns; reviewer/CPA approval is still required for uncertain coding.
EmailNeeds SMTPEmail works after SMTP settings are provided when the suite starts.

Color Rule

StatusMeaningAction
FAILWould break or corrupt the books.Stop. Open evidence and fix before sign-off or MIP import.
WARNNeeds a human look.Review, approve, or teach the brain.
OKLooks ready.Spot-check and continue.