The AI prepares the job and the invoice. Authorizing, signing and approving is a person’s call.

Yes, and it is designed for it. The field application stores the whole ticket on the phone — hours, people, equipment, consumables, photos with their location and time, dictated observations and signatures — and uploads it when there is a network, without the crew having to remember anything. If the same ticket syncs twice, it enters once. The checks against the contract run on the phone with the downloaded copy of the catalogue, so the flag for whatever does not match arrives while the crew is still at the well, not two weeks later.

No, and it rarely should. The usual path is to leave in accounting what it does well — ledgers, taxes, close — and integrate it by API, then put on top what today lives in spreadsheets and in the WhatsApp group: the contract catalogue, the balance of every purchase order, the field ticket with its signatures and the pre-invoice with its checks. The system hands accounting an already checked invoice, with its cost center and its reference to the ticket. What stays, what gets integrated and what gets absorbed comes out of the assessment.

A person, always. The AI drafts the risk analysis from the scope of the job, the site and the incidents recorded on similar jobs, and assembles the permit with its requirements; the HSE supervisor reviews it, corrects it and authorizes it with their name and the time. Each person’s eligibility is the other half: the system crosses the job with the matrix of certificates and medicals, and nobody without valid credentials is assigned. That rule is not a warning that can be skipped, it is a condition of dispatch.

It works the same. The purchase order comes in however it arrives — PDF, email, a photo of the document — and the AI reads it, validates it against the contract and leaves it with its line items and its amount. What changes is where the data comes from, not the circuit: once loaded, the balance is deducted with every approved ticket and the consumption alert works the same. If the client later opens a portal, it gets connected and manual loading stops; nothing from before is lost.

The system is multi-entity and multi-country by design: each base operates in its own country, with its working currency and its consolidation in dollars, and each invoice goes out with the format, the taxes and the withholdings of the right country. Tax issuance goes through each country’s authorized provider, which is the one holding the certification; the system supplies the document, its evidence and the trail back to the ticket. Which countries come first and which provider each one connects to is defined in the assessment, against the rules in force where you operate.

Whatever you decide to give them, and always the same thing you see: the ticket their representative signed with its hours, its consumables and its photos; the purchase order with its consumption and its balance; the invoice with the clause applied on each line. The point is that the conversation stops being “I have a different number” and starts being about the same document. What the client does not see is your cost, your margin or your price history: that lives on your side, with per-role permissions.

It is defined in the assessment. The model has three parts: setup, a monthly fee and a variable cost per processed volume. The scope — how many bases come first, whether accounting is integrated or absorbed, how many contracts and in which countries you invoice — comes from what we see in your operation. Book 30 minutes and we give you the range in writing.