Skip to main content

Niger's 2026 Payment Taxes: A Recordkeeping Guide for Cash and Mobile-Money Businesses

Published 10 min readMike ThriftMike Thrift
Niger's 2026 Payment Taxes: A Recordkeeping Guide for Cash and Mobile-Money Businesses

A CFA 102,000 bill can cost more than CFA 102,000 when it is settled in cash. That is the practical question behind Niger's 2026 taxes on certain cash payments, deposits, and money transfers: not simply whether a tax exists, but whether your business can tell which transaction triggered it, why, and who ultimately bore the cost.

For a small business, a new payment tax can easily disappear into a mixed “fees” line until month-end—when the cash balance, supplier invoice, and mobile-money statement no longer agree. The answer is a simple operating system: know the thresholds, separate the transaction from its tax, and retain enough evidence to explain both.

This guide summarizes the announced 2026 framework in practical terms. It is not legal or tax advice; confirm how the rules apply to your business, operator, and contracts with a Niger-qualified tax adviser or the relevant authority.

Start with the two taxes, not one vague “payment fee”

The 2026 framework distinguishes between two different taxes. They should not be modeled as one universal surcharge on every payment.

Tax on deposits and account-to-account transfers

The tax on deposits and transfers of money applies to defined activity involving accounts held with rapid-money-transfer entities. The published explanation describes two rates:

  • 0.5% for qualifying cash deposits and account-to-account transfers at or below the central-bank ceiling of CFA 2,000,000.
  • 5% when a qualifying deposit or transfer exceeds that regulatory ceiling, described as a deterrent for transactions beyond the permitted limit.

The important exception is operational: a transfer between accounts at the same operator is described as outside this tax. A transfer that connects accounts at different operators may be taxable. That distinction is not something a bookkeeper should infer from a customer name; it needs to come from the transaction record and the operator’s settlement detail.

For example, a qualifying CFA 10,000 deposit at the 0.5% rate produces a CFA 50 tax. The tax amount may be small, but hundreds of small deposits make a material difference to a cash-based retailer’s weekly margin and cash forecast.

Tax on qualifying cash payments

The cash-payment tax is a separate 1% tax. Under the announced explanation, it applies to cash transactions above CFA 100,000 when made by or with businesses under a real tax regime. That group includes companies, liberal professions, and certain individual businesses whose annual turnover exceeds the stated regime thresholds.

That means a cash payment is not automatically taxed merely because it is in cash. The amount, the counterparty’s tax status, and the nature of the transaction matter. A CFA 98,000 cash purchase and a CFA 102,000 cash purchase can therefore need different documentation and payment handling.

The distinction also changes the bookkeeping question. A cash-payment tax is connected to how an invoice is paid; a deposit or transfer tax is connected to how money enters or moves through the payment network. They may touch the same commercial relationship, but they are not interchangeable costs.

Map your exposure before changing how you pay

The fastest way to create confusion is to tell everyone to “use less cash” without first identifying where cash and mobile money enter the workflow. Build a short payment map for one representative month.

List each money movement by purpose

Make four columns in a worksheet or ledger report:

  1. Customer receipts — cash sales, wallet receipts, transfers, and deposits made on the business’s behalf.
  2. Supplier payments — inventory, rent, utilities, contractors, and other purchases.
  3. Internal movements — cash taken to an agent, wallet top-ups, transfers between business accounts, and cash withdrawals.
  4. Owner or employee movements — advances, reimbursements, and personal transactions that must not be mixed with business activity.

For each line, record the amount, date, payment method, originating and receiving operator, invoice or receipt number, and the staff member who initiated it. This is more useful than a year-end total because tax treatment often depends on the individual movement.

Flag threshold transactions early

Add two automated flags:

  • cash payments above CFA 100,000; and
  • deposits or inter-operator transfers approaching CFA 2,000,000.

The goal is not to split a legitimate transaction to avoid a rule. Artificially fragmenting an obligation creates its own compliance risk. The goal is to make a conscious payment choice before the money moves: confirm the supplier’s preferred compliant method, understand the operator charge, and preserve the invoice-to-payment trail.

Identify the tax regime of recurring counterparties

For recurring suppliers, landlords, service providers, and large customers, maintain a vendor master file that notes the information your business is allowed and needs to retain: legal name, taxpayer identifier where applicable, payment instructions, and whether the counterparty is expected to operate under a real tax regime. Ask an adviser how to document unclear cases.

This turns a last-minute question at the cash desk into a reviewable setup decision. It also helps prevent staff from paying a large invoice with cash simply because a bank or wallet option was not prepared.

Make the ledger show the business event and the tax separately

The accounting principle is straightforward: a payment tax should not erase the underlying purchase, sale, deposit, or transfer.

Suppose a business pays a CFA 150,000 qualifying supplier invoice in cash and the arrangement results in a CFA 1,500 cash-payment tax. The invoice remains a CFA 150,000 expense or inventory acquisition. The additional CFA 1,500 needs its own account, such as Expenses:Taxes:PaymentTaxes, until professional advice confirms the appropriate treatment.

If the tax is paid by the business, a simplified cash view might look like this:

2026-08-29 * "Supplier" "Inventory purchase paid in cash"
  Assets:Cash                              -150000 XOF
  Assets:Inventory                          150000 XOF
 
2026-08-29 * "Payment tax" "Cash-payment tax on qualifying settlement"
  Assets:Cash                                -1500 XOF
  Expenses:Taxes:PaymentTaxes                 1500 XOF

The exact accounts and tax treatment depend on the facts, but the separation is valuable in every system. It lets you answer three different questions: What did we buy? How did we pay? What tax or service charge arose because of that method?

For a qualifying wallet deposit, the same discipline applies. Record the cash leaving the till, the wallet balance increasing, and the tax or operator charge as distinct events. Do not expense the entire deposit; the wallet balance is still business money until it is spent or paid out.

Reconcile daily when cash and wallets are both in the loop

Cash-plus-wallet operations create timing differences that can look like losses. A sale may be recorded today, a customer transfer may settle tomorrow, and an operator tax may appear as a separate line. Monthly reconciliation is often too slow to find the source.

Use a three-way reconciliation

At the end of each business day—or at least each shift—compare:

  1. the point-of-sale or invoice total;
  2. the cash count and wallet/operator statement; and
  3. the ledger’s cash, wallet, clearing, tax, and fee accounts.

Every difference should be assigned a reason: pending settlement, refund, deposit in transit, operator fee, payment tax, data-entry error, or unexplained variance. “Unexplained” is a temporary status, not an account category to leave open indefinitely.

Keep a clearing account for money in transit

A clearing account can prevent a mobile-money deposit from being counted twice. When cash is handed to an agent, move it from Assets:Cash to Assets:TransfersInTransit. Once the wallet statement confirms the deposit, move it into Assets:MobileMoney. Post the associated tax separately when it appears.

This structure makes delayed credits visible without overstating either cash or wallet funds. It also gives management a daily view of how much money is with staff, agents, or payment networks rather than available for payroll or suppliers.

Preserve source documents in one place

For each flagged transaction, retain the invoice or sales record, cash receipt, operator confirmation, wallet statement, and any tax line shown by the provider. Use a consistent filename that includes the date, counterparty, amount, and reference number.

Good records reduce friction during an internal review and make it possible to challenge an apparent duplicate charge. They also protect a business when a staff member changes: the explanation stays with the transaction rather than in someone’s memory.

Budget the friction, not just the tax rate

A 0.5% or 1% charge is easy to calculate in isolation. The operational cost can be larger when it changes the timing or security of a payment.

Build a small scenario table for your most common transaction sizes. Include the purchase amount, applicable tax or operator fee, travel or agent cost, expected settlement delay, and the working-capital effect. Then compare compliant payment options for the same business purpose.

For example, a retailer that makes several supplier payments each week should measure the total cost of cash handling—not just the 1% tax where it applies. Cash collection time, cash-in-transit exposure, reconciliation effort, and missed early-payment discounts can all affect the decision. Conversely, a digital option may introduce network fees or delays that need to be visible in the forecast.

The best choice will vary by counterparty and location. The useful management habit is to treat payment method as a documented cost decision, not an afterthought once an invoice is due.

Assign clear controls to the people who move money

New payment rules work only when the person accepting cash, approving a transfer, and reconciling the statement follow the same process.

Set a written rule for:

  • who may approve payments above the cash threshold;
  • when staff must use a bank or wallet method instead of cash;
  • who reviews inter-operator transfers and their tax lines;
  • how long receipts and statements must be retained; and
  • who investigates a cash or wallet difference before the next business day.

Avoid giving one person authority to receive cash, initiate a transfer, and reconcile the operator statement. Even in a very small business, an owner can review a daily exception report or compare the wallet balance to the ledger. A simple approval trail is much easier to maintain than an investigation after a balance goes missing.

A 30-day implementation checklist

Use the first month to turn the new rules into a repeatable routine.

Week 1: clean up the payment list

List every wallet, agent, bank account, till, and staff-held cash float. Remove personal accounts from business collection instructions and confirm who controls each credential.

Week 2: configure the records

Create separate ledger accounts for cash, each material wallet, transfers in transit, payment taxes, and operator fees. Add the threshold flags and require a reference number on every large payment.

Week 3: test the reconciliation

Run the three-way reconciliation for a full week. Investigate timing differences promptly and refine the fields staff are missing on receipts or payment requests.

Week 4: review the exceptions

Review every cash payment above CFA 100,000 and every relevant deposit or inter-operator transfer. Check that the tax shown by the provider matches the transaction facts and that the supporting documents are attached. Bring unresolved classification questions to a qualified local adviser instead of making a permanent ledger assumption.

Simplify Your Financial Management

When payment methods and taxes multiply, a transparent ledger gives each cash movement, wallet balance, and charge a clear explanation. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready, so your records remain reviewable as your payment workflow changes. Get started for free.

Share this article