AI agents for business finance: what they can and can't do
What AI agents can do in bookkeeping, close, collections and compliance today, where a person must stay in charge, and how to judge a product.
The short answer
Break the project into stages that each end in something the client can test, such as approved designs, a working staging build or a production launch, and tie a payment to the acceptance of each. Write the acceptance test and the review period into the contract, keep each milestone small enough that you could absorb losing it, and agree whether Nigerian withholding tax is deducted from each payment.
Software and design projects for Nigerian startups, banks and agencies often run for months. Paying everything at the end puts all the risk on you; paying everything upfront puts it on the client. Milestones share it: each stage is paid when it is delivered and accepted. The trick is defining milestones the client can actually test, and acceptance rules that do not let a milestone drift for weeks. This guide shows how, with a labelled example.
What makes a good milestone
- It ends in a deliverable the client can see or use: a design file, a staging link, a released build.
- It has an acceptance test written in advance, for example a list of user stories that must work.
- It has a review period, such as five working days, after which it is treated as accepted unless the client lists specific defects.
- It is small enough that non-payment would hurt but not sink you.
- It does not depend on things outside your control, such as the client's third-party integrations, without saying so.
A labelled example for a mobile app
Example only. A fintech client agrees a $20,000 fixed-price build. You propose:
| Milestone | Deliverable | Acceptance | Payment |
|---|---|---|---|
| 0. Start | Signed contract | On signing | 20%, $4,000 |
| 1. Design | Approved screens and clickable prototype | Client sign-off or 5 working days with no defects listed | 20%, $4,000 |
| 2. Beta | Staging build with agreed features | Agreed test list passes | 30%, $6,000 |
| 3. Launch | App submitted to stores and backend in production | Store submission and handover | 20%, $4,000 |
| 4. Warranty | 30 days of bug fixes | End of warranty period | 10%, $2,000 |
The payments add up to $20,000 (4,000 + 4,000 + 6,000 + 4,000 + 2,000). If the client deducts Nigerian withholding tax at 10%, the rate PwC gives for professional fees paid to non-residents (reviewed 29 May 2026), you receive $18,000 in total with receipts for $2,000, unless you agreed a net price. BusinessDay's explainer on the 2024 regulations notes the obligation arises on payment, so expect a deduction at each milestone, and ask for each receipt.
Acceptance: where milestone deals go wrong
Most milestone disputes are about acceptance, not price. Avoid vague tests such as "to the client's satisfaction". Use a list of features or user stories, agreed at the design stage, and a rule for defects: critical defects block acceptance, minor ones go on a fix list without holding payment. If the client adds features, treat them as a change request with its own price and time.
Fixed price or time and materials
Milestones work best on fixed-price projects where the scope is clear. If the client cannot yet say exactly what it wants, a fixed price invites disputes. An alternative is time and materials with milestones used as checkpoints: you bill hours or days each fortnight against a budget, and each checkpoint is a moment to agree what comes next. Many projects start with a short, paid discovery milestone that produces the specification, and then switch to fixed-price milestones for the build once both sides know what is being built.
Retention and warranty
Clients sometimes ask to hold back part of the fee until after launch, as in the 10% warranty line in the example. That is reasonable if the warranty is defined: a fixed period, covering defects in what was delivered, not new features, and ending with automatic release of the retention. Without those limits, a retention can turn into an open-ended support obligation that is never quite finished.
Third-party dependencies
Nigerian fintech and commerce projects often depend on outside services such as payment gateways, identity checks or banking APIs that the client must arrange. Say in the contract that delays in the client's third-party access move the milestone dates, and that a milestone is accepted on the basis of what you control if the outside service is unavailable for reasons outside your work.
Timing and payment terms
- Invoice each milestone on acceptance, not at month end.
- Set a due date, such as 14 days from invoice.
- Say work on the next milestone starts once the previous payment is received.
- State the currency and whether exchange-rate changes affect later milestones; see FX clauses.
- Keep ownership of code until each milestone is paid; see IP assignment.
If payments slip, the contract's pause right is your strongest tool; for chasing from abroad, see chasing late payment. The Nigeria library covers the same structure from the side of freelancers billing foreign clients, in deposits and milestones.
Where Pryme fits
Raise each milestone invoice from Pryme invoicing and receive payment in naira or a foreign currency into a Pryme Business Account. The Finance agent prepares invoice drafts and payment reminders, and you approve before anything is sent.
Questions people ask
How should I split payments on a software project?
Tie payments to testable stages, such as design, beta, launch and warranty, with an upfront payment on signing.
What if the client never signs off a milestone?
Write a review period into the contract, after which the milestone is accepted unless specific defects are listed.
Does withholding tax apply to each milestone?
Usually yes, if the client is a Nigerian company. The obligation arises on payment; PwC gives 10% for professional fees paid to non-residents.
Should I keep working if a milestone payment is late?
Your contract should let you pause until it is paid. Without that clause, you risk building the rest unpaid.
Sources
- PwC Worldwide Tax Summaries: Nigeria, corporate withholding taxes (reviewed 29 May 2026) · accessed Oct 2026
- BusinessDay: Nigeria's withholding tax reforms, key changes and implications (11 Jul 2024) · accessed Oct 2026
- Mondaq (Danol Partners): Overview of the Deduction of Tax at Source (Withholding) Regulations 2024 (16 Oct 2024) · accessed Oct 2026
This article is general information, not financial, legal or tax advice. Products described are provided under the terms on this site and are subject to regulation and eligibility.