BreezyCorp Handbook

Appearance

What a document reading may and may not decide ​

When a client sends a letter, a claim form or a contract, the document reader fills in a change card on the month. This page says what that reading is allowed to settle on its own, and what still needs a person. It applies from 27 Oct 2026 (READ-1).

The rule in one line ​

A figure read from a document is trusted when a second source says the same thing, never because the reader was confident. Until then, a person confirms it: the client on their payroll link, or staff.

Money figures on a month's card ​

The figures this covers: a new monthly salary, a monthly salary, each allowance (transport, housing, meal), a bonus, a commission and a claim total.

A figure counts as agreed when it is a valid amount (not negative, at most two decimals) and one of these states the same amount:

  • another document on the same card (an offer letter and the contract, the same letter sent twice);
  • the employee's record (its basic salary), for a salary figure;
  • a "please confirm" card the client answered and staff confirmed.

The reader's own confidence score never counts. The separate low-confidence warning (a field read below 0.8) is unchanged.

A figure that no document on the card states was set by a person (staff corrected it, or a client's answer was applied), so nothing is asked about it.

A figure that is not a valid amount is not put on the card at all (since 28 Oct 2026, stage review S2-L04): a negative, zero or three-decimal amount (an allowance may be 0) meets the same rule a typed figure meets, and the card, or the file when nothing else was read, carries A figure read from the document was not used, naming the value read. Check the document and correct the card, or ask the client for a clear copy.

When a figure is not agreed ​

Only for a company with a live payroll link (a company without one runs as before: staff review every card read from a document):

  1. A please confirm card goes to the client's To do list on the link: "Please confirm: Grace Tan's new monthly salary from 1 Nov 2026 is SGD 4,500.00", with the document it was read from.
  2. The month's change card carries the warning Waiting for the client to confirm a figure. You can still confirm the change past it on your own check of the document; like any warning, you name it when you confirm. Doing so withdraws the client's question if they have not answered yet.
  3. The client answers Yes, that is right, or No, it should be… with the right amount and the corrected document (a figure is only ever changed on a document).
  4. The answer appears on the company's Employees tab under Requests to the client → Answered — check these: "The client says it should be SGD 4,800.00, with the corrected document." Open the file, check it, then:
    • Confirm (for a "yes") closes the card and the warning.
    • Confirm: use SGD 4,800.00 (for a different figure) puts the client's figure on the month's card, sends the card back to needs review and records payroll.item.figure_from_client. Refused once the month is finalised.
    • Send back reopens the question with a reason the client reads.

A question is never carried to the next month: once the month's validation is signed off, any question still open is withdrawn.

For an attendance or leave report the client uploads on the payroll link (MON-5), each person's unpaid leave (days or hours) and overtime (hours, by rate) that is more than zero is asked the same way: "Please confirm: Grace Tan's unpaid leave in October 2026 is 3 days". The client corrects it by typing the number (no document needed: these are days and hours, not amounts); staff confirming the answer puts it on the person's attendance card. Figures the client typed themselves are not asked, and attendance sheets sent by message or added by staff are not asked either (a 40-row sheet would make 40 questions).

Two documents that disagree ​

  • A contract beats an offer letter, whichever is dated first or arrives first. A contract arriving after an offer letter replaces the offer's figures, even when the contract carries an earlier date, and the warning shows both figures. An offer letter arriving after a contract never replaces the contract's figures.
  • Two letters of the same kind (two change letters, say): the later-dated letter's figures are used, the card goes back to needs review, and a warning names both (Kiran, 5 Oct 2026).
  • A letter and what the client typed (stage review S2-L07): when the client typed the change on the link first, a letter that says something different never replaces the client's figure. It is attached, and the card carries Document disagrees with what the client typed, naming both, for staff to settle with the client. (A typed figure arriving after a letter's card with a different figure is refused, R79.)

The same payment in two shapes ​

A bonus the client types is a one-off payment card; a bonus letter is a pay-change card with the bonus inside it. When a bonus, AWS, commission, sales incentive or claim lands, from either side, any live card for the same employee with the same amount in any of those shapes puts Possible duplicate payment on both cards (stage review S2-L02). Nothing is refused: approving either means naming the warning, and rejecting one closes its warning. Two claims that both carry their lines are left to the line check (same supplier, bill date and amount); a claim form read second is the reader's own Possible duplicate claim.

Identity numbers and bank letters ​

  • An NRIC/FIN read from an offer letter or contract is not copied onto the month's new-hire card (stage review S2-L03, decision R63): it belongs on the employee record, through the record's NRIC/FIN check. The document keeps it for the cross-document NRIC check. A new hire's placeholder code in the Infotech file is always NEW-001, NEW-002…, never built from an ID number.
  • A bank letter's account holder must be the employee's own name by the record's rule (R21: the same words in any order; initials or a shortened name such as TAN WEI for TAN WEI MING count as different), compared with the name on the month's card, else the month's employee list, else the employee line on the letter (stage review S2-L10). A letter with no employee line is matched by its holder. A mismatch is the Lead-only bank account is held by … finding, and keeps a new hire held, as before.

What the reader leaves empty ​

A field the reader cannot find stays empty rather than guessed:

  • a new hire's card no longer says nationality local, and a leaver's card no longer says not a foreigner: residency comes from the month's employee list;
  • a letter with no date makes a card dated the day it arrived, and the card says so with the warning The document gives no date. It closes when a dated letter arrives or you give the date; otherwise you name it when you confirm. Claims are left out, since a claim has no effective date.

What staff may fill in on a held card ​

When a document was read but left a required field out, its card is held as incomplete document. Staff may type a missing non-financial detail (an NRIC, a job title, a name) on the held card, and the hold lifts; what they typed is kept on the card's history. Three kinds of value are never typed, and the card waits for the client's corrected document instead, which releases it when it arrives:

  • an amount (salary, allowances);
  • a date (start, effective, last working day);
  • a bank detail: bank name, account number, account holder, branch code or SWIFT (since 28 Oct 2026, stage review S2-01; doc rules #13: never a payment destination without client confirmation). The list is the record's bank values below, plus the account holder, because the account not in the employee's name check reads the holder from the document.

Typing one is refused with "… cannot be typed in: ask the client for a corrected bank document" (or document for an amount or a date). Ask client asks for a corrected bank letter giving what is missing.

On the employee record ​

Identity numbers (NRIC/FIN, work pass, passport), bank details (bank, branch, account number, SWIFT) and money (basic salary, allowances) saved from a document or the onboarding form get a please confirm card on the record, showing a hidden value masked ("…account number is ••••••7890"). Another document stating the same value, or a person typing the same value, settles it. The client's correction goes on the record at once through the usual field rules, and staff confirm the card to close it. Nothing saves values from documents into the record yet; this is ready for the onboarding uploads.

The bank account name is not on this list: whether it matches the employee's name is its own check, with its own card.

Identity, bank and birth-date values on the month page ​

Since 28 Oct 2026 (stage review SX-44), the month page's What we read list (under a file, and beside the document when you open it) shows an NRIC/FIN, bank account, tax reference or passport number as its last four characters (•••••567D), and a date of birth hidden whole, the way the employee record does. Reveal next to a value shows it in full for you; each reveal is recorded on the audit trail with who looked, which field and which file (never the value). Names, salaries and dates are shown as read.

Internal use only — BreezyCorp