What we shipped, in plain language.

The Customer box on the AR direct invoice and on an adjustment note was blank for accounts-receivable users. The list was being read from the CRM customer master, which those users are correctly not members of, and the refusal was swallowed into an empty dropdown — so a permission gate doing its job looked exactly like a broken screen.

Both forms now read the customer list from the reference tier, under a permission the affected roles already hold. Nobody gains access to the CRM module in order to fill in a dropdown. The list carries the credit currency and payment term with it, because the invoice defaults both from the customer.

Two further consequences of the same fault are gone. A refusal now names the missing permission on the field instead of showing an empty list. And the adjustment note loaded its five lookups as one batch, so a single refusal emptied companies, currencies, suppliers and the chart of accounts too and reported “Failed to load reference data”; each list now stands on its own. An invoice raised against a customer since deactivated shows that customer’s name rather than an empty box.

The gate operators recording a front-desk entry had no warehouse or storage location to choose from: both lists came from the inventory master, and no front-desk role grants inventory module access.

Both lists are now served from the reference tier under a permission those roles already hold, and the storage location list carries its parent warehouse so the second dropdown still narrows to the first.

Tasks Upload takes the TA template Excel sheet a merchandiser already maintains and creates the project’s tasks from it. The upload is in two steps: a preview that writes nothing, showing the project it resolved, the counts and every question it has, and then a commit.

Only the rows marked Task reqmnt = Y are loaded. An N row is a task the plan says this order does not need — it is counted and reported as not required, never as a failure.

Where the sheet and the system disagree, the upload reports rather than guesses:

• A department name matching more than one department in the hierarchy is refused, naming both candidates, rather than picked.
• A near-miss spelling is matched, but the substitution is stated in full — both spellings, on the row — never applied silently.
• An employee is resolved by id; if the Name column disagrees with the record found, that is reported, and the name never overrides the id.
• The Dependent Task column is free text that does not name a task exactly, so it is recorded in the task’s notes and never turned into a real dependency. A dependency guessed from prose would drive the schedule off unvalidated text.

Re-uploading over a project whose work has already begun is safe: the opening status is set on creation only, so a task already in progress or completed is never walked back and no recorded progress is erased. The commit re-reads and re-checks the file itself rather than trusting the preview sent back to it, so an edited preview cannot slip a row past validation.

Reading the preview needs task view access; committing needs the right to create tasks.

An export receipt settles invoices that were booked at their own exchange rates, while the bank pays at today’s. The gap between the two is the realised exchange difference and it belongs on the gain or loss account.

The journal has posted it that way since the foreign-currency work shipped, which is why Simulate always showed the right figures. The customer ledger row did not: it converted the receipt at the receipt’s own rate, so the difference landed on the customer’s account as well as on the exchange account, and the customer ledger disagreed with the receivables control account by exactly the gain. In foreign currency the customer was always square; in rupees the account was overstated.

The ledger row now takes the settlement figure from the same calculation the journal uses — read, not recomputed — so there is one definition of what the receipt relieved and not two. Reversing a receipt no longer quietly puts the difference back onto the customer either.

Administrators: rows written before this can be repaired with the backfill_receipt_local_relief command. It refuses a row it cannot settle honestly — a foreign-currency invoice carrying no usable rate, or a home-currency row, where a gap is a discrepancy rather than an exchange difference — and names it for someone to look at.

Form-1 now carries the ESI Corporation seal at its head and Form-2 the EPFO seal, as the sheets filed with the branch office do.

The seal identifies the form, not the employer, so it is shipped with the system rather than being tenant configuration — neither form identifies the employer by letterhead in any case (Form-1 does it by code and address, Form-2 by establishment code). The company logo remains only as a fallback, and if the emblem cannot be read the head prints without a seal rather than the document failing.

Because the mother tongue now decides which language a personnel form prints in, a typo in it is a form in the wrong language. Application Particulars therefore offers the language list instead of a free-text box — the same list the Languages tab uses, so the two screens cannot spell the same language differently — and a value already recorded stays selectable, so opening the dialog can never blank it.

A starting list of languages is seeded, and the dropdown can add to it from its own dialog for a language that is not on the list. Adding is a deliberate act, never a side effect of choosing a value; renaming or removing a language people are already recorded against stays an administrator decision.

Tenant lists built by hand held the same languages twice, under different spellings and casings, once the seeded list arrived beside them. Those duplicates are merged, not deleted: everything pointing at a duplicate is moved onto the single surviving row first, so no employee’s recorded language is lost. A row that cannot be removed because something still points at it is deactivated instead and simply leaves the dropdown.

The employment application and the job request are bilingual forms, and the second language now follows the applicant’s mother tongue rather than being fixed. A Hindi mother tongue prints the title, every label and the declaration in Hindi; a Tamil one prints the form exactly as it printed before.

Both forms read from one shared catalogue of labels, because they are the same seventeen sections and must not end up saying different things about the same line. A translation is a lookup and never a transliteration: a mother tongue with no translated set prints in the language the form was drawn in, and a line with no translation prints in English alone rather than mixing two scripts on one page. The mother tongue itself now prints in both scripts — “TAMIL / தமிழ்” — taken from the language master, never invented.

The second lines can still be switched off outright when a plain English sheet is wanted.

Administrators: each language needs its font installed on the print server. Without one the second line simply drops out and the English label carries the meaning.

ESI Declaration Form-1 and PF Nomination Form-2 now print from the employee record, in the statutory layout, ready to be signed and filed with the branch office.

They are printed from the employee profile, with a preview before the paper. Both are locked layouts: their wording is prescribed, so unlike the tenant’s own forms they cannot be redesigned in the print designer.

Behind them is a proper nominee register. A nomination is not a family member: it is recorded per scheme — the ESI nominee and the PF nominee may be different people — with a share, and it is ended by being revoked rather than deleted, so the record of who was nominated when survives. Form-2 keeps the two apart as the statute does: the family table is the family, the nomination box is the nomination.

What the record does not say, the form does not invent. Shares are reported as recorded and never quietly adjusted to add up — a set that does not total 100% is flagged for HR to correct in the record, not corrected on the paper. An unanswered question prints blank rather than ticking a box, and the establishment code is taken from the statutory filing details in force today, with none on file printing blank.

The proration factor was rounded to four decimals before being multiplied, so 22/31 became 0.7097 and overpaid a few paise a month on a mid-range basic — an error that scales with salary and headcount and never reconciles. The factor is now carried at full precision through the arithmetic, with the four-decimal value kept for display on the payslip.

Loss-of-pay days were silently always zero. The engine looked for unpaid leave by matching the word “unpaid” in a field that does not exist, the resulting failure was swallowed, and every unpaid day was paid in full.

Unpaid is now read from the leave type’s explicit paid / unpaid flag rather than guessed from its name, and a failure is reported loudly instead of being absorbed — this direction of error overpays.

Proration counted the denominator over the whole period but the numerator as “all working days less unpaid days”, never consulting the employment start date. Someone who joined on the 20th came out at a full month’s factor and was paid a full month. Both sides are now counted the same way, and an unpaid day falling on a rest day is no longer deducted from a working-day denominator.

The working-day denominator was extrapolated from weeks × days per week, which gives 26.57 days for August 2026 on a six-day week against an actual 26 — the denominator of gross pay, wrong by half a day, every month, in both directions. The rest-day pattern is now counted for the period, with dated holidays from the production calendar taken off as an overlay.

The proration method is also configurable per payroll area instead of being fixed in the engine. It defaults to calendar days, so an existing payroll area keeps exactly the behaviour it has today.

A payroll run for one employee was not actually running as a single unit of work on the tenant’s own database connection, so a failure part way through left a partial result committed. It is now bound to the right connection and either completes or leaves nothing.

Two related corrections: the run number is allocated under a real lock, so two runs started at the same moment can no longer claim the same number; and generating payroll periods from the command line now requires the user and tenant it records, refusing by name instead of writing an empty tenant.

The employee list filtered on one of the two flags that record whether somebody still works here, so an employee marked inactive could still appear. The two are kept in step now — approving or revoking a separation moves both — and the default list scope excludes inactive employees, while asking for a status explicitly still returns them.

An employee’s application form can now be printed as a PDF from the employee record, with a preview before it goes to the printer.

It is a reprint of the master, not a second form to fill in: the print takes no field from the screen, so a blank on the form is a blank on the record — and the record grew the fields the form actually asks for, family particulars among them, rather than the form inventing them.

• A default is not an answer. An unrecorded blood group, an age of zero and an absent wage all print blank rather than printing a value nobody supplied
• The photograph is embedded in the document itself, so it is there on paper and in the PDF you email
• The layout is a print format like any other, so it can be tailored per tenant — and printing never depends on that: the shipped layout is always there behind it

The first half of the hiring paperwork is filled in before anybody is an employee, so the Job Request form prints from the recruitment candidate rather than from the employee master.

• The candidate record now holds the particulars the form asks for — previous experience, salary drawn and expected, and the declarations — captured on the candidate screen and previewed before printing
• The office-use block on the form is ruled space: it is there to be written on, and nothing is read back off it
• Anonymising a candidate purges the particulars this form added, along with everything else held about them

An identity card can be printed for an employee from the employee record, or for a selection of employees from the employee list, on a page of its own with a preview first.

• The card is laid out at the standard 91 × 56 mm, two to an A4 sheet, so a batch comes off an ordinary office printer ready to be cut
• Photograph, identifiers and a scannable code come from the employee master, so the card says what the record says
• The layout is a print format like any other and can be tailored per tenant, with the shipped layout always behind it so a card can always be printed

The bill-of-materials lint run during change-order impact analysis failed on every change order. The guard around it caught the failure and reported the analysis unavailable, so nothing was ever wrong — but no approver had ever seen a lint finding. The findings are read correctly now.

The staged change presented to the approver rendered raw internal identifiers — which is exactly the screen on which knowing which material is being added matters. Each side of the change now carries its label alongside the underlying value, never in place of it, since the drift check and the release both read the value.

The change-order form could only modify or remove component lines that already existed. Adding one now has a panel of its own — material, quantity, unit, scrap, sequence, component and supply type, unit cost, currency and notes — with the material, unit and currency searchable rather than a dropdown nobody can scroll at master-data scale.

An addition is now checked when it is staged, not when it is released:

• A component needs a material, a quantity and a unit. A missing one used to surface as a database error inside the release, long after the person who could supply it had left the screen
• Only component lines can be added. Staging an addition against an operation component or a variant rule was accepted, approved, and then quietly did nothing
• A new line carries no currency across from an old row, so it inherits the structure’s currency at release — and where the structure has none either, staging refuses and names the way out

Opening a project’s WBS tab showed a “built using a trial version” banner, while every other grid in the application was fine. One grid component was pinned to a different release line from the rest and ended up loading a second, private copy of the shared library — the copy that never saw the licence being registered at startup. The licence itself was never the problem. All components now share one library and the banner is gone.

Saving a leave application from Employee Self-Service failed with CSRF Failed: CSRF token missing. The screen was calling the server directly instead of through the shared client that attaches the security token, so the page loaded perfectly and only the save broke.

A sweep of the whole application found the same defect on eight more modules with live saves — data access and user management, the organisation chart, expeditor letters, the MBA dashboard, sub-contracting, numbering sequences and web push notifications. All of them now go through the shared client, as do seven further read-only screens, so the fault cannot come back the moment a save is added to one of them.