A Pakistani software business can have a healthy pipeline and still struggle to collect cash on time. The customer has accepted the proposal, the team has delivered work, but the invoice is missing a purchase-order reference or waiting for approval from someone nobody named at the start. For founders selling internationally, accounts receivable is an operating discipline, not an administrative task to postpone until payment is late.
This practical guide focuses on the path from an agreed commercial obligation to a reconciled receipt. It complements earlier coverage of payment infrastructure and export accounts without treating bank processing as a substitute for customer collections. The recommendations are an operator’s framework, not personalised tax, legal or accounting advice.
Separate customer delay from bank processing
In April 2026, the State Bank of Pakistan announced measures simplifying procedures for IT exporters and freelancers, including a one-time service declaration instead of Form R for each transaction and bank tagging of relevant service codes. The SBP announcement provides the policy context.
The underlying SBP circular sets out the applicable instructions. A founder should confirm their bank’s implementation and documentation requirements for the actual transaction. Those procedures do not make a customer approve an invoice or resolve a disputed milestone. Keep the commercial collection process and the banking process visible as separate stages.
I would ask a simple question whenever cash is late: has the buyer paid yet? If not, identify the outstanding approval or dispute. If yes, obtain the payment reference and investigate reconciliation or processing with the relevant parties. Mixing these situations produces vague follow-ups and makes it harder to assign the next action.
Agree the invoice path before signing
Before delivery starts, confirm the customer’s legal billing entity, invoice recipient, required references, currency and agreed payment terms. Ask whether a purchase order or vendor registration is needed. Identify who can confirm acceptance of the work and who handles payment queries. These are suggested commercial checks, not a claim that every customer uses the same process.
For milestone-based work, define what constitutes acceptance and how a disagreement will be handled. A vague promise to invoice when the project is finished can leave the team debating whether the project is ever finished. Have appropriate advisers review contractual terms, especially where delivery, intellectual property or service suspension depends on payment.
For subscription software, be equally clear about the billing period, included services and any implementation charge. Do not let a sales exception disappear between the contract and the invoice. A short billing brief shared by sales, delivery and finance can prevent a customer receiving a charge that nobody on either side knows how to explain.
Keep a record that leads to an action
I would maintain one receivables register with invoice number, customer, amount, due date, acceptance evidence, current status and next action. Include an owner and a date for that action. The aim is not to build a sophisticated dashboard; it is to ensure that every unpaid invoice has a specific explanation and someone responsible for resolving it.
Distinguish invoices not yet due from overdue balances. Within the overdue group, separate a genuine dispute from an administrative omission and from a customer who has not responded. A generic reminder may help with one situation and worsen another. The register should guide the conversation rather than trigger identical messages to everyone.
Keep supporting evidence together: the agreed scope, delivery confirmation, invoice and relevant correspondence. Limit access to people who need it. When staff change or a founder is unavailable, another colleague should be able to understand the account without searching several personal inboxes. That continuity is particularly useful for small teams serving international buyers.
Review cash timing without flattering the numbers
A weekly review can start with what became due, what was collected and what remains unresolved. Look at individual large balances as well as totals. One substantial disputed invoice can matter more than many small invoices paid promptly. Avoid presenting a single collection metric without explaining customer concentration and the age of outstanding balances.
Consider a hypothetical company that invoices a large annual contract while most other customers pay monthly. Its headline receivables balance may jump even if nothing has gone wrong. Conversely, a stable total can hide an old unpaid balance while new customers settle quickly. Read the underlying invoices before concluding that collections are improving or deteriorating.
For planning, separate expected receipts from confirmed receipts and show uncertainty honestly. A customer saying payment is being arranged is not the same as money received and matched. Ask the accountant how revenue, receivables and cash should be recorded for the company’s circumstances. The management forecast should not silently treat them as interchangeable.
Make follow-up useful and proportionate
A first reminder should make payment easier: identify the invoice, attach the relevant document and ask whether an approval or reference is missing. If the customer disputes delivery, route that question to the person who can resolve it. Sending more reminders will not repair a product problem or an unclear acceptance condition.
Set an escalation path appropriate to the relationship and contract. A founder may need to speak to the commercial sponsor, but that should not be the only process available. Document any revised arrangement and make sure finance and delivery understand it. Do not improvise threats or suspend a critical service without checking the agreed terms and consequences.
Automation is useful for scheduling reminders and matching records, but exceptions need human review. Before introducing an AI assistant, define what it may send, which data it may access and when it must stop. A confident but inaccurate payment demand can damage a relationship that took months to build.
Why this matters for international growth
As an early-stage investor, I would want to understand whether growth creates cash discipline or hides collection problems. Ask how many customers pay through a repeatable process, what causes delays and whether the team learns from each exception. A business that explains these details clearly is easier to assess than one that reports only signed contract value.
Related reading: Pakistan IT-export payment operations. If you are building a Pakistani B2B product with credible international ambitions, share the customer problem, traction and funding plan. My investment focus remains early-stage B2B and fintech; disciplined collections are one part of the operating picture.