Finance, Tax, and Accounting Control

Finance control starts before finance opens the report. A POS sale, sales invoice, purchase payment, stock receipt, credit note, and journal entry all create financial meaning as they happen.

That is why clean operational discipline matters. If the wrong item, customer, tax treatment, account, or payment reference is used upstream, finance inherits the cleanup downstream.

In practice, follow one customer invoice. While it is a draft, nothing is filed. The invoice itself makes its ledger postings, so finance never types a journal for it, and if your organization has connected KRA eTIMS under Settings → Connectors, it is filed the moment it is issued, whether or not it has been paid. If the customer has a valid KRA PIN in their VAT & Tax Settings, the filing goes out as business-to-business; without one it files as a consumer sale. Later, a credit note applied to that invoice raises the eTIMS reversal as well as the ledger correction. Nobody re-keys any of it, which is the point: a wrong customer, tax setting or item at entry time becomes a wrong figure in every report downstream.

Tax should not be guessed at invoice time. Global tax types, rates, workspace settings, customer VAT behavior, and item tax treatment should be configured before transactions start flowing.

Receivables and payables are also operational controls. Aging tells you which customers are dragging cash, which vendor commitments are coming due, and where a manager needs to intervene.

In practice, a month’s VAT work runs from VAT return under Accounting (/accounting/tax-returns). Choose the month and AWRA prepares output tax from issued invoices and till sales, input tax from approved supplier bills, and the net payable, with a line per document. Tie to the ledger compares those figures with the movement on Taxes Payable and Input Tax Recoverable; a difference is shown rather than netted away, and usually means a manual journal to a tax account or a document dated in one month and posted in another. Clear the exceptions, then Prepare and lock, which freezes the return and locks the period for tax. On the receivables side, Accounting → Aging shows which customers are drifting into older buckets, and overdue-invoice reminders can be sent from the same page.

A close routine is calm when exceptions are visible early. The work is not to make reports look tidy; it is to make sure the numbers are explainable from source records.

A practical close checks open approvals, unreconciled payments, unusual journals, unresolved inventory variances, outstanding receivables, and failed sync jobs before leadership relies on the reports.

In practice, open Accounting → Month-end Close and pick the month. The automatic checks are worked out every time the page loads: journals still in draft or awaiting approval, bank accounts not reconciled to month end, depreciation not run, petty cash vouchers awaiting approval, and whether the ledger balances. Below them are your own steps, each with an owner, a due day after month end and, if you want the order kept, a step it waits on. By default the checklist informs the close rather than blocking it: if items are open, the person closing says why in the notes. A workspace that wants the list to decide can switch on the close block under Settings → Accounting Defaults. Closing locks the month and stores a close evidence pack, and a month that needs changing afterwards goes through a reopen request rather than a quiet edit.