Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For the Philippines
Electronic invoicing here comes with a short reporting window — the document has to reach the Bureau in structured form within days of the sale, not at the end of the month. In a compact market that is an integration problem. In an archipelago of thousands of islands, where a rider takes an order in a barangay with one bar of signal and a delivery is confirmed on a wharf, it is something else: the compliance clock now runs on operational events that happen a long way from anybody's server. What you need is not a faster connection. It is capture that does not require one.
Where the window actually goes
Follow an ordinary sale from the moment it becomes a transaction. Nothing here is exotic — it is a routine day in a distribution business with field staff. The point is how much of the reporting window is consumed before anybody with a computer has heard about the sale at all. Reporting windows and deadlines in this area have been amended more than once; confirm your current obligations with the Bureau or your accountant rather than with a vendor page.
Hour zero
A field rider takes an order in a municipality with intermittent coverage. A site foreman confirms a delivery at a location that has never had a usable connection. A branch in a province loses power for six hours, which is not an incident, it is a Tuesday. The commercial event is complete, the goods have moved, and nothing has been recorded anywhere a system can see.
Hours 1 to 40
A photographed delivery receipt in a group chat. A phone call to the branch. A stack of carbon-copy books that comes back on the next ferry. This is not disorganisation — it is a rational adaptation to unreliable infrastructure, and it worked perfectly well when the deadline was a monthly return. Against a window measured in days it consumes most of the budget before the document exists.
Hours 40 to 72
Somebody keys a backlog. The details are reconstructed from a photograph and a memory. The customer's identifying data is guessed at or copied from the last order. Then the document is transmitted, and it is either accepted with wrong data on it or rejected with correct data missing — and there is no longer any time to find out which.
Where we fit: we do not transmit anything to the BIR. No EIS connection, no structured submission, no acknowledgement returned. That belongs with a Philippine compliance provider or your accounting system, and it is the easy half in any case — the hard half is that the thing being transmitted has to exist, accurately, within days of an event that happened where there was no network. Capture that works offline and reconciles on reconnect is something we do build, and this is the first market page in this corpus where it is the argument rather than a footnote.
What this costs today
Every one of these is the same defect measured on a different clock. That is why fixing the capture fixes more than one of them at once.
A sale, a delivery, a receipt — each real at the moment it occurs and each entering the system when somebody gets back to a desk. Against a monthly return that was survivable. Against a window measured in days it is the whole problem.
Goods between islands have left one warehouse's figures and not yet reached another's. The group position understates what the business owns, and the buyer who reorders against it is not doing anything wrong.
A delivery receipt in a chat message, retyped two days later by someone who was not there. Every field is an opportunity for a transcription error, and structured reporting is far less forgiving of those than a paper file ever was.
Freight, inter-island shipping, handling and demurrage arrive weeks after the goods on separate invoices. Absorbed into an overhead line, they leave a unit cost that makes your provincial margins look better than they are.
The same gap, measured in days
Inter-island distribution means goods spend days between your own locations, often across several legs and more than one carrier. In a market where a transfer takes an afternoon, in-transit stock is a rounding error. Here it is a real and permanent balance, and the question of who is counting it has a surprisingly common answer: nobody.
It leaves one count and does not enter another 01
What happens
What happens: the dispatching warehouse takes it out of stock on the day it ships. The receiving warehouse adds it on the day it arrives. For the four days in between it exists in no location's figures, and the group position quietly understates what the business owns.
What helps
What helps: in-transit as an actual position rather than a gap. The stock is somewhere, it is owned, and it is visible — with a dispatch date, an expected arrival and an owner while it travels.
Multiple legs, multiple handovers, one document 02
What happens
What happens: truck to port, inter-island vessel, truck again, sometimes a smaller boat. Each handover is a chance for a discrepancy and most of them are covered by a single dispatch note raised at the start. Where the shortage happened is unknowable by the time it is discovered.
What helps
What helps: recording the receipt at each leg where a leg has a responsible party. It will not stop a loss, but it converts "something went missing between Manila and Zamboanga" into a leg, a date and a name — which is the difference between a claim and a write-off.
Weather is a planning input, not an exception 03
What happens
What happens: an average of twenty tropical cyclones a year, several making landfall. Ports close, sailings cancel, and stock sits somewhere for a week. Systems that model transit as a fixed lead time treat every one of these as an error rather than as the normal operating environment.
What helps
What helps: expected arrivals that can be revised, transfers that stay open honestly rather than auto-closing on a date, and reorder decisions made against what is genuinely available rather than against a theoretical arrival.
The branch that is really a business 04
What happens
What happens: distance and travel time mean provincial branches run with real autonomy — local purchasing, local pricing decisions, local stock calls. That is usually correct, and it is invisible centrally until the year-end count.
What helps
What helps: each branch a distinct position with its own stock, its own approvals and its own numbers, rolled up rather than aggregated. Autonomy with a record is delegation; autonomy without one is just distance.
None of these is dramatic on its own, which is why the total is rarely attributed to the thing causing it.
This block and the one above it are the same problem seen twice. Both are about a gap between when something physically happens and when the business finds out — one measured in hours against a compliance clock, the other in days against a stock position. Close the first and you mostly close the second, because they are both fixed by capturing the event where it occurs.
The operation, in detail
Each links to a fuller tour. Nothing here transmits to the Bureau — the boundary, including the accreditation question, is drawn in full below.
Record the event where it happens — a delivery, a receipt, a count, a scan — and reconcile when the connection returns, rather than remembering it until you reach a desk.
Stock between locations is owned, dated and visible rather than absent, with expected arrivals that can be revised when a sailing is cancelled.
Provincial branches, warehouses and site stores each hold their own stock with their own approvals, rolled up centrally rather than averaged.
Requisitions, thresholds that refuse rather than warn, RFQ comparison with the award reason recorded, and three-way matching before an invoice is approved.
Freight, inter-island shipping, duty, handling and demurrage allocated to the receipt they belong to and carried into the unit cost you price against.
An asset register with a named holder, check-out and check-in, condition and maintenance history across branches and sites.
Scope, stated plainly
Accreditation of a computerised accounting system is a threshold question here rather than a preference, and no amount of operational capability substitutes for it.
Running in the product today
Not built
Read the second item as carefully as the first. Accreditation of a computerised accounting system is a real regulatory concept here and it is a threshold question rather than a preference — if your position requires an accredited system of record, no amount of operational capability substitutes for it. Establish that with your accountant before you evaluate anybody, us included. Where we fit is alongside whatever holds that position: the operational layer that knows what actually happened, where, and when.
How this starts
Take a sale made somewhere with poor coverage and measure the hours from the commercial event to the moment it exists as complete, accurate data in a system. Not the average — a bad day. That number is your actual reporting window, and everything else is the margin you have left.
Ask for the value of stock currently in transit between your own locations. If the answer takes more than a day to produce, or comes back as an estimate, that is working capital you own and cannot see. It is usually larger than people expect and it is entirely knowable.
Ask your accountant whether your compliance position requires a BIR-accredited computerised accounting system as your book of record. It is a yes-or-no question with a large consequence, we are not accredited, and it should shape your shortlist before you sit through a single demonstration — ours included.
Read before you shortlist
A short reporting window is an integration problem in a compact market. Across thousands of islands, where much of the selling happens beyond the signal, it becomes a capture problem instead.
Goods spend days between your own warehouses. They have left one count and not entered another, both figures are correct, and the group total is understated every single day.
One question can eliminate a vendor outright regardless of how well they demonstrate, and most buyers ask it last. It is not about features, price or the deadline.
Questions we are asked here
No. We do not generate the structured submission, transmit it, or manage acknowledgements and retries. That belongs with a Philippine compliance provider or with the accounting system you already file from. The half we build is the one that decides what gets transmitted: capturing the sale, the delivery and the receipt accurately at the moment they happen, including where there is no network, so the document is assembled from a record rather than reconstructed from a photograph.
No, and this is the most important answer on the page for some readers. We do not hold accreditation and we do not carry a permit to use. If your compliance position requires an accredited system as your book of record, that is a threshold question rather than a feature comparison, and you should settle it with your accountant before evaluating any vendor. Where we fit is alongside such a system rather than in place of it — the operational layer that knows what physically happened.
Records are captured on the device and held there when there is no usable connection, then reconciled with the server when one returns, with conflicts surfaced rather than silently resolved. The honest limits: it is designed for capturing operational events — deliveries, receipts, counts, scans, expenses — not for running the whole system disconnected for a week. It reduces the gap between an event and its record from hours to seconds, which against a short reporting window is the part that matters. Test it on your worst site rather than your best one.
It has been extended by regulation, and we are deliberately not printing a date here that a reader might plan against — that is exactly the kind of thing a vendor page gets wrong and a reader discovers late. Confirm the current position, and your own classification within it, with the Bureau or your accountant. What is stable enough to plan around is the shape of the obligation: structured documents, transmitted within a short window of the transaction, with micro taxpayers broadly outside it but able to opt in. The operational consequence of that shape is what this page is about, and it does not change when a date moves.
Not as a statutory computation. Thirteenth-month pay is a legal entitlement here that accrues through the year and is settled in December, which makes it a cash and accrual planning question as much as a payroll one — and the common failure is treating it as a December event rather than a monthly cost. Our maintained payroll engine covers Kenya only, so we do not compute or accrue it. We do attribute payroll cost to projects and cost centres, which is the piece that makes an accrual useful once your payroll provider has produced the rate.
Less than you would hope, and it is fairer to say so. Most of this page is about physical goods moving between islands, which is not your business. Where we are occasionally useful to a services organisation of that kind is project time and cost, procurement approvals, and asset custody across a large distributed workforce — real but narrow. If your central need is workforce management, client billing at scale or seat-level utilisation, there are products built for exactly that and we are not one of them.
Nairobi, remote, in English. The Philippines is UTC+8 and Nairobi is UTC+3, so five hours — your afternoon overlaps our morning and your morning does not overlap us at all. That is the largest practical gap in this wave and it is worth being blunt about: if you need somebody reachable at eight in the morning Manila time, that is not us today. The working week and public holidays are configured rather than assumed.
Measure the hours between a sale actually happening somewhere with poor coverage and it existing as complete, accurate data. On a bad day, not an average one. That number tells you whether this page is about your business, and you do not need us to find it.