The human verifies: why Muvik never sends the invoice itself

Every business we work with runs on one loop. A launch operator, a ship agent, an OOG warehouse, a forwarder and a car workshop use different words for it, but the shape is the same.

Something arrives. An email, a WhatsApp message, a phone call, a piece of paper. It asks for a job, or reports one done, or bills for one, or pays for one.

Something leaves. A quote, a job card, an invoice, a statement. A document another person is going to read and act on.

In between sits the back office, reading the first thing and writing the second. That is the work. It is unglamorous and unavoidable, and in a service business it is where the margin is made or lost, one retyped number at a time.

What Muvik does in the middle

Muvik reads what arrives and turns it into a record with the right fields. The agent's WhatsApp becomes a launch job with a vessel, a time and a passenger count. The enquiry email becomes a warehouse job with dimensions and dates. The vendor's invoice becomes a line on the job card, the boat log photo becomes four timestamps, and the payment slip becomes an amount and a reference.

Then it drafts what leaves. The PDA with sections A, B and C. The charge sheet with buy, sell and margin. The invoice priced from the rate card. The Statement of Fact from the events logged during the call.

And then it stops.

The verify step

Nothing Muvik drafts goes anywhere until a person says so. The invoice is a draft until the approver approves it. The quote is a draft until someone presses send. The extracted log sheet sits next to the scan until someone verifies the fields. The matched payment is a proposal, with its reason written in plain words, until someone records it.

People sometimes ask whether this is a limitation we intend to remove. It is the design.

There are three reasons.

The documents have your name on them. An invoice goes to your customer under your company's name. A PDA is your promise to a principal. A Statement of Fact can end up in a laytime dispute. The person whose name is on the document should be the person who decides it is right.

Uncertainty should be visible. When Muvik reads a quantity as 7 and the amount implies 1, it says so and holds the line. When a payment matches by amount alone, it says "amount only" and asks. A fully automatic system has to pick an answer. A system that stops can tell you it is unsure.

Verifying is fast. Creating is slow. The expensive part of back-office work was never the decision. It was building the thing to decide about: finding the rate card, opening the portals, retyping the sheet. When the draft is already there with its reasons attached, verifying it takes seconds. That is where the time goes back to the business, and nobody gives up control to get it.

What it looks like in practice

A dispatcher's morning is a board of jobs read from WhatsApp, waiting to be dragged onto boats. An agency operator's afternoon is a job card that has filled itself in from the day's vendor invoices, waiting for a look. A workshop's Friday is a list of payment slips, each with a proposed invoice and a sentence explaining why, waiting for a tick.

Every read, every match and every verification is timestamped and kept. When someone asks why an invoice says what it says, the answer is on the record: what was read, from where, who verified it, when.

Muvik reads and drafts. A person verifies and sends.