The work that eats your month is not judgment. It is matching.
Qualified people spend their weeks tying one list to another, chasing documents that already exist somewhere, and rebuilding files that will be rebuilt again next month. None of it requires a professional opinion, and all of it has to be right.
- Written for
- Controllers, tax leads, company secretaries, finance managers
- What changes
- Matching and chasing move to the system
- What does not
- Judgment stays with the person who signs
What each seat gains, and what it stops carrying.
Controller
Gains
A trial balance that is already in presentation form, control accounts that agree continuously, and a close calendar where every step has a named reviewer.
Stops carrying
Rebuilding the regrouping sheet and defending numbers that changed between drafts.
Tax lead
Gains
GSTR-2B matched line by line, ITC eligibility tested at entry, TDS sections applied at bill stage, and a filing calendar per registration with acknowledgements captured.
Stops carrying
Monthly matching in a workbook and reconciling 26AS against the deduction register by hand.
Company secretary
Gains
Statutory registers maintained as events occur, related-party approvals in sequence with their resolutions, and charge and director filings tracked to acknowledgement.
Stops carrying
Assembling the related-party list from memory and back-filling registers before an audit.
Finance manager
Gains
Ageing that matches the disclosure format, MSME exposure visible before the 45-day window closes, and vendor and customer queries answered from the record.
Stops carrying
Chasing documents across mail threads to prove what was already approved.
Same team, same volume, same standards. Different order of work.
The hours do not disappear. They move from reconstructing the position to deciding what the position should be.
- Week 1
Prior month's entries still being passed. Bank reconciliation reopened because two entries were back-dated.
- Week 2
GST matching in a workbook. Supplier invoices missing from 2B chased over mail with no register of who was asked.
- Week 3
TDS challans reconciled against the deduction register manually. Two lower-deduction certificates found expired.
- Week 4
Management reporting assembled, then adjusted twice as late entries land. Nothing is locked, so nothing is final.
- Week 1
Prior month is locked. Reopening requires an approval that is recorded, so back-dating is an exception with a name on it.
- Week 2
2B differences already listed with the invoice, the supplier and the follow-up status. The work is deciding, not finding.
- Week 3
TDS position reconciled continuously. Certificate limits and expiry were flagged before the bill was passed.
- Week 4
Reporting is a read of a locked period. Time goes to the two or three positions that actually need a view.
Control that does not depend on anyone being diligent that week.
Every one of these is a system behaviour rather than a policy document, which is the only reason it survives a busy quarter.
Maker and checker, with limits that are versioned
Every transaction has a preparer and an approver, and the approval is judged against the authority limit in force on that date. When limits change, history is not rewritten.
A period lock that actually holds
A period cannot be locked while a control account is unreconciled or a mandatory sign-off is open. Once locked, reopening is an approved, logged event rather than a quiet edit.
A query register instead of an inbox
Auditor and internal queries are raised in the system against the entry in question, and the response is filed against the query - so nothing is settled verbally and lost.
Escalation before the date, not after
Obligations escalate on a lead time you set, to the person who owns them. Missing a filing requires two people to ignore two notices, which is a different failure from nobody knowing.
Work that goes away entirely.
- Monthly GST matching in a spreadsheet
- 26AS reconciliation against the deduction register by hand
- Collecting vouchers for an audit sample
- Rebuilding ageing reports in the auditor's preferred format
- Reconstructing who approved a payment, from mail
- Typing up statutory registers before a filing
Work only your team can do.
- Deciding the ECL overlay, not computing the staging
- Taking a position on a disputed treatment and documenting the reasoning
- Negotiating credit terms with the ageing actually in front of you
- Reviewing exceptions the system raised, rather than hunting for them
- Preparing the audit committee with a position you can stand behind
- Planning the tax position for the year instead of reacting to a notice
Where the mechanics are described.
Tax & Regulatory Filing
How returns are built from documents and how the calendar assigns ownership.
Audit Trail & Documentation
What the edit log records, and how an audit sample pack is produced.
What each tier includes
Where the line sits between a single entity and a multi-entity group.
Show us your last close, and we will show you which parts the system takes.
Bring the files you actually maintain - the matching workbook, the calendar, the ageing sheet. We will map each one to where it lives in Profinlex, and be straight about anything that stays manual.
- Your close calendar, with owners and reviewers configured
- One month of matching run against your own data structure
- A clear list of what remains a judgment call