How an SAP day rate is built up

A day rate looks like one number and is actually a stack of them. Between the budget line a client approves and the money that reaches a contractor's account sit several parties, a set of costs an employee never sees, and a calendar that decides how many of those days exist at all. Anyone comparing a contract offer with a salary is comparing two objects of different shapes, and most of the disappointment in independent SAP work comes from making that comparison without unpacking it first. This guide unpacks it, without asserting a figure that would be wrong somewhere.

The chain between the client's budget and your invoice

The rate a client approves and the rate you are offered are rarely the same rate, because there are usually parties in between. A common chain on a large programme runs: the end client, then a prime supplier or systems integrator holding the delivery contract, then a staffing partner on the client's approved supplier list, then your own company or a payroll intermediary, then you. Each link takes a margin, and the margin is almost always a share of the rate rather than a flat fee, so it scales with you.

Two things follow. The first is that a long chain can leave less than expected even when the client is paying generously, which is why contractors on the same programme, doing similar work, can be on visibly different rates. The second is that shortening the chain is one of the few levers available: a direct relationship with a client, or a place on a framework yourself, removes a link. Large programmes often refuse direct engagement of individuals for procurement reasons, so this lever exists more often at mid-sized customers than on the biggest projects.

A rate card prices a grade, not a person

Suppliers to large customers and to the public sector work from rate cards: an agreed price per grade — analyst, consultant, senior consultant, architect, programme manager — often per role family and per location, fixed for the length of a framework agreement. The card is negotiated once, between organisations, long before anyone knows who will fill the seat. When you are told "the rate is set", that is usually literally true.

What is negotiable in that world is the grade you are proposed at, not the price of the grade — which turns the conversation into an evidence conversation about scope and decisions owned, the ground the experience guide covers. It is also why grade definitions are worth reading carefully: they are the actual specification of what the money is for.

Counting the days that can actually be billed

A rate is a price per unit, and the unit is scarce. Work out your own figure rather than borrowing anyone's: open a calendar for next year, count the weekdays, subtract the public holidays your country publishes, subtract the leave you intend to take, subtract days you expect to lose to illness, and subtract the time you will spend on training, certification, accounts and looking for the next engagement. What survives is the number of days you can invoice in a perfect year.

Then subtract the imperfect part: the gap between contracts. An engagement has an end date that may or may not be pushed back, and the renewal decision is normally taken weeks ahead of it, so hunting for the following one overlaps with delivering this one. A realistic annual figure assumes some weeks unsold. Multiply the remaining days by the rate and you have the only version of a contract number that can be compared with anything.

What the rate has to pay for before it becomes income

An employee receives a salary net of things an employer has already bought on their behalf. A contractor receives a rate and buys them personally. The list is longer than most people expect, and it does not shrink in a bad year.

• Time off that is not paid — holidays, public holidays, sickness and any parental leave, all of which are unbilled days rather than an expense line.
• Pension and social contributions in whatever form your country requires of the self-employed, plus voluntary provision for what employment would have provided.
• Insurance — professional indemnity and public liability are frequently contractual conditions of being engaged at all, alongside health cover where it is not universal.
• Professional costs — an accountant, company filings, software licences, hardware, a workspace, and the training and certification the certification guide describes, which nobody now reimburses.
• The cost of selling — the unbilled hours spent on proposals, interviews, agency calls and staying visible to the people who staff projects.

Who carries the bench, and what the premium buys

The single clearest way to read the difference between a rate and a salary is to ask who pays for the weeks with no project. Inside a consultancy the employer does: a consultant between assignments is still paid, and the firm absorbs it through its utilisation model, which is why utilisation is measured so closely and why bench time comes with pressure attached. An independent absorbs it alone.

So the visible premium on a contract rate is not a reward for being better; it is compensation for holding a risk the employer used to hold, together with the costs above. Judging whether it is a good deal means comparing across a full year in which the risk actually shows up, not across a good month. The freelance-versus-permanent guide covers the rest of what changes, and what drives SAP pay covers why the level was set where it was.

Expenses, travel and the parts quoted separately

Most SAP contracts still involve going somewhere, and how travel is handled changes the deal materially. Travel and accommodation may be reimbursed at cost, covered by a daily allowance with its own tax treatment, rolled into an inclusive rate, or simply not covered — and an inclusive rate for a client three hours away is a different offer from the same number with expenses on top. Ask which of the four applies before comparing anything, and ask whether travel time itself is billable, because on many contracts it is not.

The other separately quoted parts are overtime, weekend work and standby. Programmes concentrate exactly that kind of work into cutover weekends and hypercare, and whether those hours are paid, paid at a different rate or assumed inside the day rate is a clause, not a custom.

Employment-status rules that reshape the rate

Whether an engagement is genuine self-employment is a legal question with a different answer in every country, and it is decided by the facts of the working relationship rather than by what the contract calls it. The United Kingdom's off-payroll working rules put the determination on the client for medium and large organisations, and publish an official status checking tool; the Netherlands has its own framework for assessing whether an assignment is employment in substance; Germany treats disguised self-employment as a social-insurance matter, with a formal status determination procedure available from the pension authority.

The practical effect on the number is large. An engagement judged to be employment in substance is usually run through a payroll intermediary, which changes what the same headline rate delivers, and it is why the first question about a contract in some markets is not the rate but which status it is being offered under. Check the current rule in the country you are contracting in before you model anything; these regimes change, and they have changed several times in the last decade.

Currency, payment terms and getting paid late

A rate agreed in a currency you do not spend carries exchange risk for the length of the contract, and remote delivery across a border makes that ordinary rather than exotic — the pattern the remote-work guide describes. Payment terms are the other half: an invoice approved at the end of a month and paid a month or two later means working a long way in advance of being paid, and an agency in the chain is often paid before you are.

Timesheet approval is where this actually goes wrong. If the person who signs your timesheet is on holiday at month end, the invoice does not go out, and the delay compounds down the chain. Within the European Union, late payment in commercial transactions is regulated and statutory interest is available; knowing that the remedy exists is worth more than it sounds, because the conversation rarely has to get that far.

Turning a rate and a salary into the same object

Do it in one direction, on one page. Take the contract side: billable days from your own calendar, times the rate, minus every cost listed above, minus the tax your structure actually attracts. Take the employment side: base pay, plus employer pension and social contributions, plus bonus at a realistic rather than a maximum attainment, plus the monetary worth of paid leave, sick pay, notice period, training budget, equipment and any thirteenth or fourteenth monthly payment where that convention exists.

Compare those two totals, over the same year, in the same currency, and only then decide. Where the exercise needs a real external number to anchor it — a market rate for the grade, a typical employer contribution rate, the going price in another city — take it from a source you can check rather than from memory or from a recruiter's aside; the market-rate guide lists the sources that publish them and how to read each one.