Skip to main content
GullySystem
Professional services

Expense & Reimbursement for Business consultants

Carry employee expense claims from receipts to approval and payment.

Human Resources

Does this function belong in your operation?

Use when employees spend on the business and claim reimbursement.

An employee submits expenses or settles an advance.

A consultant files travel to a client site with the engagement it belongs to. Receipts are attached from the phone. The manager approves, and recharged items flow to the next invoice.

Bring the records the workflow depends on.

  • Expense policy
  • Receipts
  • Approvers and advances

Outputs to check

  • Approved claim statement
  • Advance adjustment record
  • Payment-status register

Follow the expense & reimbursement workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Submit the claim

    Record the business purpose, dates, amounts and supporting receipts.

  2. 2. Check policy

    Review limits, duplicates and any missing evidence.

  3. 3. Approve the amount

    Retain approved, rejected and returned lines separately.

  4. 4. Adjust advances

    Reconcile any advance before creating the payment instruction.

  5. 5. Record settlement

    Link the actual payment reference and keep unpaid approved claims visible.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Field engineer or sales executive

Claims on the day, tracks approval and stops carrying a month of receipts in a bag.

Reporting manager

Approves from anywhere, and notices an odd claim while the week is still fresh.

Accounts assistant

Pays from approved claims only, and separates the bills that can be claimed as input tax credit.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Missing receipt

Return the claim or record the authorised exception with its reason.

Duplicate claim

Hold matching receipt references for review before reimbursement.

Advance exceeds expense

Record the balance to recover or carry forward under the approved policy.

Can this work independently?

Claims can be reviewed independently using entered employees and policies. Payment occurs through payroll, accounts or banking processes after approval. Linking a claim to a payment reference is different from the module initiating or confirming a bank transfer.

Systems and records it connects with

  • Payroll management: Approved pay inputs, deduction calculations and payment instructions.
  • Employee self-service: Employee-submitted requests and permitted personal-record views.
  • Expense tracking: Approved cost entries, evidence and payment references.
  • Accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • We read your travel and allowance rules with HR and accounts. You provide the policy as it is practised today. A written summary comes back. Correct it freely.
  • Expense heads, rates and ceilings are set up on screen. You review the list with a manager. Anything unclear is settled before staff see it. A few staff try claims on their phones using real bills from the past month. Approvers work through them. Issues are logged.
  • We agree how approved claims reach employees, with salary or as a transfer. Accounts confirms the export it needs. Claimants and approvers are trained in groups. A date is set after which paper forms are not accepted.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Claims are not paid twice.
  • Rejected costs stay outside payment totals.
  • Advance adjustments reconcile.
Business consultants

How the business operates.

Consultants sell hours and judgement, and neither survives in a timesheet spreadsheet that three partners fill in differently. A twelve week diagnostic reaches week thirty before anyone totals the associate days. Overruns hide.

Proposal and engagement letter

Draft scope, assumptions, milestones, rate card lines and fees from your own templates. Follow the letter through every revision to signed acceptance, with the partner’s approval recorded beside each draft.

Engagement tracker

Log milestones, deliverables and timesheet hours against each client and flag a slipping budget early, so the extra scope is raised in week six and not on the final invoice.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Proposal, engagement letter and scope version
  • Client information request and document access record
  • Workshop note, action owner and deliverable version
  • Approved time, rate basis and chargeable expense

Operational bottlenecks to check

Engagements overrun without notice

The statement of work said twelve weeks and the work is in its twentieth, yet no change order was raised with the client. Associate days pile up unbilled.

Retainer scope absorbs project work

A request that deserved its own proposal, say a debtor ageing review, gets folded into the monthly retainer. The fee never moves while scope creeps by a workshop here and a board pack there. Nobody pushes back.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Agree the engagement

    Record the client’s question, scope, assumptions and commercial arrangement in the accepted engagement document.

  2. 2. Collect and control information

    Assign information requests and keep received documents in the authorised engagement workspace.

  3. 3. Deliver and review the work

    Track workshops, analysis, draft deliverables and partner review. Retain the version shared with the client.

  4. 4. Handle change and acceptance

    Record additional requests and their effect on deliverables, effort and fees. Keep the client’s acceptance or outstanding comments with the milestone.

  5. 5. Bill and close the engagement

    Apply the agreed billing basis to approved evidence, reconcile expenses and receipts, and retain the final work and open follow-up actions.

Industry reports to connect with

  • Engagement milestones and information still owed
  • Approved effort and remaining fee allowance
  • Deliverables awaiting partner or client review
  • Invoiced, collected and outstanding amounts by engagement

Questions before implementation.

When should business consultants consider expense & reimbursement?

Use when employees spend on the business and claim reimbursement. An employee submits expenses or settles an advance.

What should we bring to the requirements discussion?

Bring anonymised examples of Expense policy; Receipts; Approvers and advances. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Carry employee expense claims from receipts to approval and payment. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Tax treatment and reimbursement policy come from your finance team.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Claims are not paid twice. Use this check when reviewing the first working version.

Talk to us

Discuss expense & reimbursement for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements