Remittance Reconciliation
Principle 03Validated before it processesRemittances arrived as folders of Excel files, and someone had to open each one just to find a few values and check them against the source — account by account, every day. This points at the folder instead: it scans the new files, compares each value to the source, flags only the mismatches, and writes the result to the shared log in the exact format the team already documents. The reconciliation a person used to do by eye, done in one pass.
SheetJS
batch compare
+ shared log
~2 min / batch
Point it at the folder. Get back only what needs a human.
Point
Aim the tool at the source folder of remittance files — no copying, no opening.
Scan
It reads every new Excel file in the folder in one batch.
Compare
Each value is checked against the source file and the account name.
Flag
Matches pass silently; only mismatches are surfaced as warnings.
Log
One click writes the result to the shared log in the team’s existing format.
Every value checked — only the exceptions surface.
A person scanning hundreds of figures by eye misses things when they’re tired. The scan checks all of them the same way and only asks for attention where a number doesn’t agree with its source.
The matches stay quiet; the few that don’t match are the whole point.
Source value vs. remittance value — line by line.
The comparison isn’t a guess. Each remittance figure is matched against the source file and the account name, so a flag is something you can act on, not a maybe.
Fifteen minutes a file became two minutes a batch.
Opening files one at a time to hunt for values became a single folder scan, and the output lands in the same shared log the team already keeps — no new process to learn.
The documentation they relied on is produced for them, consistently, as a byproduct of the run.
A web app over a shared log — no installs.
Google Apps Script · SheetJS · HTML5/CSS3 · JavaScript — pointed at the team’s folder, backed by a shared database.