Accounting Software Integration in Nigeria: Getting Sales, Payments and Books in Step
Ask most Nigerian business owners when they last saw an accurate profit figure and the honest answer is "after the accountant finishes, some weeks later". That lag is rarely a skills problem. It is that sales sit in one system, payments in another, stock in a third, and somebody has to bring them together by hand before anything can be posted.
Integration removes that gap. The work is less about accounting software features and more about agreeing how each business event should appear in the books, then making the systems send it that way automatically. This guide covers which connections repay the cost, the chart-of-accounts mapping that decides whether the project succeeds, Nigerian specifics from VAT to cash sales, and what it costs.
What accounting software integration actually means
Accounting packages are designed to receive transactions, not to chase them. Integration builds the pipes that deliver those transactions in the right shape, at the right time, with enough detail to be useful and not so much that the ledger becomes unreadable.
Every accounting integration answers four questions for each type of event:
- What triggers a posting? A completed order, a confirmed payment, a delivery, a payroll run, a stock movement.
- What level of detail posts? Every line of every sale, or a daily summary per product group. Retailers almost always want summaries; project businesses usually want detail.
- Which accounts are affected? Revenue, VAT payable, receivables, bank, cost of sales, fees.
- What happens when it fails? A rejected posting must be visible and fixable, not silently dropped.
That last point deserves emphasis. An integration that quietly fails to post three days of sales is worse than no integration, because the books look complete and are not.
The connections that pay for themselves
| Connection | What posts automatically | Who benefits most |
|---|---|---|
| Payment gateway | Collections, provider fees, settlements to bank | Any business taking online payments |
| Point of sale | Daily sales summaries, VAT, cash and card splits | Retail, pharmacy, restaurants, supermarkets |
| Online store | Orders, refunds, delivery charges | E-commerce and multi-channel sellers |
| Invoicing or CRM | Sales invoices, receipts, customer balances | Service firms, B2B suppliers, agencies |
| Bank statements | Imported transactions for reconciliation | Everyone, particularly transfer-heavy businesses |
| Payroll | Salary, deductions and employer costs by department | Businesses above roughly 10 staff |
| Inventory or warehouse | Stock movements, cost of sales, adjustments | Distributors, manufacturers, retailers |
| Expenses and petty cash | Staff claims and approvals into the ledger | Multi-site and field-based operations |
If you can only afford two connections, choose the payment gateway and whichever system generates your sales. Those two produce most of the month-end work and most of the arguments about what was actually collected.
Chart of accounts mapping: where projects succeed or fail
Before anything is built, someone who understands your books must map each business event to an accounting treatment. This is a two-hour conversation that prevents a two-month mess.
A workable mapping table looks like this, and should be agreed in writing with your accountant:
| Business event | Debit | Credit | Notes |
|---|---|---|---|
| Online sale, paid by card | Gateway receivable | Sales revenue and VAT payable | Post net of nothing; fees posted separately |
| Gateway settlement to bank | Bank | Gateway receivable | Difference posts to transaction fees |
| Cash sale at the counter | Cash | Sales revenue and VAT payable | Daily summary per till |
| Customer transfer to virtual account | Bank or clearing | Customer receivable | Matched by reference |
| Refund | Sales revenue and VAT payable | Bank or gateway | Keep reason codes for reporting |
| Stock received | Inventory | Supplier payable | Costing method must match policy |
Three rules keep mappings sane. Post fees separately rather than netting them off revenue, so you can see what collection actually costs. Use a clearing account for money in transit between the gateway and the bank, so timing differences do not look like missing money. And agree the level of summary before go-live, because changing it later means reposting history.
Native connector, middleware or custom build?
| Option | How it works | Best when | Watch out for |
|---|---|---|---|
| Native connector or app | The vendor's own integration or marketplace app | Both systems are mainstream products | Limited mapping control, dollar subscription |
| Middleware or iPaaS | A third tool routes and transforms data | Several systems, frequent changes | Recurring cost, another dependency |
| Custom integration | Code written against both APIs | Custom or local systems, unusual rules | Needs documentation and a support plan |
| Scheduled file exchange | Exports imported on a timetable | Older software with no API | Manual failure points, slower feedback |
Many Nigerian businesses end up with a mix: a native connector for the payment gateway, a custom job for a locally built inventory system, and a file import for a legacy branch package. That is acceptable as long as each route is documented and monitored.
How an accounting integration project runs, step by step
The core sequence is: agree the mapping with your accountant, choose the connection route per system, build in a test company file, run parallel, then reconcile and hand over.
- Freeze a clean starting point. Agree an opening balance date with your accountant so you are not integrating into a ledger that is already out of balance.
- Document the mapping. Every event type, its accounts, its tax treatment and its summary level.
- Choose the route for each system. Native connector, middleware, custom or file exchange, based on the table above.
- Build into a test or sandbox company. Never test postings in the live ledger.
- Post a full sample period. Take a representative week, ideally including a refund, a part payment, a cash sale and a stock adjustment.
- Reconcile the sample manually. Your accountant compares the automated postings with what they would have done. Fix differences before going further.
- Run parallel for one cycle. Keep the manual process for a week or a month alongside the automation, comparing totals daily.
- Turn on monitoring. Alerts for failed postings, a visible queue of items that did not post, and a named person who checks it.
- Switch over and retire the manual route. Remove the duplicate spreadsheet so two versions of the truth cannot develop.
- Review at the first month-end. Time taken to close, number of unmatched items, and whether management figures arrive earlier.
What changes for Nigerian businesses
- Cash is still material. Many businesses take a meaningful share of revenue in cash. Integration must include a till reconciliation step, not assume every sale carries a digital trail.
- Transfers dominate B2B payments. Without unique references or dedicated virtual accounts, transfers cannot be matched automatically. Fixing the reference discipline is often a prerequisite to the integration, not a part of it.
- Bank feeds are limited. Automatic bank feeds into accounting software are not universally available across Nigerian banks. Many businesses rely on statement imports or an aggregator. Confirm what your bank and package support before designing the reconciliation flow.
- VAT and tax reporting. VAT treatment must be built into the mapping from the start, including exempt and zero-rated items where applicable. The Federal Inland Revenue Service has been introducing electronic invoicing and digital reporting requirements, and applicability and timelines vary by taxpayer category, so confirm your current obligations with FIRS or your tax adviser rather than assuming.
- Multi-currency exposure. Businesses with dollar costs (hosting, software subscriptions, imports) need a policy for exchange rates at posting and at settlement, agreed with the accountant, so gains and losses are visible rather than buried.
- Branches with poor connectivity. Outlets that lose internet need local capture with queued synchronisation, and a check that nothing was lost when the link returns.
- Data protection and access. Financial records contain personal data about customers and staff. Restrict access by role, keep an audit trail, and verify current obligations under the Nigeria Data Protection Act 2023 with the Nigeria Data Protection Commission.
Example (hypothetical): a Lagos pharmacy chain
Example (hypothetical): a pharmacy chain with four branches in Lagos runs a point-of-sale system in each shop, accepts cash, card and transfer, buys from about forty suppliers, and keeps its books in a cloud accounting package. At month-end the accountant collects Z-reports from each branch, a gateway statement, bank statements and a stock spreadsheet, then posts summaries by hand. Closing takes about two weeks, and stock losses are only discovered during a quarterly count.
The chain integrates in three steps. First, each branch posts a daily sales summary into accounting, split by payment method and VAT status, with cash lodgements matched to bank deposits through a clearing account. Second, the payment gateway posts collections, fees and settlements, so card and transfer income reconciles without a spreadsheet. Third, purchase orders and goods received post to inventory and supplier payables, with cost of sales recognised from the point-of-sale movement.
The expected effect, from the design rather than a claimed result, is that the accountant's month-end becomes review rather than data entry, unexplained stock differences surface weekly instead of quarterly, and the owner can compare branch margins before the month is over. On the indicative bands below, this sits in the ₦2,500,000–₦6,000,000 range plus subscriptions and monthly support.
How much does accounting software integration cost in Nigeria?
Price depends on how many systems post into the ledger, how standard those systems are, the number of branches, and how much clean-up the existing books need first. The figures below are indicative 2026 ranges; actual quotes vary with scope, vendor and exchange rate. Accounting package subscriptions are usually billed per user per month in US dollars.
| Scope | One-off build (indicative) | Recurring (indicative) |
|---|---|---|
| One connection using a native connector, configured properly | ₦150,000–₦600,000 | Package and connector subscriptions |
| Payment gateway to accounting with fees and settlements | ₦400,000–₦1,500,000 | Subscriptions, support |
| Point of sale to accounting, single site | ₦600,000–₦2,000,000 | Subscriptions, support |
| Multi-branch point of sale with clearing accounts | ₦2,000,000–₦6,000,000 | Subscriptions, hosting, support |
| Inventory and purchasing into the ledger | ₦1,500,000–₦5,000,000 | Subscriptions, support |
| Payroll posting by department | ₦500,000–₦2,000,000 | Payroll subscription, support |
| Books clean-up and opening balance preparation | ₦200,000–₦1,000,000 | None once complete |
Ask each vendor to quote against the same mapping document, and to state clearly who is responsible for the accounting treatment: the integrator builds the pipes, but your accountant must own the treatment. Support should cover failed postings and changes when a provider updates its interface.
Mistakes to avoid
- Building before the mapping is agreed. Reposting a month of incorrectly coded transactions is more expensive than the conversation that would have prevented it.
- Netting fees off revenue. It hides the true cost of collection and makes gateway reconciliation harder.
- No clearing account. Money that has left the gateway but not reached the bank will look like a discrepancy every single day without one.
- Posting excessive detail. A retailer posting every line of every till receipt makes the ledger unusable. Summarise, and keep detail in the source system.
- Skipping the parallel run. One cycle of comparison catches mapping errors that testing does not.
- Ignoring failed postings. Build the exception queue and give it an owner, or the gaps will appear at year end.
- Automating into disordered books. If the ledger is already wrong, integration accelerates the error. Clean up first.
- Leaving the accountant out. The integration must serve how your accounts are actually prepared and audited, which only they can confirm.
Conclusion
Accounting integration is an accounting project delivered with software, not a software project with accounting attached. Agree the mapping with whoever prepares your books, use clearing accounts for money in transit, post fees separately, choose a sensible summary level, and insist on a visible exception queue. Start with the payment gateway and your main sales system, run one cycle in parallel, then extend to inventory and payroll. The measurable result to aim for is a shorter close and management figures early enough to act on.
If your month-end still begins with collecting exports from four systems, Linestech can map your business events to your chart of accounts and build the integrations that post them automatically, including point of sale, payments, inventory and payroll.
Frequently asked questions
Which accounting packages can be integrated in Nigeria?
Mainstream cloud packages used by Nigerian businesses generally offer APIs or marketplace connectors, which makes integration faster. Locally built or older desktop packages can often still be integrated through their database or scheduled file exchange. Before committing to a package, confirm that it has a documented API, that it handles VAT the way your business needs, and that it supports the number of users and branches you run.
Do we still need an accountant after integrating?
Yes. Integration removes data entry, not judgement. Your accountant still sets the treatment of unusual transactions, reviews the exception queue, handles tax filings, prepares management accounts and closes the year. What changes is the balance of their time: less typing, more review and advice.
Can bank transactions flow into accounting software automatically in Nigeria?
Availability varies by bank and package, and many Nigerian businesses still import statements or use an aggregator rather than a direct feed. Confirm with your bank and your software vendor what is currently supported. Regardless of the route, use dedicated virtual accounts or a strict reference format so incoming transfers can be matched to invoices.
How is VAT handled in an automated posting?
The mapping must state the VAT treatment for each product or service category, including exempt and zero-rated items, and the integration must carry that through to the ledger. Because tax rules and electronic reporting requirements change, confirm current obligations with FIRS or your tax adviser, and review the mapping whenever rules or your product range change.
What if our point-of-sale system has no API?
Options include a scheduled export that is imported on a timetable, reading the system's database directly where the licence permits, or a small middleware component that watches for new export files. If none is workable, the cost of replacing the point-of-sale system should be compared with the cost of continuing manual posting for another two years.
How long does an accounting integration take?
A single native connector configured and tested takes one to two weeks. A point-of-sale to accounting integration for one site typically takes three to six weeks. A multi-branch programme with inventory and payroll is commonly two to four months, and the pace is usually set by the mapping decisions and the state of the existing books.
Will integration let us see profit in real time?
It will let you see revenue, collections and most direct costs close to real time, which is a considerable improvement. True profit still depends on period-end items such as accruals, depreciation, stock counts and provisions. A realistic goal is reliable weekly management figures and a much faster month-end, not a live profit number on a dashboard.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.
