How to Automate Qoyod

The books and the tax file became the same system

Qoyod is cloud accounting software built for Saudi Arabia, and the businesses on it are ordinary ones: a contracting firm in Riyadh, a retail shop with three branches, a clinic, a wholesaler in Jeddah. Some owners run it themselves; many hand the same account to an accountant.

What sits inside is the whole position of the business. Every sales invoice and the VAT on it, every supplier bill, the journal entries behind both, what each customer owes, what is left in stock, and, for shops running Qoyod's own point of sale, every sale rung up at the counter.

The reason it matters more than a ledger used to is compliance. In Saudi Arabia an invoice is not a document you print and file. It is a record the tax authority expects to receive, in a set form, the moment it is issued. Qoyod is where that happens, which makes it the books and the tax file at once.

The collecting starts the moment the invoice is issued

Issuing is fast. Everything downstream of it is somebody opening things.

A customer takes thirty days and then takes forty-five. Somebody has to know who is past due, by how much, and whether the transfer that landed on Sunday belongs to them, which means opening the bank and reading a statement line by line against what Qoyod recorded.

Then the branches. Three shops closed last night with three separate totals, and comparing them properly means three sets of reports and a lot of scrolling.

Then buying. The supplier's price this month against the previous month's rate. What is on the shelf against what the online store says is available.

Then the calendar. The VAT return has a date on it, the supplier bills have their own, and the person who knows them all is remembering rather than being told.

None of it is difficult. All of it happens after the shop shuts.

Qoyod

Overdue accounts, oldest first Who is past due and by how much, read from the invoices already in Qoyod, with a statement drafted for each name on the list.

Transfers matched to the invoice they settle Yesterday's bank credits set against what Qoyod marked as paid, so a payment that never arrived is named the same morning.

Branches compared on one page Each shop's takings, margin and stock movement put side by side, so the branch quietly drifting shows up in week two.

Qoyod stamps and submits what it already holds

Qoyod does a great deal of this on its own, and it is worth switching all of it on first.

E-invoicing is the strongest part. It is built for ZATCA Phase 2: every invoice carries the mandatory fields and a QR code, is issued as UBL XML with a cryptographic stamp and digital signature, and goes to the Fatoora platform as it is created rather than in a batch somebody remembers to send. Inventory deducts the sold quantity the moment a sale closes and raises an alert when an item falls below the minimum you set. Reporting assembles the trial balance, income statement, balance sheet, cash flow and VAT return from entries already posted. There is multi-branch and multi-currency support, recurring journal entry templates, and an integrations marketplace connecting Salla, Zid, WooCommerce and Shopify.

That is a real accounting system, and every piece of it works from something Qoyod already holds.

The bank's own website, the payment gateway's settlement page, the supplier's price list and the marketplace listing are other companies' screens, behind logins that belong to you, with no export button anywhere near them.

Riyals that never arrived can be found the same day

Four logins cover most of the evening round: the bank, the gateway, the supplier's price list and the marketplace. Read on a schedule, they come back as a page that is already written.

Yesterday's transfers and card settlements read off the bank and set against the invoices Qoyod marked as paid, so a payment that never landed is a question on Sunday rather than a discovery at quarter end.

The receivables list ordered by age, each customer's statement drafted from their own account, so chasing is reading a short list instead of building one.

Every branch's takings put beside every other branch's on the same page, so the shop quietly drifting is visible in week two, not at year end.

The buying side reads the same way. This month's price on the supplier's portal against the cost recorded on the last purchase invoice, so an increase is spotted at the order, not at the payment run. Stock in Qoyod against what the online store says is available, so the same unit does not sell twice.

Then the calendar nobody keeps: the VAT deadline and the supplier bills due in the next fortnight, in one note. And last week's catalogue prices against this week's, so a margin is never given away by accident.

A password is all any of those screens asks for

Each of those checks is a site the business already signs into and twenty minutes it does not have. The only missing part is somebody to do the opening.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens Qoyod, reads yesterday's invoices, stock and branch totals, then opens the bank, a supplier's portal or the online store, and hands back one short list: what did not match, what is short and who is overdue.

It runs on your schedule in your own private environment, and any run can be watched and stopped. Anything that reaches a customer, spends money or touches the tax authority is drafted and waits for a person.

The workflows below are already built, and each one names what it opens.