What changes
IllustrativeTypical numbers for a 5-tech shop paying weekly or every two weeks. Not measured from a real client.
- Cross-checking each pay run
2 hours in a spreadsheetbecomes 5 minutes reviewing exceptions- Double payments caught before they're marked paid
0becomes every one- Jobs marked paid on a guess
a few each runbecomes none: proven or a person decides- Jobs never marked paid
found at tax timebecomes shown as owed the same day
Bank inbox
Transfer confirmations from Cedar Ridge Bank for this pay run, in the order they arrived. Open one and check it, or press Check all new transfers. The real automation does this on its own every 15 minutes.
Pay run
| Job | Pay | Status |
|---|
Known names and saved accounts
A bank shows whatever name was typed when the payee was saved. These are the only names that count as each tech. A name that isn't here never matches, however close it looks.
Any transfer that isn't proven lands here with the email, the jobs it might cover, the difference and a suggested next step. A person approves it with a note, rejects it, or fixes what was read and re-runs the checks.
Every check, newest first, including skipped repeats and what it would have done in shadow mode. Saved in this browser.
The safety rules it follows
What it costs to run
Ted builds it for a fixed price, then a monthly retainer covers running it: watching the Needs a person queue with you, adding names to the known-names table, adjusting the pay rule when it changes, and fixing what breaks when the bank changes its email format.