AWRA OpsHub Search

A Current Asset Nobody Reconciles

For an exporter the tax balance is not a liability to settle — it is a receivable, often a large one, managed with less rigour than a debtor a tenth of its size.

Accounting Insights Washingtone Aura 10 min read

Ask a finance team how they manage receivables and you will get a real answer: an ageing report, a collections routine, somebody who chases, a policy about when a balance becomes a problem. Ask the same team about the tax balance and the answer is usually about deadlines.

That works while the balance is a liability — money you have collected and will pay over. It stops working when the balance points the other way. A business in a standing credit position is carrying a receivable, frequently one of the larger current assets on its balance sheet, and it is almost never managed like one.

This is the ordinary position for an exporter, or for anybody selling substantially zero-rated goods while buying inputs that are rated. Nothing unusual is happening. The tax on your purchases exceeds the tax on your sales, permanently, by design.

What it looks like in practice

A trade debtor of the same size The tax balance
Has an ageing profile Has a filing date
Somebody is accountable for collecting it Somebody is accountable for submitting a form
Is reconciled to invoices Is reconciled to itself
Its supporting documents are in the system Its supporting documents are gathered every couple of months
A dispute on it is visible A weak invoice inside it is invisible until it is queried

A claim is only as good as the invoices behind it — which means an unreconciled claim is not an asset, it is an estimate with a plausible number attached.

The two-monthly ritual, and what it actually costs

The recurring version of this is somebody gathering the invoices, checking them, and assembling the evidence — several times a year, from an inbox, a drawer and a folder. Two costs, and the visible one is the smaller.

The visible cost is the days. The invisible cost is that anything the assembly cannot find quietly drops out. Nobody records a decision to abandon a claim on an invoice that could not be located; it simply does not appear in the total, and the total is still plausible. Over a few years that is a real number, and there is no report anywhere that shows it, because a thing that was never entered leaves no trace.

What this post does not tell you

Whether any particular input is claimable, how a partly zero-rated business should apportion, or how long a repayment takes. The first two are your adviser's judgement about your circumstances; the third is a moving fact we are not going to publish and have you plan against. What is safely sayable is structural: a balance you intend to recover needs the same discipline as a debtor, and most systems do not offer it because most businesses are not in this position.

The fix is upstream, which is the annoying part

The instinct is to build a better assembly — a checklist, a shared folder, a better spreadsheet. That improves the ritual and leaves its cause intact. The cause is that the evidence was never attached to anything when it arrived.

Attach it at the point of receipt and the periodic exercise changes character completely: it becomes a retrieval of records that were already checked, by the person who was standing in front of the goods, at the time. Not a smaller version of the same job — a different job.

Order, receipt and invoice matched as they happen

Three-way matching with your own tolerances, and differences raised at the point of receipt where somebody can still walk to the pallet. This is the step that makes a later assembly a retrieval rather than an investigation.

Built in

The document held against the transaction it supports

Retrievable by the transaction rather than by whoever filed it or the month it arrived in. A file gathered from an inbox is only as complete as somebody's memory of what to look for.

Built in

A rate recorded on every line, at capture

Per line rather than per document, so a business whose mix moves between rated and zero-rated work has a record of the mix rather than a total to reverse-engineer.

Built in

Balances and their documents queried together

The underlying records filtered by period, project or counterparty on demand, rather than a pack assembled per cycle and rebuilt when the question changes slightly.

Built in

Preparing, apportioning or submitting anything

Not ours. We hold the detail a claim is built from. The claim itself, and any apportionment inside it, is your adviser's work — and a vendor willing to do it in a sales meeting has told you something about how they sell.

Yours to own

One number worth pulling this week

Take the current balance of the account, and then take the count of source documents that make it up.

If the second figure is available from a system, this post is not about you. If producing it means opening a spreadsheet, then the largest recoverable asset on your balance sheet is being tracked with less machinery than a customer who owes you a tenth as much — and the gap between those two levels of rigour is the whole argument.

What is built here, what is not, and what we would decline is on the Trinidad and Tobago market page. The other half of this — what happens to the mix when a domestic trader wins an export contract — is the month your input tax stops being simple. The exact opposite situation, where the tax can never be recovered at all, is the tax you paid is part of what the goods cost.

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center