Prepare the reconciliation
Organize bank statements, ledger activity, opening and closing balances, and open differences for review.
Bookkeeping / close and client packs
The bookkeeping close is a review pack, not a download.
We build private workflows that prepare bank reconciliations, transaction categorization reviews, accrual lists, and client month-end packs. The workflow assembles the draft; the bookkeeper and the client's adviser approve the entries.
Reconciliation draftsCategorization reviewAccrual listsClient pack
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where close time goes
Every client close repeats the same assembly.
The bookkeeper collects statements, reviews transactions, checks balances, and turns the work into a pack the client can understand.
Review the categories
Surface transactions that are uncategorized, uncertain, or changed and group them for the bookkeeper.
Build the client pack
Assemble the month-end summary, open items, and questions into a pack for the bookkeeper and client.
The bookkeeping boundary
The system prepares the draft. The bookkeeper owns the books.
No automatic postings
The workflow prepares and groups entries. Approval and posting remain with the bookkeeper and the firm's process.
Advisers own the judgment
Classification, accounting treatment, and client advice stay with the bookkeeper and the client's qualified adviser.
Records stay attached
Every reconciliation and category draft remains linked to the statement or transaction that produced it.
A first bookkeeping workflow
Start with one client close.
Choose the client
Pick the client whose bank reconciliation or month-end pack the team rebuilds most.
Map the sources
List statements, ledger exports, approvals, and prior-month notes behind the close.
Run the draft
Prepare the reconciliation and categorization review, then flag open differences and questions.
Hand over the pack
Deliver the draft and client pack to the bookkeeper for approval, posting, and client review.
A client close is easier to finish when the statements, entries, and open questions stay together.
Why trust Pristine3D?
We build and operate production software.
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Common questions.
Does this post journal entries?
No. It prepares reconciliation and categorization drafts. Approval and posting stay with the bookkeeper.
Can it decide how to classify a transaction?
No. It surfaces candidates and questions. Classification and accounting judgment stay with the bookkeeper and adviser.
How is this different from the bookkeeper role page?
That page covers the bookkeeper's overall role. This page is the close workflow: reconciliation, categorization, and client pack.
Own your knowledge base
The model is not the product. The knowledge base is.
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with the client close
Which client close takes the team longest?
Tell us the client, the sources, and the review owner. We will scope a workflow around the firm's own close format.