Skip to main content
GullySystem

Audit Trail for Expense Claims and Approvals

Every submission, approval, rejection, edit and payment is logged with the person and the time. A claim’s history can be read later without asking anyone to remember.

A history kept with the claim

Each claim carries its own log. The log records who filed the claim, who cleared or returned it, who edited it and who paid it. The bill photograph sits beside it. An owner or an accountant can open a claim and read what happened, in order.

What is logged

Submission

The claim is logged with the person who filed it and the time of filing.

Approval or rejection

The approver and the time are kept. A rejection also keeps its reason.

Edits

A change to an amount, head or tag is logged with the person who made it and the time of the change, beside the original entry.

Payment

The reimbursement batch, the mode, the reference and the date are kept against each claim.

Where it is used

Accounts reads the log when a claim is questioned at month close. Owners read it to see who approved spend on a branch, and reports show spend by branch with the approver on each entry. Your CA can follow a voucher in the Tally export back to its claim and its bill.

What it does not do

  • It does not decide whether a claim should have been approved
  • It does not replace the approval limits you set
  • It records actions in the system, not what happened outside it
  • Who may read the log is agreed with you during implementation
FAQ

Frequently asked questions

Is a rejection reason kept?

Yes. A rejection carries its reason, and the reason stays in the claim’s history.

Can an edited claim be traced?

Yes. Edits are logged with the person and the time, so the change can be seen against the original entry.

Does the log show who paid a claim?

Yes. Payment is logged with the batch, the mode, the reference and the date.

Can the trail be read at month close?

Yes. Accounts can open any claim beside its bill photograph and read its history in order.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements