Expense Management captures spend through every channel an employee actually uses: a photographed receipt, a forwarded supplier email, a mileage journey, a per diem allowance or a transaction that arrives directly on a corporate card feed. Receipt images and PDFs pass through optical character recognition and structured extraction, so a claim line arrives pre populated with merchant, date, gross amount, tax and currency rather than as a blank form. Spend booked in any currency is converted at controlled rates, with the original and the reimbursable amount both retained on the line.

Around capture sit the controls that make the module a system of authority and not merely a logging tool. Policy is enforced at the point of entry and again at approval: spending limits, receipt thresholds, permitted categories, mileage schemes and per diem entitlements are all evaluated automatically. Corporate card transactions are matched to submitted receipts and reconciled against the card statement, so unmatched charges and personal spend are surfaced rather than lost. Approved claims flow to reimbursement and to the ledger without rekeying, closing the loop from capture to payment.

The heart of the module is the expense claim, a container that gathers individual spend lines for a single person over a period or a trip and carries them as a unit through review, approval and settlement. Each line records what was bought, when, in which currency, against which spending category, and how the cost should be coded for accounting and analysis. A claim always resolves to a person, and that person is not maintained here: identity, grade, cost centre, home country and reporting line are drawn from the shared employee record, so entitlements and approval routes reflect the organisation as it actually stands.

Sitting behind every line is policy, expressed as effective dated rules and rate tables. A rule is never global in a way that ignores context: it is scoped by category, by grade and by country, so a mileage rate, a meal allowance or a hotel ceiling can differ for a senior engineer in one territory and a graduate in another, and can change on a stated date without disturbing claims already settled under the previous version. The third concept is coding, the bridge between a business reason for spend and its financial destination: each line carries the account, the cost centre and, where relevant, the project or client to which it belongs, which is what allows the same claim to satisfy both the general ledger and project profitability at once.

The everyday workflow begins with the claimant. An employee assembles a claim from captured receipts, card transactions and mileage entries, sees policy feedback as they go, and submits. Validation that would otherwise fall to a manager, missing receipts, duplicate charges, out of policy amounts, is already resolved or flagged before anyone else sees the claim.

Submitted claims enter an approval workflow routed on the organisation's own structure. Routing follows the reporting line and, where spend is coded to a project or a cost centre owned by someone other than the line manager, brings that budget holder in as an additional approver. Thresholds decide how many approval steps a claim needs and whether finance review is required, so low value in policy claims clear quickly while material or exceptional spend receives scrutiny. Approvers act on a clear view of each line, its receipt and its policy status, and can query, partially approve or reject with a reason that returns to the claimant.

Once authorised, the claim splits cleanly by settlement route. Amounts an employee paid personally are queued for reimbursement through payroll or payment, while amounts already settled on a corporate card are cleared against the card liability rather than paid a second time. Corporate card reconciliation runs continuously, matching feed transactions to claim lines and ageing anything unmatched so cardholders and administrators can close it out.

The module's depth shows in how precisely it treats tax, currency and accounting. Recoverable tax is separated on each line according to the rules of the jurisdiction in which the spend occurred, so the reclaimable portion of, say, hotel or fuel tax is isolated and posted to the correct control, while irrecoverable elements stay with the cost. Where a per diem or mileage scheme carries a taxable component above an approved rate, that component is identified for onward payroll and benefit reporting rather than quietly absorbed.

Reimbursement and card clearing post through double-entry accounting: a personally funded claim raises an employee liability that the reimbursement later discharges, while card settled spend clears the card control that the statement already created. Multi currency lines hold both transaction and functional amounts, and any difference on settlement is recognised as exchange gain or loss rather than distorting the expense itself. Mileage is calculated from distance and the effective scheme rate, per diems from entitlement and elapsed time against the applicable allowance.

Control is continuous rather than a final gate. Segregation between claimant, approver and payer is enforced, duplicate detection runs across both receipts and card lines, and every state change, edit, approval and rate applied is written to an immutable audit trail. Receipts and their extracted data are retained to satisfy tax authority and audit requirements for the statutory period.

Expense Management is a native part of Nashua 360 and draws its authority from the surrounding modules rather than duplicating them. Accounting & Control is its financial destination: approved claims post as journals to the general ledger, employee liabilities and card controls are maintained there, reimbursement runs are settled through it, and recoverable tax lands in the same tax accounts the rest of the suite uses. Nothing is exported or reconciled by hand.

Human Resource Management supplies the employee master: who a person is, their grade, cost centre, country and manager, which is what makes policy scoping and approval routing correct without a parallel directory to maintain. Joiners, leavers and moves are reflected automatically, so entitlements and routes never drift from reality.

Project Management receives spend coded to projects and client work, so travel and expenses booked against an engagement flow into its cost and profitability picture at the moment they are approved. A consultant's flight or a site visit appears in project margin without a separate re entry. Because all three integrations share one data core, a single expense line can serve the ledger, the employee's record and the project account simultaneously, which is what keeps expense reporting, cost recovery and budget control consistent across the organisation.

AI Workers operate inside Expense Management as first class participants, not as a bolt on assistant. They read and act on module data under the same policies and permissions as any user. Conversational query lets a manager or finance lead ask, in plain language, what is outstanding for approval, how travel spend compares to the same period last year, or which claims breach a given category ceiling, and receive an answer drawn live from the module rather than a static report.

Much of the routine handling is done by AI Workers directly. They extract structured line data from receipts and supplier emails, propose categorisation and coding, and match card transactions to claims, escalating only the exceptions. They watch continuously for anomalies: duplicate submissions, receipts that do not match a card charge, spend that clusters just under an approval threshold, out of pattern mileage, and raise these as alerts with the supporting evidence attached.

An AI Worker can also stand as a node in the approval and review workflow. Configured to a defined authority, it clears low value, fully in policy claims automatically, holds and questions those that are not, and records its reasoning in the same audit trail as a human decision. In every case it offers decision support, surfacing the policy, the history and the coding an approver needs, while a person retains authority over anything material or contested.