Industry: IT & software services
Accounting for software and IT services companies: the money never arrives the way you invoiced it.
A software or IT services company typically prices in one currency, spends in three, and is paid by clients it has never met in person. That produces a distinct set of accounting problems: bank credits that do not equal the invoices they are settling, per-seat tooling charged monthly on a founder’s card, contractors invoicing from several countries, and recurring and project work running through the same ledger on different triggers.
A finance operation that fits this business has to do four things reliably. Tie every receipt to a named invoice and contract. Explain the difference between invoiced and received as charges, deductions or exchange movement rather than leaving it as an unexplained shortfall. Hold delivery cost against the engagement that produced it. And keep the documentary trail that shows which income is foreign-service income, if an export treatment applies where you are.
A foreign receipt almost never equals the invoice. Four reasons, and only one is a loss.
Invoice 12,000 in one currency and 11,943.20 lands, three days later than expected, converted into your account at a rate nobody told you in advance, referenced by the client’s internal payment batch number. This is the single most common reason cross-border service companies have messy books: the amount on the invoice and the amount in the bank are different numbers, and treating the difference as a rounding annoyance destroys the reconciliation.
The difference has four separate causes. They need different handling and only one of them is genuinely a cost you should be measuring.
- Bank and correspondent charges. An international transfer can be reduced by the sending bank, an intermediary bank in between, and the receiving bank. Where the client agreed to bear charges and did not, that is a term to enforce — not a discount.
- Payment platform fees. Where clients pay by card or through a payment provider, the gross invoice and the net settlement are two different figures and the fee is a real cost of doing business. It belongs in the accounts as a cost, not as a smaller sale.
- Deductions made by the client. Depending on where the client is, a payment may arrive net of a deduction the client is required to make at source. What matters operationally is that the shortfall is identified as a deduction with documentation behind it, and pursued as a certificate rather than written off as a short payment.
- Exchange movement. The rate on the day you invoiced and the rate on the day the money converted are rarely the same. That difference is not an error and not a bad debt; it is an exchange difference, and it should be recorded as one so that trading margin is not quietly polluted by currency noise.
There is a fifth complication that is purely operational. One transfer often settles several invoices, and the remittance advice arrives separately, in a format the client’s finance system produced rather than one you chose — a spreadsheet, a PDF, or an email listing internal references you have never seen. Allocation should follow the remittance, never the amount alone. Two invoices that happen to sum to the receipt is a coincidence, and coincidences reconcile beautifully and wrongly.
The mechanics of putting each part of that difference in the right place are worked through separately in the invoice says one number and the bank says another. The rest of this page is about the parts specific to selling software and IT services.
Recurring and project work, in the same ledger, on different clocks.
Most IT services companies bill in more than one way at once: a monthly managed-service or support fee for some clients, milestone invoices on implementation projects, time-and-materials on others, and vendor licences resold on top. Each has a different condition that must be true before an invoice can legitimately go out. When the ledger does not know which model an engagement is on, invoicing becomes a monthly memory exercise, and memory under-bills.
| Model | What must be true before you invoice | How it fails |
|---|---|---|
| Monthly managed service or support | The month has passed and the agreed service was available. | Scope drift. Work outside the agreement is absorbed ticket by ticket until the contract is loss-making, and nothing in the accounts shows it. |
| Time and materials | Time is recorded, approved by the client contact, and priced at the agreed rate. | An unapproved timesheet is an uninvoiced month. The cost has already been paid on your side while the invoice waits on an approval nobody is chasing. |
| Fixed-price milestone | The milestone is defined, delivered and accepted. | Acceptance is a conversation rather than a document, so the milestone slips without anyone deciding that it has. |
| Licences or subscriptions resold | The underlying subscription is live and the term is known. | The vendor renews automatically, the client is never re-billed, and a recurring cost silently becomes yours. |
On time-and-materials work the timesheet is the invoice. A company that treats time recording as an internal management habit rather than a billing document will under-invoice, and will not be able to say by how much.
The fixed-price side carries a different exposure. A fixed fee is a commitment made before the work is understood, and the cost of delivering it keeps accruing after the price stops moving. That is a manageable position only if delivery cost is being held against the engagement while it runs, rather than assembled at the end — by which point the only remaining decision is how to describe the loss.
Contractors in several countries, and tooling billed by the seat.
Delivery capacity in this industry is usually a mix: some employees, some long-term contractors, some specialists engaged for a phase. They are frequently in different countries, invoice in different currencies, and are sometimes paid through a platform that adds its own layer of fees and its own statement format. Payroll and accounts payable stop being two separate worlds.
Alongside people sits a cost category that most general bookkeeping treats badly: tooling. Cloud hosting, source control, build pipelines, monitoring, error tracking, design tools, project tools, security scanning, and per-seat licences for anything the team touches. Charged monthly, on a card, per seat, in two or three currencies, by vendors who raise prices without a conversation.
Lumping all of it into a single subscriptions line is the default and it destroys the only number that matters. Three types of tooling cost behave completely differently:
- Cost that scales with headcount. Per-seat licences. Every hire adds them, and they should be understood as part of the cost of a person, not as office overhead.
- Cost that belongs to a specific client. An environment you run for one client, a cloud account billed to you and consumed by their product, a licence bought for their project. This should be identified and then either recharged or knowingly absorbed. Absorbed by default is how a profitable engagement becomes a break-even one.
- Genuine general overhead. The tools the company would run with no clients at all.
Currency adds a last wrinkle. A single card statement can hold charges in three currencies, each converted on the day it was taken, so the statement total is a blend of rates. Recording the charge in the currency it was incurred keeps the cost of a delivery month comparable with the one before it.
How a long-term contractor is classified for employment and payroll purposes depends on the jurisdiction and on the working arrangement rather than on the label in the contract, and it is worth settling deliberately. Where people are employed, payroll should agree to the ledger and to what actually left the bank.
Proving a receipt is what you say it is.
Where an export-service treatment applies to your business, the burden that comes with it is documentary. Requirements differ by jurisdiction and change over time, so they should be checked against the current rules where you are rather than assumed — but the underlying question a reviewer asks is stable: which foreign contract and which invoice does this bank credit relate to, and what proves it?
The reason this is hard is not complexity. It is that the three documents describing the same money usually share no common reference. The engagement is an email chain plus a statement of work signed by scan. The invoice quotes an internal project code. The bank credit quotes the client’s payment batch number. Each is genuine, none points at the others, and the trail has to be built by a person from memory — a year later, often after that person has left.
- One reference on the invoice that the client is asked to quote on payment, agreed at the start of the engagement rather than after the first mismatch.
- The signed engagement document held against the client record in the accounting system, not in a mailbox.
- The rate used to convert each receipt, and its source, recorded at the time — not derived afterwards from a monthly average.
- The remittance advice stored with the receipt it explains.
- A running position per client in the invoice currency, so a partial payment does not disappear into a converted balance.
Cross-border receivables have one further property worth stating plainly: for most engagement sizes, enforcement across a border is impractical. That makes the front end the real control — deposits, milestone structure, and a stated point at which work stops — and makes routine follow-up a matter of discipline rather than escalation. The general approach is set out in accounts receivable outsourcing.
If your company is based in Pakistan and most of your receipts are foreign, the jurisdiction-specific version of this is written up separately: accounting for IT export companies in Pakistan.
Where At Par fits — and the limits.
At Par runs the finance operation for owner-led software and IT services companies that sell across borders. Receipts tied to invoices and contracts with the difference explained, foreign-currency movement recorded rather than absorbed, delivery cost held against the engagement, recurring and project billing tracked against their own triggers, the period closed on a date, and reporting that shows engagement margin. Records are evidence-backed, reconciled, and organised so an auditor or a lender can review them. A qualified accountant (ACCA) is accountable for the work.
In scope: bookkeeping and month-end close, receivables and invoice follow-up, payroll, and management reporting. How your records and evidence are protected is documented separately.
Where At Par is not the answer. A company with a handful of domestic clients, one currency and no contractors will usually be served better and more cheaply by a competent local bookkeeper. A product company running consumer subscription billing at volume, with its own billing platform as the source of truth, is a different accounting problem from a services business. And hardware resale at volume — stock bought, held and sold — is inventory-heavy trading, which is outside what At Par takes on, as are retail, restaurants, manufacturing and cash-heavy businesses.
Asked by founders selling software and IT services across borders.
How is accounting for an IT services company different from a software product company? +
A services company earns from delivered work, so its central questions are what an engagement cost to deliver, which billing trigger applies, and how a foreign receipt ties back to an invoice. A product company earns from a subscription base, so its questions are about billing systems, revenue spread over subscription terms and retention. The two share a technology stack and very little else in the books. Applying product metrics to a services business produces confident answers to the wrong questions.
Why does the money received from a foreign client not match the invoice? +
Four causes, and they need separating rather than netting. Bank and correspondent charges taken in transit. Payment platform fees where the client pays by card. A deduction the client is required to make at source in their own country, which should be pursued as documentation rather than accepted as a shortfall. And exchange movement between the invoice date and the conversion date. Only the platform fee is straightforwardly a cost; treating all four as one shortfall makes the account impossible to reconcile.
How should foreign-currency income be recorded in the books? +
The invoice is recorded at a rate on a defined and consistently applied basis, and the difference arising when the money actually converts is recorded as an exchange difference rather than as a change in the value of the sale. The rate used and its source should be captured at the time. The specific policy — which rate, from which source, on which date — should be agreed with a qualified accountant and then not varied, because inconsistent rate selection makes period comparison meaningless.
How do you allocate one payment covering several invoices? +
Follow the remittance advice, never the amount. Clients routinely settle three or four invoices in one transfer and send the breakdown separately, often in a format their finance system produced. Where no advice arrives, ask for it rather than inferring. Two invoices that happen to sum to the received amount will reconcile cleanly and incorrectly, and the error only surfaces months later when a genuinely unpaid invoice cannot be traced.
Should contractors be shown as cost of delivery or as overhead? +
As cost of delivery, held against the engagement they worked on, when the work is client-chargeable. Contractors are usually a variable delivery resource rather than an administrative cost, and putting them in overhead makes gross margin look strong while the real position is invisible. Classification for employment and payroll purposes is a separate question that depends on the jurisdiction and the actual working arrangement, not on what the contract is titled.
How should cloud and software subscriptions be recorded? +
Split by behaviour rather than by vendor. Per-seat licences scale with headcount and belong with the cost of a person. Infrastructure or licences consumed by one client belong to that engagement and should be recharged or knowingly absorbed. What remains is general overhead. A single subscriptions line makes engagement margin unknowable, which matters most for fixed-price work where the price cannot move once the cost is understood.
What records prove that income is export-service income? +
The contract or statement of work, the invoice, the bank credit, and something that connects them — most practically a reference the client is asked to quote when paying, plus the remittance advice stored with the receipt. Specific requirements differ by jurisdiction and change, so they should be confirmed against current local rules rather than assumed. The operational point is that the trail must be built as transactions happen, because reconstructing it a year later is expensive and often incomplete.
What changes in the books between time-and-materials and fixed-price work? +
The invoicing trigger and where the risk sits. On time and materials, approved time is the billing document, so unapproved timesheets translate directly into unbilled revenue. On fixed price, the invoice depends on a milestone being accepted, and the cost of delivery keeps running after the price is settled — so delivery cost has to be tracked against the engagement while it is live, not assembled at the end.
How can margin per engagement be tracked without heavy timesheet systems? +
Consistently rather than precisely. Recording time at engagement level, weekly, is usually enough to allocate people cost, and it is far more useful than perfectly detailed data collected for two months and then abandoned. Contractor invoices and client-specific infrastructure should be coded to the engagement as they arrive. The purpose is to compare engagements against each other and inform pricing, which tolerates approximation but not gaps.
Can a company with clients in several countries outsource its accounting? +
Yes, and the cross-border side is usually the part that benefits most, because the work is documentary and repetitive: tying receipts to invoices, chasing remittance advice, recording rates, and keeping the evidence trail current. What cannot be outsourced is the local filing position in each place the business has an obligation, which needs someone answerable for that jurisdiction. Those two things should be scoped separately rather than assumed to travel together.
Send us a quarter of foreign receipts. We’ll tie them to invoices.
Bring three months of bank credits, the invoices they were meant to settle, and whatever remittance advice you have. We will show you what matched, what did not, and what the difference actually was.
Prefer to reach us directly? Tell us a little and we'll come back with a time.
Tie up a quarter with usWe use your details only to prepare for and hold this call. No spam, ever.
Reviewed by an ACCA on the At Par team · Last updated 29 July 2026 · This page covers operating mechanics, not the tax position in any particular country. Local rules should be confirmed where your business is. See what we actually do.