Payroll Settings Page

1Overview #

The switches and values that steer the INVENTORY side of the company — the stock valuation methods the books close on, how the scan box reads a barcode, which columns the product master demands, and how the transaction screen behaves. Change a value, press Save; every screen picks the new value up the next time it loads. Administrators only.

The switches and values that steer WAREHOUSE MANAGEMENT for the whole company: the default order of the putaway rules, how the putaway quantity is given, whether a voucher may be put away in parts, how many bins are suggested, whether a code may be typed instead of scanned, and the nightly check of the bins against the books. Change a value, press Save; the Putaway screen picks it up the next time it reads the pending vouchers, the nightly check on its next look. Administrators only, and only with the Warehouse Management licence. What one storage space sets for itself is on Putaway Rules.

The switches and values that steer the COMMUNICATION HUB - how often the mailboxes are read and what is kept from them, how fast bulk and automatic messages go out, the reply clock of the team inbox, the hour the date events are sent at, and whether the books answer a customer's BAL, STMT, INV and PAY texts by themselves. Change a value, press Save; the hub's worker picks it up on its next round (within a minute). Administrators only, and only with the Communication Hub licence.

The switches and values that steer the CASH COUNTER on the web. Special discount : 226 says when an approver is needed (Off, Above authority, Always); 227 how many hours an approval stays usable (0 = no expiry); 228 what the counter does with a bill whose discount is still waiting (Block, or Settle at full price and withdraw the request). Counter and closing : 229 flags a closing whose excess or short is above that many rupees (0 = flag every difference); 230 checks the party's credit when a bill is settled on credit at the counter (Off, Warn, Block). The desktop's own counter settings - among them 111 / 112 and 40, the discount limits used when no Cashier Discount Authority row covers a cashier - stay in the desktop Settings (module TKN). Change a value, press Save; the counter picks it up on its next bill. Administrators only.

The switches and values on this page steer how the whole payroll module behaves — whether an approved leave posts itself into attendance, which ages an employee may be enrolled at, whether payroll preparation demands approved entries first, and which weekdays count as the week-off. Change a value, press Save; every screen picks the new value up the next time it loads.

2Purpose — and the settings that matter most #

(ModuleCode == "ACC") {

• Compulsory Tracking — whether voucher entry demands a cost centre (#9), cheque details (#10) and bill-by-bill allocation (#11); whether the allocation dialog offers On Account (#44); whether bills adjust within the same branch only (#80).
• Ledger Numbering & Creation — how a new ledger's account code generates (#16 method, #17 start, #18/#19 prefix and suffix, #20 digits) and whether creating a ledger needs a request first (#78).
• Presentation & Formats — the balance shown on transaction screens (#14), the amount format (#29) and the Indian/Western digit grouping (#87).
• Credit Approval — the workflow's own three rules: the fallback approver list (#211, comma-separated user IDs), self-approval (#212) and the largest valid-for-N-bills a grant may carry (#213). These are the settings the Credit Approvals page and the save-time check read.
• Loan Module / Referral Commission — the enable switches and the ledger accounts those postings book against (#82/#83, #100-#102; the account pick-lists read the ledger master live).

} else if (ModuleCode == "WMS") {

• Putaway - the default order of the putaway rules (#291): the codes PICKBIN (the item's pick bin), SAMEITEM (a bin already holding it), CLASSZONE (an empty bin in a zone of its putaway class), ANYEMPTY (any empty bin), comma separated, first one first; leave a code out to switch that rule off. It applies to every storage space that has not saved an order of its own on Putaway Rules.
• How the quantity is given when Putaway opens (#292): Box - scan once, type the quantity; Piece - scan every unit. The operator can still switch on the screen.
• Whether a voucher may be put away in parts (#293). Yes: an entry takes what was scanned and the rest stays pending for a later entry. No: an entry must put away everything pending of the vouchers ticked.
• How many bins Putaway suggests for a scanned material (#294, 1 to 20).
• Scanning - whether a bin label or a material code may be typed (#295). No: the Putaway screen takes a code only from a scanner, or pasted whole; a code typed key by key is refused. It is the screen's rule - it keeps people honest on the floor, it is not a lock.
• What ONE storage space decides for itself - automatic allocation, who finds the bin, the checks on a scanned bin, its own rule order and refinements - is on Putaway Rules, not here.
• Nightly check - whether the bins of every storage space run by the WMS are compared with the books once a night (#296), and the hour from which it runs (#297, 0 to 23, the API server's clock). A difference puts an item on the bell of the Administrators and of the users holding Alter on WMS - Bins; it opens Bin Reconciliation. The check moves no stock.
• Screens - which storage spaces the Warehouse Management screens list (#298). No, as delivered: only the storage spaces run by the WMS. Yes: Warehouse Layout, Bin Master, Item Warehouse Settings, Putaway Rules, Bin Stock and Bin Reconciliation list every storage space open to the branch, each marked (WMS) where it is run by the WMS - useful while bins are being laid out for a storage space before it is switched on. Putaway, Picking and Opening Bin Stock list only the storage spaces run by the WMS whatever is set here: there is no bin work in the others.
• Tasks - how many minutes a task a worker has opened may stay untouched before it goes back to its pool (#299, 1 to 720, 15 as delivered). Every scan starts the time again. A task given to a named person stays that person's; only the lock is let go, so the Task board can give it to somebody else.
• Settings for picking and counting arrive with those deliveries; a setting nothing reads yet is not offered.

} else if (ModuleCode == "COMMHUB") {

• Mailboxes - how often the hub reads the INBOX of each mailbox on Communications > Channel Setup (#253, minutes, 1 to 60; blank or 0 = 5) and the largest attachment of an incoming mail kept with the message (#254, MB; a larger one is listed by name only, 0 = names only).
• Sending - how many bulk and automatic messages go out a minute, per company (#255, 1 to 600; blank or 0 = 60). Keep it within what your mail server and gateways allow.
• Team inbox - a conversation whose customer wrote and nobody answered for this many hours is Overdue (#287, 0 = no clock, 1 to 720).
• Automatic messages - the hour birthdays, work anniversaries, post-dated cheques due and credit limits are looked at, once a day (#288, 0 to 23, the server's clock).
• Self-service replies - whether a customer texting BAL, STMT, INV <number>, PAY or HELP from a number on its contact persons gets the answer from the books (#289, OFF to start with - an answer tells a customer its own figures), and at most how many such answers one party gets a day (#290, 1 to 100).

} else {

• Stock Valuation — the method the books value CLOSING stock by (#3) and OPENING stock by (#13). #3 is the single most consequential setting on this page: every stock register, the valuation cross-check and the accounts' stock figure follow it.
• Barcodes & Scanning — the prefix character (#15), Ver 5.0 self-describing labels (#42), branch-only lookups (#43), duplicate-scan refusal (#49), carton-factor multiplication (#52), single-use unique barcodes (#67) and the fixed positions a longer scan carries barcode and quantity at (#107/#108, -1 = off).
• Product Master — which extra columns and pickers the product master offers or demands (#6, #21, #22, #61, #85/#86, #141).
• Transaction Screen — the party balance beside the voucher (#4), the advanced F2 find (#5), the qty format (#30), the after-save ID message (#53), reserve stock in the stock panel (#56) and reverse calculation on the Amount column (#88).
• Serial, Batch & TranID — serial-number tracking (#1), the TranID demand (#41) and the expiry-months rule in the cost sheet (#106).

}

3Where the values are used #

• The compulsory-tracking switches are read by the accounting voucher screens as each entry is committed; the numbering settings by the Ledger Account master when a new account's code generates.
• The credit-approval rows are read by the Credit Approvals page (who may decide, the N-bills cap) and mirror what the voucher save enforces — the whole workflow is documented on that page's own help.
• #58 Show Linked Tran Pending In Financials feeds the P&L engine's two pending-linked lines AND the save-time credit check's pending arm.
• The formats (#29/#87) are read wherever amounts print; a change shows on each screen's next load.
• #291 - read whenever a bin is suggested or automatic allocation places stock, for a storage space whose own rule order was never saved on Putaway Rules. A storage space that saved its own order keeps it.
• #292, #293, #295 - read when the Putaway screen loads the pending vouchers (press Refresh there to pick up a change); #293 is checked again by the server when an entry is submitted.
• #294 - read each time a material is scanned on Putaway.
• #296, #297 - read by the API server's nightly check every ten minutes. Switching #296 to No stops the check from its next look; moving #297 to an hour that has already struck today, with no check made since that hour, runs it at the next look.
• #298 - read when a Warehouse Management screen opens; a screen already open keeps its list until it is opened again.
• #299 - read each time My Tasks or the Task Board lists tasks, and each time a task is opened: claims older than it are let go at that moment.
• Nothing here changes stock already in the bins or entries already submitted.
• The API server's Communication Hub worker reads #253, #254, #255, #288, #289 and #290 on every round, company by company - a change counts from its next round.
• #287 is read by Communications > Inbox & Outbox for the Overdue folder and the red reply clock.
• #3 is read by every stock valuation: the registers, the cross-check report, the gross-margin COGS and the accounts' closing-stock figure. Change it and the books value differently from the next load — a decision for the accountant, not a whim.
• The scanning settings are read by the transaction screen's scan box exactly as its own help describes (the desktop reads but ignores the two position settings; the web acts on them).
• The product-master switches decide which columns that master shows or demands; #61 also gates saves that arrive through imports.
• #93/#168 steer the Linked Transaction Manager's auto-refresh and its custom list query.

4Why is a pick-list empty? #

• The account-head settings (#83, #101, #102) list every ledger account — an empty list means none exist yet; create them in the Ledger Account master.
• The numbering-method (#16) and digit-grouping (#87) lists are fixed lists carried by the row itself. } else if (ModuleCode == "WMS") {
• The one pick-list here - how the putaway quantity is given (#292: Box, Piece) - is a fixed list carried by the row itself.
• The putaway rule order (#291) is typed, not picked: its order matters, and a pick-list cannot keep an order. } else if (ModuleCode == "COMMHUB") {
• The hub's settings carry no pick-lists: #289 is a switch, the rest are numbers. } else {
• A pick-list's options load once when the page opens; press Reload (F2) after creating the missing master record.

5Purpose #

• Payroll behaviour that must differ from company to company lives here rather than in code. Each row is one decision; the important ones: Auto-Post Leave Approval Entry to Payroll (#121) turns an approved leave application directly into an attendance/leave entry; Minimum / Maximum age for Employee Enrollment (#169/#170) is the age band the Employee master enforces on the birth date; Is Need Approval For Attendance/Leave/Production Entry to Prepare Payroll (#81) blocks payroll preparation on unapproved entries; Week-Off Days (#66) names the weekdays attendance treats as the weekly off.
• The rest cover salary-payment controls (authorization approval #77, restriction through voucher entry #69, finger authentication #70/#89), the attendance entry screen's Time-IN/OUT columns (#59), branch-wise attendance in the pay bill (#63), extra remuneration (#64 with its formula #65), the inter-branch salary account heads (#75/#76), the employee-reserve percentage (#57) and the mobile app's location-tracking interval (#110).
• Each setting row DESCRIBES ITSELF: the table stores what kind of value it takes and where a pick-list value comes from, and this page builds the right editor from that alone — a switch for Yes/No rows, a number box for numeric ones, a pick-list where the row carries one, plain text otherwise.
• The Employee Enrollment group grew beyond the age band: Employee ID auto-generation prefix (#179), Default probation period (#180), Mandatory fields at employee enrollment (#181, a multi-pick list), the duplicate Mobile (#182) and National ID / Aadhaar / PAN (#183) blocks, Retirement age (#184) and the Document expiry alert window (#185) — all enforced by the Employee master. These rows appear once the employee-enrollment settings seed script has been run on the database.
• The Attendance & Shift group likewise grew a set of shift rules enforced by the Shift master and the shift-assignment screens: Allow overnight shifts (#186), Warn on duplicate shift timings (#187), Maximum shift duration (#188), Default Week Off for new shifts (#189), Default shift for new assignments (#190, a live pick-list of the active shifts, blank allowed) and Block assigning inactive shifts (#191). These rows appear once the shift-rules settings seed script has been run on the database.
• The cards sit in themed GROUPS — Employee Enrollment , Attendance & Shift , Salary & Payment , Leave Policy , Leave Request & Approval — with anything unclassified under Other . The Leave Policy and most Leave Request & Approval settings belong to the leave module and appear here automatically once its settings seed script has been run on the database (until then only the auto-post switch #121 shows in that group). The notification rows #193-#198 in that same group arrive with their own seed script — and until #193 names a channel, no leave notification is ever sent.

6Where the values are used #

• #121 Auto-post leave approvals — read by the leave-approval flow: with 1, approving a leave application writes the attendance/leave entry itself; with 0 the entry is keyed manually.
• #171-#178 leave-module settings — read by the leave screens (accrual posting mode, year-close lapse, encashment, the balance check and advance-notice rules on the request screen, approver routing, rejection remarks). These rows exist only after the leave-module settings seed script has been run on the database.
• #193-#198 leave notifications — read by the leave workflow when it announces an event by e-mail, SMS or WhatsApp. #193 lists the channels and is blank by default, which switches notifications off entirely ; #194 lists the events that notify (Submitted, Recommended, Approved, Rejected, Cancelled, Escalated); #195 names the e-mail profile whose sender account — and, when it has one, whose subject and body text — carries the message; #196 names the SMS/WhatsApp gateway account (an SMS template name is accepted too, and blank lets the system pick a gateway of the right type); #197 is a standing HR / authority list that receives EVERY event, e-mail addresses and mobile numbers together, comma separated; #198 decides whether the send happens on a background task so no approval ever waits for a mail server. Who each event reaches is not a setting: while a request waits, EVERY approver able to act at its level is told - the Reporting Person(s), the named user, or every holder of the approve permission on Leave Approvals when the rule names no one in particular; once it is decided, the applicant, the person who entered the request and everyone who acted on it are told. #197 is added to both, the list is de-duplicated on the address, and the fan-out stops at 50 recipients per event (the overflow is recorded as a "Skipped" line in the notification log). A notification is always sent after the workflow action has been stored and can never delay, block or roll it back. These rows exist only after the leave-notification settings seed script has been run on the database.
• #169/#170 Enrollment age band — the Employee master (web and API) validates the birth date against this band on every save; 0 or blank switches the rule off.
• #179-#185 employee-enrollment rules — all read by the Employee master: #179 generates a blank Employee ID as prefix + next serial; #180 fills the probation days on a new record; #181 lists the fields that must be filled before a save (the picks store space-separated, and the Passport pick applies to everyone — it does not consult Is Foreigner); #182/#183 refuse a Mobile / National ID / Aadhaar / PAN already registered to another employee, naming the clash; #184 suggests the Expected Retirement Date as birth date + this age; #185 makes loading an employee warn about document expiries inside the window. These rows exist only after the employee-enrollment settings seed script has been run on the database.
• #81 Approval before payroll — payroll preparation refuses months that still carry unapproved attendance/leave/production entries while this is 1.
• #66 Week-off days — attendance processing and payroll preparation treat these weekdays as the weekly off; several days are stored space-separated. While #189 is on, the FIRST day named here also pre-fills the Week Off of every NEW shift in the Shift master.
• #186-#188 shift-timing rules — read by the Shift master on every save: #186 off refuses an Out Time not later than the In Time (and the Crosses-midnight switch), while on it treats an earlier Out Time as a shift crossing midnight; #187 makes saving a shift whose In/Out equal an existing shift's ask for confirmation (a warning, not a block); #188 caps the In-to-Out span in hours (0 = no cap, measured across midnight for overnight shifts). The page checks first and the API repeats the checks with the same wording. These rows exist only after the shift-rules settings seed script has been run on the database.
• #190/#191 assignment rules — #190 names the shift pre-selected on NEW rows of the Shift Assignment page and the Employee master's Shifts dialog (blank = none; a name that is no longer an active shift is ignored); #191 makes the assignment save paths refuse a row naming an inactive shift — the pick-lists already hide them, this closes the API-side hole.
• #59 Time-IN/OUT columns — the attendance entry screen shows or hides its time columns by this switch; #63 adds branch-wise detail to the pay bill.
• #77 / #69 / #70 / #89 salary-payment controls — the salary payment and overtime screens read these to demand authorization approval, block payment through plain voucher entry, or require finger authentication.
• #64 / #65 extra remuneration — the payroll calculation applies the formula only while #64 is on.
• #75 / #76 inter-branch account heads — inter-branch salary postings book against the ledger accounts named here (the pick-lists read the ledger master live).
• #57 employee reserve % and #110 location-tracking interval — the reserve calculation and the mobile app's tracking timer respectively (0 disables tracking).

7Your first change, step by step #

Suppose approved leave should start posting itself into attendance.

1. Find the card Auto-Post Leave Approval Entry to Payroll (#121) — it sits in the Leave Request & Approval group; within a group the cards follow setting-number order and each shows its number.
2. Flip the switch to Yes . The card gains a modified tag; the header counts how many settings you have touched so far.
3. Change anything else in the same sitting — only the changed cards are sent.
4. Press Save (F5) and confirm. Every change lands in ONE transaction — all of them or none.
5. The banner confirms the save. Screens already open keep their loaded values; the new value applies the next time each screen loads — nobody has to sign out.
6. Changed your mind before saving? Discard Changes (Esc) puts every card back to the saved value; Reload (F2) re-reads the table (it warns first when unsaved changes would be lost).

8Field details #

• Yes/No switches — stored as 1/0. The text beside the switch shows the current state.
• Number boxes — right-aligned, digits only; used where the setting's value is numeric (ages, percentages, minutes).
• Pick-lists — the row itself names its source: a fixed option list (the week-day setting) or a live query (the account-head settings read the ledger master). Typing filters the list; a value that is no longer in the list stays editable so an old saved value is never destroyed by opening the page.
• Week-Off Days — tick every weekday that counts as the off day; the picks are stored space-separated in one value, the order following the option list.
• Multi-line text — the extra-remuneration formula edits in a larger box; Enter moves fields elsewhere, so use the box's own line breaks.

9Shortcut keys #

• F2 Reload the settings · F5 Save the changed ones · Esc Discard the unsaved changes.
• Enter moves to the next field.
• Keys belong to the focused copy of the page; a dialog's own keys win while it is open.

10Why is a pick-list empty? #

• Default shift for new assignments (#190) lists the ACTIVE shifts (EmpShiftInfo) — an empty list means no active shifts exist yet; define them in the Shift master. This setting may also simply be left blank.
• Week-Off Days (#66) carries its own fixed list (the seven weekdays) inside the setting row — it can only be empty if the row's option string was cleared in the database.
• A pick-list's options load once when the page opens; press Reload (F2) after creating the missing master record.

11Rules and integrity #

• One transaction. All the changed settings save together or not at all.
• Blank values. A setting may only be left blank when its row allows it (the formula setting does; the rest refuse blank). The page checks first; the API repeats the check as the safety net.
• Yes/No and numbers. Switches can only ever send 1/0; number boxes must parse as a number — both checked again on the server.
• Fixed pick-lists. A value saved for a fixed-list setting must come from that list (each space-separated pick, for the week-day setting). Live-query pick-lists are not re-checked at save — their lists are live data.
• Changes take effect on the next screen load. Nothing is cached by this page, and the API-side readers (the age rule, the payroll gates) read the table live on every call — no re-login is needed. A screen already open keeps the values it loaded with until it is reopened.
• Nothing is created or deleted here. The page only UPDATEs existing rows; setting rows are installed with the application or added by its seed scripts (the leave-module rows arrive that way), and the page shows whatever exists — new rows need no page change.

12If something does not work #