Expense approval register

Register

Claims waiting on a decision — who is claiming, what for, how much, who owes the answer, and what they said.

A queue, not a file

The claim is one person’s piece of paper. The register is the pile on somebody’s desk. They are separate tools because a form filled in once and a queue that persists behave differently: the queue sorts by what is owed, keeps a decision date, and is useful precisely because it outlives any one claim.

It decides nothing and pays nothing

There is no policy engine, no limit, no threshold and no flag. There is also no bank account, card number or payment detail, and nothing that would use one. Approved here means a person with the authority told you their answer, and you wrote it down with their name against it.

Where it sits

The claimant fills in an expense claim. Supplier invoices are a different pile, in the invoice approval register. Money asked for before it is spent is a purchase requisition or a budget request.

A queue of claims and the decisions recorded against them. CompliMaint approves nothing itself, confers no spending authority, pays nobody, applies no expense policy, and makes no determination about tax treatment or deductibility. It holds no bank, card or payment details. Everything runs on your device.

Questions people ask

How is this different from the expense claim form?
The claim form is one person’s document — their lines, their receipts, printed and handed in. This is the other side: the queue of claims waiting on somebody’s decision, across everybody, so an approver can see what is owed an answer. Two shapes, because a form filled in once and a queue that persists are not the same thing.
Does approving here pay anybody?
No. Nothing in this product moves money. Approved is a state you set after the decision was made, and payment happens in your payroll or accounts system. The register records who decided and when, which is the part that is otherwise remembered rather than written down.
Does it apply our expense policy?
No. It knows nothing about your policy, your limits, your categories or your thresholds, and it flags nothing. If a claim exceeds something, the person approving it knows that; this tool does not, and a warning it invented would be wrong for most people who saw it.
Why is it kept per location rather than per person?
Because it is the approver’s queue rather than the claimant’s file. Somebody approving claims across a site wants one list, not one list per person. Who is claiming goes on the row, as a name you write — nothing in this product joins records on it.