What we shipped, in plain language.

The upload took the first sheet in the workbook, blindly. One real file carried fourteen sheets and position one held a TA sheet for a different, earlier order — which parsed perfectly and named a project that was not the one being uploaded. Sheets are now scored on whether they name a project, carry a planned start date and hold task rows; the best one wins, every task sheet found is offered, and an explicit choice still overrides. A workbook with no task sheet at all is refused by name instead of falling back to sheet one.

The header block was read only below the column headings, only from rows carrying a particular flag, and only from the end-date column. Real files do none of those three reliably, so the whole grid is scanned now, in any column. Labels are matched exactly, then as a phrase inside a longer cell, then by close spelling — and a column heading can never be mistaken for a header label, which is what previously turned the heading row into data and the first task into a heading.

The first heading row is not always the complete one: in that file only the second row named Employee ID and Employee Name, so every task imported unassigned. Columns the first row omits are now filled in from a later one, and columns it does name are never overridden.

When a value really is missing, the message now names what the pass did read and lists the cells it could not match, with their references — so a sheet the parser does not recognise stops looking like a blank cell.

Both AR invoice screens now show the customer’s open advances and offer to adjust them. They prompt; they never knock an advance off automatically — which invoice an advance belongs to is a judgement, not a lookup.

Administrators: after upgrading, run batch_migrate --app fi_ar and setup_rbac, then configure a GST advance account per company. Issuing a voucher refuses by name without a tax-on-advances account.

Tax on an advance is due in the month the money lands, reported in GSTR-1 Table 11A, and reversed at Table 11B when the tax invoice finally goes out. There was no document for it.

The voucher is an overlay on the customer receipt, not a second cash document. The receipt already owns the bank leg, the ledger, the reconciliation and the reversal engine, and a parallel document would fork all of them. A receipt already applied to invoices is refused by name — that supply is taxed on its invoice — as is a foreign-currency receipt, because GST is a rupee liability and nothing here gets to pick the conversion rate.

The amount received is always tax-inclusive, so the tax is the subtraction of taxable value from gross, never a rate applied forward. Computed forward off a rounded taxable value, the columns fail to add up by a paisa on roughly half of all amounts — and a statutory document whose own columns do not add up is not defensible.

The tax posts as its own journal, so a receipt with no voucher posts exactly the two legs it always did. Adjustment resolves the invoice rather than trusting the reference it was handed: an id naming nothing, another customer’s invoice or a draft is a bad filed return.

Where the rate cannot be determined the law says 18%; where the place of supply cannot be determined it says treat the supply as inter-State. Both are applied — and both are recorded as fallbacks on the voucher, because a default nobody can see is indistinguishable from a decision, and whoever prepares GSTR-1 has to know which Table 11A rows to revisit before filing. A tenant-configured default tax code is not flagged: the tenant chose it.

Rule 49 caps the voucher serial at sixteen characters, so an over-long numbering pattern is refused rather than truncated into a collision.

The delivery detail page switches to the colour and size matrix as soon as any item on the note has a variant, and then sends every line to it. A line with no variant matched no cell: it rendered nowhere, could not be edited, and was absent from the grand total — while the header, which sums every item, still counted it. One note read 7,738 in the header and 2,515 in the grid.

Items are now placed through a map that consumes each item exactly once. Whatever cannot be placed — no variant, a missing row or column attribute, or a second line landing on a cell another line already holds — is collected and shown below the grid in a flagged, editable table with its own subtotal, plus a combined product total.

The page also gained a Lines total chip summing every item including unsaved edits, and shows an amber Header says… chip when the two disagree, so a mismatch is visible rather than silent.

A help-documentation seed named a field that lives on a different record, and the chart-of-accounts seed checked for an existing chart by its filing type — which misses a tenant whose chart is filed under an older type code, and then collided with the accounts that tenant already owned.

The chart seed now works out every code it would write and stops if any of them already exists, which is what it always claimed to do. Neither change touches an existing row.

The employment application and job request forms take their second language from the applicant’s mother tongue. Gujarati was selectable as a mother tongue but held no labels, and an unheld language falls back to the default — so a Gujarati applicant was handed the Tamil form and nothing reported it.

The form embeds the typeface it asks for, so the Gujarati face ships with it. Without that the form prints correctly on a developer’s machine and renders every second line blank on the print server. A test now asserts that every language in the catalogue has its face on disk, rather than leaving that to be discovered on paper.

The adjustment entry that carries the difference between what the timers logged and the total a supervisor states now stores whether it adds or removes time, rather than leaving that to be inferred from the figures around it.

A new scheduled report sends each person their own timesheet for the day: the tasks they worked, the hours booked against each, and what remains open. It is a real schedule like any other report — it can be re-timed, paused or removed.

Its audience comes from the data, not the schedule: whoever booked time that day is who receives a mail, so nobody has to be added to a recipient list when they join and nobody keeps receiving an empty sheet when they leave.

A marker is now linked to the production orders it is being cut for, with each order’s own quantities visible while the marker is planned. The marker form and list were rebuilt around that link, and production planning answers the order and quantity lookups the form needs.

The Leads grid fetched the whole table and then paged, sorted and searched it in the browser, so the wait to open the screen grew with every lead ever created. Paging, sorting, searching and column filters are now answered by the server, and the screen opens as quickly on the thousandth lead as on the first.

The task list shares the change, and both grids keep their Excel export over the whole result set rather than the page on screen.

The posting service looked for a wage type code that no catalogue has ever contained, so the balancing net-pay leg could never be mapped however carefully the mapping table was filled in. It now reads 9920 Net Pay, which has been in the standard catalogue since the payroll engine shipped.

Creating a second wage type meaning “net pay” would have left two codes for one concept and an even chance of an operator mapping the wrong one.

A GL mapping takes effect from the day it is created, so a mapping added while closing last month’s payroll is dated after the period end and is correctly filtered out — but the refusal then said the wage type was not mapped while the operator was looking straight at the mapping they had just saved.

The message now names the effective window and says to widen it, rather than inviting a second mapping row that will not help either.

The chart of accounts came only from a command run by hand per tenant, and three production tenants had never had it run — which blocks GL account creation outright, because an account has to hang off a chart. The deploy now seeds it.

It seeds only into an empty chart. The shipped template is not the only chart in use, codes collide across standards, and renumbering a chart that already carries posted journals is a supervised act — not something a deploy may do behind the operator’s back.

The net-pay credit leg had no check on it at all. Where no net-pay account was configured the leg was simply left out — and because payroll writes its journal as already posted, the ledger accepted an unbalanced entry marked POSTED with no error raised anywhere. A missing net-pay mapping is now refused by name before anything is written.

A wage type with no GL account mapped against it was skipped, with a line in the server log and nothing on the screen. It did not even show up as an imbalance: the salary-payable credit is derived from the debits, so dropping an earning shrank the credit to match. The journal balanced perfectly while posting less salary expense than the run actually paid — the worst shape a defect can take, because everything downstream reconciles.

Posting now refuses, and the message lists every unmapped wage type with its amount in one go, so the mapping table is completed in a single pass rather than one refusal at a time. The refusal comes back as a plain validation message with the remedy in it, not a server error.

The posting wrapped its writes in a transaction opened on the wrong database connection, so on a tenant it was effectively running unwrapped. A failure part way through left the journal committed while the payroll run stayed Approved and no posting record was written — a general ledger entry that no payroll document admitted to.

The posting is now one transaction on the tenant’s own connection: it either completes in full or leaves nothing behind.