Company spend and employee claims.

Track vendor bills and employee expense claims in one place. Vendors get paid directly; approved claims are reimbursed in the next payroll run. Both count toward the same expense accounts, so your monthly burn and your profit and loss always agree.

Employee claimClient site visit, three daysAED 2,340Approve
LedgerAuto-journalnobody posted it
PayrollNext runno transfer
ProjectsCost landsno allocation
APPayable opensno re-entry
One approval, four consequences.
One approvalApprove the claim, and the ledger and the payroll both know

The expense posts to the account it is mapped to, the reimbursement joins the next run, and the project it belongs to carries the cost.

The screen

Company spend and employee claims, side by side.

Both use the same categories and the same two-stage approval. Switch between them with the tabs below.

NearSyncFinanceExpensesSearch, plan and askKAll hubs
Scoped to United Arab Emiratesswitch via the hub chip
Monthly burn34,820.00AED, base currencyEmployee claims3,385.00This monthPending approvals2Waiting on a decisionTotal records146This fiscal year

What a person paid and is owed back. Approved claims are reimbursed through the next payroll run rather than by a separate transfer.

CategoryDescriptionClaimed byAmountDateStatus
TravelClient site visit, three daysReceipt attachedA. RahalAED2,340.009 Julapproved
MealsClient dinner, four peopleReceipt attachedR. HaddadAED620.0012 Julpending
TravelAirport transfersReceipt attachedA. RahalAED185.009 Julpaid
EquipmentReplacement laptop chargerNo receipt attachedM. Al SuwaidiAED240.0017 Julrejected

Both kinds post to the same expense accounts, so monthly burn and the profit and loss agree without anybody reconciling them.

Approved claims join the next payroll run.

The two paths

What happens after approval.

The two follow the same route until the last step. A vendor is paid directly. An employee is reimbursed through payroll, and because payroll runs in NearSync too, nobody has to arrange a separate transfer.

A company expense
  1. Recorded against a vendor and a category
  2. Approved by the department, then by Finance
  3. Booked to its expense account, and the amount owed becomes a payable
  4. Paid to the vendor, which clears the payable
An employee claim
  1. Submitted by the person, with the receipt attached
  2. Approved by their manager, then by Finance
  3. Booked to the same expense account, with the reimbursement tracked
  4. Paid out with the next payroll run, so nobody arranges a separate transfer
Receipts

The receipt stays on the claim.

The proof always stays with the expense, instead of getting lost in an inbox or a shared folder.

  • Attach a receipt when you submit, from your phone or your desk
  • Open the exact receipt the approver saw, even years later
  • Reject a claim with a reason the claimant can see
  • Rejected claims stay in the history instead of disappearing
  • Find the receipt behind any expense in your accounts
Expense claimReceipt attached
AttachedOn submit
FromA phone or a desk
Read laterThe same file
Found fromThe journal entry
If rejected
ReasonShown to the claimant
RecordKept, not deleted
Evidence behind any postingreachable from the ledger
The accounts

Every expense counts toward the right account.

Your monthly burn and your profit and loss are built from the same numbers, so they always agree.

  • Set up a category once, and every expense in it is booked the same way
  • See monthly burn in your base currency, across every market
  • Compare spend against the budget you set on the same accounts
  • See recurring software costs next to one-off spend
  • Check unpaid expenses against what you still owe vendors
Category mappedOnce
Every expense in itPosts the same way
BurnIn base currency
AcrossEvery market
Compared toA budget on the same accounts
Recurring beside one-off
SoftwareMonthly
One-off spendSame view
Unpaid reconcilesagainst the payable balance
Scanning a receipt

Scan a receipt and the claim fills itself in.

The scan reads the amount, the vendor, the category and what the spend was for, and puts them straight into the form. It is done by AI, so treat it as a first draft: check the figures, fix anything it misread, then submit.

From the receipt
AmountRead for you
VendorRead for you
You doCheck and submit
AI reads it, and you confirm it before it goes anywhere
Your own fields

Add the fields your own claims need.

A project code, a client to bill it back to, a vehicle, a cost centre. Add them to expenses once and they appear on every claim afterwards. They are saved in the same step as the rest of the claim, so a claim is never half recorded.

Extra details
Added byYou, once
Shown onEvery claim after
SavedWith the claim
Ten field types, grouped into sections you name
Keeping people posted

Each step tells the people who need to know.

Submitting, approving, rejecting and paying a claim each announce themselves, so an approver hears about a claim without watching for it and the claimant hears the answer without asking. You can hang your own workflow on any of those four moments.

Four moments
SubmittedApprover told
Approved or rejectedClaimant told
PaidRecorded
The message names the person who submitted it

Access

Who can do what.

Anyone can submit a claim. Managers approve for their own department. Seeing what the whole company spent is a separate permission, and setting up categories is another one again.

See

See your own claims and their status.

Do

Submit a claim, with its receipt.

Manage

Approve claims for your department, and record company spend.

Admin

Set up the categories and the accounts behind them.

Admin is the highest role and is not limited by these permissions, so keep it to the small group of people who genuinely need it.

Finance guides

See Finance on your own data.

Half an hour on your own books, with the operations that post into them running beside.