AI Advisory for HLB Zambia
A ZRA-compliant copilot for VAT reconciliation and PBC list chasing, piloted with three SME clients, owned end to end by HLB.
Pilot cohort
Three SME clients
The pilot cohort for the first release of the copilot, chosen for how much of their admin load sits in VAT reconciliation and PBC chasing today.
Multi-branch retailer reconciling VAT across five tills a month by hand.
Seasonal import VAT and supplier invoices that rarely match the ZRA portal on the first pass.
Audit PBC items chased over WhatsApp and email, with no single owner or deadline.
Where the copilot works
Copilot drafts, CA signs off
Books vs. ZRA portal
The copilot ingests the client's bank statements, sales and purchase ledgers, and the ZRA portal export, then lines them up line by line. It flags missing invoices, timing differences and rate mismatches before a partner ever opens the file.
Outstanding items, chased automatically
Every open item on the Prepared-By-Client list gets an owner, a due date and an automatic follow-up over email, on a schedule the copilot manages, so the audit team stops manually tracking who owes what.
Built under NDA, on HLB's Azure tenant
HLB owns the client data, the client relationship and the revenue. The copilot is an internal tool, not a third party in the engagement. It is trained and hosted inside HLB's own Azure environment; no client data is sent to, or used to train, any external model provider.
Private by construction
Client financials stay inside HLB's Azure tenant end to end. Nothing is shared with, or used to train, third-party models.
Human in the loop
Every reconciliation and every PBC escalation the copilot produces is reviewed and signed off by an HLB CA before it reaches the client.
ZRA and BoZ aligned
Built directly against Zambia's tax code and reporting rules, not adapted from a generic, US-centric tax model.
Bound by NDA
Built and trained under a signed NDA for HLB specifically. Not a shared or resold product.
What changes for the client
Today's cadence is manual and reactive. Run through the copilot, the same engagement becomes fast enough to act on before ZRA penalties hit.
Who owns what
Owns the client data, the client relationship and the revenue. The copilot is HLB's tool, run inside HLB's engagement, not a third-party service the client is being onboarded to.
Builds and trains the copilot under NDA, on HLB's Azure tenant. No client data leaves HLB's environment at any stage of build, training or operation.
Natasha Zulu signs off every reconciliation and every PBC escalation before it reaches the client. The copilot proposes; the CA is the one who is accountable.