Pharma expense management: TA and DA that the field can't game and finance doesn't re-check
For most pharma companies the monthly expense statement is the most argued-over document the field produces. Travel allowance depends on distance, daily allowance on where the day was spent, and both are usually typed by the person being paid. Expense management software is worth having only if it changes that — if the amounts come from the work recorded, not from the claim.
Why manual TA/DA goes wrong
The problems are well known to anyone who has approved a field expense sheet, and none of them is solved by putting the same form on a phone.
- Distance is self-reported. Kilometres are rounded up, routes are lengthened, and nobody checking the sheet can tell which.
- Day type is self-declared. An outstation day pays more than a headquarters day, so the incentive is to call a local day outstation.
- Travel and daily allowance can describe different days. The sheet pays outstation kilometres for one trip and outstation allowance for another, and the mismatch is invisible line by line.
- Approval becomes re-checking. Because every line might be wrong, managers and finance re-verify every line — or stop checking at all.
What a sound expense calculation looks like
The fix is structural: the representative records the work, and the system computes the money from it. Policy lives in configuration — by role, by expense head and by station type — rather than in the head of whoever approves the sheet.
| Rule | What it prevents |
|---|---|
| The server computes the amount, not the app or the rep | Typed or edited totals. The representative sees the calculated sheet; they do not fill it in. |
| Distance comes from a defined source, and the sheet records which | Unexplained kilometres. Whether the figure came from the GPS trail, the admin-approved route distance or the actual visit chain, the reviewer can see it. |
| One route pays per day | Two trips' worth of travel claimed for one day, or travel and daily allowance describing different trips. |
| Outstation pays only if outstation work was done | Selecting an outstation route without calling on it. That day pays neither outstation allowance nor outstation kilometres. |
| Day type comes from the route worked | A local day declared outstation. The allowance follows the beat's own classification. |
Approval: review the exceptions, not every row
When the amounts are computed, approval changes character. The reporting manager confirms the claim reflects the month's work; finance processes it and looks at the exceptions — distance outliers, policy overrides, late claims — instead of re-adding every line.
Two things are worth checking in any product. First, that a rejected claim goes back with a reason the representative can act on. Second, what happens to an expense when the call report it came from is corrected — the two must stay reconciled, or the sheet pays for a visit that no longer exists.
How PharmaMonitor handles expenses
In PharmaMonitor the app never computes money; the server does. When the representative finalises the day with a punch-out, the expense sheet comes back already calculated. Travel allowance uses a distance ladder — the GPS trail, the admin-approved route distance, or the actual visit chain — and every sheet records which was used. Only one route pays per day, and an outstation route selected but not called on pays neither outstation allowance nor outstation kilometres.
Policies are configured per company by role, expense head and station type. Claims move from the reporting manager to finance, and either can reject with a reason.
Frequently asked questions
What is TA and DA in pharma?
TA is travel allowance — reimbursement for distance travelled on field work, usually per kilometre. DA is daily allowance — a fixed amount per working day that depends on the day type: headquarters, ex-station or outstation. Together they make up most of a medical representative's monthly expense claim.
How is travel allowance calculated for medical representatives?
By multiplying a distance by the per-kilometre rate in the company's policy. The question is where the distance comes from. In PharmaMonitor it comes from a distance ladder — the GPS trail, the admin-approved route distance, or the actual visit chain — and every expense sheet records which source was used, so the reviewer never sees an unexplained number.
Can an MR edit the expense amount?
Not in PharmaMonitor. The app does not compute or accept money amounts for allowances; the server calculates the day's sheet from the recorded work when the day is finalised. The representative sees the result, and disagreements go through the approval chain rather than through an edited total.
Does PharmaMonitor scan receipts automatically?
No. Automatic receipt scanning (OCR) is not built. Expense lines that need a bill can carry a photo, but the amount is not read from it automatically.
Who approves expense claims?
In PharmaMonitor a claim goes first to the representative's reporting manager and then to finance. Either can reject it with a reason, and the representative sees that reason against the claim.
Read next
See it against your own field force
Rather than take any of the above on trust, run it on one division for a month — including a month-end expense cycle. We will set up the hierarchy, import your doctor and chemist master, and walk your managers through the reports that come out of it.
Free 30-day pilot for founding companies
Run it with your actual field force before committing to anything.
Personalised onboarding support
We import your doctor and chemist master records for you.
No credit card required to start
Nothing is charged during the pilot, and there is no auto-conversion.
Reporting hierarchy mapped for you
We configure your levels, from MR through to national head.
Book a walkthrough
A 30-minute session on your own hierarchy and territories. We respond within 4 business hours.
We respond within 4business hours · Each tenant's data is isolated