The RSD Payroll dashboard on a monitor in a dark office at night: the month as earned and as cash, founder payouts and validation checks (figures anonymised)

Payroll System

Software & SaaS
Software & SaaS

Payroll System

Payroll is where a small calculation error becomes a real payment. RemSoft.Dev built its internal payroll application with ConnectOtherAIs - the review gate of Dew Flow, our multi-agent development orchestrator - checking the work: the coding agent sent every plan and every implementation to models from other vendors, fed the findings back into the work, and recorded a decision for each one. Over 26 review rounds in 12 sessions, all 196 findings received a decision and 155 were accepted for action. A review found a commission path that ignored the part-month scale - the calculation produced 500 where 357 was due - and a failing test exposed it before the fix aligned commission with the scaled cash allocation. Fractional or out-of-range day counts, which were silently truncated or crashed the server, are now rejected. Administrators whose rights are revoked lose access at their next action, even in a tab that is already open. Sign-in is bound to the account's durable Microsoft identifier instead of a changeable email address, viewing and editing got separate permission rules before the manager view was built, and a rule that a tampered form could bypass moved into the server-side use case.

AI code reviewPayrollAccess controlConnectOtherAIs

Key Challenges

Client: RemSoft.Dev internal

Product: Company payroll application

Review: ConnectOtherAIs - plan and code rounds

Sign-in: Microsoft Entra ID

The project faced several key challenges:

  • Money must be exactly right: A commission path skipped the part-month scale. A failing regression test proved the discrepancy before the fix.
  • Access must follow role changes: A demoted administrator with an open tab kept working. The session is now revalidated before each unit of work, covered by a browser test.
  • Identity must not change with an email: Sign-in now binds to Microsoft's durable object identifier, with a mismatch check.
  • Rules belong on the server: A tampered form could record hours without an eligible hourly deal. The rule moved into the server-side use case, with a test.

Results

  • Commission payable follows the part-month scale
  • Invalid day counts rejected instead of truncated
  • Revoked administrators lose access at the next action
  • Separate permission rules for viewing and editing
  • Concurrent day-log edits no longer overwrite each other

196 of 196

review findings received a decision; 155 accepted for action.

26 rounds

of plan and code review across 12 sessions.

3.6 / 6.0 min

average plan and code review round.

Related case studies

Want to Build Something Similar?

Tell us about your project - we will propose an approach, a timeline and a first estimate.

An unhandled error has occurred. Reload 🗙