FBT & EOFY Governance in SAP Concur

Why FBT risk quietly builds all year

FBT exposure rarely comes from one big mistake. It builds when:

• Classification relies on judgement
• Reviews are pushed to month-end or EOFY
• Exceptions accumulate without visibility

By EOFY, finance teams are fixing issues that should have been prevented.

What "FBT-ready" actually means

FBT compliance only works when decisions are made at submission, not after payment.

A governance-led setup ensures:

• FBT categorisation enforced before reimbursement
• Policy logic applied consistently across users
• Exceptions visible early — not discovered at year-end

Compliance is designed in, not cleaned up later.

What CFOs actually see

CFOs gain visibility into:

• FBT category summaries by entity
• Policy exception trends
• EOFY-ready FBT exposure views

EOFY becomes a review — not a firefight.

Who this is for

Designed for organisations that:

• Manage growing expense complexity
• Face recurring EOFY FBT pressure
• Want system-led consistency without re-implementation