A.01 Internal financial process review

See where your accounting controls break before a reviewer does.

A fixed-scope review of accounting controls, financial documentation and operational reporting for Ukrainian businesses, issued as a workpaper dossier.

This is an internal process and controls review, not a statutory audit. A written scope note follows within two working days.

A.02 / Scope boundary

Scope and exclusions

Four process areas in, four boundaries out. Agreed in writing before fieldwork starts.

Status reflects coverage agreed at the scope call. Exclusions are listed per row and repeated in the scope note.
Process area Status Explicit exclusion
Revenue and receivables In scope Statutory tax filings and VAT returns
Procurement and payables In scope Legal review of supplier contracts
Inventory and cost of sales Partial Physical count attendance outside Kyiv
Payroll and reporting pack In scope Individual employment law advice

Not part of the engagement

  • A statutory audit opinion or any assurance statement issued under ISA.
  • Legal opinions on contracts, employment terms or disputes.
  • IT security testing, access reviews or penetration work.
  • Valuation of assets, inventory or shareholdings.

The one-page scope note is issued within two working days of the scope call.

A.02

Control coverage matrix

Which process areas get documented, tested, and reported on inside the fixed scope.

Six process areas, three evidence columns. Each status marker shows what the review can evidence today and what stays open when the file is handed over.

Coverage by process area as agreed on the scope call.
Process area Documentation Control test Reporting gap Status
Procure to pay Vendor invoices, purchase orders, goods receipt records Three-way match and approval limit testing Supplier aging not reconciled monthly Gap
Revenue and receivables Contracts, issued invoices, bank statements Cut-off testing and credit note review No deferred revenue schedule Gap
Payroll Employment contracts, timesheets, payroll registers Approval trail and register to payment reconciliation Headcount not tied back to the register Tested
Inventory and cost of sales Warehouse records, count sheets, cost allocations Count variance follow-up and costing method check Variance note missing at month end Open
Cash and banking Bank statements, payment approvals, payment run logs Two-signatory check and unmatched receipt tracing Payment run log kept incomplete Open
Month-end close Close checklist, journal log, review sign-offs Journal approval and review evidence testing Close calendar not version controlled Gap

Sample size per area runs from 25 to 40 transactions, traced from primary document to ledger to the reported figure and weighted toward high-value and period-end items. Three of the six areas above sit below the documentation standard we would sign off on.

A.03 / Evidence

Evidence checklist

What we ask for before fieldwork begins, and how much of it we actually test.

Evidence types and sampling quantities per process area

Ref Evidence type Format Sample
E-01 Primary documents: invoices, acts, bank statements PDF exports from the accounting system 25-40 transactions
E-02 Ledger extracts: trial balance and general ledger detail XLSX or CSV, unedited Full period
E-03 Reporting packs: management accounts, KPI sheets Final issued version plus draft 3 reporting cycles
E-04 Control evidence: approval trails, access and duty matrix System screenshots with date stamps All listed controls
E-05 Period-end procedures: accruals, reconciliations, cut-off Signed working files 2 closing periods
  • Rule 01Samples skew to high-value and period-end transactions, not a random draw.
  • Rule 02Each item is traced from primary document to ledger to reported figure.
  • Rule 03Missing or reconstructed documents are logged as exceptions, not chased indefinitely.

Sample sizes are fixed in the written scope note. Book the scope call.

A.04

Sample findings

One worked example of the Evidence, Observation, Recommendation format, plus a short extract from a live exception log.

EX-07 · Supplier invoice approval, procurement

Evidence

From 32 supplier invoices posted between January and June, 9 were released for payment without a documented second approval. In 4 of those 9, the invoice date preceded the purchase order by more than five working days.

Observation

The approval threshold is written into the finance policy but not enforced in the accounting system, so release depends on individual judgement. No exception report reaches the controller for review.

Recommendation

Make the second approval field mandatory above the UAH threshold and add a monthly exception report listing every invoice released without one. Target completion is one reporting cycle.

Exception log extract

Severity bands run high, medium and low. Status records the position agreed at the closing meeting.
RefProcess areaConditionSeverityStatus
EX-07ProcurementSecond approval not evidenced above thresholdHighException
EX-11RevenueCut-off tested on 28 invoices, 2 posted in the wrong periodMediumException
EX-14PayrollReconciliation prepared but never reviewed or signedMediumOpen
EX-18InventoryCount sheets retained and agreed to the ledgerNonePass

Every entry is agreed with management before the closing meeting, so the log records accepted exceptions rather than open disputes. Items resolved during fieldwork are closed and listed separately. Book the scope call to see the log built for your process areas.

A.05 / Engagement timeline

30 / 60 / 90-day remediation roadmap

Three dated blocks. Each closes only when a named owner signs the acceptance test.

  1. Weeks 1-4 / Days 1-30

    Exception triage and ownership

    Owner Finance Controller

    Every line in the exception log receives a severity band, a named owner and a target date. Period-end journals are re-routed through one preparer and one reviewer.

  2. Weeks 5-9 / Days 31-60

    Documentation repair and control redesign

    Owner Chief Accountant

    Primary documents are matched to ledger entries and reported figures. Missing approvals, split invoices and manual reclassifications are rebuilt as written control steps.

  3. Weeks 10-13 / Days 61-90

    Retest and reporting pack

    Owner Internal Control Lead

    The coverage matrix is retested on a fresh sample and the monthly reporting procedure is handed over with the exception log showing closed, open and deferred items.

A control closes only when the sample of 25 to 40 transactions retraces cleanly.

Book the scope call
A.06 Closing band Boundary restated, scope call routed.

The boundary holds from first call to final log

This engagement reviews accounting controls, financial documentation and operational reporting procedures. It is not a statutory audit, not a tax filing, and not a legal opinion. Scope is fixed in writing before fieldwork starts.

A one-page scope note follows within two working days of the call.