Business · Expenses

From receipt
to the ledger.

Money spent by people in the business still has to be evidenced, attributed and approved before it reaches the books. BINK handles that as a claim with a state: the spend, its receipts, the department it belongs to, a decision by someone else, and an export your accountant can read.

Talk to us See corporate cards

The state of a claim

DraftBeing prepared, not yet submitted

SubmittedHanded to review

Under reviewWith an approver

ApprovedAccepted for reimbursement

RejectedDeclined, with a reason

PaidSettled back to the claimant

One state at a time, visible to the claimant — so nobody has to ask where a claim has got to.

ClaimsSubmitted, with receipts

ApprovalPolicy-driven, or straight through

StructureDepartments and budgets

ExportFormatted for your ledger

The claim

Five things, on one record.

A claim is only useful later if the spend, its evidence, its attribution and its decision all live on the same record. Split them across systems and the audit becomes archaeology.

On the claimWhat it holdsWhy it is there

The spendAmount, currency and dateEntered by the person who incurred it

EvidenceReceipts attached to the claimStored against the record, not emailed

AttributionDepartment, and budget where usedSo the cost lands where it belongs

PolicyRules on merchant, category, amount, regionBreaches recorded as violations

DecisionApproved or rejected, with a reasonBy an approver, not the claimant

The path

Claim to export.

ClaimEnteredThe spend, its evidence and where it belongs.
SubmitFor reviewIt leaves the claimant’s hands.
DecideBy anotherApproved or rejected, with the reason recorded.
ExportTo the ledgerFormatted for the accounting system you use.

What you get

Spending that reconciles.

The value is not the form — it is that months later the amount, the evidence, the approver and the cost centre are all still attached to each other.

Claims with a state

An expense moves through draft, submitted, under review, approved or rejected, and paid — so "where is my claim" has an answer that does not require asking anyone.

Evidence attached

Receipts are stored against the claim itself rather than forwarded as email attachments, so the proof and the record cannot become separated.

Approval where policy asks

Where an approval policy applies, a claim is routed for a decision by someone other than the claimant, using the same four-eyes engine as the rest of the platform.

Departments and budgets

Claims are attributed to a department — which can nest — and to a budget where one is in use, so cost lands against the structure the business actually has.

Policy breaches recorded

Rules on merchant, category, amount and region are evaluated and a breach is written as a violation on the record, so exceptions are visible rather than silently accepted.

Export your accountant reads

Reports are produced in the shapes QuickBooks, Xero, NetSuite and SAP expect, plus CSV — so the handover is a file your finance team can use immediately.

Scope, stated

What is available today.

This surface is named for where it sits in the platform. What it does today is narrower than that name, and saying so is more useful than implying otherwise.

What BINK offers on this surface today is expense management — claims, receipts, attribution, approval and export. Supplier bills, vendor records, invoice matching and payment runs are not available, and no bill can be paid from here.

What this is: Expense management: claims raised by people in the business, with receipts, attribution and approval. It is the reimbursement side of spending, not supplier payment.
What it is not: There is no vendor master, no bill record, no invoice matching and no payment run. BINK does not offer accounts payable today.
Receipt capture: Receipts are attached by the person making the claim. There is no automatic data extraction from a receipt or invoice, and none is claimed.
Approval coverage: Where no approval policy is configured for a claim, it proceeds without one. The behaviour is deliberate and worth knowing rather than assuming every claim is gated.
Accounting export: The connectors generate a correctly-shaped payload for each system and hand you the file. They do not sign in to your accounting platform or post entries into it.
Spend policy: Policies are evaluated and violations logged. They are not applied at the moment of purchase, so a policy records what happened rather than preventing it.

In the platform