Enterprise DNA

Instead of SAP Concur

Stop renting SAP Concur. Own your expense claims system.

We build your version around your categories, limits and approval rules, bring your Concur history and card statements across, and run it with your finance team.

SAP Concur lists Concur Expense from US$7 a report on Base and US$11 a report on Plus, with Premium on a custom quote and the price varying with your monthly commitment.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the invoice

What sits inside a SAP Concur bill?

Concur charges by the expense report, so the bill rises with every claim your people file. Separate the screens from the work your finance team does each month.

receipt_long

A charge on every report

Base starts at US$7 a report and Plus at US$11. A team that files more claims pays more, even when nothing about the work has changed.

handshake

A monthly commitment

The per-report price depends on the volume you commit to in the contract. Commit low and pay more per report, commit high and pay for reports nobody files.

photo_camera

Receipt reading on the higher plan

ExpenseIt, the receipt capture, sits in Plus and above. Underneath, a receipt is a date, a merchant, an amount and the GST.

insights

Reporting as a tier

Reporting is listed in Plus, and the analysis tools sit in Premium. Most finance teams need five answers a week, not a reporting suite.

flight

Travel bundled in

Premium adds Concur Travel. If your people book flights through a travel agent or directly, you are paying for a booking tool you do not use.

hub

Add-ons and connections

Card feeds, audit services and the link to your accounting system are scoped and priced as you go. Your own version writes the file your accounting system already imports.

Your own expense claims

Every claim checked before it is paid

GST

Know which GST credits will hold up

GST is worked out for each line by country, and every credit is checked against the document behind it.

  • check Australian purchases over $82.50 with no tax invoice, flagged before the BAS
  • check New Zealand supplies over $200 without taxable supply information, and over $1,000 without your business named
  • check GST supported and GST at risk, by company and month
  • check Foreign spend converted to your currency with no GST claimed on it

Approvals

Approvals that follow your rules

Each person has a manager and an approval limit. The rules are checked every time, including on history brought across.

  • check Nobody approves their own claim or a claim above their limit
  • check Anyone but the manager records why they approved on their behalf
  • check Claims waiting longest first, with the approver named
  • check A batch is held while any claim in it fails the approval check

Cards and duplicates

Stop paying for the same spend twice

Company card statements come in from your bank, and every charge is matched to the claim line that explains it.

  • check Card charges nobody has claimed, oldest first, with a reminder drafted for the holder
  • check A personal claim that a company card already paid, caught
  • check The same taxi on two claims, caught
  • check Mileage above your rate and meals over the daily limit, listed by person

Records

The records your adviser asks for

Entertainment, receipts and batches kept in one place, in your brand, ready when the accountant or an auditor asks.

  • check An entertainment register for the year from 1 April, with who attended and why
  • check An expense claim form for every claim and a reimbursement summary for every batch
  • check One accounting file per batch with account, cost centre, GST and gross for each line
  • check Your own categories, limits and checks, changed in plain words

Make it yours

Design your own SAP Concur replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from SAP Concur. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your SAP Concur replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your SAP Concur data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Expense Claims for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Expense Claims for Claude Code

Connected to your own database

Which claims are waiting for approval, and who is holding them?

EXP-0991

Person
Ben Walsh
Approver
Aroha Ngata
Submitted on
2026-10-02
Days waiting
12
Currency
NZD
Total
575.20
Missing receipts
1
Findings
4

EXP-0994

Person
Tom Fraser
Approver
Kate Chen
Submitted on
2026-10-09
Days waiting
5
Currency
AUD
Total
443.00
Missing receipts
0
Findings
2

EXP-0993

Person
Liam Morgan
Approver
Kate Chen
Submitted on
2026-10-12
Days waiting
2
Currency
AUD
Total
728.00
Missing receipts
0
Findings
2

Ask it anything

Ten questions your own expense claims answer

Each one works today in the free version on the demo records. Ask in plain words and get the answer from your own data.

chat_bubble Which claims have waited more than five days for approval, and who is sitting on them?
chat_bubble How much GST are we claiming without the tax invoice to back it?
chat_bubble Which company card charges still have no claim against them?
chat_bubble Who claimed the same taxi twice, or claimed a card charge as their own money?
chat_bubble Which claims were approved by the claimant, or above the approver's limit?
chat_bubble Which client dinners have no attendee list for the entertainment record?
chat_bubble Who is claiming mileage above the company rate?
chat_bubble What did each team spend on flights and accommodation over the last three months?
chat_bubble Which claims came in more than 60 days after the money was spent?
chat_bubble What do we owe each person in the next reimbursement batch, and what is holding it?

Switching

How to switch from SAP Concur

A move usually involves exporting the Concur reports you need, mapping your layout and rules, then checking the imported records before you change over.

  1. 1

    Export your Concur records

    Ask your SAP Concur administrator to export the expense reports you want to bring across using Concur Expense File Export. Concur writes an expense export when batches close. The export can use the default GL file or a custom CSV layout set by your administrator. Export what your account allows, and check with SAP Concur if you cannot find the export or need to include receipt archives.

  2. 2

    Load a test run first

    Use the import path to load your Concur export, starting with a dry run so you can check it before anything is written. The file layout is set by your administrator, so it may need to be mapped to the new database's fields and expense types. If you have custom layouts or receipt archives, include them in the mapping work rather than assuming they will carry over automatically.

  3. 3

    Resolve the import flags

    Review the dry run results before loading the records for real. The import stops without writing anything if it finds an unknown person or expense type, so resolve those mappings first. Check that paid reports will come across as exported history and open reports as submitted or draft. This helps preserve the difference between completed claims and claims still waiting for approval.

  4. 4

    Run both systems briefly

    Keep SAP Concur available while you begin using the new database and Claude Code for a short period. Compare the claims and approval status you expect to see, and check that imported paid reports remain history rather than being batched again. Use this period to find missing records or mapping issues before your team relies on the new process alone.

  5. 5

    Switch off Concur

    Once you have checked the imported records and your team is ready to use the new process, set a clear cutover point. Stop entering new claims or processing reimbursements in SAP Concur after that point, so the same work is not handled in both systems. Keep the export you used for the move with your records, and follow your own retention requirements for Concur data.

construction

Where the real effort goes

The main work is usually matching your administrator's Concur layout to your fields, people and expense types, then deciding how much history and which receipt archives to bring across. You will also need to check how your own rules fit the new setup. If Enterprise DNA installs and runs it for you, they handle this mapping work as part of the move.

Not ready for a call?

Get your SAP Concur switch plan by email

We will send you the step-by-step plan for moving your business off SAP Concur, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, customise it, or have us run it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Type /attention and /compliance on the demo claims
  4. 4 Import a Concur expense export with a dry run first
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your companies, categories, limits, approvers and accounts
  • check Your SAP Concur history and card statements brought across and checked
  • check A phone app for receipts or approvals by email if you want one
  • check A live link to your accounting system or bank card feed, scoped with you
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Card statements loaded and matched every week
  • check Monday expenses review and reminders prepared for your approval
  • check A team to change the rules as your policy changes
Book a call

Questions

Instead of SAP Concur, answered

Can our people still photograph a receipt on their phone? expand_more

Not in the free version. A receipt is recorded with where it is kept, and lines are added by asking. If your team wants to snap a receipt and have it read, we build a phone app or an email-in address into your version.

Can we bring our Concur history across? expand_more

Yes. Concur writes an expense export when batches close, and its layout is set by your administrator. Each report comes across as one claim, paid reports as history that is never paid again, open ones as waiting for approval. Unknown people and expense types stop the import before anything is written, so nothing lands half done. Custom layouts and receipt archives are part of what we map for you.

Does it pay our staff? expand_more

No. It writes one file per batch for your accounting system, with the amount owed to each person, and someone pays from there. Company card spend is never reimbursed. A direct link to your accounting system is something we build into your version.

Does it work out FBT and the 50% entertainment rules for us? expand_more

It keeps the record those rules need: every entertainment line with who attended, how many and why, for the year from 1 April. The tax treatment is your adviser's call. The checks flag entertainment with no attendees before it is approved.

What will Enterprise DNA charge? expand_more

One setup fee, then a retainer for the agreed service. Sam scopes your companies, rules, history and connections with you on a call. The free version is open source if you want to run it yourself.

Make your expense claims yours

Book 30 minutes with Sam. Bring your expense policy, your last Concur invoice and a month of card statements. We will map what your own version needs.

Book a call Get the free version

Expense Claims for Claude Code is free and open source, published by Enterprise DNA.

Done paying for SAP Concur?

Get your version built